02 / Agency Launchpad

Making agency setup
feel manageable.

A guided onboarding concept for TikTok Business Center that makes the next action, permission scope, and approval owner easier to understand.

Project: Independent concept
Focus: Onboarding & permissions
Timeline: Concept Aug · Prototype Sep 2026
Status: AI-assisted prototype · Untested

Agency Launchpad

One setup plan.
A visible next step.

Bring guidance and approval status into the same workspace.

Northstar workspace

Your activation plan

Ready to connect your first client?

✓Business verifiedDone

✓Team roles assignedDone

3Request client accessNext

A workflow with several owners

The original Agency Launchpad work sample explored how agency setup could become a coordinated journey: verify the business, connect a client, assign access, configure assets, and reach a campaign-ready state.

The key hypothesis is that uncertainty about status and ownership can be as frustrating as the number of steps. A small agency may need guidance; a larger agency may need reusable configurations and greater visibility across clients.

How might we make a complex setup feel like a clear sequence of decisions?

This extends an independent product strategy work sample from August 2026. It is a conceptual experience, not an existing TikTok interface or work commissioned by TikTok.

Working prototype

Explore the approval states

Choose an agency size, review a permission request, and use the demo controls to simulate approval or rejection.

Fictional workspace · Local demo

Your setup plan

Agency size

2 of 5 steps complete

✓Business verified
✓Team roles assigned
3Connect first client
4Configure client assets
5Campaign-ready check

Demo only. Client names and permission states are fictional. No access request is sent, and no real account permissions change. Changing agency size restarts the demo.

Progress that tells the truth

Separate waiting from completion

Sending a request is not receiving access. The step stays incomplete until the simulated client approval arrives.

Say who owns the next action

The waiting state names the client administrator as the approval owner. The agency can inspect the request without wondering if setup has stalled.

Preview permissions before requesting

The default request is read-only. A scope review and an explicit confirmation create a pause before asking for access.

Reuse structure, not permissions

The larger-agency template reuses a checklist. Each client's access still needs separate review and approval.

From proposal to interaction

The August work sample proposed a role-aware setup plan, reusable client templates, approval visibility, and a feedback queue. Its impact targets were illustrative hypotheses, not measured outcomes.

For this portfolio, ChatGPT helped extend that concept into an interactive front-end prototype, including the request review, waiting, rejection, and approval states. The extension makes the permission boundaries concrete enough to critique.

State	What the experience should communicate
Ready to request	Which client, which scope, and what the agency can do next.
Awaiting approval	The request was sent, but access has not been granted. The client owns the next action.
Request declined	No permissions changed. Review the scope and prepare a new request.
Access granted	The client connection is complete. Asset configuration still remains; the workspace is not yet campaign-ready.

A feedback loop worth testing

The broader concept includes a structured intake for agency feedback: workflow step, impact, frequency, and supporting evidence. Requests would be grouped and prioritized before a decision is communicated back to the agency.

That operating model is a proposal. This prototype focuses only on the first-client access flow, where clarity and permission safety can be examined together.

Can a first-time agency admin identify the next action without help?
Can they distinguish a submitted request from approved access?
Do they understand the difference between read-only and campaign-management scope?
Can they recover from a rejection without assuming access was granted?

A proposed study would compare comprehension and completion across small and large agencies, then examine support needs and permission errors. Interviews, usability tests, and product experiments have not yet been conducted.

Scope & next steps

The next iteration should be informed by actual agency admins and checked against real permission models. A polished checklist is only helpful if it reflects the real owners, dependencies, and failure states of the underlying workflow.

Starting material: Agency Launchpad independent product strategy work sample, August 2026. Product context: TikTok for Business. The screens, client names, and simplified permission labels here are illustrative.

Next exploration

One setup plan.A visible next step.