Latest / Solopreneur Sessions with Fexingo: One-Person Businesses, Freelancing, and Independent Work / How a Solopreneur Automated Client Onboarding with Zero-Code Tools
Transcript
- Lucas: You know that moment when a new client says 'I'm ready to start' and your stomach drops because you know what comes next — the back and forth, the forms, the confusion about what they actually need to send you? Luna: Oh, I know it well. For me it used to be a 12-step email chain that took about two hours per client. And I only had maybe five new clients a month, so it wasn't a crisis. But still. Lucas: Right. And if you're a solopreneur, that time is literally your revenue. So today I want to talk about a consultant named Jenna Mason — she runs a niche marketing consulting practice for B2B SaaS companies — and how she rebuilt her entire client onboarding process using exactly three tools, none of which required her to write a single line of code. Luna: This is going to be very personal for me. I'm taking notes. Lucas: Good. So Jenna's old process — and she shared this in a Twitter thread that I think is still worth reading — went something like this. Someone books a discovery call via her website. She has the call, sends a proposal manually as a PDF. If they say yes, she sends a contract via DocuSign. Then she sends an invoice. Then she sends a welcome email with a questionnaire. Then she sends a calendar link for the kickoff call. Then she sends a reminder. Then she logs everything in her CRM. That's about eight separate touchpoints, most of them manual, and she said the average time from 'yes' to 'first real work' was eleven days. Luna: Eleven days. And during those eleven days, the client's excitement cools. They start second-guessing. Meanwhile, Jenna is spending probably four hours total just managing logistics. Lucas: Exactly. So she set a goal: get that down to under 48 hours, and reduce her own time spent to under 30 minutes. And she did it with a combination of Calendly, Notion, and Zapier. No custom development, no API calls, nothing that would break if a tool updated. Luna: I want the specifics. What was the first thing she changed? Lucas: The discovery call booking itself. She was using Calendly already, but only for the initial call. She added a second event type called 'Client Kickoff' that would only appear after a specific trigger. The trigger? She set up a Zapier zap that watches for a new row in a Google Sheet — a sheet she uses as her deal tracker. When she moves a deal to 'Closed Won' in that sheet, Zapier automatically creates a Calendly invite link for the kickoff call and sends it to the client via email. The client doesn't see the link until they've paid. Luna: So the payment is the gate. That's smart. Did she tie Stripe into it? Lucas: Yes. Another Zapier zap watches for successful Stripe payments. When a payment comes in, it creates a new client record in a Notion database she built — a simple template with fields for name, email, project scope, and status. Then a second zap takes that Notion record and generates a personalized welcome page using a tool called Softr — which is essentially a front-end builder that connects to Notion as a database. The client gets a link to a page that says 'Welcome, — here's your account setup checklist.' And it's all automated. Luna: Wait — so the client goes from paying their invoice to having a personalized portal? Without Jenna touching anything? Lucas: Correct. Jenna said the whole sequence — from Stripe charge to welcome page live — takes about 90 seconds. And the client gets an email with the link, plus the Calendly invite for the kickoff call already pre-scheduled for three business days later. She also added an automated reminder sequence: 48 hours before the kickoff, an email asks them to complete a brief questionnaire in Notion. 24 hours before, another reminder. If they haven't filled it out four hours before, she gets a notification. Luna: That's the part I'd worry about — the questionnaire. Because if it's automated, you might get low-quality answers. Did she see that? Lucas: She did. Initially she had a 12-question form. Completion rate was about 40 percent. So she cut it to four questions — all multiple choice, with one open-ended 'anything else?' field. Completion rate jumped to 85 percent. And she said the answers were actually better, because clients weren't fatigued. They gave thoughtful responses to the four key things she actually needed. Luna: So the automation forced her to be disciplined about what she really needed to know upfront. That's a lesson in itself. Lucas: Absolutely. She said the biggest insight from the whole project wasn't technical — it was realizing that most of her onboarding steps existed because 'that's how we've always done it.' She was asking for information she never used. Once she stripped it down to the essentials, the automation became trivial. Luna: What about the contract? Did she automate that too? Lucas: Yes. She uses a Zapier integration with DocuSign that creates an envelope from a template when a deal moves to 'Closed Won' in her sheet. The contract auto-fills with the client name, project fee, and start date from the sheet. She reviews it once — takes about two minutes — then hits send. She said previously she was manually copying and pasting into Word, then converting to PDF, then uploading. That alone saved her 20 minutes per client. Luna: I'm going to guess her close rate went up too, because the friction disappeared. Lucas: It did. She tracked it. Before the automation, her close rate — from proposal sent to signed contract — was about 62 percent. After, it went to 81 percent. Her theory is that the faster she moved, the less time the client had to get cold feet or get distracted by another vendor. The whole process from 'yes' to signed contract went from an average of four days to about six hours. Luna: Six hours. That's insane. And she's one person. Lucas: One person, no developer, no VA. The total setup time for the entire system — building the Notion templates, connecting the zaps, testing — she said it took her about eight hours spread over a weekend. And she saved roughly two hours per client after that. For her, that's about 10 hours a month. Which she reinvested into actually doing the work. Luna: I want to talk about what she didn't automate. Because I think that's just as instructive. Lucas: Great point. She kept one thing deliberately manual: the welcome gift. Every new client gets a handwritten thank-you note and a small book — usually something related to their industry. She says that's the moment where the relationship shifts from transactional to personal. And she's right. Automation handles the logistics, but the human touch at the right moment is what builds loyalty. Luna: So the rule might be: automate the stuff the client never wants to think about, but show up personally for the stuff they'll remember. Lucas: Exactly. Jenna also said she tested the entire workflow with a spreadsheet before she ever connected a single zap. She literally walked through the steps manually, timing each one, identifying where the delays were. Only then did she automate. She warns against automating a process that's broken — you just get broken results faster. Luna: That's a good caution. I think a lot of solopreneurs hear 'automate' and immediately think of fancy tools, but the real work is mapping out what actually needs to happen. Lucas: Right. And the tools she used are all free or low-cost. Calendly's free plan covers the basics. Notion's personal plan is free. Zapier's free tier gives you 100 tasks a month — for someone with five clients a month, that's plenty. So the barrier to entry is basically zero. Luna: What about the client experience? Did she survey them? Lucas: She did. She sent a quick three-question survey after the kickoff call. The net promoter score from clients who went through the automated onboarding was 92, compared to 74 before. Clients specifically mentioned the speed and the fact that everything was in one place as reasons they felt more confident. Luna: That's a huge jump. And I bet referrals went up too, because happy clients talk. Lucas: They did. She said referrals increased about 30 percent in the six months after she implemented the system. She attributes that partly to the speed — clients were more likely to recommend someone who made starting easy. Luna: So the takeaway for a solopreneur listening today: pick one bottleneck in your client flow, map it out on paper, cut the steps that don't add value, then automate the rest. Start with something small — like the payment to welcome page sequence — and build from there. Lucas: Exactly. And if you want to see the exact Notion template Jenna used, she actually shared it for free on her Twitter. I'll link it in the show notes. But honestly, you could recreate it from what we just described in under an hour. Luna: I might do that this afternoon. My current onboarding is a mess. Lucas: Before we wrap, one quick thing. If this episode — or any episode of Solopreneur Sessions — has helped you streamline something in your business, we wanted to mention that a small group of listeners already supports the show monthly through buy me a coffee dot com slash fexingo. That support is what keeps the show ad-free and allows us to keep digging into these specific, actionable stories. No pressure at all — just wanted you to know that if you find value here, that's the way to keep it going. Luna: Yeah, it genuinely makes a difference. We don't run ads, so listener support is how this stays sustainable. And we're grateful for everyone who's chipped in. Lucas: Alright. So to tie it back: Jenna's story is a reminder that as a solopreneur, your time is your scarcest resource. Every hour you spend on logistics is an hour you're not serving clients, building your offer, or — honestly — resting. Automation isn't about replacing yourself; it's about freeing yourself up for the work that actually matters. Luna: And maybe writing a few handwritten notes along the way. Lucas: Exactly. That's it for this episode of Solopreneur Sessions. We'll be back next week with another specific story. Until then.