Last week I shared the system I used to build a side project while working full time, the Building Loop, the concept of sovereign hours, and why "stay consistent" is terrible advice.
A few of you replied with something I didn't expect: "I've been building for months and I still don't know if anyone would actually pay for this."
That's not a building problem. That's a business model problem. And it's the one most technologists never address, because we'd rather write code than answer uncomfortable questions.
The Code-First Trap
Here's a pattern I've seen repeat dozens of times, both in my own career and in conversations with builders:
You have an idea. It can even be a very good one. You can see exactly how it should work technically. So you open your code editor and start building. Feature by feature, component by component, you make progress. It feels productive. It is productive in the sense that code is being written.
But six months later, you have a working product and zero users. Or you have users who love your product but will never pay for it. Or you have a product that solves a problem nobody actually has, or at least not badly enough to switch from what they're already doing.
The painful truth: the code was never the risky part. Now even less so with the advent of AI assisted coding. You know how to code. You've been doing it professionally for years. The risky part was always the business model: the set of assumptions about who this is for, why they'd use it, how they'd find it, and how it would sustain itself.
Most builders never make those assumptions explicit. They live as vague feelings in the back of your mind: "developers would probably use this" or "I could charge a subscription" or "people will find it through word of mouth." These aren't plans. They're hopes. And hopes don't survive contact with reality.
What a Business Model Canvas Actually Does
The Business Model Canvas, originally created by Alexander Osterwalder, is a single-page framework that forces you to articulate nine interconnected assumptions about your product. This is not a business plan: the 40-page documents of a business plan that people rarely read. This is a canvas which results in one page split in nine blocks. Each one answering a question you need to face.
Here's why it matters specifically for technologists building side projects:
It surfaces the questions you're avoiding. You might have a crystal-clear picture of your Value Proposition, but have you honestly thought about Channels? How will people discover this thing you built? "I'll post it on Reddit" is not a channel strategy. The canvas forces you to be specific.
It reveals which blocks are empty. When you sit down and try to fill in all nine blocks, some will flow easily and others will stare back at you blank. Those empty blocks are the most valuable output of the exercise. An empty block means you have an untested assumption that could sink the entire project.
It shows how the blocks connect. Your Customer Segments determine your Channels. Your Channels affect your Cost Structure. Your Revenue Streams need to exceed your Cost Structure or the whole thing is unsustainable on the long run. The canvas makes these connections visible in a way that keeping everything in your head never can.
How to Think Through It Properly
When you fill in the canvas, start with Customer Segments, and not with Value Proposition. This is counterintuitive because most builders start with what they're building, not who they're building for. But everything flows from the customer.
Here's the sequence I recommend:
Start with Customer Segments. Be ruthlessly specific. Not "developers" - answer which developers? Doing what? At what company size? Facing what specific frustration? If you can't name five real people who fit your segment, it's too vague.
Then Value Propositions. Now that you know who you're serving, what problem are you solving for them? And critically: is this a painkiller or a vitamin? Painkillers solve urgent, painful problems people will pay to fix. Vitamins are nice-to-have improvements people intend to try but never prioritize. Most failed side projects are vitamins disguised as painkillers.
Then Channels and Customer Relationships. How will these specific people discover your product? And once they do, what relationship do they expect? Self-service? Community? Direct support? Your answer here directly determines how much of your time the product will consume, which matters enormously when you're building in your sovereign hours.
Then Revenue Streams and Cost Structure. Be honest with yourself. What would you charge? What would you pay if you were the customer? What are the unavoidable costs? Can you sustain the costs with zero revenue for six months while you find product-market fit? If not, you need to adjust the model before you build, not after.
Finally: Key Resources, Activities, and Partners. What do you personally need to do that nobody else can? What could be automated or outsourced? What platforms or services does your product depend on, and what happens if they change their pricing or terms?
The Real Output Isn't the Canvas - It's the Conversation you have with yourself while doing it
Here's something that surprised me when I first did this exercise for The Sovereign Technologist: the value wasn't the filled-in canvas. It was the process of filling it in. The blocks that made me pause, the assumptions I couldn't defend, the connections I hadn't thought through. Those were the real insights.
When I tried to fill in Revenue Streams for this newsletter and service offering, I had to confront the fact that I didn't have a clear monetization path yet. That was clear right away. It told me exactly what to figure out next, instead of vaguely worrying about it while writing more content.
The canvas doesn't give you answers. It gives you better questions. And better questions lead to better products.
The Tool
I built an interactive version of the Business Model Canvas specifically for technologists.
It has guided prompts for every block like "Can you reach your first 50 users without paid ads?" and "What's the minimum tech stack to validate this?"
Fill it in online, download it as a branded PDF when you're done.
If You Want a Second Pair of Eyes
Filling in the canvas alone is valuable. But having someone pressure-test your assumptions is even better.
I'm offering 5 free 30-minute brainstorm sessions this week for anyone who fills in the canvas and wants to walk through it together. We'll look at your nine blocks, find the gaps, and stress-test the assumptions that matter most.
Same deal as the Visibility Triage calls as I learn what builders are struggling with and you get a sharper business model.
The One Thing
Code is the easy part. The hard part is answering all questions honestly before you start.
Most side projects don't fail because of bad code. They fail because the builder never made their business assumptions explicit. The canvas doesn't take long. The clarity it creates lasts the life of your project.
What I'm Building This Week
This week I shipped the interactive Business Model Canvas tool, the second resource on The Sovereign Technologist after the Visibility Audit. I used my own Building Loop to do it: shaped the scope to a single interactive page with PDF export, validated by testing the prompts with a few builders first, and shipped before it felt complete.
I also filled in my own canvas for a product idea I've been sitting on. Three blocks came back empty. That told me exactly what to research next instead of what to code next.
Next week: the patterns I'm seeing from canvas brainstorm sessions, and what most technologists get wrong about Revenue Streams.
What resonated? What did I get wrong? Hit reply: I read everything and I'm building this with you and with your input.
P.S. If you haven't taken it yet, The Builder's Visibility Audit scores your career visibility across 6 dimensions in 2 minutes. It pairs well with the canvas, one shows you where you stand, the other shows you where you're going.
P.P.S. Know a technologist with an idea they haven't validated? Forward them this email. They can subscribe at thesovereigntechnologist.com.
That’s all for this week.
See you next Thursday.
