Positioning, landing pages, tech stack valuation, and founder strategy Q&A

Executive overview

Indie founders face recurring decisions where the answer genuinely depends on context — but "it depends" is only useful when paired with a decision tree. This episode works through six listener questions, each with a structured framework rather than a generic answer.

The throughline: specificity beats vagueness — in positioning, in testing, and in evaluating exit risk.

Positioning against large incumbents

• Name a competitor only if the name is widely recognised in your market — unknown names send traffic to them, not credibility to you.
• Being the "anti-Salesforce" works because everyone already knows Salesforce's complaints: expensive, complex, annual contracts.
• Vague positioning ("tired of clunky solutions?") is a valid fallback when the competitor name doesn't carry weight.
• Comparison pages can draw cease-and-desist letters from large companies; few reach actual lawsuits, but the threat alone causes many founders to pull or alter the page.
• If you're honest and factual, legal exposure is low — but litigation defence costs money you don't have.
• General lean: name them if it helps, but weigh the liability risk case by case.

Evaluating H1 changes on your landing page

• Don't change your H1 frequently unless positioning is actively broken — frequent changes signal a lack of product-market fit, not optimisation discipline.
• Stable, growing companies rarely change their H1 dramatically within a three-month window.
• Split test headline changes only if you have enough traffic to reach significance; at 1,000–5,000 uniques/month, tests take too long to be reliable.
• Poor person's split test: compare trial signups over the previous 60 days vs the next 60 days after the change — imperfect, but the best available tool at low traffic volumes.
• Three rules: don't change it often; split test if traffic allows; use the poor person's test if it doesn't.

Identifying viable niches without magazine ad benchmarks

• The classic $5K full-page ad rule (Tim Ferriss / Start Small, Stay Small) was a proxy for audience size — the principle still holds, the medium has changed.
• Subreddits as a proxy: community size and engagement can signal whether a niche is large enough.
• SimilarWeb / Alexa: directionally correct traffic estimates for competitor sites — a competitor at 100K uniques/month can support a lifestyle SaaS.
• Crunchbase: funding raised and headcount give a rough sense of market size and competitive density.
• Bureau of Labor Statistics: for vertical or orthogonal SaaS, look up the actual count of target roles (architects, accountants, hairdressers) in the US.
• Three SaaS categories worth knowing: vertical (niche-specific), horizontal (any business), orthogonal (role/title-specific).
• For a bootstrapped business targeting $1–5M ARR, the total reachable market doesn't need to be huge.

Stair step approach with 12 months of runway

• The stair step method (step 1 → step 2 → standalone SaaS) was designed to fund the transition out of employment; if you're already out, the logic shifts.
• Step 1 and step 2 businesses are faster to revenue — standalone SaaS takes longer to build, iterate, and reach product-market fit.
• With 12 months of runway, speed to revenue matters more than passion for the vehicle.
• A reasonable constraint: only pursue step 1 ideas that could plausibly reach your income target (e.g. $10K/month).
• Unique advantages — audience, network, domain expertise — compress timelines; if you have them, weight toward your strongest edge.

How niche tech stack affects company valuation

• Exit price is the primary variable; the same tech stack is a deal-breaker at one price and irrelevant at another.
• Sub-$250K exits: buyers are typically technical individuals who will write the code themselves — a niche stack (e.g. Clojure) significantly limits the buyer pool.
• $500K–$10M exits: strategics and micro-PE care more about business fundamentals, but will ask: "Can we hire for this?" A shrinking or obscure language is a real concern.
• Nine-figure exits: the tech can be rewritten — brand, user base, revenue, and team matter far more than the stack.
• Key questions a buyer will ask: How many developers exist for this language? Is it growing or sunsetting?
• Practical fix: Rob rewrote HitTail from classic ASP to Rails before selling — a few months of dev cost made the business "infinitely more sellable."
• A rewrite is viable below a certain complexity threshold; above it, the exit price must be high enough to justify the migration cost.

B2C vs B2B framing for a health publishing platform

• If clinicians pay out of pocket, it's effectively B2C — a nice-to-have competing with personal budgets.
• If the buyer is a clinic, university, or institution, it's B2B — and pricing should reflect that.
• $15/month is a structural problem: the LTV is too low to fund paid acquisition, in-person events, or most non-free marketing channels.
• Freemium can work if combined with a dual funnel: a $15/month consumer plan plus an enterprise "call us" plan for site licences.
• At scale, enterprise licence revenue will likely dominate — that's where the margin is.