Detect the stack. Synthesize the pitch.

Three methods working together. Website tag scan for anything exposed in HTML, script tags, network calls, or CDN paths. JD scan parses public job descriptions for explicit tool mentions ("experience with Amplitude") — this catches internal tools that never appear on the marketing site. GitHub org scan checks public repos and package manifests for SDK imports. Most enterprise tools that don't show in the website tag get caught by JD or GitHub. SPAs that load tools post-auth are the hardest to catch — for those we rely heavily on the JD signal.

We've been continuously scanning since launch. Solo plans see 30 days of change history; Team sees 12 months; Pro sees everything. The most useful window for outbound is the last 60 days — fresh enough that the buying decision is still open, old enough that you can see the trajectory. The stack timeline in the brief defaults to that window, with a toggle for longer history.

Honest answer: BuiltWith's basic tier is cheaper than ours ($295/mo for API access vs our $599/mo Pro), and Wappalyzer's API starts at $250/mo. If you only need raw tech detection data and don't care about brief synthesis or signal cross-referencing, BuiltWith is a fine choice. Mama charges more because we bundle tech detection with five other signal categories, the synthesis layer, the brief, the workflow integrations. We're optimized for outbound teams replacing 3–5 tools, not data analysts replacing one. Full pricing breakdown →

On Pro, yes. Define the tool's detection fingerprints — script tag patterns, package import strings, JD keyword patterns — and Mama starts tracking it across all accounts in your workspace. Useful for category-specific tools we haven't prioritized yet (compliance tools for fintech, specialized analytics for healthcare, etc.). On Solo and Team, drop us a request at [email protected] — we add new tools roughly every week, and customer requests jump the queue.

Yes — that's a major part of our roadmap. Programmatic /tech/[slug] pages for the top 500 technologies ship in the next few months, expanding to 25,000+ at maturity. Each page will show: who uses it, recent adopters, recent churners, alternatives, head-to-head comparisons, and a sample of companies in your ICP that recently changed their relationship to it. Same shape BuiltWith built their moat on, with the synthesis layer added.

The three-method verification (tag + JD + GitHub) is the main defense. A tool only enters the brief when at least two of three methods confirm it. When only one source detects a tool, we flag it as "single-source · low confidence" rather than hiding it — your rep sees both the signal and the caveat. If a customer disputes a detection we got wrong, we fix it within 24h and re-scan their workspace. Honest false-positive rate across our last 30 days: 0.7% of detected tools.