Client reporting for agencies

Reporting your client actually reads

Enter the period’s numbers and three lines of context. Get back a designed, written report that explains what moved and why — grounded only in the figures you supplied, and frozen the moment you publish it.

No integrations to connect. Works from the numbers you already pull.

reports.isonicmedia.ai/r/aveline-dental
Aveline Dental · Period 1218–31 Aug

Implant enquiries grew while the cost of winning them fell.

Revenue

$83,295

+24.6%

Cost per enquiry

$141

−21.4%

Organic sessions

24,820

+18.4%

Conversions

372

+19.6%

Organic sessions by day

Everything it measures, in one document

Organic sessions, Cost per acquisition, Return on ad spend, Keyword rankings, Conversion rate, Engagement rate, Impression share, Click-through rate, Reach, Leads, Revenue, Average position

What a report covers

Six things, in one document

Not a dashboard with everything on it. The things a client asks about, in the order they ask them.

S

Search

Sessions · Conversions · Rankings · Impressions · Position

Where the demand came from, whether it converted, and what moved in the index behind it.

See it in a report
P

Paid media

Spend · CPA · ROAS · Conversions · Impression share

Efficiency reported alongside volume, so a big month on spend is never mistaken for a good one.

See it in a report
So

Social

Reach · Engagement · Followers · Link clicks

Distribution and engagement quality, kept apart from the channels that actually close business.

See it in a report
T

Targets

Set at the start · Measured at the end

What was promised for the period and exactly where it landed — ordered worst-first, so nothing hides.

See it in a report
E

Evidence

Screenshots · Captions

The platform screens behind the numbers, captioned, so a figure can be checked rather than believed.

See it in a report
Q

Questions

Threads on any figure · Internal notes

The client asks on the number itself. Your internal notes on the same thread stay invisible to them.

See it in a report

How a report is built

Six steps, and only two need you

Dates follow on from the last period, last period’s numbers are pre-filled and the writing is one pass. What is left is the numbers and ninety seconds of context.

  1. 01

    Client

    Who it is for

  2. 02

    Period

    What it covers

  3. 03

    Metrics

    What moved

  4. 04

    Context

    Why it moved

  5. 05

    Written

    Grounded in both

  6. 06

    Published

    Frozen for good

Monday, 9am

Last period is already filled in

Open a new period and the dates follow on, the cadence is the client’s own, and every previous figure sits in the comparison column waiting.

Ninety seconds

Three questions turn numbers into a read

What was the goal, what did you ship, what happened that was not you. That is the whole difference between a data dump and an account read.

One pass

Written only from what you entered

Anything the writing states that cannot be traced back to your figures is flagged for you before publishing — not discovered by your client afterwards.

Sent

Frozen the moment it is published

The database refuses to change a published report. The one you sent in March reads today exactly as it did in March, and always will.

What changes

The fortnightly report stops being the job nobody wants

9

Minutes to produce one

Once the numbers are to hand.

0

Statistics it can invent

It only ever sees your figures.

3

Channels in one document

Search, paid and social together.

100%

Reports kept, forever

Frozen, never edited or removed.

“Organic visibility strengthened while paid acquisition became more efficient.”

Every report opens with one sentence a client would repeat to their business partner. The numbers sit underneath it, not in place of it.

Read the whole report

Included in every report

  • Period-on-period change on every figure
  • Targets shown as progress, worst-first
  • The last four periods, side by side
  • Captioned screenshots as evidence
  • A PDF built from the same page

What is guaranteed

Three promises, each enforced somewhere you cannot click past

Isolated by default

Every read is filtered in the database by the signed-in identity. One client cannot see another’s report, and internal notes never leave your side of the thread.

Immutable once sent

Publishing writes a snapshot and a trigger refuses every later edit. A correction is a new period, never a quiet rewrite of what was already read.

White-labelled end to end

Your domain, your logo, your name on the cover and in the sign-in. Nothing in the experience a client touches names a vendor.

Enforced in the database, not in the interface — so it holds even when the interface is wrong.

The next report is due. Start it now.

Nothing to configure. Open the desk, pick a client, and the dates are already filled in from the last period.