inBeat sales analyst agent

Every sales question was a request to somebody else. How is this campaign actually converting, which source produces meetings that close, what does next month look like if the last six weeks repeat.

Each answer lived in a different tool: Google Analytics, Pipedrive, the ad platforms, Calendly, the meeting note-takers. So the answer was always the same shape. Someone exports something, someone else joins it to something else, and two days later the question has moved on.

What I built

A custom MCP server that puts all of those sources behind one interface, so the team could ask questions directly in Claude and get an answer from their real data. Each source is exposed as tools rather than copied into a warehouse, so nothing goes stale between syncs.

The point is the cross-source question. Attribution only means anything when ad spend, the session, the deal and the meeting are joinable in one place. Forecasting runs off the live pipeline rather than a spreadsheet someone updated last month, and a report gets generated for the question actually being asked instead of picked from a fixed menu.

Why not another dashboard

I built the dashboard too, for the views that genuinely are the same every week. But a dashboard answers the questions you had when you built it, and the useful questions are the ones nobody anticipated.

Exposing the sources as tools moves the flexible part to where flexibility is cheap. The question changes constantly. The interface does not have to.

It also changed who could ask. The people with the questions were not the people who could write the query, and that gap is what turned every question into a two-day round trip.

I have not got a usage number for this one, so I am not going to claim one.