Listener Q&A: Mock features, failed launches, and freelancing

Executive overview

Most SaaS founders encounter avoidable mistakes — premature launches, content gaps, and unclear paths to self-employment. This episode answers six listener questions covering sales tactics, launch recovery, marketing without expertise, acquisition dynamics, and the contracting-to-founder transition.

Build an email list before you launch; a phased rollout beats a single high-stakes debut every time.

Mock features as a B2B sales tactic

• Mock features are UI elements that look functional but execute manually — or never at all.
• They target buyers who demand checklist requirements they rarely use once the contract is signed.
• Example: a report generator button that shows "48–72 hours to generate" — used zero times over two years by a $250k contract customer.
• Only works when the buyer is not the end user; corporate procurement commonly makes demands the actual users never care about.
• Ab Advani reports building 50+ mock features across 10 years, helping close $6M in software licenses.
• Does not work for sub-$1,000/month products sold directly to end users.

Recovering from a premature launch

• The root cause of most failed launches: no pre-launch email list, so all bets ride on one public moment.
• Start marketing the day you start coding; build a list of hundreds or thousands before launch day.
• A phased launch — releasing to 50, then 300, then more — lets you fix pricing and features between waves.
• A bad launch is salvageable: treat it as a learning experience, then execute standard SaaS marketing (cold outreach, SEO, integrations, partnerships).
• Consider a "2.0 relaunch" — frame it as a story of iteration and learning, then re-hit all original channels.
• Many successful SaaS companies had mediocre or no formal launch at all.

Content creation outside your area of expertise

• If you don't have subject-matter expertise, avoid content/SEO and use other channels instead: cold outreach, trade shows, integrations, partnerships.
• Alternatively, hire a writer who already has domain expertise — not a generalist who will need to learn it.
• AI-generated content without expert review produces bland output that won't rank or resonate.
• A co-founder with subject-matter expertise is another viable path — the developer-plus-domain-expert pairing is common in bootstrapped communities.
• Content is not a hard requirement; many funded-but-bootstrapped companies grow entirely without it.

Consumer-facing vitamin products

• Rob explicitly declines to advise: consumer products are a different world with high churn and low repeatability.
• His consistent stance: don't build consumer vitamins — use the stair-step approach and start with B2B SaaS instead.
• If you're committed, find a specialist podcast or channel; domain-specific advice will far outperform general startup wisdom here.

Joining a seed-stage startup before acquisition

• Acquirers almost always want the team, not just the technology.
• Engineers are typically offered a new stock grant in the acquiring company, vesting over four years — the real retention mechanism.
• A key person clause can contractually require founders to stay for 1–3 years to receive the full purchase price; less common for individual engineers.
• Acceleration clauses (single or double trigger) determine whether unvested options vest on acquisition.
• Outcomes vary significantly by company size and deal structure.

Contracting and consulting for software engineers

• Contracting = writing code for dollars per hour; consulting = giving advice without implementing. In practice, most developers do both interchangeably.
• Rates scale with location, seniority, and how clients are sourced: agencies and Upwork yield lower rates than direct clients.
• Building a public presence (blogging, community) lets you command retail rates and attract inbound clients.
• Project-based work is feast-or-famine; long-term retainer arrangements are more stable.
• The employment ladder: employed → self-employed (selling your time) → entrepreneur (leveraging others' time or technology) → investor.
• Contracting is a viable stair-step move: dial back client hours as product revenue grows, avoiding a hard leap from salary to zero income.