ThresholdWire

1. One-liner

Watches every contractor’s running total and stops you paying past $2,000 without a W-9 on file.

2. Trend signal — why now?

The One Big Beautiful Bill Act raised the 1099-NEC/MISC reporting threshold from $600 to $2,000 for payments made on or after 1 January 2026 — the first move in that number in decades. Every accounting blog on the internet has spent 2026 telling small businesses this is relief.

It is not relief. It is a trap with a bigger magazine, and three things make it bite in 2026 specifically:

One — the same Act moved the backup-withholding floor. OBBBA §70433 lifted the §3406(b)(6) backup-withholding trigger to the same $2,000. So the moment a contractor without a valid TIN crosses $2,000 cumulative in a calendar year, you must withhold 24% of every subsequent payment and remit it on Form 945. Beancount’s August 2026 write-up puts it plainly: “the withholding gun has a bigger magazine. A contractor working regularly with you can be paid $1,999 with zero friction. At $2,001, all future payments that calendar year get hit with 24% withholding.”

Two — the states did not follow. Federal relief ≠ state relief. Thomson Reuters’ 2026 state-reporting update names Mississippi and Wisconsin as still sitting at $600, Missouri at $1,200, and Arkansas at $2,500 when no state tax is withheld. California conformed to $2,000. So a payer who “helpfully” stops collecting W-9s under $2,000 still owes a state filing in a dozen jurisdictions — with no federal form to copy from.

Three — the trap is invisible until January 2027. Payments made across 2026 get reported in early 2027. Nobody finds out they got this wrong until the filing season, at which point the money is already out the door and 24% cannot be retroactively withheld. The payer eats it: you become liable for the amount you should have withheld, plus §6721/§6722 penalties.

Provenance:

• Signal 1 (demand): OBBBA raises 1099-NEC/MISC threshold $600 → $2,000 for payments on/after 1 Jan 2026; every SMB advisory outlet is framing it as relief — https://www.kroll.com/en/publications/irs-reporting-threshold-raised — 2026
• Signal 2 (feasibility/economic): Backup-withholding floor moved to $2,000 by OBBBA §70433; crossing it mid-year triggers 24% on all subsequent payments + Form 945 — https://beancount.io/blog/2026/08/06/backup-withholding-threshold-600-to-2000-contractor-payments-guide — 2026-08-06
• Signal 3 (economic/regulatory): States did not conform — MS/WI at $600, MO $1,200, AR $2,500, CA $2,000; state filing obligation survives with no federal form — https://tax.thomsonreuters.com/blog/state-tax-information-reporting-what-changed-in-2025-and-what-to-expect-for-2026/ — 2026
• Signal 4 (demand, verbatim pain): Agencies hit January with missing W-9s and a two-week deadline; chasing freelancers who are “on new projects, unresponsive, or no longer working with you” — https://www.irvinebookkeeping.com/post/1099-nec-year-end-checklist — 2026 Category: Regulatory arbitrage

3. The opportunity

Every vendor in this space sells filing. Track1099, Tax1099, TaxBandits, Zenwork — they are excellent at taking a list you hand them in January and transmitting it to the IRS and the states. Their state-threshold logic runs at filing time, on the population you already decided to report.

Nobody sells the decision that happens in March, when you are about to pay a freelancer $900 and the question is whether this is their first payment or their third.

That’s the gap. The threshold is cumulative across the calendar year, but small businesses pay contractors transaction-by-transaction, often across multiple rails — bank transfer, Zelle, cheque, a card, sometimes two different bank accounts. No single system holds the running total. The AP-automation incumbents (Tipalti, Bill, Ramp, Stampli) solve this only for money that flows through them; they are irrelevant to the enormous population of businesses that pay contractors directly from a bank account and reconcile in QuickBooks later.

The 10× is not “file your 1099s better.” It’s: know, before you release a payment, that this one crosses the line — and hold it until the W-9 is in. That’s a tripwire, not a tax form. The incumbents structurally can’t do it because they only see you once a year.

There’s a second, sharper edge. The threshold raise has actively made behaviour worse: payers who previously collected a W-9 from everyone (because $600 caught nearly everyone) now believe small vendors are exempt. The advice content telling them “relief!” is manufacturing the exposure. That’s my favourite kind of market — the pain is being created right now, by the reassurance.

4. Target market

Primary customer: The bookkeeper or fractional controller at a US business with 10–150 employees that pays 20–300 contractors a year outside a formal AP platform. Concretely: marketing and creative agencies, construction and trades subs, medical and dental practices with locums and hygienists, property managers paying repair vendors, film/production companies, e-commerce brands paying freelancers and UGC creators. Also the outsourced bookkeeping firm that runs 1099 season for 30–80 such clients — that’s the higher-value buyer.

