Tidewater Creative

Chapter 05

What the team was left with

Four monthly readouts against the audit baseline, counted from the first go-live: one as the build finished and three in the proof window. Measured together with the client from the engine's own log. These are the sample numbers for a fictional client, in the shape every readout takes.

Sample deployment record. Tidewater Creative is a fictional client and every number here is illustrative.

Before and after, against the audit baseline

  • Days from month-end to report sent

    6.51.872% faster

    All twelve clients out by the 3rd in months three and four

  • Days from report to invoice

    90Same day

    Invoice created the day the work ships

  • Days sales outstanding

    412615 days

    Reminder cadence plus invoicing the day the work ships; target was 24

  • Hours per month across the three workflows

    713239 hours back

    Owner and account lead combined, from the log and a two-week diary

  • Overage cycles billed

    0 of 34 of 4$6,900 billed

    Overages invoiced across four months

  • Owner approval wait

    2.1 days4 hours92% shorter

    Median, including one travel week

Drafts approved without edit

Share of change summaries the account lead sent without changing a word, by week. Edits are kept as examples, so the drafts get closer to how the team writes.

65%75%85%95%W0W4W8W12W161234
  1. 1Week 0Go-live: report assembler
  2. 2Week 4Tolerances set per client
  3. 3Week 8Seasonal examples added
  4. 4Week 1691% in month four

The log

  1. 07:10:02AgentExport ·Pulled September spend and results for 12 clients from Meta Ads and Google Ads
  2. 07:10:04HeldMismatch check ·Harbor Dental held: template total $4,080 against export $5,952; spend 18% above August
  3. 07:10:11AgentChange summary ·Drafted 12 summaries from 23 logged changes
  4. 09:40:18PersonClear flag ·Account lead cleared Harbor Dental: budget raised Sep 18 per the change log
  5. 14:45:51PersonApproval ·Owner approved 8 reports from a phone; 1 returned with an edit
  6. 14:46:03AgentInvoice ·Created 8 draft invoices in QuickBooks with the approved reports attached

Every agent action is logged with the time, what it read, what it did, and who approved it. The monthly readout is built from this log.

Four monthly readouts

  1. Month 1

    Reports out on day 3. The mismatch check flagged a third of them, mostly tolerances set too tight. The old path ran in parallel and the numbers matched.

  2. Month 2

    Old workbook retired. Overage detection caught its first missed line. Day-14 reminders went out for the first time; two clients paid the same week.

  3. Month 3

    About one draft in ten needed edits. Month-end approvals took the owner under an hour, all from a phone. One client at day 45 went to the owner with the history attached.

  4. Month 4

    Steady state. Reports out on day 2, invoices the same day, days sales outstanding at 26. The numbers held at the readout that closed the proof window, and the client made its choice.

The agency owns all of this

  • The agents run in the agency's accounts

    Every connection, mailbox, and template belongs to the agency. Nothing runs through a platform of ours.

  • The data stays in the agency's systems

    The engine reads from the ad platforms, QuickBooks, and Drive, and writes back into them. There is no copy of the business anywhere else.

  • Handed over in full

    The SOPs, the rules, and the log are documented and handed over. When the engagement ends, everything keeps running and the agency keeps it.

  • Priced against the baseline

    The audit set the numbers. The build was quoted from the map's $118K a year. After the proof window the client picks a monthly run fee per connected system or the next zone.

Value, month-four run rate

$58K / yr

Hours returned, at loaded cost

$27K / yr

Overages billed

$19K / yr

Faster cash, at the agency's borrowing cost

$14K / yr

Fewer report errors

Projected annual value from the month-four run rate, against the audit's own projection of $118K. The monthly readouts report what was measured.

What happens next

  • Monthly run fee per connected system after the proof window.
  • Next zone scoped: proposals and intake for new clients.
  • The first-month plan assembler stays unbuilt until onboarding volume justifies it.

At the end of the proof window the client chose to keep the engine running and point the next zone at proposals and intake. Every number above comes from the engine's log and was reviewed with the client at each monthly readout.

Ready to see your back office this way?

Every engagement starts with the four-week audit, so you see the map and the numbers before you commit to a build.