What changed
Two things converge: (1) a dev-consultancy owner publicly complained on HN that there is no affordable technographic API beyond BuiltWith and that using the Anthropic API to detect stacks hallucinates; (2) cheap open-weight inference is now production-viable, so the rare ambiguous bundle can be classified for fractions of a cent — but the CORE product needs no LLM at all, just deterministic HTTP fingerprinting.
Why now
The complaint (HN item 48883101) is dated and specific: LLM stack-detection hallucinates and no cheap API fills the gap. Wappalyzer's open-source rules were relicensed/commercialized, leaving a hole for a low-cost drop-in. HYPOTHESIS: the exact size of that hole is inferred from a single complaint, not proven.
Converging signals
PAIN (HN: 'Builtwith is the leader but lacking on tech that isnt front end or JS focused', and 'Ant[hropic] API' hallucinates) × cheap-capability (open-weight inference at production volume, Vercel AI Gateway index). The pain names both the price problem AND the accuracy problem a deterministic fingerprinter directly solves.
Customer pain
Agencies and SDRs prospect by tech stack to tailor pitches (e.g., 'you use X for CI/CD, we can help'). BuiltWith is expensive and weak on backend/infra tech; free Wappalyzer is inconsistent and rate-limited at scale; LLM detection invents stacks. So prospecting is either costly, wrong, or manual.
Who pays
Dev consultancies, SEO/marketing agencies, and B2B SDR/lead-gen teams who already pay for BuiltWith/Wappalyzer/Clearbit-grade data and buy by card. FACT (from input): the complainant runs a dev consultancy and already pays for this class of data. Beneficiary = buyer here, which is clean.
Solved today
BuiltWith (paid, expensive, frontend-biased), Wappalyzer (open-core + paid API), Clearbit/HG Insights/Datanyze (enterprise-priced), or DIY scraping/LLM guessing. Many teams fall back to manually eyeballing a site.
Why current solutions are bad
BuiltWith is priced for volume buyers and thin on non-frontend signals; Wappalyzer's free tier is unreliable and its API isn't cheap; LLM detection hallucinates (the stated pain); DIY is a maintenance treadmill of signatures.
Proposed product
A REST endpoint: submit a domain, StackProbe fetches HTML, response headers, JS bundle paths, cookie names, DNS/MX, and TLS/CDN fingerprints, applies a deterministic ruleset (script src patterns, meta generators, header signatures, cookie prefixes, favicon hashes), and returns detected CMS/analytics/framework/host/CDN/email/CI-hints with a confidence score and the evidence for each detection. Open-weight inference is used ONLY to classify genuinely ambiguous minified bundles — never as the primary detector.
MVP version
One /lookup endpoint, 200 hand-written signatures weighted toward the underserved backend/infra layer (hosting, CDN, WAF, email provider, analytics, CI hints from headers/robots/security.txt), Stripe metered billing, an API key gate, and a public 100-site accuracy benchmark vs BuiltWith/Wappalyzer as the marketing asset. Ship a tiny hosted playground for the 'try one domain free' hook.
30-day build
Build the fingerprint engine + 200 signatures; assemble a labeled 100-site test set (hand-verified); publish accuracy vs BuiltWith/Wappalyzer; stand up Stripe + keys; ship playground and docs. Post the benchmark back to the HN thread and to r/SEO, r/agency, indiehackers.
60-day build
Add bulk/CSV endpoint and a Google-Sheets + Clay/Instantly integration (where SDRs actually live); expand to 500 signatures; add webhook 'stack-change' alerts (a domain switched hosting/analytics) as an upsell; onboard first 20-50 paying keys.
90-day revenue plan
Convert playground/free-tier users to $49/$149 plans; land 1-3 agencies on the $149 tier or annual; add an enrichment-partner/reseller (white-label lookups inside an existing SDR tool). Target $1-3k MRR. HYPOTHESIS on the dollar figure.
Distribution path
Direct reply on the HN thread with the benchmark; SEO/agency and indiehacker communities; a free 'what's this site running' browser extension + public single-lookup page as top-of-funnel; Clay/Instantly/Apollo integration listings; content ('BuiltWith alternative', 'detect backend stack') for the exact search intent.
Pricing hypothesis
$49/mo for 5k lookups, $149/mo for 25k, $0.01/overage — as specified. Add an annual and a metered API-only tier for developers embedding it.
Technical difficulty
Low-to-moderate to start (HTTP fetch + rule matching is a weekend engine) but the REAL work is the never-ending signature maintenance and accuracy at scale — that IS the moat and the burden simultaneously.
Legal / regulatory risk
Low. Fetching public HTML/headers is standard (respect robots/rate limits, no login-walled scraping). No PII, no government portal, no platform owner to deplatform it.
Platform dependency
None material — it calls arbitrary public sites, not one platform's API. Not exposed to marketplace-approval or policy risk.
Founder fit
Moderate-to-good: it's an API/micro-SaaS with card-paying prosumer buyers and demonstrated-value selling (a public benchmark), which matches his preferences and skills. It is NOT the government/forced-buyer shape that is his highest-fit lane — no mandate, no appropriation, no forced buyer — so founder-fit is real but not maximal.
Breakout potential
Moderate. Ceiling is a solid lifestyle/micro-SaaS ($5-30k MRR). Technographics is a real, monetized category, but it is a commoditizing data product with entrenched incumbents; breakout would require a distinctive data angle (best-in-class backend/infra detection + change alerts) rather than being a cheaper BuiltWith.
Final recommendation
CONDITIONAL PROCEED as a small, fast, low-cost validation, not a conviction bet. Do the cheapest thing first: build the fingerprint engine + the public 100-site benchmark and post it to the HN thread and agency communities BEFORE building billing. If the benchmark genuinely beats incumbents on backend/infra detection and ≥10 people ask for access, proceed; if not, kill it — the kill test in the input is the right gate.
Next action
Build the deterministic fingerprint engine against a hand-labeled 100-site set (weighted to backend/infra/host/CDN/email signals) and publish an honest accuracy comparison vs BuiltWith and Wappalyzer; use that single artifact to test both accuracy and willingness-to-pay in the HN thread.