What changed
FACT (per source): Zapper announced a shutdown on Aug. 3 after ~7 years, orphaning computed/priced portfolio history for a formerly ~2M-MAU base. FACT (per source): a low-cost 'computer use' model tier (Gemini 3.5 Flash) makes browser automation cheaper for solo builders. HYPOTHESIS (single unverifiable news-aggregator link): Illinois 'became the first state to tax crypto transactions.'
Why now
The only genuine time-box is Zapper's Aug. 3 shutdown — roughly three weeks out. That is the hard gate the whole rescue thesis rests on. The Illinois tax, even if real, is 'not-yet-enforced,' so its urgency is speculative.
Converging signals
Three signals nominally meet: (1) a data-deletion event (Zapper), (2) a claimed new compliance burden (Illinois crypto tax), (3) a cheap automation capability (Flash computer-use). But the meeting is engineered, not organic: the tax and the tracker have no causal relationship, and the 'imaginative leap' does the connecting.
Customer pain
Real but weak. Crypto holders dislike losing history and dislike tax season — but this pain is ALREADY served by Koinly, CoinTracker, CoinLedger, TokenTax, ZenLedger, Zerion and Debank. There is no unmet, unanswered pain in demand_evidence (empty array).
Who pays
Claimed: crypto individuals/businesses and their CPAs, $29–$99 one-time rescue then a reporting subscription. The one-time rescue is a single-event, non-recurring buyer; the recurring buyer is contested by well-funded incumbents.
Solved today
Crypto tax software (Koinly/CoinTracker/CoinLedger) already reconstructs per-lot cost basis from wallet addresses + on-chain history + historical price oracles, and files/exports tax forms. Portfolio history is reproducible today via Zerion, Debank and public price APIs — the exact free path the idea's own KILL TEST names.
Why current solutions are bad
The brief's 'MUST BE TRUE' (that Zapper's priced history is materially expensive to reconstruct after the fact) is the entire moat and is almost certainly FALSE for mainstream tokens: incumbents reconstruct priced history from chain data as their core product. Only illiquid long-tail token pricing is genuinely hard — a thin, low-value edge case.
Proposed product
A user-authorized computer-use agent that logs into Zapper and bulk-exports each user's history before Aug. 3, then normalizes it into per-lot cost-basis ledgers and an Illinois transaction-tax report template.
MVP version
Landing page targeting 'Zapper shutdown' search traffic + a consent flow + an export agent. But shipping a credential-handling, financial-data-scraping agent AND a reconciled cost-basis engine in <3 weeks is not a realistic solo MVP.
30-day build
Do the one-day KILL TEST first, not a build: take a real 3-year wallet and attempt full priced-history reconstruction with Zerion/Debank + public price APIs, and check whether Zapper ships an official bulk export. If either succeeds, stop.
60-day build
Only if the kill test survives: normalize snapshots into per-lot ledgers reconciled against on-chain data — the hard, incumbent-owned part.
90-day revenue plan
Partner one crypto CPA to review an Illinois report template — but only AFTER independently verifying that Illinois's tax exists, applies to the claimed filer class, and creates a documentation obligation software can serve.
Distribution path
Ephemeral: 'Zapper shutdown' search/social traffic evaporates within weeks of Aug. 3. No durable acquisition channel. The CPA-referral channel is unproven and slow.
Pricing hypothesis
$29–$99 one-time rescue; subscription later. The one-time fee funds nothing durable; the subscription competes head-on with $49–$199/yr incumbents on their turf.
Technical difficulty
High for the timeline: reliable authenticated computer-use export at scale, secure custody of credentials/financial data, and accurate multi-chain cost-basis reconciliation — each non-trivial, together infeasible in three weeks.
Legal / regulatory risk
Significant. Automating logins to Zapper may violate its ToS; handling users' financial account credentials and full transaction history is high-liability PII custody; producing tax reports edges toward regulated tax advice (mitigated only via a licensed CPA partner).
Platform dependency
High and adversarial — the product depends on scraping a platform that is actively shutting down and whose data may be gated or purged, plus a third-party model vendor for the agent.
Founder fit
Poor. This is a consumer/prosumer CRYPTO tax tool in a crowded, network-effect-adjacent market the founder explicitly avoids. It is NOT the government-portal forced-filer shape that scores 8–9 for him. The Illinois-tax sliver could fit that shape, but it is unverified and buried under a crypto data-scraping gimmick.
Breakout potential
Low. Even if executed, the rescue is a one-time event and the reporting layer walks into an incumbent buzzsaw. No defensible wedge.
Final recommendation
KILL as specified. The Zapper-rescue mechanic is a clever gimmick with reproducible data, a crowded downstream market, an ephemeral channel, and heavy PII/ToS risk on an unbuildable timeline. The ONLY fragment worth a second look is orthogonal: independently verify whether Illinois genuinely created a crypto compliance FILING obligation for a defined class — if so, pursue THAT as a standalone forced-filer opportunity, decoupled entirely from Zapper.
Next action
Spend one hour verifying the Illinois crypto-tax claim from the primary statute/DOR source (not the aggregator link). If a real, defined filing obligation exists, spin it out as its own brief; otherwise archive this convergence.