For agencies abroad
White-label AI automation for agencies that sell the work and want it delivered
Marketing, web and GoHighLevel agencies brief us on a client build. We scope it with you, build it in the accounts you name and hand it to you with notes written for your brand. Your client deals with you. The arrangement is agreed per engagement and written into the scope.
- For
- Marketing, web and GoHighLevel agencies
- Client contact
- Yours, unless you ask otherwise
- Handover
- Unbranded or in your template
- Priced
- Per project, quoted to the agency
Agencies this arrangement fits
Marketing agencies
Leads you generate need follow-up
Your campaigns produce enquiries. The client's follow-up is slow, and an automated first reply, pipeline and reminder sequence would make your results show.
Web agencies
Sites that should do more than display
Clients ask for a chat assistant, a booking flow or a form that feeds their CRM. You want to say yes without building an automation practice.
GoHighLevel agencies
Sub-accounts waiting on builds
You sell the platform and the onboarding queue is longer than your builders can clear. A snapshot built to your standard shortens every later setup.
This is delivery of scoped builds. An agency that wants dedicated builders on its own roster, directed daily, is looking for staffing: see agency or hiring staff.
Who does what in a white-label project
- Agency sells and briefs (Brief), Your agency
- Scope and quote written (To the agency), Our team
- Agency approves the scope (Sign-off), Your agency
- Build and internal test (In named accounts), Our team
- Agency reviews, then shows client (Review), Your agency
- Handover pack to the agency (Your template), Our team
Briefs, client communication, handover and confidentiality
These four points are settled before a build starts and are written into the scope for each engagement.
- Briefs
- A brief names the client's business type, the process to automate, the tools and plans involved, the access route and the result the client was sold. If the brief is thin, we send questions to you, not to the client.
- Client communication
- By default we never contact your client. If you want us on a call or in a shared channel, we join under the name and email arrangement you set, and that is agreed in advance.
- Handover
- Notes, access lists and walkthrough recordings are delivered unbranded or in your template, so you can pass them to the client as your own documents.
- Confidentiality
- Client names and details are kept confidential, and a confidentiality agreement is handled per engagement. We do not list agency clients, show their work or approach them.
- Accounts
- Builds sit in the client's accounts or your agency account, whichever your client agreement calls for. Nothing depends on an account of ours.
Builds agencies hand to us
After the ad
Lead response for campaign clients
An ad or form lead lands in the CRM with its source, gets a first reply and is assigned, with a reminder sequence that stops on a response.
On the site
A chat assistant for a client website
An assistant that answers from the client's own content and hands over to their staff. See AI chatbot development.
In GHL
A niche snapshot
Pipelines, workflows and calendars for one niche, saved as a snapshot in your agency account. See GoHighLevel builds.
Reporting
Client reports assembled automatically
Figures pulled from ad platforms, analytics and the CRM into one sheet or dashboard on a schedule, ready for your account manager to comment on.
Onboarding
Your own client onboarding
A signed proposal creates the project, the folder, the access-request email and the kickoff checklist inside your agency.
Reviews
Review requests after a job
A completed job triggers a review request and a reminder, with unhappy replies routed to the client privately. See review request automation.
How the engagement runs
From your brief to your handover
Scope
You send the brief. We return a scope and a quote addressed to your agency. What you charge your client is your business and is never part of our documents.
Build
We build in the accounts named in the scope, using access your client grants to you or to a build user you create.
Test
We test first, then your team reviews. Only when you are satisfied does the client see it, presented by you.
Handover
You receive the handover pack in your template, plus an internal note for your team on how to make common changes.
Support
Optional. Requests come from your agency, are quoted to your agency and are answered to your agency.
Three time zones, one point of contact
A white-label project can involve three clocks: ours, yours and your client's. We work on UTC+8, which stays fixed all year because the Philippines has no daylight saving time. The overlap window is agreed with your agency, since you are the only party we speak to.
Written updates are sent at the end of each stage in a form you can forward or rewrite. Recorded walkthroughs carry no branding of ours, so they can go to your client as they are.
What you provide, what is included and what is left out
From your agency
- A brief per client, with the tools and plans involved
- Access arranged through you, in line with your client agreement
- One contact on your side who answers build questions
- Your document template, if the handover should carry your brand
- Confirmation that your client agreement permits subcontracted delivery
Included and left out
- Included: the scoped build, testing and a handover pack
- Included: an internal how-to note for your team
- Left out: selling, account management and client training, which stay with you
- Left out: tool subscriptions and usage fees, billed by vendors to the account owner
- Left out: strategy for your client's marketing
Limits, and what moves the price
Limits
- White-label delivery is agreed per engagement. Some projects need direct access to the client's staff, and we will say so at scoping
- What can be built depends on the client's tool plans, which we can only confirm once access or screenshots are provided
- We do not pose as employees of your agency in writing or on calls unless that arrangement is agreed and lawful where you operate
- Responsibility to the client under your contract stays with your agency
What moves the price
- The size of each build and the number of systems it touches
- How complete the brief is
- Whether a reusable template or snapshot is built for repeat use
- Whether we join client calls
- Whether handover documents are produced in your template
- Support after launch
Request scoping
Tell us about your agency and the first client build
Do not name your client in this form. The business type, the tools and what was sold are enough. Include your country and time zone.
Questions we get asked
Will our client know you exist?
Not from us. We do not contact your clients, name them or show their work. Whether you tell your client that delivery is subcontracted is a matter for your client agreement.
Who owns what we deliver to our client?
Ownership passes as your agreement with your client says. Builds sit in the client's accounts or yours, and we keep no copy in an account of ours beyond what the engagement terms allow for support.
Where does our client's data sit while you build?
In the client's own tools. We work inside those accounts, build with sample or test records first and list every system touched in the scope so you can answer your client's questions.
How do we communicate with your team?
Through one contact at your agency, in the channel you prefer: email, a shared workspace or a messaging group. Updates are written so that they can be forwarded.
Can you work to our process and naming standards?
Yes. Send your conventions with the first brief and they are applied to workflow names, folders and documents. If you have none, ours are offered for you to adopt.
What if the client's tool changes after handover?
The handover pack shows what each automation depends on. Your agency raises the change with us, and it is handled under support or quoted as a small job.
How do quotes, contracts and NDAs work for agencies?
Each build is quoted to the agency from its scope. Engagement terms, including confidentiality and non-solicitation of your clients, are handled per engagement before any client detail is shared.
Next step
Brief us on one client build.
Describe the business type, the tools and what you sold. We will reply to your agency with what delivery involves.