3. Feature-by-Feature Scrutiny (the Stated Idea)
The idea arrived as one line: "Connect to an email-marketing platform (Mailchimp, Klaviyo, Kit/ConvertKit, Brevo and others) and remove invalid, risky or mistyped addresses on a schedule." Below are the features that line implies, plus the typical feature set of the products it would compete with.
Categories:
- Table stakes (TS): customers expect it. It earns nothing, but its absence costs you.
- Differentiator (D): a real reason to choose you over the alternatives.
- Distraction (X): built but unlikely to move revenue or retention.
- Liability (L): creates support, compliance, legal or trust risk.
3.1 Classification table
| # | Feature | Category | Reasoning |
|---|---|---|---|
| 1 | Connectors to Mailchimp, Klaviyo, Kit, Brevo and others at launch | X / L | Each connector is a separate API, auth flow, billing model and support queue. Mailfloss already has 40+. You'd be the 11th vendor with a shorter list. Launch with Klaviyo only. |
| 2 | Syntax, MX, disposable-domain and role-address checks | TS | Every vendor does it, and it's cheap to build. Run it in-house so your cost per check is near zero. |
| 3 | SMTP mailbox verification ("does this inbox exist?") | TS / L | Expected, but unreliable on Gmail, Outlook and catch-all domains (low-confidence sources), and running your own probing gets IPs blocked. Buy it wholesale (e.g. Bouncer) for uncertain addresses only. |
| 4 | Typo correction (gmial.com → gmail.com) | TS → D at signup | Batch typo fixes are table stakes. Fixing typos at the signup form, before the profile exists, is a small edge and a daily reason to stay. |
| 5 | Scheduled removal of invalid addresses | TS | Mailfloss does it daily. Klaviyo already auto-suppresses hard bounces. On its own it saves little money. |
| 6 | "Risky" address removal (catch-all, unknown, spam traps) | L | "Risky" often means "we couldn't tell". Removing them removes real customers. Flag them, don't suppress them, unless engagement data agrees. |
| 7 | Per-credit pricing | L (commercially) | Credits are bought once and then sit. It creates the churn pattern that kills the idea. Price by profile band. |
| 8 | Real-time verification API | TS | Expected by developers, but it's a separate market. Offer it only through the signup-form feature. |
| 9 | Deliverability monitoring (blocklists, inbox placement, DMARC) | X as core | Klaviyo has a deliverability score and Reputation Repair AI. Google has Postmaster Tools. DMARC tools are crowded. Keep a small section in the monthly report. |
| 10 | "99%+ accuracy" marketing | L | Can't be proven, and verifiers disagree with each other. It invites refund claims when bounces happen anyway. |
| 11 | Automatic deletion of bad contacts | L | Irreversible, loses purchase history, and can breach the brand's own data-retention rules. Suppress, never delete. |
3.2 What the wedge adds (not in the original line)
| Feature | Category | Why |
|---|---|---|
| Read-only bill audit (profiles, dead weight, $ per month) | D | It's the hook, the proof and the sales pitch in one screen. |
| Purchase- and click-aware scheduled suppression | D | The job Klaviyo doesn't automate. Opens are ignored as a sole signal. |
| Suppression log with one-click restore | D | Makes it safe to hand the job to software. |
| 5% holdout with revenue reporting | D | Proves suppressed profiles weren't buying. Nobody in the verification tier offers it (not confirmed for Orita). |
| Monthly savings report, before the Klaviyo invoice | D | The renewal moment. |
| Agency multi-account dashboard, white-label report | D | The channel to $5k+. |
3.3 Scoreboard
| Category | Count | Features |
|---|---|---|
| Table stakes | 5 | Syntax/MX/disposable checks, SMTP check (bought in), batch typo fixes, scheduled invalid removal, real-time API |
| Differentiator | 6 (all from the wedge) | Bill audit, purchase-aware suppression, restore log, holdout, savings report, agency dashboard |
| Distraction | 2 | Multi-platform connectors at launch, deliverability monitoring as core |
| Liability | 5 | "Risky" removal, credit pricing, accuracy claims, deletion, own SMTP probing |
Of the original idea's features, none is a reason to buy. Every reason to buy comes from reframing the job as "shrink the bill without losing buyers".
3.4 Building to avoid selling: explicit call-outs
- The integration list. Adding Brevo and Kit connectors feels like progress. It's the same commodity, five times.
- Your own SMTP verification engine. Technically interesting, operationally painful, and worse than buying it wholesale.
- A deliverability dashboard. It demos well and Klaviyo already shows a score.
3.5 What a disciplined v1 looks like
Keep: Klaviyo OAuth app + read-only bill audit + scheduled purchase-aware suppression + restore log + holdout + monthly savings report, with in-house syntax, disposable and typo checks and a wholesale verifier for uncertain addresses. Defer: signup-form verification (v1.5, month 3–4), agency dashboard (month 5–6), Mailchimp (after $5k MRR). Cut: other platforms, credit pricing, deliverability monitoring as a product, deletion, accuracy claims.