automation.engineer
All case studies

ScaleClients.io / Project case study

2023Recorded work

Each new client.
A clean dashboard.
A guided connection setup.

ScaleClients.io needed a fresh reporting workspace for each new client. Intake prepared a dashboard and guided the client through connecting booking and lead sources, keeping internal setup separate from connections the client had to authorize.

Client
ScaleClients.io
Contribution
Integration walkthroughs and onboarding coordination
Project status
Configured provisioning & setup guides

Tools & working context

Project scope and implementation.

  • Google Sheets
  • Make
  • Calendly
  • OnceHub
  • GoHighLevel
  • ClickFunnels
  • Facebook

01 / Business context

The problem
to solve.

A repeatable reporting service needs a consistent starting structure for each client. It also needs the correct booking and lead-source context, with clear instructions for connecting the tools that supply the data.

The build copied a dashboard for each client and paired it with setup instructions for the booking and lead sources they used. Several platforms had their own setup rather than one connection that worked for everything.

Inside the workflow

A closer look
at the handoffs.

Start with the main path and its branches. Select a step for context, or switch to the technical map for implementation detail.

  • Client platform intake
    Capture booking and form-platform choices plus source identifiers.
  • Scenario and guide registry
    A shared sheet links reusable templates, tutorials and internally configured workflows.
  • Copy clean dashboard template
    Create a per-client Sheets dashboard with formulas and cleared source tables.
  • Prepare client Make environment
    Create the client/team setup under the parent account and invite the client.
  • Send selected setup guides
    Supply source-specific template and tutorial links for the chosen platforms.
  • Client completes connections
    The account owner authorizes the supported source connections.
  • Booking-event setup
    Configure the selected booking-platform webhook and calendar context.
  • Form and lead-event setup
    Configure selected form or lead-source events, including GoHighLevel workflows.
  • Distinct booking and form tables
    Map each source to its own event meaning and the correct per-client destination.
  • Client reporting scaffold
    The template’s formulas and views use the prepared source tables.
Read the workflow notes
  1. 01 / Collect

    Capture the client’s system context

    Intake identified the booking-system information needed for setup, keeping client-specific configuration separate from the reusable dashboard template.

  2. 02 / Prepare

    Provision a clean working copy

    The process copied a Google Sheets dashboard and prepared the relevant Make team/client setup, rather than reusing another client’s working data.

  3. 03 / Connect

    Guide the remaining account steps

    Instructions and templates explained the client-authorized connections for supported booking/lead platforms and how those connections fitted the reporting workflow.

Historical sales pitches and self-reported commercial projections are excluded from the outcome of this implementation.

03 / Implementation detail

How it
was built.

Setup guidance covered Calendly, OnceHub, GoHighLevel, ClickFunnels and Facebook leads. A guide for a platform did not confirm that its live events had reached the report successfully.

Internal provisioning and client authorization were separate responsibilities. A prepared dashboard can be a useful deliverable while some source connections still require client action.

The sending account, rollout and rules for identifying the source of leads still needed clarification in parts of the work. One metrics recording was incomplete, so it does not support a performance result.

04 / Outcome & scope

Result
and scope.

The configured setup provided a repeatable dashboard starting point, platform-specific connection guidance and a client handover.

The scope focused on dashboard provisioning and onboarding, rather than advertising strategy or campaign performance.

Source contracts and setup

One client destination.
Distinct source events.
Clear setup ownership.

The more detailed handover separates per-client spreadsheet destinations and tables for form submissions versus bookings. A source event has to mean the same thing as the metric it feeds; an account connection alone does not establish that definition.

GoHighLevel workflow webhooks were part of the source setup, alongside booking and lead-platform connections. Client authorization, available calendar behavior and ClickFunnels/lead-source details still required clarification in the recording.

Several setup guides are partial or aborted. Their existence supports a guided handover approach, while successful source-event ingestion, attribution accuracy and full adoption remain separate verification steps.