Why they buy, in their words: The Irvine Bookkeeping year-end checklist describes the exact moment — agencies with “missing W-9s from contractors and facing a January 31 deadline just two weeks away,” and notes that reaching out to freelancers in January to collect W-9s they should have provided in March is “one of the most frustrating parts of agency bookkeeping.” The same source: “Waiting until January to reconstruct a year of Venmo transfers and cash payments is where most 1099 errors begin.” And getw9.tax spells out the exact failure this product prevents: “You onboard a freelance designer in January for a $1,200 project. No W-9 collected because payments are under the $2,000 threshold. In June, you bring them back for a $900 follow-on project. Total payments: $2,100. You now have a 1099-NEC filing obligation and no W-9 on file.”

Rough TAM reasoning: I could not source a clean IRS filing-volume figure for 1099-NEC, so I won’t invent one — treat the sizing as directional. The honest frame: this is a feature-sized wedge into the US small-business accounting stack, and I only need a few thousand paying accounts. If 3,000 businesses and 400 bookkeeping firms pay an average of $85/mo, that’s ~$3.5M ARR. That’s the whole ambition; I don’t need the true TAM to be big, I need it to be several hundred thousand plausible accounts, which it obviously is.

Why now for them: 2026 is the first calendar year under the new threshold. The payments accumulating right now — September through December — are the ones that will blow up in January 2027. There is a four-month window where the fix is still cheap.

5. Product sketch (MVP)

• Running-total ledger per contractor. Connects to QuickBooks Online / Xero (and a bank feed via Plaid) and maintains a live cumulative-paid figure for every vendor, deduplicated across name variants, DBAs and multiple payment rails.
• The tripwire. Flags any vendor at $1,400+ who has no W-9 on file, and hard-flags the specific next payment that would cross $2,000 — before it’s released. This is the product.
• One-click W-9 request. Sends the vendor a mobile-friendly form, runs IRS TIN matching where the payer is eligible, files the signed W-9 to the vendor record. Chases automatically on a schedule.
• State-threshold overlay. Per-vendor, tells you which states still want a filing at their own number — MS/WI at $600, MO at $1,200, AR at $2,500 — based on where the vendor and the payer sit. This is the bit the “relief” articles skip.
• Backup-withholding calculator and Form 945 prep. If a vendor did cross without a TIN, computes the 24%, tracks what’s been withheld, and assembles the 945.
• January readiness board. A single screen in December: who’s clean, who’s missing a W-9, who’s over threshold federally, who’s over only at state level, projected penalty exposure at $340/return.
• Multi-client mode for bookkeeping firms. One console across all client files, sorted by exposure.

6. AI angle — what’s load-bearing

Strip the AI out and this product mostly doesn’t work, because the hard problem isn’t arithmetic — it’s identity resolution over messy payment data.

The cumulative threshold is per payee, but the underlying records say “J. Martinez”, “Jose Martinez Design”, “JM Design LLC”, “MARTINEZ J” from a bank feed, and “Jose M” in a Venmo memo. Deciding those are one legal payee — or crucially, that “JM Design LLC” and “Jose Martinez” are different payees for TIN purposes — is fuzzy entity resolution over unstructured strings with real money on the outcome. Getting it wrong in either direction creates a false clear or a false alarm, and a false clear is a penalty.

Second load-bearing use: classifying which payments even count. 1099-NEC covers services; payments for goods, rent (different box), payments to corporations (mostly exempt), and reimbursements don’t land the same way. Reading a transaction description plus the invoice PDF and deciding “this is reportable nonemployee compensation” is exactly the judgement call an LLM does well and a rules engine does badly.

Third: reading the vendor’s uploaded W-9 or invoice header to extract entity type and TIN, which determines whether they’re exempt at all.

If you removed the AI you’d have a spreadsheet that alerts on a number — and the number would be wrong, because the names wouldn’t match up.

7. Localization angle (if any)

N/A — this is a US-only play by construction. The entire product is the interaction between a federal threshold, a federal backup-withholding rule, and 50 non-conforming state regimes. That specificity is the moat; there’s nothing to localize. The nearest analogue elsewhere (India’s 194C/194J TDS thresholds, which work similarly on cumulative annual payments) is a genuinely separate product and, per my own catalog, already crowded.

8. Business model — path to $1M–$5M ARR

