Build something real, without a team.
Design, build, and ship a product people pay for — without waiting for a team.
For developers, designers, and operators who are tired of waiting for permission.
- A sharper idea — and a clear reason someone would pay for it
- A scope you can actually finish, with the non-essentials removed
- A stack and build sequence that fit one person's attention
By Amber Anand — senior software engineer, designer, and builder of five products in production.
SOLO
BUILT
A field guide for one-person product teams
Amber Anand
First edition
The honest problem
You don't need more advice. You need a smaller plan.
Most one-person products fail in the gap between an ambitious idea and a usable first version. Not because the builder lacks talent — because the scope quietly assumes a team that doesn't exist.
The fix isn't a bigger hustle. It's a narrower wedge, a smaller release, and a sequence you can actually finish on the hours you have.
Solo Built is the map I wish I'd had before shipping five products by myself. It skips the motivation and gets straight to the decisions.
What's inside
A map from idea to something people use.
Start with a wedge
Find a problem small enough to solve and painful enough to pay for.
Scope the sellable thing
Turn a sprawling idea into a product you can build, explain, and charge for.
Design the first mile
The screens that decide whether anyone gets to the value.
Choose boring infrastructure
A stack you can operate alone without becoming a full-time sysadmin.
Build the 80% that matters
Ship the core loop, hide the sharp edges, and stop polishing the wrong thing.
Price before you feel ready
Packaging, positioning, and the first number you say out loud.
Launch smaller than you think
A launch plan that creates users instead of a day of applause.
Sell the second version
How to learn from the first customers and turn a launch into a business.
Operate like a studio of one
Systems for support, marketing, and maintenance without burning out.
The next product
When to double down, when to stop, and how to build a body of work.
The one-page product brief
A launch-week checklist
The stack decision worksheet
“The first version of a product is not a smaller version of the final thing. It's a sharper version of one true thing. Your job is not to build everything the product could become. Your job is to build the shortest honest path from someone's problem to a result they'd pay for. Everything else is a feature request from a future you haven't met yet.”
Who it's for
For the person who keeps thinking, “I could build this.”
You don't need a technical co-founder, a funding round, or permission. You need a smaller plan and the nerve to finish it.
Not for you if
- You want someone else to build the thing for you.
- You're looking for a get-rich-quick playbook.
Written by Amber Anand
Senior software engineer · five products shipped
The author
Built by someone who's done it five times.
I'm Amber Anand, a senior software engineer and designer based in Patna, India. I've spent 7+ years building production software — including page-building platforms and multi-tenant systems at Ticketmaster — and have designed, built, and shipped five products of my own.
I wrote Solo Built because the advice I kept finding was either too abstract to use or too online to trust. This is the version I needed: specific, honest about the trade-offs, and short enough to act on.
When does the book launch?
The first edition is being finished now. Join the launch list and you'll get the first chapter free, plus early-access pricing when it's ready.
Do I need to know how to code?
No, but the book assumes you'll either learn enough to build a first version or work closely with someone who can. Every technical decision is explained in plain language.
Is this for non-technical founders?
It's written for people willing to get close to the work. Non-technical readers will get the most from the scoping, positioning, pricing, and launch chapters. Technical readers can move faster through the build.
What format do I get?
PDF, EPUB, and a Notion companion with the templates and worksheets. Buy once, read on whatever you use.
Is this written by AI?
No. Every chapter is written by me, from my own experience designing, building, and shipping five products. AI helps with research and editing — not the thinking or the stories.
Will I get future updates?
Yes. Every future edition of this book is included in your purchase, at no extra cost.
What if it isn't for me?
If the book isn't useful, email me within 14 days of purchase and I'll refund you. No interrogation, no hoops.
The next thing you build could be the one.
Get the first chapter now, and the full book the moment the first edition is ready.
The launch list
Be first to read it.
Join the list for the first chapter, the launch date, and early-access pricing.
Read it, use it, and if it doesn't change how you build, email me within 14 days for a refund.