Founder Playbook · Starter Story

12 tactics from Yaser

Chatbase$6.8M ARR

How I Built A $1M Business in 117 Days

Watch the full episode
Idea validation
No one was building a product around it. I knew this is a good idea — I didn't do any validation or anything. I just said, if I don't do this, someone else will.

Skip validation when the gap is obvious — if you don't build it, someone else will

When you see demos of a capability but no real product wrapping it, that gap itself is the signal. Treat speed as the validation — if you don't build it, someone else will, and the window closes fast.

Idea validation
Find something that you can't build yet and the only bottleneck is the AI model itself… then start building that and just bet that in a year you're going to have GPT-5 capable of doing that, and you have one full year as a head start.

Bet on the model curve — build for the capability that is coming next

Pick an idea that the current models can almost — but not quite — handle. By the time the next model lands, the product is ready and you have a year-long head start on everyone who waited for the capability to arrive.

Shipping
You don't have to have a lot of features, just have one core feature… just have a good UI, don't have any bugs, have a good MVP, and then launch it into the universe. Find the balance between launching fast and not launching garbage.

Ship one core feature, a clean UI, and a Stripe button — nothing more

Resist the urge to build wide. One core feature, a clean landing page, no bugs, a UI you're proud of, and a Stripe button is enough to start charging. Anything beyond that delays revenue without adding signal.

Launching
Minimizing the seconds to the aha moment… it shows exactly what I built was capable of in the first 20 seconds. I mention the tools I was using… those people picked it up and they were going viral, so my thing also went viral.

Make the demo land the aha in 20 seconds and name-drop the tools you used

A launch tweet needs a familiar interface, a 20-second aha moment, and credit to the tools you built on. Tagging the infrastructure providers turns their hunger for case studies into free distribution and a viral loop.

Launching
With every new release I would frame it as a new launch… I try to frame every single launch to make it make sense to new people that don't know me, that don't know Chatbase.

Frame every feature release as a fresh launch for people who have never heard of you

Most founders treat shipment two and three as feature updates, which loses anyone who missed the first one. Re-introduce the product from scratch every launch so a cold viewer can grasp it in seconds and convert.

Audience
The easiest thing is just to share what you're doing every day… one tweet is not going to do it. People need to see your face a lot, preferably if you can do videos too, post them on X.

Audience compounds from daily posts — one viral tweet won't do it

Audience growth on X compounds from consistent daily posting, not from one breakout tweet. Show your face, post short videos, and frame the journey as building and learning out loud — the medium most builders avoid is where you stand out.

Audience
An important part is not to be boring. I think it's better to be more personal, share your personal story, have a personality, have controversial takes — maybe, if it's something you actually believe in — because that's how you get people to notice you.

Don't be boring — personality and controversial takes are how strangers notice you

A neutral, professional feed gets ignored. Lead with personal story and sharp opinions you actually hold — controversy that reflects genuine belief is the cheapest way to break through the noise and earn attention from people who don't know you yet.

SEO
Going into subreddits of books, I would create a ChatGPT for their book. It was free, I was losing money on this. The only point of doing this is to have my domain opened by a lot of people so I get more domain authority.

Burn money on free niche giveaways to harvest domain authority

Giving away small, hyper-targeted versions of the core product — a chatbot for a specific book, influencer, or community — burns money short-term but seeds links and traffic that lift domain authority. Treat the free instances as SEO and distribution, not a feature.

Pricing
Right now we're exactly at 6.8 million ARR… right now it's only PLG. We just passed actually 2 days ago 10,000 customers that are paying us between $40 and $500 a month.

A wide $40–$500/month PLG ladder scaled to $6.8M ARR with zero sales motion

A self-serve SaaS can scale past $6M ARR on pure PLG with a price band that starts at $40 and stretches to $500 per month. The wide ceiling matters — it lets power users self-select into bigger plans without ever needing a sales motion.

Distribution
When I mentioned LangChain and Pinecone… it made sense for them to push it too because no one else was building stuff like this on their platforms yet… it created this viral loop.

Tag the infrastructure you built on — they will amplify your launch for free

Name-drop the platforms and tools powering your build. Early-stage infra companies hunt for real customer demos and will amplify your launch to their audience — turning their distribution into yours for free.

Mindset
The advice you're getting from people that have done this before, it's just good to listen to but mostly irrelevant — because no one knows your situation as much as you.

Best-practice advice is mostly noise — trust your gut, you know your situation

Generic founder advice rarely maps to your specific situation. Listen, then trust your gut — even seasoned operators will tell you the same thing once you press them. Your context is the asymmetric information.

Mindset
My goal was to just get my 10K, move to Bali, live the indie hacker lifestyle. I just realized — why not shoot for the stars, right? Why not build the first 100 million ARR bootstrapped company.

Aim for $100M bootstrapped — not the $10K Bali indie-hacker ceiling

The $10K MRR indie hacker ceiling is a self-imposed mental cap. Aim higher from day one — being too reserved about a working product costs more than being too aggressive.