Jordan: I got a DM last Tuesday that I want to read to you — because I think this person is describing your week. "Jordan, I just spent four hours writing a proposal for a two-workflow automation. Four hours. I scoped it from scratch, Googled what other people charge, wrote custom SLA language I half-understood, and sent it over feeling like I'd underbid. The client came back and asked for a third workflow. I had to re-scope the whole thing. Another two hours. I'm doing this for every single lead and I'm losing money before the project even starts."
Jordan: I read that and I just... yeah. I've been there. I spent my first eight months writing bespoke proposals for every project. Every single one was a blank page. New scope doc, new pricing math, new SLA section copy-pasted from some contract template I found online. And every time the client asked for something outside the original scope, I had no language to point to. No boundary. Just a conversation where I either said yes and ate the margin, or said no and felt like I was being difficult.
Jordan: The fix is not getting faster at writing proposals. The fix is stopping. You need a menu. Three tiers, two add-ons, one hard scope gate — documented in a single page you can pull up on any sales call and price the project in minutes instead of hours. I call it an Offer Catalog. And once you have one, the proposal problem disappears — because the proposal is the catalog.
Jordan: Here's what you'll have by the end of this episode. A three-tier productized services menu — Starter, Pro, and Enterprise — with specific caps on workflows, channels, interactions, and support windows pulled from nine real automation shops I studied this week. Two standardized add-ons that absorb scope expansion without reopening your base pricing. A red-and-yellow scope gate that tells you in sixty seconds whether a lead fits a tier or needs a custom conversation. And the exact Notion Offer Catalog I use to price projects on the call — not after it. This is Headcount Zero. I'm Jordan. Let's build it.
Jordan: So why does every project feel like starting from zero? Because it is. When you don't have a menu, every lead triggers the same cycle — discovery call, custom scope, custom pricing, custom SLA language, custom proposal doc. You're doing product design on every deal. And the brutal part is that most of your projects actually look the same. You're building one to three workflows. You're connecting one to three channels. You're supporting the client for a few weeks after launch. The variation between projects is way smaller than the variation between your proposals.
Jordan: I pulled up my last twelve projects. Nine of them — nine — fit into three buckets. One-workflow, single-channel builds with a short support window. Multi-workflow, multi-channel builds with a longer support window and some iteration. And then the big custom stuff — multi-system orchestration, regulated data, twenty-four-seven on-call. Three buckets. But I'd written twelve completely different proposals. Twelve different SLA sections. Twelve different pricing justifications. That's not a sales process. That's a creative writing exercise.
Jordan: And I was charging for the automation, not for the proposal writing.
Jordan: So here's the structure. Three tiers. Two add-ons. One scope gate. I call it the three-two-one portfolio, and I'm going to walk through each piece using real boundary language from nine automation shops I studied — Automagic Developer, WillWay Media, Polaris AI Studio, Mister Khan, TaskOps, Zadix, Cognex, QNTX AI Ops, and NextStep Logic. Some of these are confirmed solo operators. Others are small teams. But the patterns are remarkably consistent.
Jordan: Tier one is your Starter. This is the entry point — one workflow, one channel, capped interactions, short support window. Automagic Developer does exactly this. Their Starter automates one simple workflow with a two-week support window. WillWay Media caps their entry tier at five hundred interactions per month and two knowledge base sources. Polaris AI Studio limits Starter to a single-channel chatbot — chat only, no email, no SMS.
Jordan: The key insight is what you're constraining. It's not just price. It's four things — workflows, channels, interactions, and support duration. Those four caps make the tier predictable for you and clear for the client. One workflow. One channel. Five hundred interactions a month. Two weeks of post-launch break-fix support. That's it. If they need more, there's a tier for that.
Jordan: And the pricing? You publish it. Polaris charges eight hundred a month plus an eight-hundred-dollar setup fee for Starter. QNTX starts their AI Assistant at a hundred and ninety-nine dollars. The range is wide, but the point is the same — the number is on the page before the call happens. Michael Zipursky at Consulting Success has been arguing this for years: published pricing compresses sales cycles because the client self-qualifies before they ever talk to you.
Jordan: Tier two is Pro. This is where most of your revenue lives. Up to three workflows. Multi-channel — pick two or three from chat, email, SMS, voice, web form. Higher interaction caps. And a longer support window — four weeks instead of two, with a weekly iteration slot built in.
Jordan: WillWay Media's Pro tier is a good model here. Up to three agents, unlimited interactions, Make or n8n pipelines, ten-plus knowledge base sources, and four-hour priority support. Automagic Developer's Pro adds a dashboard and four-week support at twelve ninety-nine. Mister Khan — who's a confirmed solo operator — runs a Professional tier at nineteen ninety-five a month with two active tasks, twenty-four-hour response time, and a private Slack channel.
Jordan: That concurrency limit is something I didn't appreciate until I was juggling four Pro clients at once. Mister Khan caps active tasks at two for Professional. That sounds restrictive, but it's actually a margin protector. When you're solo, every task you're actively working on competes with every other task. If you don't cap concurrency, you end up context-switching between six projects and delivering all of them slowly. One active task at Starter. Two at Pro. That's not a limitation you're imposing on the client — it's a promise that their work gets focused attention.
Jordan: The SLA shift matters too. Starter gets forty-eight-hour email support. Pro gets four-hour priority response during business hours. That's not just a faster reply — it's a different support channel. Email at Starter. Slack or Teams at Pro. The channel upgrade is part of the value, and it's part of the boundary.
Jordan: Tier three is Enterprise, and this is where you stop publishing fixed prices. This tier exists for two reasons. First, to catch the complex work that genuinely needs custom scoping — multi-system orchestration, regulated data, custom API development. Second, to give you a place to send leads that don't fit your menu without turning them away.
Jordan: Zadix does this well. Their Enterprise tier includes a full SLA with incident response windows, ninety-nine point five percent uptime, defined maintenance windows, and specified support channels. But — and this is critical — they only promise uptime because they host the runtime. If you don't host the client's infrastructure end to end, do not promise uptime. Promise response time and restore time instead. That's a response-restore SLO, not an uptime SLA. The distinction matters because an uptime promise you can't control is a liability, not a feature.
Jordan: WillWay Media's top tier commits to ninety-nine point nine percent uptime with one-hour twenty-four-seven support. But again — they host everything. If you're building automations that run on the client's Make account or the client's n8n instance, you don't control the runtime. You control your response. So your Enterprise SLA says "one-hour response, twenty-four-seven, via pager" — not "ninety-nine point nine percent uptime."
Jordan: Now — the two add-ons. These exist to absorb legitimate scope expansion without reopening your base tier. The pattern I see across almost every menu I studied is the same two things: an additional workflow, and a support upgrade.
Jordan: Add-on one — Additional Workflow. Client's on Pro with three workflows and they need a fourth? That's not a re-scope. That's a line item. One additional workflow, fixed setup fee, plus a monthly hosting fee if you're running it. Zadix sells extra workflows, HA/DR, and region pinning as modular add-ons. You don't need all of those. You need one: plus-one workflow. Fixed price. Clear delivery timeline. Done.
Jordan: Add-on two — Priority Response SLA upgrade. Client's on Starter with forty-eight-hour email support and they want faster response? Don't move them to Pro. Sell them the SLA upgrade. Four-hour business-hours response for a monthly fee. Or one-hour twenty-four-seven if they need it — but only if you have paging and monitoring set up first. Mister Khan's tier structure essentially does this — the jump from forty-eight-hour to twenty-four-hour response is baked into the tier price, but you can unbundle it as a standalone add-on.
Jordan: Two add-ons. That's it. Not five. Not a custom menu of twelve optional extras. Two. Because every add-on you offer is a decision the client has to make, and every decision slows the sale.
Jordan: The scope gate is the piece that makes the whole system work on a sales call. It's a simple yellow-and-red flag system. Yellow flags are things you can solve with an add-on or by bumping to Pro. One extra workflow beyond the tier cap — yellow. An additional channel — yellow. More knowledge base sources — yellow. These are expansion, not complexity.
Jordan: Red flags trigger Enterprise. Multi-system orchestration across three or more core systems — red. Net-new custom API development — red. Twenty-four-seven on-call without observability in place — red. Regulated data — HIPAA, PCI, FERPA — red. And the biggest red flag of all: "unlimited requests" or undefined success criteria. If a client can't tell you what done looks like, that's not a Starter project. That's not even a Pro project. That's a discovery engagement.
Jordan: I keep the scope gate as a toggle list in my Notion catalog. On a call, I'm literally scanning the list while the client describes their project. Yellow, yellow, green, green — okay, that's Pro plus one add-on. Red — okay, let's talk about a custom scope. Takes about sixty seconds. That's the whole qualification.
Jordan: Now — I want to be honest about where this breaks. Because the obvious objection is: what about the client who doesn't fit any tier? The one with a genuinely unique workflow, volatile API costs, or a use case you've never seen before?
Jordan: That's real. And the AsyncForge guide on productized development services makes this point directly — rigid productization can repel higher-complexity buyers and misprice variable costs. If your LLM token spend swings wildly based on the client's usage patterns, a fixed monthly fee might eat your margin on month three even if it was profitable on month one.
Jordan: The answer is not to abandon the menu. It's to build the escape hatch into the menu. That's what the Enterprise tier is. That's what the red scope gate is for. When a lead trips a red flag, you don't force them into a tier that doesn't fit. You route them to a custom conversation with a discovery fee attached. QNTX AI Ops does this — they charge ninety-nine dollars for an AI Workflow Audit before any build begins. That audit is the gate between "this fits a tier" and "this needs custom scoping."
Jordan: And for volatile costs — interaction caps are your friend. WillWay caps interactions at five hundred a month on Starter. Cognex does a thousand on their entry tier. You're not eating unlimited token spend. You're capping it, publishing the cap, and selling overages or tier upgrades when the client exceeds it. The menu doesn't pretend every project is simple. It just makes the simple projects fast and routes the complex ones to a conversation that starts with a paid discovery.
Jordan: Let me walk you through how this actually works on a call. Client says: "I need a chatbot for our support page. One channel — web chat. Maybe five hundred conversations a month. We use Zendesk and want tickets created automatically."
Jordan: I'm scanning the scope gate. One workflow. One channel. Five hundred interactions. Native connector to Zendesk — no custom API. All green. That's Starter. I say: "That's our Starter tier. Setup fee is X, monthly is Y, and you get two weeks of post-launch support. If you need a second workflow later — say, an email intake — that's an add-on at a fixed price. Want me to send the service card?"
Jordan: Sixty seconds. No proposal to write. No scope doc to draft. The service card is a one-pager generated from the catalog — outcome, caps, SLA, price, stack, and a button. I send it before the call ends.
Jordan: Now — different client. "We need to connect our CRM, our invoicing system, and our project management tool. Custom API to a legacy ERP. HIPAA-compliant data handling. And we want twenty-four-seven support."
Jordan: I'm scanning the scope gate. Multi-system orchestration across three-plus systems — red. Custom API to a legacy system without SDK — red. HIPAA — red. Three red flags. That's Enterprise. I say: "That's a custom engagement. We start with a paid discovery — takes about a week — and I'll scope the build, the SLA, and the run cost from there. Discovery fee is X." Different conversation. Different pace. But I knew which conversation to have in under a minute.
Jordan: So — remember that DM I read at the top? Four hours writing a proposal for a two-workflow build. Another two hours when the client asked for a third workflow. Six hours of unpaid product design on a single deal. With the three-two-one portfolio, that same deal takes sixty seconds to qualify, sixty seconds to price, and one service card to send. The two-workflow version is Starter. The third workflow is an add-on. The SLA is a toggle. The proposal is the catalog.
Jordan: Constraints don't limit what you can sell. They limit how long it takes to sell it. And for a solo operator, that's the same thing as margin.
Jordan: If you want the exact Offer Catalog I walked through today — three tiers, two add-ons, the red-and-yellow scope gate, the SLA toggles, the service card generator — it's on the Resources page. It's a Notion template. Duplicate it, fill in your brackets, and you can be pricing on calls by the end of the week.
Jordan: One thing to do this week. Just one. Open a blank Notion page and write down the three tiers. Name them. Put one cap on each — workflows, channels, interactions, whatever makes sense for your work. Don't try to finish the whole catalog. Just name the tiers and set one boundary per tier. That's the foundation. Everything else builds from there.
Jordan: I'm Jordan. This is Headcount Zero. Go build something.