How Tally got its first 11,000 users

In October 2021, Tally shared a milestone that would make most bootstrapped founders jealous.

No money spent on marketing. 11,000 users. 200 paying customers. $5,000 in MRR. In one year!

It is tempting to explain that growth with one event.

Tally launched on Product Hunt in March 2021, finished as the number four product of the day, and doubled its user base from 1,500 to 3,000.

That was clearly a big moment.

But it leaves out the more interesting question.

Where did the first 1,500 users come from?

The answer is a sequence of small, mostly manual distribution moves. None of them looked spectacular on its own. Together, they gave Tally a way to grow from a barely working MVP to a product with its own acquisition loop.

That is what I find inspiring about the story.

Tally's first MVP was so basic that users could not even publish a form.

Marie Martens and Filip Minev first shared it with friends and family. Once they had worked through that feedback, they began contacting creators, Indie Hackers, and startup founders who might need a form builder.

They searched Product Hunt and Twitter, built lists with hundreds of prospects, and asked them for feedback.

Many did not reply. The people who did became some of Tally's earliest users and ambassadors.

By October 2020, Tally had 184 users and $64 in MRR.

Cold outreach did two jobs at once. It put the product in front of potential users, and it helped the founders understand what those users actually wanted.

That distinction matters in the beginning. When you have no audience, no search traffic, and no word of mouth, a channel does not need to scale yet. It needs to create learning and bring in the first people who care.

Getting attention was only useful because Tally had a clear wedge in a crowded market.

Existing form builders felt restrictive and full of limits. Tally went in the other direction. It made 99% of its features free, including unlimited forms and responses, and kept one paid plan for advanced team features.

It also removed a common piece of friction. Visitors could start using the form builder directly from the landing page without creating an account first.

This was not only a pricing decision. It supported distribution.

The generous free plan made Tally easy to recommend. The instant product experience made it easy to understand. Both helped the attention from outreach and communities turn into actual users.

Tally then added another layer.

The founders published their roadmap and changelog, spoke with users constantly, and built a Slack community around the product. Whenever they shipped an update, they treated it as a reason to talk about Tally again.

They shared those mini-launches on Twitter, Reddit, Indie Hackers, in no-code communities, and in relevant Slack groups.

“Building in public” can sound like a vague content strategy. Tally's version was much more practical. Shipping created something worth sharing. Sharing brought users and feedback. That feedback shaped the next release, which created another reason to share.

The result was not one viral post. It was repeated exposure inside communities where likely users already spent time.

By March 2021, Tally had reached 1,500 users and $380 in MRR before its official Product Hunt launch.

Tally did not arrive on Product Hunt with an idea and an email signup page.

It arrived with a working product, crucial features, 1,500 users, and a small community that already cared.

The launch still mattered. Tally briefly held the number one position, finished fourth, and doubled its user base to 3,000.

But Product Hunt did not create Tally's distribution from nothing. It amplified the groundwork the founders had done during the previous seven months.

That changes the lesson.

“Launch on Product Hunt” is not especially useful advice. Build enough momentum so a launch has something to amplify is much more useful.

After the launch, Tally's growth no longer depended only on the founders starting every conversation.

Free forms included a “Made with Tally” badge. Every time someone shared a form, the people filling it out could discover the product too.

Tally even experimented with the design of the badge to improve it as an acquisition channel.

The mechanics fit the product unusually well. A form is designed to be sent to other people. A generous free plan led to more forms being created. More forms meant more people saw the badge. Some of those people created forms of their own.

By April, Tally listed the badge alongside Product Hunt, Twitter, no-code communities, and Indie Hackers as one of its main acquisition channels. Users were also beginning to recommend the product when others asked for form-builder suggestions.

The founders kept feeding the system with new integrations, product updates, documentation, and direct participation in relevant conversations. But the product had started carrying part of the distribution load itself.

Tally reached 5,800 users and roughly €2,080 in MRR in June, 7,500 users and $2,774 in MRR in August, and 11,000 users and $5,000 in MRR by October.

It would be easy to turn this story into a list of channels.

Cold outreach. Twitter. Slack. Indie Hackers. Reddit. Product Hunt. Freemium. A powered-by badge.

But copying that list misses why it worked.

Tally's distribution changed as the product changed.

At the start, the founders needed conversations more than reach. Manual outreach gave them both.

Once they had early users, product updates gave them repeated reasons to show up in relevant communities.

Once they had a working product and 1,500 users, Product Hunt could amplify real momentum.

Once thousands of people were creating and sharing forms, the badge turned usage into exposure.

Each stage produced an asset for the next one: insight, advocates, credibility, reach, and finally a product-led loop.

Not every SaaS can copy Tally's badge. The loop works because forms naturally travel beyond the person who creates them. A back-office tool used by one internal team will need a different mechanism.

But every founder can ask the same question.

What kind of distribution can my product support today, and what do I need to build before the next channel can work?

The most inspiring part of Tally's first year is not that growth looked easy. It is that it did not.

The founders sent hundreds of messages, answered questions, wrote documentation, participated in communities, and launched one update after another. Over time, those unscalable actions created a system that could grow beyond them.

Which stage are you in right now? Direct conversations, repeated launches, a bigger launch, or a product-led loop?

Hit reply and tell me.

Source: Marie Martens, Year 1: How we bootstrapped Tally to 11k users and $5k MRR, published October 11, 2021.