Case Study

Case Study: Agency Onboarding, Reporting & Approvals

We built a connected set of automations for a digital marketing agency: a new business pipeline in the CRM, client onboarding with access tracking, automated monthly reporting with draft commentary, a creative approval workflow and retainer tracking that feeds draft invoices. Account managers now spend month end checking and writing rather than copying numbers and chasing logins.

Agency type
Digital marketing agency: paid media, SEO and content on retainers
Team involved
Owner, new business lead, account managers, designers, finance
Systems connected
CRM, proposal tool, project tool, time tracker, accounting, ad and analytics APIs, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

New business lived in the owner's inbox and a spreadsheet. Proposals went quiet without follow-up, and nobody could say which sources brought clients.

New clients took weeks to onboard because access requests and brand assets were chased by email, and nobody kept a record of what access had been granted.

Monthly reports took account managers most of the first week of each month, and commentary was written in a rush.

Feedback arrived through email, chat and PDF comments, sign-off was not recorded, and retainer overruns were discovered only at invoicing.

Goals

What the project had to change

  • Every new business opportunity sits in one pipeline with a next step.
  • New clients are kickoff-ready faster, with an access log from day one.
  • Reports are built automatically and account managers focus on commentary.
  • Feedback for each round lives in one list and sign-off is recorded.
  • Retainer overruns are flagged during the month and invoices are drafted for finance.

What we built

What we built, as one connected system.

01

New business pipeline

We captured web enquiries, referrals and RFPs into the CRM with sources, added research briefs before discovery calls, tracked proposal events and created won clients in the project tool.

Service details
02

Client onboarding

Signed scope now generates a checklist per service, platform access instructions, one onboarding form, scheduled reminders and an access log.

Service details
03

Automated reporting

Monthly data from GA4, Search Console, Google Ads and Meta fills each client's branded template, unusual movements are flagged and commentary is drafted for the account lead.

Service details
04

Creative approvals

Comments from the proofing tool, email and chat are gathered into one list per round, conflicts and scope are flagged, and sign-off is recorded with the version.

Service details
05

Retainer tracking and invoicing

Daily comparison of logged hours with each retainer, threshold alerts, out-of-scope tagging and draft invoices in the accounting system for finance to approve.

Service details

Architecture

How the agency workflows connect

CRM New business Project tool Tasks, approvals Ad and analytics GA4, Ads, GSC, Meta Time tracker Hours logged n8n Five workflows AI drafts Briefs, commentary Reports Branded templates Draft invoices Accounting Account managers Review and send Finance Approves invoices Logs and reports Owner summary
  • Input
  • Logic and services
  • AI step
  • Output
  • Data
  • People

How it flows

  1. 1 The CRM, project tool, ad and analytics APIs and time tracker feed one n8n instance.
  2. 2 Five workflows build reports, prepare invoices and use AI steps for briefs, comment sorting and commentary drafts.
  3. 3 Account managers review and send; finance approves every invoice.
  4. 4 Every step is logged, and the owner gets a monthly summary of pipeline, onboarding and retainer health.

How it behaves

How the system behaves day to day

What each person sees and what runs in the background, including what happens when something goes wrong.

What clients see

  • A quick, prepared reply to new enquiries
  • One clear onboarding list with access instructions
  • Reports on time with thoughtful commentary
  • One summary per feedback round and accurate invoices

What the agency sees

  • One pipeline, one checklist per client, one review queue
  • Flags for unusual figures, conflicting feedback and scope
  • Retainer alerts mid-month and draft invoices at month end

What the automation does

  • Captures, builds, gathers and drafts on schedule
  • Applies opt-outs and approval rules
  • Logs every step and alerts the owner if a run fails

Edge cases and fallbacks

A client revokes analytics access
The report section is marked missing and the account manager is alerted before month end.
Tracking breaks mid-month
Large drops are flagged as possible tracking issues rather than explained as performance.
Feedback arrives after sign-off
Logged as a new request instead of reopening the approved round.
Time logged to the wrong client
Flagged for correction before invoices are drafted.
n8n or an API is unavailable
Runs retry, nothing is sent incomplete and the owner gets an alert.

Integrations

What we connected

All integrations

HubSpot

CRM

New business deals, sources, tasks and won-deal handover.

HubSpot CRM REST API and webhooks.

PandaDoc

Proposals

Proposal views, completion and signatures moving deals.

PandaDoc API.

Asana

Project management

Onboarding checklists, approval tasks and requests.

Asana API.

Harvest

Time tracking

Time entries, projects and invoices for retainer tracking.

Harvest API v2.

Xero

Accounting

Draft invoices, contacts and payment status.

Xero Accounting API.

Filestage

