The Un-SaaS Ch. 6 — The Un-SaaS Identity

Chapter 6 of 26

This is a chapter from The Un-SaaS: A Toll Stack Engineer's Handbook. Each Friday, we're publishing a chapter as a bonus for our readers.

I want to tell you about the best developer I’ve ever worked with.

She built a SaaS. Beautiful architecture. Clean code. CI/CD pipeline that would make a platform engineer weep. The thing did exactly what it was supposed to do — project management for construction contractors. She built it in eight months, solo, nights and weekends after her day job.

She launched it with a $29/month price point and a well-written landing page. In the first ninety days, she acquired eleven paying customers. Two of them churned in month two. Another three churned by month four. By month six, she had eight customers paying $29 each — $232 a month before Stripe fees. Her hosting cost $47 a month.

She kept building features. She added invoicing. She added subcontractor management. She added a Gantt chart because three customers asked for it. The codebase grew. The support tickets grew. The monthly revenue stayed at $232 because the three features she added satisfied the eight existing customers but didn’t acquire new ones.

After fourteen months, she shut it down. Not because the product was bad — it was genuinely good software. Not because the market didn’t exist — construction project management is a massive space. She shut it down because the distribution problem was unsolvable at the scale she could operate.

She could build software. She couldn’t build an audience. She could write code. She couldn’t write content that ranked on Google against ClickUp and Monday and Asana and the forty-seven other tools already occupying page one. She could architect a database. She couldn’t architect a go-to-market strategy that produced forty new trials a month instead of four.

The software was excellent. The business was dead.

A developer at two desks. One has a beautiful SaaS with no users. The other has a simple landing page earning money.

The SaaS Tax

Here’s what the SaaS model actually costs an engineer who tries to build one solo:

Creation risk. You spend six to eighteen months building before you know if anyone wants it. The market gives you no signal until the thing is live, and by then you’ve already invested thousands of hours.

Distribution cost. The product needs traffic. SEO takes twelve to eighteen months to produce meaningful results. Paid ads require budget and expertise you don’t have. Content marketing requires consistency over years. Cold outreach is a full-time job masquerading as a tactic.

Support burden. Every customer generates tickets. The tickets don’t scale with revenue — they scale with customer count, which means your worst-performing customers consume the most support time.

Feature treadmill. Customers request features. Competitors ship features. The product must grow to retain existing customers and attract new ones. You are now a product manager, a support agent, a marketer, and a developer — all at once, all solo.

Churn. SaaS customers leave. The median monthly churn rate for small SaaS products is 5-7%, which means you’re replacing half your customer base every year just to stay flat.

I’m not saying SaaS is bad. I’m saying SaaS is a specific bet — creation risk up front, distribution cost throughout, and a support burden that grows with success. For a well-funded team with dedicated roles, it’s a proven model. For a solo engineer working ten to fifteen hours a week? It’s a bet where the odds are structurally against you.

The developer I described above didn’t fail because she lacked skill. She failed because the SaaS model punishes single-player execution. The skills she had — architecture, infrastructure, automation, systems thinking — are extraordinary. The model she applied them to was wrong.

The Permission Tax

The SaaS Tax is the cost of building your own product. But there’s a second invisible tax that hits operators who escape SaaS but don’t fully own their toll positions.

Every position that depends on someone else’s permission bleeds value across three dimensions:

Time bleed. Hours per month spent seeking approval, coordinating schedules, waiting for responses, and re-earning access. A partner who controls your send schedule costs you 8-12 hours per month in coordination alone — hours that should be spent on the experiment log.

Money leakage. Revenue lost to restricted pricing, capped commission rates, and deals you couldn’t negotiate from a position of strength. The standard affiliate rate is what you get when you don’t have leverage. The strategic rate — 30-50% higher — is what you get when you own the distribution.

Freedom constraints. Strategic decisions blocked by third parties. You can’t A/B test a subject line if the partner approves all copy. You can’t pivot to a higher-converting merchant if your agreement restricts competitive offers. Every blocked experiment is a compound-interest payment you’ll never collect.

An operator earning $8,000/month from a partner-attached position who calculates their permission tax honestly might find it at $2,400/month: $1,200 in time bleed, $800 in rate compression, $400 in blocked experiments. The position isn’t producing $8,000. It’s producing $5,600.

The three dimensions compound. Time spent seeking permission is time not spent optimizing. Money lost to restricted pricing reduces the budget for testing. Freedom constraints prevent the experiments that would reveal higher-performing strategies. The tax isn’t flat — it’s a drag coefficient on growth.

