Latest / Solopreneur Sessions with Fexingo: One-Person Businesses, Freelancing, and Independent Work / How a Solopreneur Used a Simple Checklist to Double Revenue
Transcript
- Lucas: So I was talking to a solopreneur last week — Maria runs a brand strategy consultancy, just her, no team, and she told me she doubled her revenue in six months without raising her rates or taking on more clients. Luna: Okay, that's a pretty big claim. What'd she do, clone herself? Lucas: Close. She created a single checklist. A two-page document that standardized every client engagement from the discovery call through to the final deliverable. And she told me it was the single highest-leverage thing she's ever done. Luna: A checklist. Like a pre-flight checklist for pilots? Lucas: Exactly like that. She modeled it on the Atul Gawande approach from 'The Checklist Manifesto' — the idea that checklists catch stupid mistakes and free up mental bandwidth for actually creative work. Maria was spending about a third of her time putting out fires, dealing with scope creep, clarifying what she'd already clarified. The checklist eliminated almost all of that. Luna: So what was actually on it? I'm imagining something like 'send proposal, get signed contract, do the work' — but that can't be it. Lucas: No, it's way more granular. She split it into two columns. Column one is 'Before the client sees it' — things like 'confirm the brief aligns with the proposal scope', 'check if any deliverables require third-party approval', 'schedule internal review buffer'. Column two is 'During delivery' — 'send weekly status snapshot every Friday at 3 PM', 'log all out-of-scope requests in a separate doc', 'flag any change that adds more than two hours of work'. Luna: That second one — logging out-of-scope requests — that's the money move, isn't it? Lucas: That's exactly where she saw the biggest impact. Before the checklist, she'd get a client saying 'hey, can you just add a competitor analysis?' and she'd say yes because it didn't feel like a big deal. But those little adds compounded. After the checklist, she had a system: she'd say 'happy to do that, let me add it to the scope change log and we can discuss pricing.' And because it was written down, it wasn't awkward — it was just process. Luna: So the checklist gave her permission to say no without feeling like she was being difficult. Lucas: Exactly. And it also made her look more professional. Clients actually respected her more because there was a clear structure. She said one client told her 'you're the most organized consultant I've ever worked with.' That came from a checklist. Luna: I can see how that reduces stress and makes you look good, but how does it double revenue? You said she didn't take on more clients or raise rates. Lucas: Right, so the revenue increase came from two places. First, she stopped leaking money on scope creep — she estimated she was giving away about 15 to 20 percent of her time for free before. Second, she freed up enough mental energy to actually do the work faster and better, which meant she could deliver the same quality in less time, and then use that extra time to take on one or two additional projects per quarter. That alone got her from about 80k to 120k. Luna: So the checklist didn't just prevent loss, it created capacity. Lucas: Exactly. And the other thing she did — and this is key — she didn't just use it for herself. She shared the checklist with clients at the start of each engagement. She'd say 'here's how we're going to work together, here's what you can expect from me every week, here's how we handle changes.' That set expectations up front and reduced a ton of back and forth. Luna: That's smart. It's basically a service-level agreement, but written in plain English and framed as a collaboration tool rather than a contract. Lucas: Precisely. And the interesting thing is, she didn't design it all at once. She started with a rough version after reading Gawande's book, then iterated over three months. Every time a problem came up, she added a step to prevent it next time. So the checklist became a living document that encoded everything she'd learned about running her business. Luna: That's actually a really good argument for why checklists are especially powerful for solopreneurs. When you're a team of one, you don't have colleagues to catch your mistakes. The checklist becomes your second pair of eyes. Lucas: Right. And Maria's story is not unique — I've seen similar results from freelancers in design, consulting, even coaching. The common thread is that they all had some version of a delivery system that reduced cognitive load. And the ones who do it best make the checklist part of their brand, not a hidden backstage tool. Luna: I want to push back a little though. Doesn't a rigid checklist risk making the client experience feel… robotic? Especially in a creative field like brand strategy, where the whole value proposition is bespoke thinking? Lucas: It's a fair concern. But Maria's take on this is that the checklist handles the predictable stuff so she can be fully present for the creative stuff. She said before, she'd be in a meeting thinking about whether she remembered to send the brief, whether the timeline was realistic, whether she'd missed an email. Now, she trusts the checklist, so her brain is free to actually listen and think strategically. Luna: So the checklist is invisible to the client in terms of the experience, but it structures the backend so the frontend feels effortless. Lucas: Exactly. And she's not the only one. There's a consultant named David C. Baker — he wrote a book called 'The Business of Expertise' — and he recommends something very similar. He calls it a 'delivery system' and argues that the most successful solo firms are the ones that systematize the non-creative parts of the work. Luna: I've heard of that book but never read it. What's his argument for why that works? Lucas: Baker says that clients don't actually want 'bespoke' in the logistics. They want bespoke in the thinking. They want to feel like you've tailored the solution to them. But they don't want to wonder when they'll get the next update or whether you'll forget a deliverable. A good delivery system gives them confidence, and confidence is what lets them pay a premium. Luna: Okay, so let's get practical. For someone listening who wants to build their own checklist — what's the first step? Lucas: Maria's advice is to spend one week tracking every single time you get interrupted, or feel confused, or realize you forgot something. Just write it down. At the end of the week, look at the list and pick the top three recurring issues. Build a checklist step for each one. That's your first version. Then iterate. Luna: Track your pain points. I like that. It's almost like debugging your own workflow. Lucas: Exactly. And she also recommends sharing the checklist with a trusted peer or a past client and asking 'does this make sense? Would this feel helpful or off-putting?' Because the framing matters. You want it to feel like a sign of competence, not a sign of rigidity. Luna: I can imagine a client seeing that and thinking 'wow, this person really has their act together.' That's a good thing. Lucas: It is. And there's a nice side effect — once you have the checklist, you can also use it to train a virtual assistant if you ever decide to hire one. The checklist becomes the foundation of your operations manual. Luna: Right, so it's not just a tool for now, it's an asset for scaling. That's a good point. Lucas: You know, speaking of the practical side of this — a handful of listeners actually chip in monthly to keep our show ad-free through buy me a coffee dot com slash fexingo, and that support lets us spend time digging into stories like Maria's and sharing the nitty-gritty details. Luna: Yeah, and we really appreciate that. It's a small group, but it makes a big difference in terms of what we can cover and how deep we can go. Lucas: So if these conversations have moved your work forward in some small way, that's the best way to keep them going. But back to the checklist — Maria also mentioned that she now has a version for the end of each engagement too. A close-out checklist. Luna: What's on that? Like, send the final invoice, archive the files, ask for a testimonial? Lucas: All of that, plus a few things you might not think of. She includes a step to schedule a 30-minute 'lessons learned' call with the client, where she asks what went well and what could be improved. She also adds a step to update her own checklist based on anything that came up. And she sends a small thank-you gift — a book or a handwritten note — which she says has generated a surprising number of referrals. Luna: That's a nice touch. And it's all just part of the system, so it doesn't feel like extra work. Lucas: Exactly. And that's the real takeaway for me — the checklist isn't about adding more steps, it's about making the right steps automatic so you can focus on the work that actually matters. Maria went from feeling overwhelmed and reactive to feeling like she was running a real business. And all it took was a two-page document. Luna: I'm going to try this. I think I'll start with my own top three pain points this week. See if I can build a mini-checklist for my own workflow. Lucas: I'd love to hear how it goes. Maybe we can do a follow-up in a few months — a listener challenge episode where people share their checklists. Luna: That's a great idea. Okay, so for anyone listening — start with one week of tracking your interruptions and confusion points. That's the first step. Lucas: And if you want to read more about the theory behind it, pick up 'The Checklist Manifesto' by Atul Gawande. It's a quick read and it'll change how you think about process. Luna: Or just listen to this episode again. Alright, that's all for today. See you next time. Lucas: Take care.