All Case Studies

    Case Study

    Turning Chaotic Client Onboarding Into a Profitable, Automated Operating System

    Problem: Client Onboarding

    Company

    Marketing & Web Development Agency

    Industry

    Agency / Marketing & Web Development

    Problem

    Every new client onboarding was long, chaotic, and resource-heavy. First projects were almost always unprofitable, with the agency relying on future projects to recover lost margin.

    What we built

    • • Mapped and redesigned the full onboarding workflow
    • • Automated client information capture and AI-assisted analysis
    • • Structured onboarding meetings with clear outcomes
    • • Client-facing task and asset collection system

    Outcome

    • ✔ First client projects became profitable
    • ✔ Team participation in onboarding reduced by 50%
    • ✔ 12–15 hours saved per client onboarding
    • ✔ Onboarding meetings reduced to 1–2 focused sessions

    The Situation

    Where things stood

    A growing marketing and web development agency was struggling with the profitability of new client projects. Every time a new client signed on, the onboarding process became long, chaotic, and extremely resource-heavy. Typical onboarding looked like this: • Multiple long meetings with the client • Up to five or six team members attending each meeting • Conversations that lacked structure or clear outcomes • Key project information gathered inconsistently • Client logins and assets collected manually The biggest consequence: The first project for almost every client was unprofitable. Leadership had come to accept this as normal. The assumption was that the agency would recover the lost margin by securing additional projects from the same client later. But this created ongoing pressure inside the business: • teams constantly tried to "sell the next project" • delivery teams felt drained by inefficient onboarding • business owners were heavily involved in early project stages What initially looked like a pricing problem turned out to be something else entirely. It was an operational design problem.

    The Bottleneck

    What was actually in the way

    When we mapped the onboarding workflow, several structural issues became obvious. The agency had never actually designed an onboarding system. Key gaps included: • no clear definition of where onboarding started or ended • no clear outcome for onboarding • no structured way to collect client information • no standardised asset collection process • too many people attending meetings unnecessarily • no clear documentation flow for the project team Most onboarding sessions were essentially open-ended discovery conversations. Important information was gathered inconsistently, duplicated across meetings, and often needed to be clarified again later. This led to: • wasted team hours • delayed project starts • slower delivery cycles • reduced project profitability The real issue wasn't the client. It was that onboarding had never been designed as a repeatable operating system.

    The Fix

    What we built

    We rebuilt onboarding as a structured operating system designed to: • capture information efficiently • minimise unnecessary team involvement • create clarity before project work begins Five major improvements were introduced. 1. Mapping the Current State We first mapped the full onboarding workflow to understand: • what information was required • where delays and waste occurred • what decisions actually needed to be made • who truly needed to be involved This revealed major inefficiencies in meetings, information gathering, and documentation. 2. Automated Client Information Capture Instead of gathering information through long meetings, we introduced a structured digital intake process. Clients could now: • upload documents • answer guided questions • provide voice responses if needed This allowed the agency to collect critical background information before any meeting took place. 3. AI-Assisted Information Analysis We introduced a lightweight AI agent that could: • analyse the information submitted by the client • structure it into a clear project brief • identify missing or unclear information Instead of spending hours trying to "figure things out" during meetings, the team could now focus directly on filling the remaining gaps. 4. Structured Onboarding Meetings With preparation completed in advance, onboarding meetings became far more focused. The meeting now had: • a clear purpose • a defined participant list • specific information to validate • clear outputs for the delivery team Instead of five or six people attending, only the essential team members were present. Meeting time dropped significantly. 5. Client Task Visibility & Asset Collection Another major delay had been collecting essential client assets such as: • website access • hosting credentials • analytics accounts • brand assets We introduced a simple client-facing workflow system that: • automatically requested required information • provided clear deadlines • showed the client what was needed before the project could begin This removed dozens of manual follow-ups.

    Tool Layer

    The system was supported by a small number of practical tools. AI Intake Agent • analysed client-submitted information • structured it into a project brief • identified missing inputs Otter • captured onboarding conversations • transcribed discussions • allowed decisions to be shared easily with the team Asana • client-facing onboarding workflow • automated requests for logins and assets • clear project readiness tracking

    The Outcome

    What changed

    • Team participation in onboarding reduced by 50%
    • Onboarding meetings reduced to 1–2 focused sessions
    • 12–15 hours saved per client onboarding
    • Project teams began delivery much sooner
    • Time-to-billing improved significantly
    • First client projects became profitable

    The Human Payoff

    What it actually meant

    The impact went far beyond operational efficiency. Before the change: • onboarding was the most stressful part of the business • business owners had to be heavily involved • delivery teams felt drained by inefficient processes Once the new system was implemented: • business owners spent far less time in onboarding meetings • projects started faster and with better clarity • delivery teams received better information from the start • the pressure around first-project profitability disappeared For the business owners personally, the change meant something even more meaningful. They were finally able to step away from late-night work and reclaim their evenings — something that had become rare during the most stressful phases of growth.

    Ready to fix what's slowing you down?

    Book a free 30-minute call

    No prep required. Just an honest conversation about what's slowing your business down.