Latest / Solopreneur Sessions with Fexingo: One-Person Businesses, Freelancing, and Independent Work / How a Solopreneur Built a 200k ARR with Zero-Code Automation
Transcript
- Lucas: Sarah Chen spent two years as a marketing manager at a mid-sized SaaS company, doing the same onboarding flow for every new client. She quit in early 2025, started a consulting practice, and within 18 months hit 200,000 dollars in annual recurring revenue. The twist? She never hired anyone. She automated everything with no-code tools. Luna: I love that story. Was it really just Zapier and Airtable? Lucas: Not quite just those—she used Notion for client portals and a tool called Make for complex workflows—but the principle is the same. She replaced herself with software for every repeatable task. And what's interesting is that she didn't start with automation. She started by doing everything manually for the first three months, just to understand where the friction points were. Luna: So she mapped out the process before trying to streamline it. Lucas: Exactly. She had a whiteboard in her home office—she showed me a photo—covered in sticky notes. Every step from first discovery call to final invoice. She color-coded them: green for tasks that only she could do, yellow for tasks that could be templated, red for tasks that felt purely administrative. And the red ones were where she started. Luna: If today's episode saves you even one hour of that kind of admin work, it's probably worth a coffee. And if it is, there's a link in the show notes—buy me a coffee dot com slash fexingo. Keeps this show ad-free and independent. Lucas: Absolutely. And honestly, Sarah's approach to that first red task is a great lesson. She picked the most annoying one: sending welcome emails and scheduling intake calls. She built a Zapier workflow that connected her Calendly to a Gmail template, automatically sent a personalized welcome note, and added the client to a Notion database. That one automation saved her about four hours a week. Luna: Four hours a week from one automation. That's huge. Lucas: And it's not just time. She told me it also reduced her anxiety because she no longer worried about forgetting to follow up. The system was reliable. So she built on that momentum. Next, she automated the creation of a project folder in Google Drive, a shared workspace in Notion, and an invoice in Stripe—all triggered by the same Calendly event. Luna: So the entire onboarding sequence became a single booking. Lucas: Exactly. And she did that without writing a single line of code. The most complex part was a multi-step Zap that created a new row in Airtable, which then triggered a Make scenario that generated a custom proposal PDF using a template and sent it via DocuSign. All done in about two hours of setup. Luna: What about client delivery? Consulting is usually very hands-on. Lucas: Right, and that's where most solopreneurs get stuck. Sarah's insight was to standardize her deliverables. She created a modular set of templates—strategy documents, audit reports, implementation guides—that she could customize per client. She used Notion's database feature to store each module and then built a dashboard that automatically populated a client's workspace with the relevant modules based on a dropdown selection. No copy-pasting. Luna: So she's essentially productizing her service while still appearing bespoke. Lucas: Exactly. Clients get a customized experience because she chooses the right modules, but the heavy lifting of formatting and structure is automated. She told me that before automation, she spent about 60 percent of her time on delivery and 40 percent on sales and admin. After automation, it flipped: 20 percent on admin, 40 percent on delivery, and 40 percent on sales and strategy. That shift alone allowed her to take on more clients without burning out. Luna: And that's how she hit 200k ARR with just herself. Did she ever consider hiring a virtual assistant? Lucas: She did, actually. She hired a VA in the Philippines for about 10 hours a week, but she quickly realized that the VA was also spending time on repetitive tasks. So she automated those too. Eventually, she let the VA go and relied entirely on automation. She says the VA was great but the systems were cheaper and more scalable. Luna: Interesting. So automation replaced human help in her case. Lucas: For the admin layer, yes. But she still does all the strategic work herself. The key is that automation freed up her brain space. She no longer has to remember to send a follow-up email or update a spreadsheet. The system does it. And she told me that the biggest unlock was not the time saved but the mental load reduction. Luna: That's a really important point. Many solopreneurs underestimate the cognitive cost of task-switching. Lucas: Absolutely. Sarah's weekly routine used to be fragmented: she'd check email, update a client tracker, prepare a meeting, jump to another client. Now she has dedicated blocks for deep work because the systems handle the interruptions. She also uses a tool called Motion to automatically schedule her tasks based on priority—that's another zero-code layer. Luna: So her entire backend is a stack of no-code tools. What's the stack, specifically? Lucas: It's pretty lean: Calendly for scheduling, Zapier and Make for automation, Airtable as the central database, Notion for client-facing workspaces, Stripe for payments, DocuSign for contracts, and Motion for task management. She also uses Loom for asynchronous video updates, which she says replaced about half her client meetings. Luna: That's a lot of tools. Was there a learning curve? Lucas: She says the hardest part was the first month. She tried to automate too much at once and broke a few workflows. For example, she set up a Zap that accidentally sent every new Airtable record as a separate email to a client, spamming them with 12 emails in one day. She learned to test each automation with a dummy account first. Luna: So she iterated. That's the solopreneur way. Lucas: Exactly. She now has a 'staging' environment—a duplicate Airtable base and a separate test workspace in Notion—where she runs new automations for a week before deploying them. It sounds overkill, but she says it's saved her from many embarrassing mistakes. Luna: What about client trust? Did any clients feel like they were getting a 'robotic' experience? Lucas: That's a great question. Sarah was worried about that too. So she made sure to inject personal touches into the automated flows. For instance, the welcome email includes a short personalized video she records using Loom—that's not automated. But the email that sends the video link and the calendar invite is automatic. So the client feels the human touch where it matters, but the system handles the logistics. Luna: So she's hybrid: personal where it counts, automated where it doesn't. Lucas: Exactly. And she actually surveyed her clients after six months. Ninety percent said they felt she was more responsive than previous consultants they'd worked with—because she never missed a follow-up and always had materials ready on time. The automation made her look superhuman. Luna: That's a powerful endorsement. Did she have any clients who explicitly noticed the automation? Lucas: A few, but they were impressed, not put off. One client said, 'You run your business like a well-oiled machine.' She took that as a compliment. And honestly, for a solopreneur, being able to say 'I'll have that proposal in your inbox in ten minutes' and then actually delivering it consistently is a competitive advantage. Luna: So what's the one takeaway for someone listening who wants to start automating? Lucas: Start with the most annoying task. Not the most important, not the most strategic—the one you dread doing every week. For Sarah, it was welcome emails. For someone else, it might be expense tracking or invoicing. Pick that one thing, automate it, and let the confidence from that success pull you into the next automation. She went from one Zap to about 30 over 18 months. Luna: And don't try to automate everything at once. Lucas: Right. She advises building a 'manual first' map—do it manually for a month, document every step, then automate one step at a time. That way you understand the process deeply before you hand it over to software. And you avoid the spaghetti automation problem where you don't know what's connected to what. Luna: I think the broader lesson here is that solopreneurs can compete with larger firms not by working more hours, but by designing systems that multiply their effort. Lucas: Exactly. Sarah's business now runs on a set of systems that she could hand off to a clone of herself—but she doesn't need a clone because the systems do the work. She's thinking about adding a second service line next year, and she's confident because the automation layer is already built. It's just a matter of duplicating the templates. Luna: That's really inspiring. And she's proof that you don't need a technical background to build this kind of infrastructure. Lucas: Not at all. Sarah's background is marketing, not engineering. She learned Zapier from YouTube tutorials. The barrier is lower than most people think. Luna: Alright, I'm going to look at my own workflows this weekend with a fresh pair of eyes. Lucas: Good plan. And if you build one good automation, let us know. We might feature it on a future episode.