Kitebird: from idea to paying users in nine days

Ananya Rao spent six years running social media for small brands. She knew the tools well, and she knew where they fell short for the people she worked with: independent shops, cafes and studios that post a few times a week and do not need an enterprise dashboard.

She had the idea for Kitebird, a simple scheduler for small businesses, long before she had a way to build it. She did not have an engineer, and she did not want to raise money just to find out whether anyone would pay.

Nine days after her first prompt, Kitebird had paying customers.

Starting small

Ananya’s first prompt described one kind of user and three things they do: connect their accounts, write a post with an image, and pick a time for it to go out. She was explicit about what she did not want yet: no analytics, no team seats, no AI caption writer.

“I had a list of forty features in a notebook,” she says. “I picked the three I would pay for myself and left the rest in the notebook.”

Within the first hour, she had a working app with logins, a Postgres database for posts and schedules, and file storage for images. She spent the rest of the first day using it to schedule her own posts, then asking Nest for small fixes as she hit rough edges.

The nine days

Here is roughly how the time went.

Days 1 to 3: the core

Composer, calendar view and scheduled publishing. Ananya iterated in short messages, one change at a time, and rolled back twice when a change went in a direction she did not like.

Days 4 and 5: a waitlist

Instead of opening the doors right away, she asked Nest to add a landing page with a waitlist. Signups were stored in the database, and she could invite people in batches from an admin page. She shared the page with former clients and in a few small business communities. Around 300 people joined in two days.

Days 6 and 7: Stripe billing

She connected Stripe and asked for two plans: a free plan with ten scheduled posts a month, and a paid plan at $9 a month with no limit and a 14-day trial. Nest set up checkout, the customer portal and the webhooks for renewals and failed payments. She tested the whole flow with Stripe’s test card before switching to live keys.

Days 8 and 9: launch

She invited the first 50 people from the waitlist, published Kitebird on her own domain and spent two days answering emails and making small fixes. By the end of day nine, eleven people had started paying.

“The first payment notification arrived while I was making dinner. I just stood there looking at my phone. Nine days earlier, Kitebird was a page in a notebook.” Ananya Rao, founder, Kitebird

Growing past one person

Over the next few months, Kitebird grew steadily through word of mouth. Ananya kept building on Nest, adding team seats and a shared content calendar when customers asked for them.

Eventually the product was large enough, and the revenue steady enough, that she hired her first engineer, Marco. She worried that bringing in a developer would mean starting over.

It did not. Kitebird had been synced to a GitHub repository from early on. Marco cloned it, read through the TypeScript, and started working in his own editor on day one. Because sync runs both ways, Ananya can still ask Nest for changes, and Marco’s commits show up in her project as versions.

“He said the code was more organized than he expected,” Ananya says. “I took that as a compliment for both of us.”

What she would tell other founders

We asked Ananya what she would say to someone with an idea and no engineer. Her answers were practical:

• Pick three features. Build only what you would personally pay for.

• Charge early. A waitlist tells you people are curious. A payment tells you they care.

• Talk to every early user. Most of Kitebird’s best features came from emails in the first month.

• Keep the code somewhere you own. Turning on GitHub sync early made hiring painless.

Kitebird now serves small businesses in more than a dozen countries, and Ananya still writes most new features as prompts before Marco reviews them.

If you are building a product of your own, our page for founders covers what to set up first, and you can read more stories like this one on our customers page.