Skip to content
Idea AtlasSign in

Slotwise

As described:StopNarrowed:Continue

No as described. Go as scheduling and hour records for teen driver-ed schools, starting in Ohio.

driving schools · ~$150 a month per school · last reviewed (next review by 29 Dec 2026) · 33 cited sources

Save
Share

← All research

6. Fundability

6.1 Would I invest at pre-seed or seed?

Pre-seed: No, as presented. "Scheduling for a narrow trade" with no trade chosen is a category, not a company. Even narrowed to driving schools, the market is ~6,000 professional schools and a software SAM of roughly $10–20M a year. The best-known incumbent looks like a 3–5 person business after 20 years. That's a good small business, and not a venture return.

I'd consider a small angel cheque only if all of these were true:

  • a founder who has run or worked at a driving school;
  • 20+ schools paying, with ≥90% month-3 retention;
  • a credible path to a payments take-rate or to Canada, which could lift the ceiling.

Seed: No. Not a close call. The ceiling is the problem, not the team.

6.2 What a skeptical investor says in the first five minutes

  1. "Which trade? If it's 'any trade', how are you different from Calendly or Acuity?"
  2. "How many driving schools are there really, and how many have more than one instructor?"
  3. "Zutobi already sells this with curriculum and a student app. Why would a school pick you?"
  4. "DanubeNet has been in this market since 2005. What stops them fixing their product?"
  5. "Every state has different rules. How much work is each new state?"
  6. "These are owner-operators in a seasonal business. What's your churn in winter?"
  7. "You're storing teenagers' personal data. Your biggest competitor just got sued over a breach. What's your security story?"
  8. "How do you reach schools without a sales team?"
  9. "What does a school earn or save in dollars from using you?"
  10. "Why this team?"

If you can't answer questions 2, 3 and 8 crisply, the rest doesn't matter.

6.3 Three proof points that would flip my answer (to a small angel or strategic cheque)

#Proof pointThresholdWhy it matters
1Paid retention in one state≥40 Ohio schools at ≥$140/month average, ≤1.5% monthly logo churn across one full winterProves the hour record makes the product sticky in a seasonal trade
2Money outcome per schoolMedian school collects ≥$150/month in no-show fees or fills ≥10% more instructor hoursTurns "nice software" into "pays for itself", and supports a price rise
3Repeatable acquisition across statesA second state reaches 15 schools within 6 months of launch, with ≥50% of trials from search, lists or referralProves growth isn't capped by one state or by founder calls

A fourth, for a larger outcome: payments volume. If schools process $100k+ a year each through Stripe Connect, a small platform fee could double revenue per school. That's the only path that makes the ceiling interesting.

6.4 Bootstrap or raise?

Bootstrap. Specifically:

  • The v1 is cheap to build. Records, calendars, Stripe, SMS and a PWA. No heavy compute. One developer can ship it in 8–10 weeks.
  • Revenue arrives early. Schools pay from month one if it saves them phone time and collects no-show fees.
  • Money doesn't fix the constraint. The constraint is calls, migrations and state rules. Paid sales reps at $150/month per school don't pay back.
  • Raising pushes you to go horizontal ("scheduling for all lesson businesses"), which is the as-described version, and it has ~2% odds of $10k MRR.
  • A later sale is the realistic exit. Small SaaS businesses sell at around 3.9x profit (Acquire.com median, in the catalog). A profitable $10k MRR business with low churn is sellable to a vertical-software buyer.

Honest bottom line: the version you described isn't fundable and wouldn't work bootstrapped either. The narrow version doesn't need funding to prove itself. Build that one.