Where these 33 reports land
Build it7
Scope it13
Keep it13
Category report
Analytics
33 products ranked by how much of their useful core an AI coding agent can reproduce: 7 strong builds, 13 scoped builds, and 13 weak replacements.
How the score breaks down here
- Interface
- 48
- Core workflow
- 49
- Data access
- 46
- Operations
- 21
- Trust & safety
- 43
47/100 average buildability
Why people keep paying here
- scale infra31 of 33 reports
Reliability at the vendor's scale is an operations problem, not a prompt.
- execution polish21 of 33 reports
The last 20 percent is sync, migration fidelity, speed, and edge cases.
- integrations6 of 33 reports
Connectors, OAuth flows, and vendor API changes require constant upkeep.
The typical achievable core in this category: ingest a known data source, calculate a focused metric set, and render a useful dashboard.
Build it
Umami Cloud
The software is open source, so the cloud subscription is mostly paying for managed hosting, upgrades, and not touching a server.
Build it
HitKeep Cloud
The subscription is managed hosting of the same MIT-licensed application, so an agent does not need to reproduce HitKeep. It can deploy the official binary or container in a focused implementation; the real gap is upgrades, backups, email delivery, monitoring, and being on call for the analytics box.
Build it
ReSlug
The redirect is a slug, a lookup, a 302, and a row in a table · Cloudflare Workers with KV and D1 does the whole job on the free tier, and the QR code is one library call. Routing rules, expiry, and password links are an afternoon more. What you cannot build in a sitting is permanence: your links only outlive the project if you keep renewing the domain and the account. The wrinkle with ReSlug specifically is that its free plan already includes a custom domain and real analytics at personal scale, so the DIY build is competing with 0 USD rather than 9 · build it for the ownership, not the savings.
Build it
Bitly
A slug, a lookup, a 302, and a row in a table. Cloudflare Workers plus KV and D1 does the whole job on the free tier, and QR codes are one library call. The only thing you are really buying is that bit.ly resolves links created in 2012 and will presumably still resolve them in 2032, which is an institutional promise rather than a technical one. If the links are going in a magazine ad or on packaging, that promise is worth something. If they are going in this week's newsletter, it is worth nothing, and Growth is 420 USD a year.
Build it
Fathom Analytics
A simple privacy analytics clone is very buildable; the paid service is hosted compliance posture, uptime, data retention, and polished reporting.
Build it
Plausible
Basic pageview/event analytics are easy, and Plausible's own code is open source; the paid value is hosted reliability, maintenance, and support.
Scope it
Matomo Cloud
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Matomo Cloud, run first-party web analytics with goals, campaigns, and user-owned data. The hard boundary is mature analytics depth, privacy controls, hosted operations, and premium plugins, plus data pipeline reliability and analytical depth.
Scope it
Baremetrics
The visible subscription analytics loop is buildable, but a credible replacement needs more than the first screen. Baremetrics earns its keep through ingestion, storage, reliability, so expect a substantial build and a narrower personal scope.
Scope it
Cabin
The visible privacy web analytics loop is buildable, but a credible replacement needs more than the first screen. Cabin earns its keep through ingestion, storage, reliability, so expect a substantial build and a narrower personal scope.
Scope it
GoSquared
The visible web analytics + customer data loop is buildable, but a credible replacement needs more than the first screen. GoSquared earns its keep through ingestion, storage, reliability, so expect a substantial build and a narrower personal scope.
Scope it
June
The visible B2B product analytics loop is buildable, but a credible replacement needs more than the first screen. June earns its keep through ingestion, storage, reliability, so expect a substantial build and a narrower personal scope.
Scope it
Pirsch
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Pirsch, collect cookieless page views and custom events with compact dashboards. The hard boundary is hosted reliability, privacy operations, apis, email reports, and scale, plus data pipeline reliability and analytical depth.
Scope it
Usermaven
The visible product + web analytics loop is buildable, but a credible replacement needs more than the first screen. Usermaven earns its keep through ingestion, storage, reliability, so expect a substantial build and a narrower personal scope.
Build it
Simple Analytics
Pageview analytics, events, dashboards, and exports are very buildable; paid value is hosted privacy posture, reports, reliability, and support.
Scope it
ChartMogul
The visible subscription analytics loop is buildable, but a credible replacement needs more than the first screen. ChartMogul earns its keep through ingestion, storage, reliability, so expect a substantial build and a narrower personal scope.
Scope it
LnkFlow
A short link that 302s, logs the click, and injects UTMs is genuinely straightforward on Cloudflare Workers and KV, and the prompt below builds exactly that. What is not straightforward is the loop back out to the ad platforms. Meta and Google bid against the conversion events you send them, and since ATT the browser pixel misses a large share of purchases, which is the entire reason the Conversions API and offline conversion import exist. Closing that loop means persisting fbclid and gclid at redirect time, carrying that identity to a sale that happens days later on another device, posting a Purchase with a stable event_id so it deduplicates against the pixel, rebuilding fbc in Meta's fb.1.{timestamp}.{fbclid} form, importing offline conversions to Google on gclid, gbraid, or wbraid, and reversing all of it on refund. Every one of those fails silently. That is the expensive part: the dashboard still shows clicks while the bidder optimizes against nothing.
Scope it
DataFast
The pageview half of DataFast is the same contained build as Plausible or Umami. The revenue half is where it stops being a contained effort. Attribution is only worth anything if the anonymous visitor who found your launch post on a phone is still recognisably the customer who pays from a laptop three weeks later, and that stitching is exactly what an agent will hand you a naive version of. A localStorage id plus an email match at signup does get you a channel table that is directionally right for a single-domain solo product, which is genuinely worth having. It also quietly under-counts every cross-device path, every privacy browser that clears storage between visits, and every customer who pays with a different address than they signed up with. You can build the dashboard in a contained effort. Trusting it enough to move ad spend is the part that keeps costing you weekends.
Scope it
Grow or Die
An agent can build the honest personal version: a first-party tracker, a Stripe webhook, an OpenAI usage wrapper, and a SQLite join keyed by your own account ID. That is enough to show which customers make money. The paid product starts earning its fee when the inputs stop being tidy. Analytics exports drift, refunds arrive late, model prices change, streaming calls fail after consuming tokens, and anonymous visitors do not naturally become the same people who paid. A focused build can give one founder a useful ledger for one stack. Matching Grow or Die's connector coverage, SDKs, missing-data discipline, retention, and production reliability is ongoing analytics infrastructure, not a prompt.
Scope it
Metorik
The good news: every number Metorik shows you is already sitting in your own WooCommerce database, so nobody is gatekeeping your data. An agent can pull orders, customers and products through the Woo REST API into a local store and give you revenue charts, cohort and repeat-purchase views, product breakdowns and CSV exports in a focused implementation. The gap is everything that is not a chart: abandoned cart tracking needs a script on your storefront plus a capture endpoint, email automations need a sending domain and deliverability you do not have, and segment-driven campaigns need a rules engine that is a project of its own. Large stores also punish naive syncs, Metorik has spent years making that part boring. Build the dashboard, keep paying for the email side if that is why you signed up.
Scope it
Piwik PRO
The visible privacy analytics suite loop is buildable, but a credible replacement needs more than the first screen. Piwik PRO earns its keep through ingestion, storage, reliability, so expect a substantial build and a narrower personal scope.
Keep it
Crazy Egg
Do not mistake the interface for the product. Crazy Egg's durable value is ingestion, storage, reliability, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
Keep it
Amplitude
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Amplitude, build a bounded event explorer for funnels, cohorts, and retention on one product. The hard boundary is behavioral data platform, experimentation, identity, governance, and scale, plus data pipeline reliability and analytical depth.
Keep it
FullStory
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For FullStory, collect explicit product events and targeted debug snapshots with strong privacy controls. The hard boundary is high-fidelity replay, privacy redaction, indexing, search, storage, and compliance, plus data pipeline reliability and analytical depth.
Keep it
Mixpanel
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Mixpanel, collect a small transparent event stream and build funnels and retention locally. The hard boundary is large-scale ingestion, identity handling, query engine, governance, and product expertise, plus data pipeline reliability and analytical depth.
Keep it
Heap
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Heap, instrument explicit first-party events and avoid automatic capture of unrelated user behavior. The hard boundary is automatic capture engine, identity graph, data science, governance, and enterprise operations, plus data pipeline reliability and analytical depth.
Keep it
Lucky Orange
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Lucky Orange, collect limited consented interaction events and build basic heatmaps for an owned site. The hard boundary is session replay, chat, surveys, funnels, privacy tooling, and always-on ingestion, plus data pipeline reliability and analytical depth.
Keep it
Mouseflow
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Mouseflow, capture a small consented session sample and render a simple playback for debugging. The hard boundary is capture compression, privacy redaction, storage, heatmaps, funnels, and hosted scale, plus data pipeline reliability and analytical depth.
Keep it
Smartlook
Do not mistake the interface for the product. Smartlook's durable value is ingestion, storage, reliability, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
Keep it
Woopra
Do not mistake the interface for the product. Woopra's durable value is ingestion, storage, reliability, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
Keep it
PostHog
First-party collection and a dashboard that answers your top five questions is achievable solo, and PostHog's free tier covers a million events a month before you pay anything. What the bill buys past that is the rest of the platform: session replay, feature flags, SQL over years of events, and ingestion that stays correct while your event schema drifts underneath it.
Keep it
NicheMaps
You can build a personal watchlist that checks a handful of store listings and ad-library pages, but NicheMaps' value is a continuously refreshed catalog of millions of iOS/Android apps with ad-status, IAP, velocity, and creative evidence you cannot rebuild.
Keep it
Vernigo
You can build filters, bookmarks, and an outlier score over a small set of YouTube channels, but Vernigo's product is the continuously refreshed corpus: millions of videos, channel baselines, niche-level supply and demand signals, and ranking data improved by how thousands of users interact with the library. A one-shot app can reproduce the interface and formula, not the dataset that makes the results useful.
Keep it
AppsFlyer
You can absolutely build a click tracker: log clicks, generate deep links, receive install pings from your own SDK, join them in SQLite. What you cannot build is the reason AppsFlyer exists, which is that Meta, Google, TikTok and Apple do not hand raw attribution data to random self-hosted endpoints. Those self-attributing networks report only to certified measurement partners, and SKAdNetwork/AdAttributionKit postbacks are aggregated and privacy-thresholded by design. Add install fraud detection, which is a data problem across billions of devices rather than a code problem, and the gap stops being about engineering effort. The honest consolation build is a first-party attribution tracker for channels you control: your own links, emails, influencer codes, organic web to app.