askbowtie

The Problem

Site data lives in silos: analytics in one dashboard, Google Ads in another, Search Console in a third, JS errors and uptime nowhere useful. When you run sites with an AI agent, there is no single place it can query to answer "is anything broken, and is it costing me conversions?" It started as itbroke.dev, a conversion sanity-check, but the real gap was bigger than alerts.

What It Is

An MCP server that joins first-party analytics, conversions, Google Ads, Search Console, JS errors, and uptime into one queryable interface, so Claude Code, Cursor, or any MCP client can answer cross-cutting questions about a site in plain language. Originally launched as itbroke.dev (conversion monitoring), then rebranded and expanded into askbowtie. Built for vibecoders, agencies, and anyone running sites with AI in the loop.

What I Built

Full-stack SaaS with event-sourcing architecture. Session stitching across pageviews, conversion baselines that learn normal patterns, incident clustering, and revenue-impact estimates, then an MCP server layer with OAuth integrations (Google Ads, Search Console) and a lightweight async tracker on top. Multi-surface: marketing site, app dashboard, docs, onboarding, admin panel, and the MCP server itself.

The Outcome

First paying customer acquired from $3 ad spend while still itbroke.dev. Handling real production traffic. Largest solo SaaS build to date, since rebranded to askbowtie as it grew past conversion monitoring into a full site-data layer for AI agents.