This is why the chapter on position types — demand-capture assets, landlord tolls, vendor indexes — matters. Each one reduces the permission tax by moving the operator closer to grantor status. The SaaS Tax punishes solo builders. The Permission Tax punishes operators who build inside someone else’s terms. The solution to both is the same: own more of the infrastructure.

What Transfers

Here’s the recognition moment this chapter exists to create.

If you’re a failed or educated SaaS founder — someone who tried building a product and discovered that distribution is the hard part — then you already have every skill the Toll Stack requires. You just need to apply those skills to someone else’s business instead of your own.

If you’ve ever thought “I’m great at building things but terrible at marketing them” — that’s not a weakness. That’s a job description. The Toll Stack model is specifically designed for someone who can build infrastructure but doesn’t want to build an audience. The creator handles distribution. You handle everything behind it.

Let me map it.

Infrastructure engineering → Building landing pages, email sequences, redirect layers, and analytics pipelines. The toll position’s technical stack is simpler than any SaaS you’ve built, but it uses the same skills: clean architecture, reliable deployment, monitoring, and version control.

Data engineering → Building the experiment log, the behavioral database, the cross-network intelligence system. You already know how to design schemas, write queries, and analyze behavioral data. The toll position just applies those skills to conversion data instead of product usage data.

Automation → Wiring AI agents to handle drafting, QA, triage, and routine optimization. If you’ve ever built a CI/CD pipeline, you know how to orchestrate automated workflows. The agent workforce is a CI/CD pipeline for conversion experiments.

Systems thinking → Designing portfolio architecture: diversification across partners and niches, concentration risk limits, compounding dynamics, and failure mode analysis. This is capacity planning applied to revenue streams instead of server clusters.

Integration → Connecting to partner systems via APIs, webhooks, and embed codes. You’ve wired Stripe, Twilio, SendGrid, and AWS services. The toll position wires Stripe Connect, email ESPs, landing page builders, and analytics tools. Same skill, different vendors.

Debugging → Diagnosing conversion problems is debugging with different metrics. Why did open rates drop by 12% this week? The same diagnostic process you’d use for a production latency spike applies: check the logs, isolate the variable, test the hypothesis, deploy the fix.

Metrics obsession → SaaS trained you to watch numbers that matter — MRR, churn rate, LTV, CAC. The toll position has its own dashboard: capture rate, conversion rate, revenue per subscriber, revenue per email sent. Different acronyms. Same discipline. The SaaS founder who compulsively checked Stripe every morning is the operator who compulsively checks the experiment log. The compulsion transfers. The metrics just change.

Funnel thinking → You already know that a thousand visitors don’t equal a thousand customers. You’ve designed onboarding flows, activation sequences, and retention hooks. A toll position funnel is structurally simpler — landing page to email capture to nurture sequence to purchase — but it rewards the same instinct: find the drop-off, diagnose it, fix it, measure the improvement. If you’ve ever stared at a SaaS onboarding funnel wondering why 60% of trial users never activate, you already have the skill. You know how to stare at a welcome sequence wondering why email three has a 40% drop in click-through rate.

Everything transfers. Nothing is wasted.

What You Leave Behind

Here’s what the Un-SaaS operator doesn’t do:

You don’t build a product. The product already exists — it’s the partner’s course, service, membership, or digital good. You’re not responsible for product-market fit, feature development, or customer satisfaction with the product itself.

You don’t create content on a calendar. The partner publishes videos every Tuesday. You don’t. The partner maintains a social media presence. You don’t. What you create is conversion content — landing pages and email sequences that turn traffic into revenue. You’ll write them once, optimize them over months, and never publish on a schedule.

This is closer to copywriting than content creation, but let’s not pretend it’s trivial. A good pre-sell page requires you to understand the partner’s niche well enough to write persuasively about it. You’ll need to consume their content — watch their videos, take their course if they have one, read their posts — until you can write in their voice and anticipate their audience’s objections. This isn’t a weekend of research. It’s an ongoing immersion that deepens every month the position runs.

AI collapses the drafting time dramatically. Feed it the partner’s transcripts and it produces voice-matched copy in minutes. But you still need the judgment to know which product recommendations are genuine, which angles will resonate, and which claims cross the line. That judgment comes from niche knowledge. No shortcut.

The honest framing: you’re not a content creator. You’re a conversion architect who needs to understand the creator’s world well enough to build persuasion infrastructure inside it.

You don’t handle customer support. The partner handles support for their product. You handle optimization of the infrastructure — which means your “support” load is reading dashboards and approving experiment results, not answering tickets.

You don’t manage a team. The AI agent workforce handles the operational load that used to require a small team. You manage agents, not people. Agents don’t have PTO, don’t have one-on-ones, and don’t quit.

