What changed
A law-firm marketing article (businessattorneychicago.com, via Google News RSS) asserts Illinois became the first state to tax crypto transactions, framed as something 'every business needs to know.' Separately, Robinhood announced (not launched) AI agents will 'soon' trade crypto for retail users, and a joint SEC/CFTC interpretive release on crypto-asset classification was issued (its actual conclusions are not stated in the source).
Why now
IF the Illinois tax is real and imposes per-transaction obligations, it creates an immediate, novel, deadline-bearing compliance burden with no established tooling — a genuine first-mover window before accountants/incumbents build spreadsheets or software for it.
Converging signals
Three signals meet at one point: a state per-transaction crypto tax (the forcing function), machine-speed agent trading that multiplies taxable events (the volume driver), and a federal classification framework (the legal scaffolding). This is a real convergence SHAPE — but two of the three legs are speculative (agents not live; framework conclusions unknown) and the load-bearing leg (the tax) is single-sourced from a law-firm blog.
Customer pain
HYPOTHESIS, not established: Illinois businesses touching crypto would face novel per-transaction tax calculation and remittance they cannot do by hand at volume. No complaint, no job posting, and no primary statute text is in the input to prove the pain exists or its magnitude.
Who pays
Illinois businesses that transact crypto (compliance need) and, secondarily, agent-trading tool builders embedding a guardrail. Buyer reachability is plausible but the addressable count is unknown and likely small until the tax is confirmed and its scope defined.
Solved today
If the tax is new, today's answer is CPAs, crypto tax tools (CoinTracker, TokenTax, Koinly) extended by hand, or exchange-level remittance. Critically: if exchanges remit the tax upstream, there is NO business-level buyer at all — the KILL TEST.
Why current solutions are bad
General crypto-tax tools compute federal capital-gains after the fact, not a state per-transaction tax pre-trade, and none block tax-negative trades in real time. That gap is real ONLY if the statute creates a per-transaction, business-remitted obligation.
Proposed product
A REST + MCP 'tax throttle' endpoint: submit a proposed trade, receive Illinois tax impact, after-tax P&L, and a block/allow signal against a user policy; plus exchange-export ingestion (Coinbase/Robinhood CSV/API) to generate period filing reports.
MVP version
A deterministic Illinois-tax calc engine (rate/base/remittance encoded from the ENACTED statute, with tests) behind a single API call returning tax impact + allow/block. No agent integration needed for v1.
30-day build
KILL TEST FIRST, before any code: pull the actual enacted Illinois statute/regulation text, confirm it imposes a business-level per-transaction calculation/remittance duty (not exchange-collected), and call 10 Illinois crypto-touching businesses to confirm they feel the burden and would pay. If the tax is exchange-remitted or the article overstates a general sales-tax application, stop.
60-day build
If validated: encode the calc engine with a test suite tied to statute citations; ship the REST/MCP endpoint; build Coinbase/Robinhood export ingestion for filing-period reports.
90-day revenue plan
Sell directly to the article's exact audience (Chicago crypto-touching businesses) at a flat monthly compliance-tool price; pitch the guardrail API to 2-3 agent-trading tool builders as an embeddable safety layer. First revenue is realistic within ~90 days only if the tax and buyer are confirmed early.
Distribution path
Direct outreach to Illinois crypto businesses via the law firms and CPAs already publishing 'what you need to know' content (partner/referral), plus developer distribution through MCP/agent-tooling communities.
Pricing hypothesis
$99-$399/mo per business for the compliance tool + filing reports; usage-based per-call ($0.001-$0.01) for the embedded guardrail API. Price validated only after buyer calls.
Technical difficulty
Low-to-moderate: a deterministic calc engine + REST/MCP wrapper + CSV/API ingestion is squarely within a solo AI-assisted builder's range. The hard part is legal interpretation of the statute, not code.
Legal / regulatory risk
Moderate: the product asserts tax-compliance outcomes. Positioning must be 'calculation tooling, not tax advice' to avoid unauthorized-practice / reliance liability. No licensure is strictly required to sell a calculator, but errors carry reputational and possibly liability exposure.
Platform dependency
Low — submits nothing to a government portal (no deplatform risk), but depends on exchange export formats (Coinbase/Robinhood) and on Illinois not changing/repealing the tax.
Founder fit
Good shape-fit (regulation-driven compliance tool, per-transaction monetization, solo-buildable) matching the founder's proven government/compliance edge — BUT it is crypto-centric (an adjacency he's cooler on) and the mandate is unverified, so it is not the clean forced-filer-to-portal pattern his FMCSA win exemplifies.
Breakout potential
If the Illinois tax is real and other states copy it (likely, given 'first state' framing), the calc engine replicates across 50 near-identical markets — a genuine expansion path. Contingent entirely on the premise being true and the trend spreading.
Final recommendation
CONDITIONAL / VALIDATE-BEFORE-BUILD. The shape is founder-appropriate and the wedge is clean IF true, but the entire opportunity rests on an unverified single-source claim and two speculative signals. Do NOT build. Spend one week on the input's own KILL TEST — read the enacted statute and call 10 Illinois crypto businesses. Proceed to code only if the tax imposes a business-level per-transaction burden and a reachable buyer confirms willingness to pay. Otherwise archive and revisit if a second state acts.
Next action
Retrieve the primary enacted Illinois statute/regulation text and confirm (a) it taxes crypto transactions per-transaction and (b) the calculation/remittance duty falls on the business, not the exchange — before writing any code.