Client call requested
The partner decides whether LOKAL attends, under which identity and who leads. The technical owner prepares the explanation; the agency keeps the relationship.
Partner process
The client sees your agency. You see every handoff.
White label should remove production pressure, not remove visibility. The account record shows the owner, the next decision and the work waiting for approval.
Decision first
How long does white-label onboarding take?
A first client typically takes two to three weeks to onboard because the team must align scope, access, templates, communication and escalation. Later accounts can move faster once that partner framework is working, but no account skips access and ownership checks.
Before access
Register the account and expose collisions early
You name the company and relationship before sharing credentials or making an introduction. LOKAL checks whether it already knows the account, records the protection boundary and agrees whether its involvement is invisible, disclosed or client-facing.
- Account owner and market
- Current promise and deadline
- Prior relationships or conflicts
- Communication mode and case-study permission
Before production
Turn the proposal into a responsibility map
The scope names the deliverables, inputs, approver and turnaround. It also names the work that stays with the agency. That last column prevents a technical team from assuming the account manager will write the brief, or the account manager from assuming a technical recommendation is already approved.
During delivery
One queue, a named reviewer and a client-ready handoff
Work is produced in the agreed system, reviewed by the named owner and returned with decisions or risks visible. Reporting separates what changed, what moved and what needs the client or agency to act.
- Production owner
- QA owner
- Partner approver
- Client decision, when one is needed
When something moves
Escalation is a route, not a dramatic email
Urgent work, blocked access and scope changes follow the escalation path agreed at onboarding. If a deadline cannot hold, the delivery owner states what changed, the effect and the next defensible date.
Put it in a real account
What this looks like when delivery starts
A brief is incomplete
Production does not guess. The owner returns the exact missing input, the decision it blocks and the deadline impact.
The account ends
Open decisions, source files and access are handed back during the paid transition. New work stops; the account-protection period does not.
Limits matter
What this page does not promise
- Two to three weeks is the existing typical first-client onboarding window, not a promise for every account.
- Same-day or emergency work needs an agreed capacity and escalation rule before it is sold.
- A partner remains responsible for promises made outside the signed scope until LOKAL accepts them in writing.
Questions to settle before signature
Who attends client calls?
The partner decides. A LOKAL specialist can remain invisible, join as part of the agency team or be introduced openly; the chosen mode is recorded for the account.
How does reporting work?
LOKAL works in the partner’s agreed template or supplies a client-ready report. The report names completed work, movement, risks and decisions rather than filling a dashboard with unexplained metrics.
Who approves work before the client sees it?
LOKAL runs its own delivery QA, then the partner receives the client-facing artefact for approval unless the signed account workflow grants another route.
What happens when scope changes?
The delivery owner records the requested change, its effect on fee and timing, and waits for the authorised partner approver before adding it to production.
Start with one account
Tell us what you sell, what is already promised and where delivery is tight
We’ll use the brief to put the right operator on the first conversation and flag a mismatch before it reaches your client.