Solopreneur Sessions with Fexingo · 2026-07-01 · 12 min
Key moments - from our scoring
Substance score
52 / 100
Five dimensions, 20 points each
This episode examines the counterintuitive strategy of building a solopreneur business around one or two high-value retainer clients instead of chasing multiple small projects. Maya's case study - transitioning from a project-based model (15 clients × $500 - $2K invoices, 70% utilization) to a single $120K retainer - reveals how productizing a service (in her case, a design system with reusable components, templates, and monthly design sprints) can eliminate admin overhead, reduce payment friction, and increase effective hourly rates. Hosts Lucas and Luna discuss value-based pricing (Maya charged $250/hour on her retainer vs. $150/project), the critical importance of building intellectual property the solopreneur owns (not just client relationships), and how a 90-day exit clause and a second retainer client ($40K annually) provided necessary diversification without sacrificing simplicity. The conversation covers infrastructure (Notion + Stripe), the Indie Hackers data showing 40% of six-figure solo founders have three or fewer clients, and Maya's evolution toward eventually licensing her design system as a product. This episode appeals to freelancers burned out on proposal writing, payment chasing, and client acquisition - those ready to trade flexibility for stability by packaging repeatable outcomes rather than hourly blocks.
Price the retainer based on the value it delivers to the client, not on hours, and package a repeatable outcome (like a design system with monthly sprints) that gets faster to deliver each month. Maya charged $250/hour effective rate on her retainer versus $150 project rate because she was selling access and predictability, not time blocks.
Maya mitigates this risk by maintaining a two-retainer ceiling with a 90-day exit clause on both, plus keeping a waiting list of prospects interested in her design system. The key is owning the intellectual property (the design system itself), so if a client leaves, you can resell that system to another company.
It depends on whether you're selling hours or outcomes. Selling monthly time blocks is just pre-sold hours and often results in working more for less money. A profitable retainer must include something that scales - like a design system, content library, or analytics report - that gets cheaper or faster to produce each month.
Identify a repeatable outcome you can deliver efficiently each month (not just hours), then approach your best existing client with a trial period at a slightly lower rate to prove the model reduces their risk and proves the value before committing to full price.
According to Indie Hackers data cited in the episode, about 40% of solo founders earning over $100K annually have three or fewer clients, and those with a single client often have the highest profit margins because overhead is nearly zero.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode contains a useful core insight (shifting from hourly billing to productized retainers) and practical details (design system as leverage, 90-day exit clauses, value-based pricing), but much of the dialogue is clarification and agreement rather than novel claims. The Indie Hackers survey reference adds weight, but most of the framework is established thinking in solopreneur circles.
She didn't sell them hours. She sold them access to her design system. She had built a library of reusable components - templates, color palettes, font pairings, icon sets - and the retainer gave the client unlimited use of that system plus two monthly design sprints.
Maya's retainer was actually priced higher per hour than her project rate - because she was selling access, not time.
The productized service framework is well-established in indie/solopreneur content; the episode recycles common concepts (productization, value-based pricing, systems-building) without significant counterintuitive claims. The single-client case study is illustrative but not conceptually novel, and the 'two-retainer ceiling' is a sensible tactic rather than original thinking.
If you're giving up the flexibility to take other projects, you should be compensated for that.
The goal shouldn't be to get more clients. The goal should be to build a system that delivers enough value to a small number of clients that they're happy to pay a premium for predictability.
The episode features two hosts (Lucas and Luna) discussing a third-party case study ('Maya'), not a direct operator interview. Neither host identifies themselves with relevant credentials, and 'Maya' is anonymized and narrated rather than present to validate or add depth. This is fundamentally a second-hand anecdote, not a primary source with hands-on authority.
So there's this freelance designer I've been following for about a year - let's call her Maya.
She started out doing logo projects, website mockups, the usual one-off stuff.
The episode contains concrete numbers for Maya's case (five hundred to two thousand per project, sixty thousand baseline income, one hundred and twenty thousand retainer, forty thousand second client, two hundred and fifty dollars per hour effective rate) and one external data point (Indie Hackers survey showing 40 percent of six-figure solopreneurs have three or fewer clients). However, the Indie Hackers reference lacks a date, link, or sample size, and all other evidence rests on a single anonymized anecdote without verification.
Fifteen different clients a month, each paying somewhere between five hundred and two thousand dollars. She was barely clearing sixty thousand dollars a year.
one hundred and twenty thousand dollars a year.
Luna pushes back constructively ('For every Maya, there are probably ten freelancers who tried the retainer model and failed') and asks for evidence ('Do you have any numbers on that?'), which shows some questioning instinct. However, follow-ups are often brief and don't press on gaps (e.g., the Indie Hackers survey is cited but never questioned for rigor, and the two-client concentration risk is acknowledged but not deeply explored).
I want to push back a little. For every Maya, there are probably ten freelancers who tried the retainer model and failed because they didn't have a productized offering.
Do you have any numbers on that? I'd love to see the data.
Computed from the transcript - who did the talking, and the words that came up most.
In this episode of Solopreneur Sessions, Lucas and Luna explore the counterintuitive strategy of building an entire one-person business around a single recurring invoice. They examine the case of a freelance designer who replaced 15 erratic project clients with one monthly retainer that generated $120,000 annually, using a simple Notion page and a Stripe subscription. The conversation covers the psychological shift from selling time to selling outcomes, the math behind the lone invoice model, and when this approach makes sense versus when it's a trap. Lucas argues that the solopreneur's real breakthrough was pricing access to her design system rather than per-project hours, turning the retainer into a productized service. Luna pushes back on the risk of total dependence on one client, and together they discuss redundancy strategies like the two-retainer ceiling and the exit clause that kept the relationship healthy. If you've ever wondered whether you could simplify your freelance business down to one monthly payment, this episode offers a concrete, repeatable blueprint.
Transcribed and scored by The B2B Podcast Index.
Lucas: So there's this freelance designer I've been following for about a year - let's call her Maya. She started out doing logo projects, website mockups, the usual one-off stuff. Fifteen different clients a month, each paying somewhere between five hundred and two thousand dollars. She was busy all the time and barely clearing sixty thousand dollars a year.
Luna: That sounds like the classic freelance treadmill. Lots of work, not much money. Lucas: Exactly. And then about eighteen months ago, she made a change that I think is worth unpacking.
She dropped all but one client and replaced those fifteen invoices with a single monthly retainer. One invoice, one client, one hundred and twenty thousand dollars a year. Luna: Wait - one client? That sounds terrifying.
What if that client leaves? Lucas: That's the obvious risk, and we'll get to it. But the math is interesting. Before, she had maybe a 70 percent utilization rate - the rest was admin, proposals, chasing payments.
After, she had basically 100 percent billable time because the retainer covered a fixed set of deliverables each month. No scoping new projects, no negotiating rates, no overdue invoices. Luna: So how did she convince one client to pay that much? A hundred and twenty thousand dollars is a big commitment for a single freelancer.
Lucas: She didn't sell them hours. She sold them access to her design system. She had built a library of reusable components - templates, color palettes, font pairings, icon sets - and the retainer gave the client unlimited use of that system plus two monthly design sprints. It was basically a productized service.
The client got consistency and speed, and she got predictable revenue. Luna: So she shifted from selling time to selling outcomes. That's the playbook a lot of productized service businesses use. Lucas: Right.
And the interesting thing is, she didn't need fancy tools. She used a simple Notion page to share the design system and set up a Stripe subscription for the monthly payment. The whole infrastructure cost maybe twenty dollars a month. Luna: But let's go back to the single-client risk.
If that one client decides to pivot, or gets acquired, or just wants to take design in-house, she's back to zero overnight. Lucas: That's real. And Maya actually thought about that. Her solution was to have what she calls a 'two-retainer ceiling' - she'd never take a third retainer, but she'd always keep two.
She started with one, but after six months she added a second client at a smaller retainer, about forty thousand a year. So now she's at a hundred and sixty thousand total, with the second client as a buffer. Luna: So the one-invoice model evolved into a two-invoice model. That's more diversified, but still pretty concentrated.
Lucas: Which is exactly the trade-off. The solopreneur's real asset here isn't the client - it's the design system. That's what she owns. If one client leaves, she can take that system to another company.
The retainer is just the delivery mechanism. Luna: That's a key distinction. The product isn't the client relationship, it's the intellectual property. I've seen a lot of freelancers confuse the two.
Lucas: Yeah. And Maya built in something else that I think is smart - a 90-day exit clause. Either side can cancel with 90 days notice. That gives her time to find a replacement client, and it gives the client time to transition.
It keeps the relationship from feeling like a trap. Luna: So she's not locked in, and neither are they. That probably makes the retainer feel safer for both sides. Lucas: Exactly.
And I think that's the real lesson here. The one-invoice model isn't about being lazy or avoiding sales. It's about designing a business where your energy goes into the work, not into the process of getting work. Luna: Okay, but I want to push back a little.
For every Maya, there are probably ten freelancers who tried the retainer model and failed because they didn't have a productized offering. They just tried to sell monthly blocks of time - which is basically a subscription to their availability. Lucas: That's a great point. A retainer for hours is just a different way to bill time.
It doesn't change the economics. The shift only works if you're selling something that scales - like a design system, a content library, a monthly analytics report that gets easier to produce each time. Luna: So the productized service has to have a component that gets cheaper or faster to deliver over time. Otherwise you're just pre-selling hours at a discount.
Lucas: Right. And that's where I think a lot of people get it wrong. They offer a retainer at a lower hourly rate than their project rate, and then they end up working more hours for less money. Maya's retainer was actually priced higher per hour than her project rate - because she was selling access, not time.
Luna: That's counterintuitive. Most people think retainers mean a discount. Lucas: Most people think wrong. If you're giving up the flexibility to take other projects, you should be compensated for that.
Maya's retainer worked out to about two hundred and fifty dollars an hour for the actual time she spent. Her project rate was a hundred and fifty. Luna: So she basically got a raise by simplifying her business. That's a powerful story.
Lucas: It is. And I think it points to a broader principle for solopreneurs. The goal shouldn't be to get more clients. The goal should be to build a system that delivers enough value to a small number of clients that they're happy to pay a premium for predictability.
Luna: And that system - the design system, the Notion template, the recurring deliverable - that's the real business. The client is just the customer. Lucas: Exactly. And I think that's a mindset shift that a lot of freelancers never make.
They stay in the project model because it feels safer to have many clients. But the data shows that the most profitable solopreneurs often have the fewest clients. Luna: Do you have any numbers on that? I'd love to see the data.
Lucas: There's a survey from Indie Hackers a couple years back that looked at solo founders making over a hundred thousand dollars a year. About 40 percent of them had three or fewer clients. And the ones with a single client had the highest profit margins - because their overhead was basically zero. Luna: That's fascinating.
But it also means those businesses are fragile. One bad quarter and they're done. Lucas: True. But fragility isn't the same as risk.
A business with one client and a six-month runway is actually less fragile than a business with ten clients and a two-week runway. You have to look at the whole picture. Luna: That's a fair point. And Maya's exit clause gives her a three-month buffer.
Plus she has the second retainer now. So she's built in some redundancy. Lucas: Right. And she's also got a waiting list of companies that want access to her design system.
She just doesn't take them on because she wants to keep her workload manageable. That's a good position to be in. Luna: So for someone listening who wants to try this - what's the first step? They're currently doing project work and they want to move to a retainer model.
Lucas: First, they need to identify what they can productize. It's not just about packaging hours. It's about finding a repeatable outcome they can deliver efficiently. For a writer, that might be a monthly content audit and strategy document.
For a social media manager, it might be a weekly set of ten posts with analytics. Luna: So the deliverable has to be something that gets faster with repetition. The first month might take twenty hours, but by month six it's down to ten. Lucas: Exactly.
And then they need to price it not based on hours, but on the value to the client. If that content audit saves the client two thousand dollars in ad spend, you can charge five hundred dollars for it. The hours don't matter. Luna: That's easier said than done.
A lot of freelancers struggle with value-based pricing because they don't know what their work is actually worth to the client. Lucas: That's why Maya started with one client she already had a good relationship with. She didn't pitch a cold prospect on a retainer. She went to her best client and said, 'I want to give you more consistent support, and I want to build a system that makes your life easier.
Here's what it would look like.' Luna: So she started with a warm lead. That makes sense. And the client already knew her quality, so they were more willing to take a chance on a new model.
Lucas: Exactly. And she offered a three-month trial at a slightly lower rate to prove the model. After three months, the client saw the consistency and speed, and they agreed to the full price. Luna: I like that.
A trial period reduces the risk for both sides. If it doesn't work, they go back to project work. Lucas: And that's the beauty of the solopreneur model. You can experiment.
You can try a retainer for three months and if it's not working, you pivot. The overhead is so low that you can afford to be wrong. Luna: That's a good note to end on. Experiment, iterate, and don't be afraid to simplify.
Lucas: If these conversations have moved your work forward in some small way, a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these. It keeps the show ad-free and lets us dig into stories like Maya's without worrying about sponsors. Luna: Yeah, and it's a small group that makes it possible. We're grateful for every person who does that.
Lucas: So back to Maya - she's now at eighteen months with her first retainer client and twelve with the second. She's thinking about adding a third, but she's hesitant because she doesn't want to hire. And that's the real constraint for solopreneurs: how much can you scale without adding headcount? Luna: That's the million-dollar question.
And I think the answer is: you scale by building better systems, not by adding more clients. Lucas: Exactly. Maya's design system is her leverage. Every time she adds a new component to the library, she makes future work faster.
Eventually, she could license that system to multiple clients without doing much additional work. That's the dream. Luna: So the one-invoice model might just be a stepping stone to a product business. First you productize your service, then you productize your product.
Lucas: That's a great way to put it. And I think that's the trajectory for a lot of successful solopreneurs. They start with project work, move to retainers, and then eventually create a digital product that generates revenue while they sleep. Luna: Maya's not there yet, but she's on the path.
And the retainer gives her the stability to work on that product without worrying about where next month's rent is coming from. Lucas: Exactly. So if you're a freelancer feeling the burnout of constant client churn, maybe consider: what if you only had one invoice? What would that business look like?
Luna: That's a good question to leave listeners with. Thanks, Lucas. Lucas: Thanks, Luna. See you next time.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.
How API Webhook Delivery SLOs Create Hidden Reliability RisksThe Developer Tools Podcast with Fexingo · on Stripe98 / 100
Trust, stablecoins, and the AI margin squeeze:What McKinsey and QED's fintech report means for banksTearsheet Podcast: Exploring Financial Services Together · on Stripe89 / 100
He quit Stripe and hit $10M ARR in 4 years - with $0 marketing spend. | Anurag Goel, Founder of RenderA Product Market Fit Show · on Stripe89 / 100
Shifting to Value-Based Pricing the Right Way with Lori Williams and Kirsten ProstRattle & Pedal: B2B Marketing Podcast · on Value-based pricing88 / 100
Interview: Maple Cofounder Joe FlanaganFintech Business Podcast · on Stripe85 / 100
Why the Best Fintech Companies Are Staying Private With Sahej Suri, Founder of Blue Dot InvestorsFintech One-On-One · on Stripe81 / 100How a Solopreneur Used One Client Exit to Pivot and Grow72 / 100How a Solopreneur Used One Client Complaint to Reframe an Entire Business75 / 100How a Solopreneur Used One Podcast Appearance to Land 100K in Sales59 / 100How a Solopreneur Used One Strategic Partnership to Triple Revenue82 / 100How a Solopreneur Built a SaaS with Zero Code80 / 100