Latest / Solopreneur Sessions with Fexingo: One-Person Businesses, Freelancing, and Independent Work / How a Solopreneur Used a Simple No-Code App to Replace an Assistant
Transcript
- Lucas: So I was talking to a friend last week — freelance graphic designer, does brand identities for small businesses. And she mentioned she spends about fifteen hours a week just on admin. Client emails, scheduling, invoicing, chasing payments. Luna: That's almost a full day out of the week, gone. Lucas: Exactly. And she's not alone. I see this pattern over and over with solopreneurs — they hit a certain revenue level, maybe around 80 to 100 thousand a year, and suddenly the non-billable work eats into everything. The obvious answer is 'hire a virtual assistant.' But that comes with its own overhead — training, delegation, trust. Luna: Right, and not everyone wants to manage another person. Or can afford a consistent retainer. Lucas: Yeah. So instead, she built her own no-code app. And that's what I want to dig into today. Her name is Sarah Chen — she's based in Austin, runs a design studio called Curve & Color. And over two weeks, she built a custom application using Bubble that basically functions as her client operations hub. Luna: Wait — she built an entire app in two weeks? I've dabbled in Bubble myself, and it's not trivial. Lucas: It's not. But Sarah had a very specific, narrow scope. She didn't try to build a CRM from scratch. She automated three things: client onboarding, project scheduling, and invoicing. That's it. The onboarding piece alone was worth it — she used to send four or five back and forth emails just to collect a brief, get files, and confirm scope. Luna: And now there's a form, I assume. Lucas: Exactly. A branded form in Bubble that captures the project brief, uploads reference files, and automatically creates a record in Airtable — that's her backend database. Then Zapier triggers a Calendly invite for a kickoff call, and once that call is marked done, a Stripe invoice draft is generated. All without her touching anything. Luna: So the flow is basically: client fills out form → Airtable gets a row → Calendly email goes out → after call, invoice appears. That's elegant. Lucas: That's the core. And the whole thing runs on about fifty dollars a month in platform fees — Bubble's free tier plus a twenty-dollar Airtable plan, and Zapier's free tier covers her volume. She didn't need to hire anyone. Luna: I love that. But I also wonder — what's the catch? I mean, building and maintaining a no-code app takes time. You said she spent forty hours building it. That's a week of non-billable work. Lucas: Right. And that's the trade-off. She invested one week up front to save fifteen hours per week ongoing. So the payback period is less than three weeks. After that, it's pure time gain. But — and this is important — she had to learn Bubble basics first. She spent maybe ten hours on tutorials before she even started building. Luna: So the real cost is about fifty hours upfront. For someone already drowning in admin, finding fifty hours to learn a tool is not easy. Lucas: No, it's not. And that's why I think a lot of solopreneurs default to just hiring a VA. But Sarah's argument is that the app is more reliable — it doesn't get sick, doesn't quit, and it scales with her without needing to retrain someone. She's now had the app running for eight months, and she's only had to tweak it twice — once when she changed her invoicing terms, and once when she added a new service tier. Luna: That's a pretty low maintenance burden. What about the user experience for her clients? Does the app feel polished? Lucas: She spent a lot of time on that, actually. The Bubble front end is styled to match her brand — custom fonts, consistent colors, even a little animation when the form submits. She says clients often comment that it feels 'more professional than the big agencies I've worked with.' Because most agencies still use Google Forms or just email. Luna: There's a lesson there — a good experience is a differentiator even for a solo operator. Lucas: Absolutely. And I think the bigger point is that no-code tools have matured to a point where a non-technical founder can build production-grade workflows. Sarah doesn't know JavaScript. She's a designer. But she was able to chain together Bubble, Airtable, Zapier, Stripe, and Calendly into a system that genuinely replaces a part-time employee. Luna: I want to talk about the limits, though. Where does this fall apart? Like, if she wanted to add a client portal where clients could see project status or download past invoices, could she do that in Bubble? Lucas: She could, but that's where the complexity ramps up. Bubble can handle user accounts and permissions, but it's a lot more work. Sarah decided not to go that route because her clients don't need it — she sends invoices via Stripe's hosted page, and project updates happen in Slack. But if she wanted to, she could. The question is whether the incremental time savings justify the build effort. Luna: That's the solopreneur calculus: every feature has an opportunity cost. You have to be ruthless about what you automate. Lucas: Exactly. And Sarah was very disciplined. She only automated the tasks that were both repetitive AND time-sensitive. Chasing late invoices? That's a manual email she still sends — but she automated the generation. Scheduling? Automated, because it's a fixed process. The things that require judgment, like deciding whether to offer a discount or how to handle a scope change, she keeps manual. Luna: That's smart. A lot of people try to automate everything and end up with a brittle system that needs constant babysitting. Lucas: Right. So I asked Sarah what she'd recommend to someone listening who's thinking about doing something similar. Her advice: start with one workflow — the one that annoys you the most. For her, it was the back and forth of client onboarding. For someone else, it might be expense tracking or content publishing. Build that one flow, get it stable, then decide if you want to expand. Luna: And don't try to learn everything at once. Just pick one tool. Bubble can be overwhelming. She started with just Airtable and Zapier, then added Bubble later. Lucas: Yeah, she actually prototyped the workflow in Airtable alone — using linked records and automations — before she built the Bubble front end. That way she could validate the logic without learning a new platform. Once she knew the flow worked, she invested the time to make it look good. Luna: That's a great iterative approach. Validate, then polish. Lucas: So the net result for Sarah: she's now billing about twenty percent more hours per month because she's not doing admin. Her revenue went from about 90K to 110K annually — not just from the time gain, but because she can take on more clients without feeling overwhelmed. And she's happier. She told me she actually looks forward to Mondays now. Luna: You love to hear that. And it's a reminder that tools are only part of the equation — it's about designing your business so you actually enjoy running it. Lucas: Yeah, and that's what this show is really about. If these conversations have moved your work forward in some small way, we're glad. 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. No ads, no sponsors — just people who find value here. Luna: It's a small group, but it keeps us independent. So if that's something you'd want to be part of, we'd love to have you. Lucas: Alright. Back to Sarah's story — one last detail that stuck with me. She said the biggest unexpected benefit was that clients now see her as more 'tech-forward.' She's a designer, but clients perceive her as having operational maturity. That's helped her land larger projects. Luna: Perception is reality. When you present a polished client experience, people assume you have a whole team behind you. Lucas: Exactly. So the no-code app didn't just save her time — it elevated her brand. And that's a double win that you don't get from just hiring a VA. Luna: So for anyone listening who's on the fence — maybe start by mapping out your most painful workflow this weekend. You might surprise yourself with what you can build. Lucas: Yeah. And if you do, let us know. We'd love to feature your story on a future episode.