• Pricing: $39/mo for up to 50 vendors (the solo agency / small practice), $99/mo up to 200 vendors, $249/mo unlimited + multi-entity. Bookkeeping firms: $199/mo for 10 client files, $499/mo for 40. Benchmarked against the category — WeltPixel-style flat $39 app pricing is the norm SMBs accept, Conversios-style per-unit pricing is what they resent, and Tipalti-class AP platforms are 10× this and out of reach.
• ACV: ~$1,100 direct SMB; ~$4,000 bookkeeping firm. Blended target ~$1,400.
• Rough math to $1M ARR: 600 SMB accounts at $79 average + 120 firms at $330 average ≈ $570K + $475K = $1.05M. That is a small, reachable number.
• Rough math to $5M ARR: ~2,500 SMBs and ~600 firms, which means winning the accountant channel properly rather than selling one business at a time. Realistically requires the product to expand into the filing itself (see below) so it can displace a Track1099 line item rather than sit beside it.
• Expansion path: Vendor-count tiers grow naturally. Then add the actual 1099 e-filing (federal + state) at $2.50/form — at that point you’ve absorbed the incumbent’s revenue line, and the cumulative ledger you’ve been keeping all year is what makes your filing product better than theirs. Then multi-entity for franchise and PE-backed rollups.

The honest weakness: this is a seasonal-anxiety purchase fighting to become a year-round subscription. Mitigated by the fact that the tripwire only has value if it’s running in March — which is precisely the pitch.

9. Go-to-market wedge — first 100 customers

• Ride the misinformation. Hundreds of accounting firms, payroll companies and SaaS blogs published “the threshold went up to $2,000, good news” content across 2026. Build the free State Threshold Checker — enter your state and your vendor’s state, get the real number and the real filing obligation. Then run a rebuttal content play: “The $2,000 threshold is not relief in Mississippi, Wisconsin, Missouri or Arkansas.” Every one of those articles is a link-building and comment target with a genuinely correcting message, not spam.
• Cold-outreach the bookkeeping firms before December. Scrape the QuickBooks ProAdvisor and Xero Advisor directories (both public, both filterable by location and firm size) for firms advertising 1099 services. Send a personalised one-pager showing that firm’s likely January exposure: “you file 1099s for N clients; under the new threshold your clients stopped collecting W-9s in March; here’s the list you’ll be chasing in January.” Target 2,000 firms, expect 3–5% to take a demo. This is the highest-leverage channel because one firm brings 30 businesses.
• r/Bookkeeping, r/Accounting, r/smallbusiness in the January window. These subs run an annual, entirely predictable wave of “I paid someone and never got a W-9, what now” posts. Be genuinely useful in those threads with the correct answer including the state wrinkle. This is a real channel, not “content marketing” — the posts are dated, findable, and the audience is the buyer.
• QuickBooks App Store listing. The integration is the install path; QBO’s marketplace is a real discovery surface for exactly this buyer, and “1099” is one of its highest-intent searches every January.
• Partner with the filing incumbents rather than fighting them. Track1099/TaxBandits want a clean vendor list handed to them in January. Being the thing that produces the clean list is a co-marketing conversation, not a competitive one — at least until year two, when you eat their lunch.

10. Build complexity — justification

Low. The integrations (QuickBooks Online, Xero, Plaid) are all documented, self-serve, well-trodden APIs — no partner approval gate, which per my own hard-won rule is the thing that usually kills an integration play. W-9 capture is a form plus e-signature. IRS TIN matching is an existing service. The only genuinely custom work is the entity-resolution layer and the state-threshold rule table, and the latter is research, not engineering — roughly 50 rows that need to be right and maintained.

A competent pair ships a credible v1 in 8–10 weeks. A solo builder could do it in 12–14. Nothing here needs a model to be trained, a dataset to be acquired, or a regulator to say yes.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Bookkeeping-support software. Not tax advice; ship with the standard “not a substitute for your CPA” posture and let the accountant remain the decision-maker.
Ethical — no harm / dark patterns	✅	The product exists to make people pay contractors correctly and get workers their tax forms. Straightforwardly good.
Market exists (evidence above)	✅	Threshold change is law; state non-conformity is documented; the January W-9 scramble is a recurring, sourced complaint.
1–5 person team can build this	✅	Two people, 8–10 weeks.
Launchable with <$50K / ₹40L	✅	Well under. API costs are trivial at this scale; the spend is time and a rules-table researcher.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Real money — 24% payer liability plus $340/return under §6721 and again under §6722. But it’s felt acutely once a year, not daily, which is what keeps this off a 17+.
Demand evidence	15	11/15	Strong regulatory and mechanic evidence, multiple independent sources, documented annual pain. Docked because I found no evidence of anyone paying for this specific tripwire yet — the willingness-to-pay is inferred from adjacent spend, not observed.
Build feasibility	15	13/15	Off-the-shelf integrations, no approval gates, 8–10 weeks. Entity resolution is the only real engineering.
Distribution clarity	15	12/15	ProAdvisor/Xero directories are named, scrapeable and filterable; QBO marketplace is a real surface; the January subreddit wave is dated and predictable. Not a 14 because the bookkeeper cold-outreach conversion is unproven.
Revenue mechanics	15	11/15	Pricing is benchmarked and the $1M math needs only ~700 accounts. Docked because seasonal-anxiety products churn in February and I don’t yet know the retention curve.
Time to first revenue	10	8/10	Sellable pre-build to bookkeeping firms in Oct–Nov on the January exposure pitch. First cash inside 8 weeks is realistic.
Defensibility	10	5/10	Execution moat plus an accumulating per-vendor payment ledger that gets stickier every month. But the state rule table is copyable in a fortnight and Intuit could ship this as a QBO feature. Honest 5.
Total	100	76/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · content-heavy

