4. Expanded Feature Catalog (What Buyers Ask For)
About 35 features that brands, agencies and email marketers ask for in list hygiene, each classified with the same honesty as the stated idea. Being in demand doesn't mean you should build it. Most of these demands are already met by the platform or a verification vendor.
Legend: TS = Table stakes, D = Differentiator, X = Distraction, L = Liability. Priority: P0 = v1 of the recommended wedge, P1 = next, P2 = later, — = don't build.
A. The bill and the list (the core, so lean in)
| Feature | Demand signal | Category | Priority | Notes |
|---|---|---|---|---|
| Read-only bill audit: active profiles, dead weight by type, $ per month at Klaviyo's price bands | High since Klaviyo's Feb 2025 billing change (secondary source) | D | P0 | Free. Needs only read scopes. The acquisition hook. |
| Scheduled suppression rules (e.g. no click, purchase or site visit in 180 days, and received ≥10 emails) | High. Klaviyo community threads ask for it; no native schedule. | D | P0 | Default rules plus a simple editor. Run weekly. |
| Purchase-aware safeguards (never suppress buyers in the last N days, VIPs, subscribers under N days old) | High among agencies | D | P0 | The difference between a tool and a liability. |
| Suppression log and one-click restore | Medium, but trust depends on it | D | P0 | Confirm the unsuppress API behaviour before launch (see 09). |
| Holdout group with revenue report | Low as a request, high as proof | D | P0 | 5% default. Report the holdout's revenue every month. |
| Monthly savings report (profiles removed, $ saved, trend) | High | D | P0 | Email and PDF. Timed before the Klaviyo invoice. |
| Sunset flow template (last-chance email before suppression) | Medium. Klaviyo recommends it. | TS | P1 | Install a flow template via the API. Don't build an email editor. |
| Mailchimp auto-archive of unsubscribed and dormant contacts | Medium-high. Mailchimp bills for unsubscribed contacts. | D | P2 | Second platform, after $5k MRR. |
B. Address quality
| Feature | Category | Priority | Notes |
|---|---|---|---|
| Syntax, MX, disposable and role-address checks | TS | P0 | In-house, near-zero cost. |
| SMTP mailbox check for uncertain addresses | TS | P0 | Wholesale API. Report "unknown" honestly. |
| Typo correction at signup (Klaviyo and Shopify forms) | D | P1 | A daily reason to stay after the big first cleanup. |
| Bot and fake-signup detection (burst signups, gibberish names, known bot domains) | D | P1 | Bot signups inflate profile counts and trigger spam traps. |
| Spam-trap detection | TS / L | P2 | Vendors claim it. It's hard to verify, so don't market it. |
| Catch-all "risk score" | L if used to suppress | P2 | Flag only. |
| Real-time verification API for developers | X | — | A different market. |
C. Deliverability
| Feature | Category | Priority | Notes |
|---|---|---|---|
| Bounce and spam-rate trend in the monthly report | TS | P1 | Pulled from Klaviyo metrics. |
| Gmail 0.3% spam-rate warning | D (small) | P1 | Uses the customer's own Postmaster Tools data, if they connect it. |
| Blocklist monitoring | X | — | Many free tools exist. |
| Inbox-placement (seed) tests | X | — | GlockApps, Bouncer's kit. Not your fight. |
| Email warm-up | X / L | — | Warmup Inbox and others. It's aimed at cold email, and the platforms dislike it. |
| DMARC setup and reports | X | — | Crowded (dmarcian, EasyDMARC, PowerDMARC, Red Sift). Link out. |
D. Agencies and teams
| Feature | Category | Priority | Notes |
|---|---|---|---|
| Multi-account dashboard | D | P1 | The channel to $5k+. |
| White-label savings report | D | P1 | Agencies want to show clients the saving as their own work. |
| Roles and approval before suppression | D | P1 | Agencies need client sign-off for the first run. |
| Agency billing (one invoice, many accounts) | TS | P1 | Expected. |
E. Trust, privacy and operations
| Feature | Category | Priority | Notes |
|---|---|---|---|
| Data-processing agreement, subprocessor list, EU data option | TS | P0 | Brands' customers' data passes through you. |
| Minimal data storage (IDs and scores, not full profiles) | TS | P0 | Lowers breach risk and GDPR scope. |
| Job monitoring and alerts (failed runs, token expiry) | TS | P0 | Unattended jobs need self-checks. |
| Dry-run mode for every rule | D | P0 | Shows what would be suppressed before anything happens. |
| Status page | TS | P1 | Cheap trust. |
| SOC 2 | X at this stage | — | Only if enterprise asks, which you're avoiding. |
F. Things buyers ask for that you should refuse
| Feature | Category | Why |
|---|---|---|
| Email appending / finding addresses | L | Breaks opt-in rules and privacy law. |
| Re-permission campaigns to purchased lists | L | Same. |
| "Guaranteed inbox" or "guaranteed accuracy" | L | Can't be delivered. |
| AI subject-line or send-time tools | X | Klaviyo ships these natively. |
| Predictive purchase scoring for campaigns | X | Orita and Klaviyo's own predictive analytics own it. Keep to "who is dead weight". |
Net effect
Of about 35 features, about 10 are differentiators, and about 9 belong in v1. Almost all of them come from the bill-and-safety job, not from address verification. Verification is a component you buy, not the product you sell.