Skip to content

For client reporting

Write every client report with the why already in it.

Write every client report with the why, real numbers, last month, and open promises already in it.

Armbrain gathers the numbers from each client's apps, then adds what you decided and promised in meetings, so the report tells the client what happened and why.

Start FreeWatch it work

See it work

Watch it remember.

Pick a demo. Each starts with a question and ends with an answer you can check.

More examples, each with a fictional client:

Build the monthly recap
  1. Draft Copperleaf Bakery Co.'s September report for Jordan. I want revenue, traffic and email, and tell me what drove the month.
  2. switch_clientCopperleaf Bakery Co.
  3. briefingmonthly_reportSeptember4 weekly GA4 snapshotsStripe totals
  4. briefingcampaign_historyKlaviyo5 sends

  5. The September report for Jordan is drafted.

    Revenue: online sales rose 9 percent on August, and refunds held at 1.2 percent of payments.

    Traffic: 31,600 sessions across four weeks, up 7 percent.

    Email: the pumpkin loaf pre-order send was the best of 5 Klaviyo sends, with a 4.6 percent click rate.

    The story: the pre-order push you and Jordan agreed on Sep 3 lines up with the revenue rise.

    Check revenue in Stripe and the email numbers in Klaviyo before you send it.

Report on the pipeline
  1. For Fieldstone Software's monthly report, how did deals and the nurture emails do in September? Luis sees it Thursday.
  2. switch_clientFieldstone Software
  3. relationshipscrm_reportHubSpotread-onlySeptemberby source
  4. search_memoryActiveCampaignSeptember campaigns3 found
  5. briefingcommitment_audit3 open1 for Luis

  6. Here is the sales section for Luis.

    Deals: 14 closed in HubSpot in September, 9 won and 5 lost.

    By source: webinar leads won 5 of 6, and referrals won 2 of 4.

    Email: the trial nurture series had a 3.8 percent click rate, the best of the 3 ActiveCampaign campaigns.

    Open promise: on Sep 12 you told Luis you would add loss reasons. Price was the reason on 2 of the 5 lost deals, and that is now in the draft.

    Check the deal counts in HubSpot before Thursday.

Add the meeting story
  1. Finish Lumen Health Clinic's September report for Dana. Include what we decided in meetings and what is still open, then draft the email that goes with it.
  2. switch_clientLumen Health Clinic
  3. briefingmonthly_reportSeptember3 Granola meetings4 weekly GA4 snapshots
  4. briefingcommitment_audit5 open1 at risk
  5. briefingdraft_followupDanaSeptember report
  6. Waiting for your OK · 1 draft

  7. The report and the email to Dana are ready for you to read.

    Decided this month: the flu shot page went live Sep 8, and the Saturday hours campaign starts Oct 5.

    The flu shot page drew 2,150 page views in its first three weeks.

    Still open: you owe Dana the October content calendar by Oct 3, and it is at risk.

    Read the draft first. It waits for your OK before anything is sent.

Demo 1 of 4

Claude

Write this week's update

  1. Switch to Brightpath Learning and write this week's update for Maya. Use GA4, the Mailchimp send and what we decided on Tuesday's call.
  2. switch_clientBrightpath Learning
  3. briefingweekly_summaryWeek of Sep 22GA4 snapshot1 Mailchimp send
  4. search_memorydecisionslast 7 days2 found

  5. Here is the weekly update for Maya.

    Traffic: 9,400 sessions, up 6 percent on the week before. The course pages brought in most of the gain.

    Email: the Tuesday Mailchimp send went to 12,800 subscribers, with a 41 percent open rate and a 2.4 percent click rate.

    Decided on Tuesday: the free webinar moves to Oct 14, and the October course launch comes first.

    Check the numbers in GA4 and Mailchimp before you share this with Maya.

Fictional client example. Real answers use your data.

Plug every app into Armbrain

From the first number to the final report, one mind has it.

Armbrain reads from 31 apps today. Connect the analytics, email, CRM and revenue tools each client uses, and every report starts with their real numbers.

and 25 more

See every integration

Try these

Copy a prompt. Swap in your client.

Paste one into Claude with Armbrain connected. Each links to the full use case.

  • Apps: Google Analytics 4 (GA4), Mailchimp.

    Change these first:

    CLIENTCOMPANY = Brightpath Learning CLIENTCONTACT = Maya Armbrain, switch to CLIENTCOMPANY and write this week's update for CLIENTCONTACT from GA4, the Mailchimp send and our last call.

    Weekly client report
  • Apps: Stripe, Google Analytics 4 (GA4), Klaviyo.

    Change these first:

    CLIENTCOMPANY = Copperleaf Bakery Co. CLIENTCONTACT = Jordan Armbrain, draft last month's CLIENTCOMPANY report for CLIENTCONTACT from Stripe revenue, the GA4 weekly snapshots and every Klaviyo send. Tell me what drove the month.

    Monthly results recap
  • Apps: Granola.

    Change these first:

    CLIENTCOMPANY = Lumen Health Clinic Armbrain, before I send CLIENTCOMPANY's monthly report, list every promise from this month's meetings and flag any that slipped.

    Keep every promise you made
  • Apps: HubSpot, Gmail.

    Change these first:

    CLIENTCOMPANY = Fieldstone Software CLIENTCONTACT = Luis Armbrain, draft the email that goes with CLIENTCOMPANY's monthly report to CLIENTCONTACT, in my voice. Show it to me before anything is sent.

    Follow-up email in your voice

Fictional client names. Replace with your own.

One mind per client

Each client's numbers stay in their own mind.

Every client has its own mind, with its own connected apps, meetings and promises. Ask for Brightpath Learning's report and you get Brightpath's numbers, not another client's.

Illustration. Client names are fictional.

Works where you work

Change AI tools. Keep the memory.

Armbrain works in Claude Desktop, claude.ai, Claude Code and Cursor. Your reporting history and app connections live in Armbrain, not in one chat window.

  • Last month's report is still there when you write this month's.
  • Your app connections stay put when you change tools.
  • Scheduled briefings can arrive by email or in Slack.

Built to be careful

Each client stays separate, and drafts wait for you.

Each client stays in its own mind. GA4, HubSpot, and Stripe are read-only. Stripe shares totals only. Report emails are drafts that wait for your OK.

Each client in its own mind

Every client gets a separate mind. Switch by name, and what you save for one client stays with that client.

Read, don't rewrite

Most connections only read. The few that add something, such as Notion recaps on pages you choose, say so on their own page.

Drafts wait for you

Follow-up drafts are shown to you for approval by default, and meetings are booked only after you confirm who is invited. You can change the email setting.

How we handle security Privacy policy Sub-processors

Questions

Questions, answered.

Is each client's information kept separate?
Yes. Each client has its own mind. When you ask for a report, Claude works from that client's apps, meetings and notes only.
Where do the numbers come from?
From the apps you connect for that client. GA4 provides weekly traffic snapshots. Stripe gives monthly totals, and HubSpot is read-only. Always check the numbers in the source app before a report goes out.
How does the report know what happened in meetings?
Decisions and promises come from meeting notes and transcripts you bring in, from tools like Granola, Zoom or Fireflies. A report only uses what is stored, so if a meeting is missing, the story will be too.
Will it send reports to my clients?
Report emails wait for your OK by default. You can change this setting anytime.
What if the app I use isn't listed?
Request apps at /integrations/request. You can also paste notes or upload files manually.
What does it cost?
See pricing at /signup.

Write your next client report with the story already in it.

Connect one client's analytics and email tool, then ask Claude for this week's update.

Start FreeSee pricing