Building Our SaaS Startup Team + Pitch Deck Walkthrough

Team-building + Execution Pitch Deck Walkthrough (SaaS Startup)

Goal

Recruit founding team members by clearly explaining:

• Vision
• Product opportunity
• Commercial model
• Execution timeline

Why teamwork mattered

They needed people to help build an app on top of already-tested technology/algorithms, including:

• Centralized onboarding
• Data import

Recruiting playbook used

They presented a complete deck to trusted friends in a personal setting (e.g., a living room / home pitch) to create belief + commitment, rather than relying on a “just start building and see what happens” approach.

Positioning of the challenge

Co-pilot targets a narrow vertical/customer base (trucking operations). This is framed as:

• A learning advantage
• A way to drive early impact with early hires

---

Product + Offering (What the App Does)

Product suite vision

They showed “Copilot V1” / “Copilot V1, Lyman Copilot” as three components that combine into operational excellence for trucking companies.

Core workflow implied

Customers can:

• Log in
• Import their data
• Use the centralized system to improve day-to-day operations

---

Pricing Strategy + Business Model (Subscription Mechanics)

Tiered subscriptions

• Gold: target pricing level of $30 per truck per week
• Platinum (V2): “more features” / upgraded version
• Bronze (renamed later): simplified/baseline feature set (still includes “basic features”)

Usage-based scaling principle

Revenue scales with customer size by charging:

• Per truck
• Billed weekly

Example rationale:

• Revenue from a 1-truck business shouldn’t equal revenue from a 20-truck business.

Retention / virality assumption

The product is framed as “addictive”:

• Early adoption at small fleet size increases likelihood of retention as fleets grow.

Strategic implication

They’re willing to accept early losses to build loyalty and enable expansion later (customer lifetime expansion).

---

Market Sizing + Revenue Scenarios (TAM-Based, Transparent Worst-Case)

TAM-style revenue math example

Assumptions (as presented):

• Company has ~20 contracts/trucks
• Price: $30 per truck/week

Calculations:

• Weekly revenue per client: 30 * 20 = $600/week
• Annualized revenue per client: ~$31k/year

Capture assumption

• If they capture 20% of TAM → ~$1.2M/year revenue (as presented)

Revenue scenarios to align team incentives

They used explicit scenarios:

• Worst case: 5% market share on Gold → ~$280k annual revenue
• Target case: 20% market share on Gold → ~$1.1M annual revenue

Explicit hiring / commitment test

They use worst-case numbers to ask early team members whether the risk/reward is still worth it.

Framework / process highlighted

• Market → pricing → revenue scenario modeling
• Transparency-first recruiting: “Here’s the worst case; decide for yourself.”

---

Go-to-Market Planning + Launch Schedule (Timeline as an Execution System)

They presented a launch schedule from December (pitch) through November, with:

• An update in Q1 2024
• Color-coded workstreams

Color-coded workstreams

Technology workstream (dark blue)

• Core technology development
• User interface creation
• Review + feedback loop

Testing (pink)

• Laminar testing (their internal testing approach)
• They were the first demo customer for the application

Marketing / demand generation (light blue)

• Marketing website / landing page development
• Treated as launch-critical infrastructure

Initial rollout (yellow)

• Smaller-scale local launch with nearby/closest companies

Milestone called out

• V2 core technology development started in September 2024

Framework / process highlighted

• A color-coded execution plan by function (tech, testing, marketing, local rollout)
• A feedback loop built into product development for continuous iteration

---

Actionable Recommendations Implied by the Pitch Deck Structure

• Recruiting template: Build a deck that covers market, product, team role/ownership, pricing, TAM, go-to-market, and timeline.
• Pricing model for B2B vertical SaaS: Use per-unit pricing aligned with customer scale (here: per truck) so revenue naturally grows as customers expand.
• Reduce adoption friction: Let users import existing data and begin quickly via centralized login.
• Align risk tolerance early: Present explicit revenue downside scenarios so early hires can make informed decisions.
• Treat marketing site as launch infrastructure: Landing page + website work should be on the critical path.

---

KPIs / Targets Explicitly Mentioned

• Price target: $30 per truck per week
• Per-customer annual revenue estimate: ~$31k/year (example using 20 trucks)
• Market capture targets (TAM-based):
  • Worst case: 5% → ~$280k/year
  • Target: 20% → ~$1.1M/year
• Time horizon / timeline target: Dec → Nov (with Q1 2024 update) and V2 tech start in Sep 2024

Note: No CAC/LTV/churn metrics were stated in the provided subtitles.

---

Sources / Presenters

• Presenter: Kevin (also refers to “Moses, my co-founder”)
• Co-founder mentioned: Moses