Kira: Someone DMed me in the Slack community on Friday. She said — and I'm paraphrasing — "Kira, I have four Notion databases, a Trello board, two Google Docs with pricing ideas, a Make scenario that's half-built, and a Sheets tab I haven't opened since March. I'm flying to Lisbon next week for the summer. How do I turn all of this into something I can actually run?"
Santi: Four Notion databases.
Kira: Four. And a Trello board.
Santi: For one business.
Kira: For one business that's doing — she told me — about thirty-eight hundred MRR. Which is not nothing. She has clients. She has revenue. She just doesn't have a plan she can look at on her phone and know whether she's winning or losing.
Santi: I was that person. Two years ago, almost exactly. I had revenue spread across two offers, costs I was tracking in my head, and zero idea what my actual margins were. I was in Gili Air, running the whole thing from a hammock with a Bluetooth keyboard, feeling productive — and I was bleeding money I couldn't see.
Kira: Because you didn't have the numbers in one place.
Santi: I didn't have the numbers in one place. I didn't have a review cadence. I didn't have a single page that said "here's the offer, here's what it costs to deliver, here's what I need to survive, and here's what I'm checking every Monday." I had vibes. And vibes don't survive a visa run.
Kira: When this episode ends, you'll have a filled-in one-page operating plan — offer, pricing, margins, acquisition, QA, moats, and ninety-day milestones — on a single Notion page you can pull up on your phone between flights. Plus a Google Sheet that tracks your KPIs and runway so every Monday you spend twelve minutes knowing exactly where you stand.
Santi: One page. One sheet. One ninety-day window. That's the whole system. And we're going to walk through it with real numbers for three different AI business models so you can see what yours should look like before you fill it in.
Kira: So why one page? Why not a proper business plan, a pitch deck, a strategy doc?
Santi: Because you're going to look at this on your phone. In a café. With wifi that drops every nine minutes. If it doesn't fit on one screen, you won't check it. And if you don't check it, it's decoration.
Kira: I had a twelve-page ops doc for my agency last year. Beautifully formatted. Color-coded sections. I opened it exactly twice after I wrote it.
Santi: Twice is generous.
Kira: The second time was to show someone how organized I was. I never actually used it to make a decision. And this is the important part — the one-pager isn't about simplifying your business. It's about forcing yourself to make the tradeoffs you've been avoiding. When you only have one page, you can't list six offers. You pick one. You can't say "my ICP is anyone who needs AI." You name the person.
Santi: Right. So let's walk through the fields. And I want to do this with real numbers, because the fields are useless without defaults.
Kira: Start at the top.
Santi: Offer and ICP. One line for each. Your offer is the outcome you deliver, not the tools you use. Not "I build Make automations." It's "I run your content ops — eight SEO articles, twelve social repurposes, one email brief a month — and you don't think about it."
Kira: And the ICP is specific enough that you could find ten of them on LinkedIn in five minutes. Title, company size, the pain they wake up with.
Santi: Next block — pricing and margin. And this is where most nomads go blank, because they've never actually calculated their delivery cost. They picked a price that felt right and hoped the math worked out.
Kira: The "feels right" pricing method.
Santi: The "feels right" method. Which is how you end up charging five thousand a month for content ops and spending forty-two hundred to deliver it. That's a sixteen percent margin. You're working for tips.
Kira: So what's the target?
Santi: For an AI-assisted agency — and this comes from Parakeeto and the Agency Management Institute — you want fifty to sixty-five percent delivery margin. That means if you charge five thousand, your delivery cost — labor, AI API spend, tools, contingency — needs to stay under twenty-five hundred. For a pure self-serve SaaS, you're targeting seventy-five to eighty-five percent gross margin because your costs are mostly compute and hosting.
Kira: Okay but what about the person who's doing both? Half agency, half product?
Santi: Then you track them separately on the same page. Two lines. Two margin targets. Because blending them hides the thing that's killing you.
Kira: Yeah. I blended mine for six months and couldn't figure out why my agency felt profitable but my bank account didn't grow. The SaaS was eating the margin.
Santi: And that connects to the next field — the one David Skok has been hammering since his SaaS Metrics two-point-oh framework. LTV to CAC ratio. You want that above three. And your CAC payback — the number of months it takes to earn back what you spent to acquire a customer — needs to be under twelve.
Kira: Wait — slow down. For someone who's never calculated this. LTV is what?
Santi: Lifetime value. Your average gross profit per customer per month, times how many months they stay. So if you make twenty-one hundred in gross profit per client per month and they stay six months, your LTV is twelve thousand six hundred. If you spent eighteen hundred to acquire that client, your LTV to CAC is seven. That's healthy. That's very healthy.
Kira: And the payback?
Santi: Eighteen hundred divided by twenty-one hundred. Point-eight-six months. Less than a month to earn back your acquisition cost. That's the content ops example — five thousand a month retainer, twenty-nine hundred in delivery costs, eighteen hundred blended CAC.
Kira: Under a month. That's the kind of number that lets you spend on growth without panicking.
Santi: Exactly. And you're checking this every Monday. Not quarterly. Not when you feel like it. Every Monday, twelve minutes, on your phone.
Kira: Okay — acquisition model. This is where I see people write "LinkedIn and referrals" and call it done.
Santi: Which tells you nothing. The field needs your primary channel, your secondary channel, your expected CAC per channel, and your conversion rates — lead to qualified, qualified to won. Because if you don't know those numbers, you can't tell whether a channel is working or just busy.
Kira: And then there's the self-serve piece, which — I'll be honest — I resisted for a long time because I run a service business. I thought self-serve was a product thing.
Santi: What changed your mind?
Kira: A template. I put a Notion template on my website — "paste your topic, get a content brief outline in five minutes." No call. No form. Just... value. And people who used it booked calls at three times the rate of people who came through my normal funnel. Because they'd already seen what working with me felt like.
Santi: That's the PLG playbook applied to services. OpenView has been pushing this — time to value under five minutes. Even if you sell a fifty-five hundred dollar a month retainer, you can give someone a taste in five minutes with a template, a demo, a calculator. Something they can touch.
Kira: And you put that link on the one-pager so you never forget it exists. Because the self-serve asset is doing sales while you're asleep.
Santi: Next field — and this one's non-negotiable — the QA wall.
Kira: We did a whole episode on this. Episode fifteen. Three layers.
Santi: Three layers. LLM-as-judge on every single job. Weekly golden-set replay to catch drift. And five to ten percent human sampling on high-impact work. The old way — manual QA — covers two to five percent of interactions. EdgeTier and MaxContact both confirmed this. That means ninety-five percent of your output is unchecked.
Kira: And when you're traveling, you're even less likely to catch problems manually. I was in Guatemala when one of my content workflows started hallucinating client names into blog posts. Took me three days to notice because I was offline dealing with an internet outage.
Santi: Client names.
Kira: Real client names. In the wrong blog posts. If I'd had the LLM judge running, it would've flagged that in the first batch.
Santi: So on the one-pager, you write three things. Is the LLM judge on? What day is your golden-set replay? And what's your human sampling percentage? That's it. Those three lines protect your margins and your reputation.
Kira: Let's make this concrete with a different model. Imagine you're not doing content ops — you're doing fractional RevOps. HubSpot hygiene, lead routing, lifecycle stages, renewal risk flags. Fifteen to twenty-five senior hours a month.
Santi: Pricing on that — and OpsEthic published a good breakdown — runs four to seven thousand a month with a one-time audit fee. Call it fifty-five hundred a month, three-month minimum, thirty-five hundred for the onboarding audit.
Kira: Your delivery cost is the senior operator — twenty to thirty hours at their rate — plus tooling. Maybe twenty-four hundred total. So your margin is—
Santi: Fifty-two to fifty-eight percent. Right in the target range. And your ninety-day milestones are different from content ops. Month one, routing and lifecycle implemented. Month two, pipeline hygiene SLA is live. Month three, you've got a renewal risk model and your net revenue retention is at or above a hundred percent.
Kira: Same one-pager. Different numbers. Same structure.
Santi: Now the third model — support automations. This one's interesting because the pricing is usage-based. You're deploying an AI agent — Intercom Fin, for example — and Fin charges ninety-nine cents per confirmed resolution. You pass that through to the client.
Kira: So the client sees exactly what the AI costs them.
Santi: Exactly. Your enablement fee is three thousand a month plus a three thousand setup. Your costs are operator time, infrastructure, QA hours. Margin lands fifty to sixty percent. But the KPI that matters here is autonomous resolution rate — what percentage of inbound tickets does the AI handle without a human?
Kira: And what's realistic?
Santi: It depends. Intercom's published numbers range from about forty-one percent average early on to sixty-six, seventy-three percent in more recent claims. But those numbers depend heavily on documentation quality and how well you've configured intent coverage. So the honest answer is — start with a target of fifty percent on your covered intents, validate it against a golden set, and expand from there.
Kira: Don't promise seventy percent on day one.
Santi: Don't promise seventy percent on day one. Promise the QA wall that proves whatever number you hit is real.
Kira: Okay — last two fields on the one-pager, and these are the ones that make this a nomad plan instead of just a business plan. The Lisbon Test and Visa Run Revenue.
Santi: The Lisbon Test is five questions. Can I review KPIs on my phone in under three minutes? Do my critical delivery steps have an offline fallback? Are all handoffs async with an owner, a due time, and a definition of done? Is my tool spend capped as a percentage of MRR with alerts on spikes? And does one Notion page link everything I need to run the week?
Kira: If any of those fail, you add a mitigation before you move on. Because the plan that works in your apartment with fiber internet is not the plan that works in a café in Alfama when the wifi drops.
Santi: And Visa Run Revenue — this is your survival number. Your base living cost, plus coworking, plus tools, plus your visa run cost amortized monthly, times a twenty percent buffer. If you're in the Schengen zone without a residency permit, you're on the ninety-one-eighty rule — ninety days in any rolling one-eighty-day period. That means flights, temporary housing, the whole disruption. Budget it or it surprises you.
Kira: I know people who've had to leave a country mid-project because they didn't track their days. That's not a business problem — that's a survival problem.
Santi: And it goes on the one-pager. Your comfort MRR. The date of your next visa check. Because if your revenue dips below that number, everything else on the page is academic.
Kira: Okay but I want to push on something. Because I can hear the objection already — "my business is too complex for one page. I have bespoke deliverables. My sales cycle is three months. A rigid Monday cadence doesn't fit how I work."
Santi: And... honestly, there's some truth to that.
Kira: There is.
Santi: If your deals take three months to close, tracking CAC payback weekly is noise. You'd track it by cohort and review it bi-weekly or monthly. If your scopes are genuinely bespoke, you can't productize every deliverable — but you can standardize the QA and the handoffs.
Kira: And the self-serve piece — the time-to-value-under-five-minutes thing — that's harder for a service business than a product. I'll admit that. My Notion template works, but it took me three iterations to make it feel like a real preview instead of a gimmick.
Santi: So the answer isn't "the one-pager is perfect for everyone." The answer is — the one-pager is a forcing function. It makes you write down the tradeoffs you've been carrying in your head. And then you adapt the cadence. Maybe your Monday review is bi-weekly. Maybe your self-serve is a Loom video instead of a template. The structure flexes. The discipline doesn't.
Kira: The discipline doesn't. That's the line. Because the alternative is what that woman in my Slack described — four Notion databases, a Trello board, and no idea whether she's winning. The one-pager doesn't oversimplify. It forces you to stop hiding behind complexity.
Santi: So that woman in your Slack — the one with four Notion databases and a flight to Lisbon next week. What would you tell her now?
Kira: I'd tell her to block sixty minutes tonight. Open the Nomad AI Operator One-Pager Kit — it's on the Resources page — duplicate the Notion canvas, and fill every bracketed field. Don't research. Don't optimize. Just write down what's true right now. The offer she's actually selling. The price she's actually charging. The costs she can actually name. And then open the Google Sheet, plug in her living costs and her visa run math, and see what her comfort MRR is. That number alone will change how she thinks about the next ninety days.
Santi: And then Monday — wherever she is — twelve minutes. Phone. KPI tab. Is she above or below comfort MRR? What's one lever she can move by Friday? That's the whole review. That's the whole discipline. Ninety days from now she'll either have a business she can see clearly or she'll still be staring at four Notion databases wondering where the money went.
Kira: If you fill yours out this week, post it in the community. We're doing live teardowns on Wednesday's office hours — we'll look at your numbers, pressure-test your margins, and run the Lisbon Test on your stack.
Santi: One page. One sheet. Ninety days. Go fill it in.
Kira: See you Wednesday.