1
2 Comments

Why I threw away the frontend on my first product

My first product was called Cheap Analytics. The goal was simple: easy to set up, designed for people running multiple side projects, and cheap as chips. With a few little differences, it looked like every other analytics tool. The main distinction was in the name, and the one extra feature was a weekly AI summary email that told you what happened across your sites so you didn't have to log in.

That email was the thing people actually liked. A simple analysis of what was happening, shared where you were. The most useful part of the product was the part that meant you never had to open the product.

Around the same time, MCP started taking off and I was spending most of my day inside Claude Code. I wanted my AI analysis there, not just summarising your analytics once a week, but querying them whenever it needed to. Not a dashboard with an AI bolted on, but analytics where the AI is the interface.

So I started from scratch, rebuilding it as an API with 37 MCP tools optimised for how agents work, and giving it a new name. Traffic sources, page performance, date comparisons, geographic breakdowns, custom events, the lot. Your agent connects, queries what it needs, and when a human actually wants to see a chart, the agent generates one on the fly. Design for what an LLM needs: focused, structured, token-saving output.

There's still a website for signing up and managing API keys, but the core product has no GUI. Your agent is the interface.

A month in now. Free up to 2,500 events/month, €9.99/mo for 100K. Tracking script is 2KB, setup is about two minutes if you're already in Claude or Cursor.

This obviously only works if you already have an AI agent running. If you want to check your traffic the old-fashioned way, Plausible and Fathom are great. But if you're in Claude Code all day anyway and you'd rather your agent just knew your traffic without you alt-tabbing to anything, that's what this is.

https://lodd.dev if you want to try it.

on May 12, 2026
  1. 1

    That insight about the useful part being the bit you never had to open is the kind of thing you only spot once people are actually using the product. The MCP-first call is bold. How are you handling the subscription gate with no UI? Does the agent just surface a 'free tier exhausted, upgrade at lodd.dev' message, or have you baked the upgrade flow into the MCP tools themselves? I'm about to launch a small finance app and have been wrestling with the inverse problem: lots of UI, trying to make pricing feel invisible.

    1. 1

      Good question! While Stripe just launched payment-for-agents setup, I've not gone that far yet, instead it will surface as limit reminder as you use up. I also send emails that get triggered at 50% ,75% and 100% usage. Of course, there is also a get_usage MCP tool so you can check or build it into your managed agent flows.

      Curious why you're trying to make pricing invisible? Especially for a finance app, I'd said you have a real opportunity to tie pricing to genuine value created?

Trending on Indie Hackers
I've been building for months and made $0. Here's the honest psychological reason — and it's not what I expected. User Avatar 177 comments 7 years in agency, 200+ B2B campaigns, now building Outbound Glow User Avatar 65 comments This system tells you what’s working in your startup — every week User Avatar 53 comments 11 Weeks Ago I Had 0 Users. Now VIDI Has Reviewed $10M+ in Contracts - and I’m Opening a Small SAFE Round User Avatar 46 comments The "Book a Demo" Button Was Killing My Pipeline. Here's What I Replaced It With. User Avatar 29 comments My AI bill was bleeding me dry, so I built a "Smart Meter" for LLMs User Avatar 18 comments