Crutan is built for agencies. Connect every client's GA4 property to a single account. Each client gets their own isolated context, daily AI-written briefings, and a live chat interface backed by real-time data. Your team answers client questions in seconds. The reports write themselves.
Free during early access · Read-only GA4 access · No credit card
Clients
B2B SaaS
The Good Cup
Ecommerce
Agency
Publishing
Sessions
+18%
Revenue conv.
+0.4pp
Today's Briefing
Strong Thursday. Email campaign drove 34% of revenue at a 3.8% conversion rate — nearly double site average. Mobile checkout drop-off worth investigating before the weekend…
The agency reporting trap
Every week, someone on your team logs into GA4 for each client. Pulls metrics. Reformats them into a deck or PDF. Writes a summary. Emails it. Then answers three follow-up questions that could have been answered in thirty seconds with live data. Multiply that by ten clients and you've burned a working day on something a well-configured AI could handle overnight.
Average time agencies spend per week on client analytics reporting, per 10 clients
That's a full working day, every week.
Time to onboard a new client property in Crutan and start receiving daily briefings
Per client, one time.
Time to answer a client's follow-up question using Crutan's live GA4 chat
No report-building required.
The workflow
Onboarding a new client takes under five minutes. From there, Crutan handles the daily and weekly reporting automatically.
One OAuth flow. Read-only access. Crutan links to the client's GA4 property and optionally their Search Console.
A short AI conversation captures the client's industry, revenue model, audience, and KPIs. This shapes every briefing and chat response.
Every morning, Crutan writes and delivers the client's AI briefing. Weekly rollups arrive every Friday. Your team doesn't touch it.
When a client asks a follow-up, open their property in Crutan and query their live data. You have an answer in thirty seconds.
The account model was designed with agencies in mind from day one. A single Crutan login manages every client property you connect. Switching between clients in the dashboard is instantaneous — one click changes the active property and every AI response, report, and conversation thread is immediately scoped to that client.
Client data is isolated at the database level. There is no setting to enable this — it is how the product works. A question about one client will never surface data from another. A briefing for one client will never reference another's numbers. Each client lives in their own context and it never bleeds.
Each client has its own business name, display label, and industry context
Each client's onboarding is independent — KPIs, audience, revenue model
Each client's briefings, chat history, and reports are stored separately
Each client can have its own delivery address and schedule
Add, pause, or remove clients without affecting others
Each client property is a sealed context
· B2B SaaS
Lead gen form completions up 12% vs last week. Organic driving 41% of new MQLs…
· Ecommerce · Coffee
Thursday strong. Email campaign at 3.8% conv. rate. Mobile checkout worth investigating…
· Creative Agency
Case study page up 28%. Top referrer: Dribbble. Time on page avg 4m 12s…
Each property has its own context, briefings, and chat history.
None of it is ever shared between clients.
Monday Briefing — Hartwell & Co.
B2B SaaS · KPI: MQL conversions
Action items
Monday Briefing — The Good Cup
Ecommerce · KPI: Revenue & AOV
Action items
Same data patterns. Same AI. Completely different analysis — because each client's context shapes every word.
A briefing for a B2B SaaS company reads completely differently from a briefing for an e-commerce brand — even if their traffic numbers look identical. The AI uses each client's business context to decide what matters, what to flag, and what to recommend.
Context is set once during onboarding and permanently attached to every response for that client. Briefings reference the client's specific KPIs, revenue model, and audience — not generic analytics advice. Your B2B client's briefing talks about lead quality. Your e-commerce client's briefing talks about conversion rate and AOV.
What each client context includes
Business name and display label
Industry and revenue model (SaaS, ecommerce, services, etc.)
Target audience and customer type
Primary and secondary KPIs
Website URL (with scraped page summary)
Custom delivery schedule and timezone
Crutan's live chat queries the active client's GA4 data and Search Console in real time. Every question is answered with that client's actual numbers — not estimates, not averages, not generic advice.
Conversation history is stored per client. Every thread is saved to the sidebar, organized by property. Pick up any past conversation, reference old analyses, or start a new thread — all while staying in the context of the client you're looking at.
The AI is explicitly anchored to the active client. It will never reference another client's data. Switch to a different client and the entire interface — history, context, and live queries — switches with it.
Which landing pages drove the most MQLs last month?
Looking at Hartwell & Co.'s conversion data for March:
Top MQL-driving pages: 1. /pricing/compare — 31% of all conversions (up from 18% in Feb) 2. /features/integrations — 24% 3. /blog/saas-onboarding — 19% (new entry)
The Compare page jumped significantly — your February pricing change seems to have made it more compelling to buyers actively evaluating. Worth promoting in campaigns.
What's the form completion rate on /pricing/compare?
Form completion on /pricing/compare: 34.2% — well above your site average of 18.7%.
Page visitors who scroll past 75% convert at 51%. The drop-off is mostly users who leave before reaching the form. A sticky CTA on mobile could push that significantly.
Every feature is available for every connected client. No tier gates. No add-ons. Add a client, configure their context, and they immediately have the full capability.
Each client receives a morning briefing written from their specific GA4 data and shaped by their business context. Delivered to their inbox or phone.
Every Friday, a 7-day summary covering trends, channel performance, top content, and recommendations tailored to the client's KPIs.
Conversational AI with real-time access to the client's GA4 Data API and Google Search Console. Any question, answered with their actual data.
All chat threads are saved and organized by property. Reference past analyses. Pick up where you left off. Never lose a past answer.
Set delivery time, timezone, and channel (email, SMS, or both) independently per client. Each client gets their briefing on their schedule.
Crutan requests the minimum read-only OAuth scope for GA4 and Search Console. Nothing is written. Nothing is modified. Safe to connect on behalf of clients.
There is no hard limit. You can connect as many GA4 properties as you need — one per client. Each property is fully independent with its own business context, onboarding, briefing schedule, and conversation history. Switching between clients takes one click.
Never. Crutan's architecture isolates every property at the database level using row-level security. When you're viewing a client, every AI response, briefing, and chat query is scoped exclusively to that client's GA4 property. There is no crossover. This is a core design principle, not a setting.
Yes. Briefings are delivered directly to the client's email or phone via SMS — you configure the delivery address during onboarding for each property. You can also access all briefings from the Crutan dashboard on their behalf.
Yes. Each client property can optionally connect its own Google Search Console account. Once connected, the AI has live access to that client's search queries, keyword rankings, impressions, CTR, and page-level SEO performance — all scoped to that client.
During onboarding for each property, you run a short AI-guided conversation that captures the client's business name, industry, revenue model, target audience, KPIs, and website URL. Crutan also scrapes a summary of the client's site pages. This context is permanently attached to every briefing, chat response, and analysis for that client — so reports for an e-commerce brand read completely differently from reports for a B2B SaaS client, even if the traffic patterns look similar.
The AI has live access to the full GA4 Data API for each connected property: sessions, users, new users, conversions, bounce rate, session duration, top pages, traffic sources (channel, source/medium, campaign), custom events, and custom dimensions. It can run any combination of metrics and dimensions over any date range. It can also query real-time active users.
Crutan requests read-only OAuth access to GA4 and Search Console. It never writes to, modifies, or deletes any analytics data. The access scope is the minimum required to read reporting data. You can revoke access at any time, per property, from either Crutan's settings or the client's Google account.
Looker Studio builds dashboards that clients have to interpret themselves. GA4's reporting requires logging in and building queries manually. Crutan writes the briefing, draws the conclusions, and delivers the answer — clients and account managers get a plain-English explanation of what happened and what to do next, without opening a dashboard. And when a client asks a follow-up question, you can answer it in seconds using live chat.
White-labeling is not available in the current version. Briefings are sent from Crutan's delivery infrastructure. We're evaluating branded delivery as a future agency feature based on demand.
Every Friday, each connected client property receives a 7-day rollup covering traffic trends, channel performance, conversion rate, top content, week-over-week comparisons, and prioritized recommendations for the following week. The rollup is generated from the client's actual GA4 data and filtered through their specific business context — so a retail client's rollup highlights revenue and product performance, while a content site's rollup emphasizes engagement and organic search.