I recently finished writing a guide to help small SaaS teams figure out what to build (and what to ignore) once they’ve found some traction.
It’s based on my experience bootstrapping a B2B SaaS to over €1M ARR in the past 10 years. The framework came out of our own mess: too many ideas, no PM, lots of pressure, and no clear way to prioritize.
I tried to make it practical, with real examples, clear steps, no fluff. It covers:
- How to figure out who you’re really building for
- Mapping KPIs to outcomes
- Building a “Decision Map” and 3-year execution plan
I recently finished writing a guide to help small SaaS teams figure out what to build (and what to ignore) once they’ve found some traction.
It’s based on my experience bootstrapping a B2B SaaS to over €1M ARR in the past 10 years. The framework came out of our own mess: too many ideas, no PM, lots of pressure, and no clear way to prioritize.
I tried to make it practical, with real examples, clear steps, no fluff. It covers:
- How to figure out who you’re really building for
- Mapping KPIs to outcomes
- Building a “Decision Map” and 3-year execution plan
- Avoiding reactive product work
It’s ~16k words and free on Notion (no email wall): https://www.notion.so/redokun/What-Should-We-Build-Next-21f3...
I’d love feedback, especially:
- Is this useful for other small/bootstrapped teams?
- Anything confusing or unclear?
- Should I turn it into a more polished book?
Thanks to anyone who checks it out
P.S. You can also leave comments directly in the Notion file