6. Fundability
6.1 Would I invest at pre-seed or seed?
Pre-seed: No. There's no team, no traction, and the product is an app on one platform in a category with 10+ established vendors. The version as described is a later copy of Mailfloss. The wedge is sharper, but its ceiling is a slice of Klaviyo's customer base, and Klaviyo can remove the gap with one release.
Seed: No, and not a close call. Nothing here grows into a venture outcome. Even the market leaders in verification are $5–10M businesses (Latka estimates).
6.2 What a skeptical investor says in the first five minutes
- "Mailfloss already cleans Klaviyo lists every day for $59 a month. What's different?"
- "Bouncer sells a million checks for $2,000. How do you not end up in that price war?"
- "Klaviyo can add a scheduled-suppression toggle next quarter. Then what?"
- "Once the list is clean, why does anyone keep paying?"
- "How do you know suppressed profiles weren't going to buy?"
- "Gmail and Outlook block the verification checks. How accurate are you, really?"
- "Who sells this? Brands don't search for 'list cleaning' until something breaks."
- "What stops the next developer building the same thing in a weekend?"
If you can't answer 1, 4 and 5 crisply, the rest doesn't matter. The answers are: bill savings rather than verification, ongoing signup and dormancy jobs plus agencies, and the holdout.
6.3 Three proof points that would change my answer (to "worth running", not "worth funding")
| # | Proof point | Threshold | Why it matters |
|---|---|---|---|
| 1 | Savings per account | Median saving ≥3x the fee in month 1, and ≥1x in months 2–6 | Proves the value continues after the first cleanup. |
| 2 | No lost revenue | Holdout revenue per profile ≤10% of the active list's, across 20+ accounts | Proves the product is safe to leave running. |
| 3 | Retention through a channel | ≤4% monthly revenue churn after month 6, and ≥30% of MRR from agencies | Proves it's a subscription, not a one-off service. |
Even with all three, this stays a bootstrapped business. The proof points decide whether to keep going, not whether to raise.
6.4 Bootstrap or raise?
Bootstrap. Specifically:
- Cheap to build. One OAuth app, scheduled jobs, rules, a report and a wholesale verification API. A capable developer ships v1 in 6–8 weeks.
- Revenue arrives early. A paid audit can be sold in week 2, before the app exists.
- Money doesn't fix the constraint. The constraints are platform risk and churn. Neither improves with capital.
- Exit option: at $5–15k MRR with churn under 4%, an app like this is a candidate for a sale to an agency, a verification vendor or a marketplace buyer. Acquire.com's median is 3.9x profit (catalog, Part A). Keep the codebase and the books clean from day 1.
Honest bottom line: the version as described isn't fundable, and bootstrapping it would struggle too, because it's a late entry into a price war. The narrow version doesn't need funding to prove itself. Build that one, and keep it small.