Aytekin Tank and the business of getting your time back

Portugal got there first. In 2007, Aytekin Tank and his first employee released Jotform’s paid subscription early in the morning. They thought they had a few hours before people in the United States woke up. About a minute later, somebody in Portugal bought it. The plan cost $9 a month. After a year of offering the service free, Tank had an answer to the question that sits beneath every useful piece of software: would anyone pay?

The transaction was small enough to disappear in a bank statement. It stayed in his memory. “That’s when I knew that JotForm would be successful,” he recalled. More subscriptions followed that day. There was no need to stage a ceremony. A customer had done the honors.

The customer who woke up first

Tank had spent that first year letting people use Jotform and tell him what was wrong with it. There were problems to fix. The free version supplied something an isolated programmer cannot manufacture: other people’s experience. When the paid version arrived, those users already understood what the service did. Some were ready to keep it.

He also had somewhere to announce it. He wrote a blog and participated in online communities, posting the product where people could try it, discuss it, and pass it along. The first audience grew through forums, blogs, and mailing lists. This was work done in public, at the scale a solo developer could manage.

Twenty years after its February 2006 launch, Jotform reports more than 40 million users. Tank remains its founder and CEO. The company has grown without outside funding, extending the original form builder into a collection of tools for apps, signatures, workflows, and conversations with AI agents. The little subscription from Portugal belongs at the beginning of that account. It shows what Tank was waiting for: useful work becoming a business.

A paycheck, a student website, and too many forms

Tank was born in Istanbul and grew up moving between Turkish cities because his family worked for the government. He has linked those moves to an appreciation for different cultures and meeting people. A programming course in middle school gave him a more durable interest. He could make something happen on a computer, and he wanted to keep doing it.

In 1996, he began studying computer science at the University of Bridgeport. He built a website for a student organization, including member profiles, then released it as free, open-source software. People asked him to make changes and offered to pay. The commercial version followed in 1999. His first business lessons arrived through requests from users.

He graduated in 2000 and took a job at a New York company. For five years, he kept developing his own software alongside employment, getting up before work and coding on weekends. He left in 2005 when the business earned more than his salary. The existing product supplied the income; Jotform was the next project. That distinction gives the story its practical shape. There was a bridge between a paycheck and a new idea.

The idea came from his job at a media company, where editors and writers repeatedly needed online forms. Contact forms. Questionnaires. Another form, please. Building them by hand consumed a developer’s time without providing much novelty. Tank recognized a task that could become a tool. A drag-and-drop builder would let people assemble the fields themselves.

His employment had given him both income and a close view of the problem. He had been doing the work he wanted to simplify. When Jotform launched, the proposed customer benefit was easy to demonstrate: move things into place and see the form take shape.

Google arrives. The inbox remains.

Founding a company produced a fresh inventory of recurring jobs. Tank answered customer emails, dealt with accounting and personnel matters, and attended to office supplies. The person selling relief from repetition had acquired a sizeable collection of it. Snacks, it turns out, will not order themselves out of respect for your vision.

Google Forms entering the market made that arrangement harder to tolerate. A small company competing with Google needed time to improve its product. Tank was spending his on the support queue. His account of that period centers on a decision to delegate support and automate routine work, opening space for development and growth.

There is an awkward adjustment in moving from programmer to employer. Solving a problem personally gives an immediate reward. Teaching somebody else to own it takes longer, and the result may arrive without your fingerprints. Tank had to make that exchange. Hiring people to share the work changed what he could pay attention to.

How to stop being everyone’s bottleneck

By 2015, he described dividing work into cross-functional teams with a single goal and a metric each team could use. Engineering was in Turkey, marketing in San Francisco, and other colleagues worked remotely. The organization needed ways to make decisions without routing every conversation through the founder.

In a later account of product development, he described groups of five or six, bringing designers and developers together. Hack weeks produced prototypes that could be tested with users. For Jotform Cards, three teams worked through seven hack weeks, generating 21 prototypes. Patience here had a working method: try things, compare them, and keep improving the result.

Tank also admitted that the company had previously swung between big launches developed in isolation and a stream of small changes that left the product cluttered. Neither habit had served users well. The response combined longer projects with continued releases and feedback from smaller groups of customers. He made room for ambition while giving it checkpoints.

His personal systems can sound almost comically meticulous. In a 2023 podcast conversation, he described using roughly 3,000 Gmail filters. Emails were sorted into different priorities, allowing urgent messages to surface while other material waited. The detail suits him: a founder who turned forms into software also treated his inbox as something that could be designed.

His book gives that approach a sequence. Break work into steps. Map the process. Put an automation into practice. Measure and revise it. The machinery needs attention too, but an hour spent improving a recurring process can change how the following hours are used.

The quiet founder finds an audience

At the end of 2017, Tank had a growing company and an irritation of a different kind. Competitors were attracting attention with funding announcements while Jotform kept operating quietly. He decided to tell the story of how he had built it.

Early essays on Medium found readers. He committed to writing regularly in 2018, and experimented with turning a successful article into a Twitter thread. One campaign eventually cost $24,098 and generated more than 17 million impressions. Those were paid distribution results, a useful detail when considering how a quiet founder became more visible. Writing supplied the message; an advertising budget helped it travel.

He has since contributed to outlets including Entrepreneur, Fast Company, and Forbes. His topics tend to return to decisions he has made himself: bootstrapping, delegating, organizing work, and deciding what deserves attention. The technical founder acquired a second way to communicate the usefulness of a system. A reader could try an idea before ever opening the product.

In May 2023, Wiley published Automate Your Busywork. The book develops a framework for removing repetitive tasks and making room for meaningful work. It also gives a name to the condition he wants readers to reach: timefulness, having enough time. There is something pleasantly unfashionable about treating enough as an achievement.

“All thoughts of startup growth or conversion rates slip away when you’re picking olives.”Aytekin Tank

A form learns to talk

In February 2025, Jotform launched AI Agents. Tank described a shift from sending someone a form to allowing them to give information through a conversation. An agent could gather details and answer questions along the way. The product extended an old concern into a different interface: how much effort should a person spend giving a business the information it needs?

The move connects to the earlier software without requiring the founder’s story to start again. Forms organize an exchange. Apps, signatures, and workflows extend what can happen after that exchange. Conversational agents offer another route into it. For Tank, the opportunity continues to involve making everyday work easier for people who may have no developer available.

He explores the broader field with Demetri Panici on the AI Agents Podcast. Their 2026 episodes include discussions of workflow automation and demonstrations of tools. His writing remains practical too. An October 7 guide explains an AI system for keeping track of follow-ups. After two decades of building a company, remembering to get back to somebody still makes his list.

The olives keep their appointment

Tank’s account of success includes returning to Turkey to help with his family’s olive harvest. He has written about taking at least a full week for it and arranging the company so he could be there. The work requires his presence in a way that an automated reminder does not.

He has also described trying to grow vegetables at home, imagining salads and ending up with dead stems. His wife pointed out the difference: during the olive harvest, he gives the task his attention. At home, that attention is divided. A founder can design an elaborate email system and still neglect a garden. The vegetables decline to be impressed.

The anecdote makes his wider argument tangible. Saving time creates a choice about where to spend it. A company can keep claiming the next available hour, even after software has freed it. Tank’s harvest trip puts a specific use on the calendar. People he loves are there, and the job is waiting.

That is the line connecting the subscription from Portugal to the founder’s later work. He wanted an easier way to build forms. He learned to share the work of running the business. He keeps designing ways to remove the tasks that repeat. Somewhere in that arrangement, there must be room for a week among the olive trees.