Technical because entity resolution over messy financial data is the whole product and doing it sloppily produces false clears, which are worse than nothing. Content because the distribution wedge is literally correcting a year’s worth of published misinformation — that requires someone willing to write a lot of precise, sourced, unglamorous tax content.

Key assumptions to validate (3–5)

1. Assumption: Businesses have genuinely relaxed W-9 collection because of the $2,000 headline. How to test: Interview 25 bookkeepers in September–October and ask directly: “has your policy on collecting W-9s from small vendors changed since January?” If they all say “we still collect from everyone,” the trap doesn’t exist and the product is a vitamin.
2. Assumption: Bookkeeping firms will pay for a preventive tool rather than absorbing the January scramble as billable hours. How to test: This one worries me most — the scramble is revenue for them. Pitch 30 firms and watch whether they frame it as cost-saving or margin-loss. If they resist, pivot the primary buyer to the SMB and sell firms a white-label version.
3. Assumption: Entity resolution across bank feeds and QBO can hit accuracy high enough to be trusted. How to test: Get 5 real chart-of-accounts exports, run resolution, hand-audit every cluster. Needs to be near-perfect on false clears specifically.
4. Assumption: The state-threshold angle is a genuine differentiator and not something Track1099 already surfaces at filing time. How to test: Run a live 1099 batch through two incumbents in January and see what they warn about.

Risk flags

1. Platform dependency / incumbent absorption: Intuit could ship “W-9 missing” warnings into QBO as a checkbox feature and vaporise the wedge. Intuit’s 2026 App Partner Program push cuts both ways — better API access, but also a signal they’re paying attention to this surface.
2. Seasonality: The pain peaks in January. A subscription that only feels valuable for six weeks a year churns hard in Q2. The whole product design has to fight this by being visibly useful in March.
3. Regulatory drift: The threshold is inflation-indexed from 2027, and more states will conform over time — which slowly erodes the state-mismatch differentiator. The trap narrows as states catch up.
4. Advice-liability perception: Getting close enough to tax determination that a customer treats your flag as advice. Needs careful product language and the accountant kept in the loop.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder who can do entity resolution properly,
                        paired with (or who is) someone fluent enough in US
                        information reporting to write the content wedge credibly.
Time to revenue:        8–10 weeks (pre-sell to bookkeeping firms before January)
Capital to launch:      $8–15K
Top 3 assumptions to validate first:
  1. W-9 collection behaviour actually loosened post-threshold — 25 bookkeeper interviews
  2. Bookkeeping firms buy prevention rather than billing the scramble — pitch 30 firms
  3. Entity resolution accuracy on real messy ledgers — hand-audit 5 client exports
Kill criteria:
  - Abandon if <15% of 25 interviewed bookkeepers report any change in W-9
    collection policy since January 2026 — no behaviour change means no trap
  - Abandon if Intuit ships native cumulative-threshold warnings in QBO before v1
  - Abandon if entity-resolution false-clear rate exceeds 2% on hand-audited
    real ledgers — a missed crossing is worse than no product

15. Next step — 1-week validation sprint

• Day 1–2: Build the free State Threshold Checker as a single static page. It takes 2 hours and it’s the validation instrument, the lead magnet and the content hook simultaneously. Post it in r/Bookkeeping and r/Accounting framed as “the $2,000 threshold doesn’t apply in your state, here’s what does.”
• Day 3–4: Pull 300 firms from the QuickBooks ProAdvisor directory advertising 1099 services. Send a plain-text email asking one question: “Since the threshold went to $2,000, have your clients stopped collecting W-9s from small vendors?” No pitch, no demo. Just the question.
• Day 5: Decide on two falsifiable numbers. Go if (a) ≥15% of respondents confirm loosened collection behaviour, and (b) the checker page draws ≥300 uses with ≥5 unprompted “can this watch my vendors all year?” replies. No-go if the bookkeepers uniformly say nothing changed — that outcome means the entire premise is wrong and I should stop, not iterate.