You don’t chase feature requests. The toll position infrastructure is simple by design: landing pages, email sequences, analytics, and experiments. There’s no feature backlog because the “product” is the infrastructure, and the infrastructure’s improvement comes from experiments, not feature development.

There are also three SaaS habits that will actively sabotage you if you don’t leave them behind.

The recurring revenue addiction. SaaS trained you to worship MRR — the number that grows by $29 every time a customer signs up and shrinks by $29 every time one churns.

The toll position doesn’t produce MRR in the SaaS sense. It produces variable income that compounds through infrastructure improvement, not subscription growth. Month one might produce $400. Month four might produce $1,200. Month seven might produce $800 because a partner took a week off from publishing. The curve is upward but lumpy. If you’re checking for the smooth MRR graph every morning, you’ll panic at the lumpiness and miss the compounding underneath it.

The feature roadmap mentality. SaaS founders default to “what should I build next?” when revenue stalls. In a toll position, the answer to stalled revenue is almost never “build something new.” It’s “optimize what exists.” A found money audit — thirty minutes reviewing your conversion rates and product placements — routinely surfaces more revenue than a new feature ever could. The operator who keeps adding features to their landing page is thinking like a SaaS founder. The one who keeps testing subject lines on the existing sequence is thinking like a Toll Stack Engineer.

VC fundraising theater. This one is more subtle. SaaS culture glorifies fundraising as validation. The pitch deck. The demo day. The seed round. The series A. The toll position model needs zero external capital. Total infrastructure cost: $15 to $50 a month. The “round” is your first month’s commission, which you parlay into the second position. The only investor is you, and the only pitch deck is your experiment log.

The things you leave behind are exactly the things that made your SaaS fail. The creation risk. The distribution cost. The support burden. The feature treadmill. The churn.

What you keep is the part you’re actually good at: building reliable infrastructure, analyzing data, running experiments, and improving systems over time.

The Identity

In Chapter 4, I told you about three practitioners across seventy years — the mold maker, the matchmaker, the licensing strategist — who all ran the same model without sharing a vocabulary for it.

You’re the fourth practitioner. The Toll Stack Engineer.

The identity is specific. You are not a founder (you don’t create products). You are not a freelancer (you don’t bill for time). You are not an agency owner (you don’t hire people). You are not a content creator (you don’t publish on a schedule or build an audience). You are not an affiliate (you don’t drop links and hope).

You are an operator who installs small, indispensable revenue infrastructure inside other people’s businesses, runs it with AI agents, and collects a toll every time demand converts to revenue. Building inside someone else’s business sounds like renting. It’s not. You own the infrastructure, the intelligence, and the compounding layer. The creator owns the traffic. The split is clean, and both sides are better off because of it.

The “Un-SaaS” label isn’t cute branding. It’s a precise description. You use everything you learned building SaaS — the infrastructure skills, the data skills, the automation skills, the systems thinking — and you apply it to a model that doesn’t carry the SaaS tax. Same skills. Different game.

And unlike a SaaS founder, you don’t need to build a personal brand. The guru builds an audience — their income depends on attention. The operator builds a reputation with the right two hundred people. That’s it. One professional presence. One proof artifact — an anonymized case study or a published framework. Enough activity that you’re not a ghost. Total time investment: two to four hours a month after the initial setup. Your competitive advantage isn’t visibility. It’s the experiment log that nobody can see.

The developer I told you about at the top of this chapter? If she’d spent those fourteen months installing toll positions instead of building a SaaS, the math would look different. She’d have four to six positions producing $3,000 to $8,000 a month, a growing experiment log, a compounding email list, and zero support tickets.

Same engineer. Same hours. Same skills.

Different model. Different outcome.

What Monday Looks Like Now

At the end of the manifesto, I asked you to imagine Monday. Pick a niche. Identify three partners. Read the deployment chapter. Send one outreach message.

Now you have the frame to understand what that Monday actually is.

You’re not starting a company. You’re not launching a product. You’re not building an audience.

You’re doing what the mold maker did in 1957, what the matchmaker did in 1978, and what the licensing strategist did in 2010 — updated for 2026. You’re identifying existing demand that’s flowing through someone else’s business, building a small piece of infrastructure that captures and converts that demand more effectively, and collecting a toll on the lift.

The next five chapters teach you the mechanics. How to find the right partner, how to build the infrastructure for less than $15 a month, how to write landing pages and email sequences that convert. Also: how the money actually flows, and how the experiment log becomes your moat.

If Part I was “See It” and Part II was “Believe It” — Part III is “Learn It.”

Let’s go.

Next Friday: A scoring framework that separates real residual income from disguised labor.