Creative proofing

Review comments and approval status.

Filestage API or its Zapier integration.

Google Analytics 4

Analytics

Traffic and conversion data for reports and dashboards.

Google Analytics Data API.

Google Ads

Paid search

Campaign performance for reports.

Google Ads API at an approved access level.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We sat with account managers through a month-end, mapped new business, onboarding, reporting, approvals and invoicing, and agreed data flows and processor terms.

  2. 02

    Design and access

    Week 2

    Pipeline stages, onboarding checklists, report templates, approval rules and retainer thresholds; API access and Google Ads API application.

  3. 03

    Sprint 1: pipeline

    Week 3

    Built source capture, briefs and proposal tracking; shadow-ran beside the old spreadsheet.

  4. 04

    Sprint 2: onboarding

    Week 4

    The pipeline went live. Built checklists, the onboarding form, reminders and the access log.

  5. 05

    Sprint 3: reporting

    Week 5

    Onboarding went live for new clients. Built data pulls, templates, anomaly flags and drafts.

  6. 06

    Sprint 4: approvals

    Week 6

    Reports ran in parallel with manual ones for a month-end. Built comment gathering, round lists and sign-off.

  7. 07

    Sprint 5: retainers

    Week 7

    Approvals went live. Built time sync, scope alerts and draft invoices.

  8. 08

    UAT and handover

    Week 8

    The team ran acceptance tests, we switched everything on, handed over run books and trained the team.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Captures enquiries and drafts research briefs
  • Builds onboarding checklists and sends reminders
  • Pulls report data, fills templates and flags anomalies
  • Gathers feedback into one list per round
  • Compares hours with retainers and drafts invoices

The team does

  • Account managers check reports and rewrite commentary
  • Account managers resolve feedback with clients
  • Finance approves every invoice
  • The new business lead edits follow-ups

Account lead or agency owner decides

  • Decides pitches, pricing and commercial terms
  • Decides how to handle scope overruns with each client
  • Approves how difficult results are presented
  • Owns sensitive access and ownership questions

Compliance handled

Privacy, consent and safety, built in.

Processor duties

Every vendor touching client data was covered by Article 28 GDPR terms before go-live.

Source: gdpr-info.eu

B2B email rules

Proposal follow-ups and reminders honour opt-outs within CAN-SPAM's 10-business-day limit.

Source: www.ftc.gov

Google Ads API access

Reporting runs at an approved Google Ads API access level for the agency's Google Cloud project.

Source: developers.google.com

Endorsement disclosures

Influencer and partner creative is checked for clear disclosure of material connections before sign-off.

Source: ftc.gov

No report or invoice sent unread

Account managers approve every report and finance approves every invoice.

Outcomes

What changed for the practice

  • Every new business opportunity now sits in one pipeline with a source and a next step.
  • New clients receive one clear onboarding list, and the agency keeps a record of every access granted.
  • Account managers spend month end checking flagged figures and writing commentary instead of copying numbers.
  • Feedback for each round lives in one list, and sign-off is recorded against the version.
  • Retainer overruns surface during the month, and invoices arrive as drafts for finance.

What we track

The measures the practice watches.

Pipeline

Enquiries by source, proposals followed up and win rate by service line.

Onboarding

Days from signing to kickoff-ready.

Reporting time

Hours spent per client report and reports sent on time.

Approval rounds

Rounds per deliverable and time to sign-off.

Retainer health

Retainers flagged before overrun and out-of-scope hours rescoped or charged.

Invoicing

Days from month end to invoices sent.

Cost estimate

What a project like this costs

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Process mapping, data flows and backlog for all five workflows.

    $900 – $1,900

  • Pipeline module

    Source capture, briefs, proposal tracking and handover.

    $700 – $1,600

  • Onboarding module

    Checklists, form, reminders and access log.

    $700 – $1,700

  • Reporting module

    Data pulls, templates, anomaly flags and drafts.

    $900 – $2,200

  • Approvals module

    Comment gathering, round lists and sign-off.

    $600 – $1,500

  • Retainer and invoicing module

    Time sync, alerts and draft invoices.

    $700 – $1,700

  • Integrations

    CRM, proposal, project, time, accounting and ad platform connections.

    $200 – $600

  • Testing, UAT and launch

    Parallel runs, acceptance tests, launch and training.

    $300 – $1,300

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for this scope: five workflows at our per-workflow range. Every agency gets its own fixed quote after a free call.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • AI model usage: Billed by the provider per use; briefs, comment sorting and report drafts stay small at agency volumes.
  • Vendor plans: CRM, proposal, project, time tracking and accounting tools on their own plans.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Free 20-minute call

Want this built for your marketing agency?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call