Agency HQ and white label

Agency HQ is the partner operating layer: client accounts, a lightweight CRM, onboarding tasks, proposals, client intelligence, reports, fee rules, and branded delivery.

Organization model

Tailwin uses three levels:

1. the platform organization operates Tailwin;
2. a partner organization operates its agency workspace and brand;
3. client organizations hold each customer’s sites, sources, credentials, reports, and measurements.

Partner members can act into descendant client organizations when authorized. The switch is audited. Work in the client organization whenever data or credentials belong to that client.

Add a client

You can create a client account directly, promote a scan-widget lead, or provision an account after proposal acceptance.

1. Open Agency → Client accounts or HQ → Pipeline.
2. Create or select the company.
3. Add the primary contacts and lifecycle stage.
4. Provision the child client organization.
5. Assign the plan and confirm entitlements.
6. Switch into the child organization to add its site and connections.

Do not reuse one client organization for multiple unrelated businesses. Organization scope is the main data-isolation boundary.

CRM and onboarding

HQ stores companies, contacts, activities, notes, tasks, recurring task templates, proposals, invoices, and comments. It is intentionally an operating view, not a replacement for every CRM function.

Use task templates for repeatable onboarding. Record external dependencies (OAuth approval, DNS access, GBP quota, billing contact) as explicit tasks rather than assuming they are complete.

Proposals and provisioning

1. Build a proposal from service packages.
2. Send the tokenized acceptance page.
3. After acceptance, verify that the client organization and entitlements were created.
4. Complete the connection and measurement checklist inside that client.

Proposal acceptance can provision the workspace, but it cannot grant access to a client’s third-party accounts. Those OAuth or credential steps still require the account owner.

Client intelligence

The client company page can summarize ranks, visitors, Search Console, advertising, captured leads, and crawler activity from the linked client organization. Each tile can contain a value or a reason it is unmeasured.

Links from this view must preserve client scope. Never interpret a partner-level aggregate as a client-specific result.

White-label setup

1. Open Settings → Branding in the partner organization.
2. Set the public name, logo, colors, and email identity.
3. Add the custom domain.
4. Complete the DNS and Cloudflare for SaaS verification shown by the product.
5. Test login, client portal, report share, PDF, approval link, receipt, widget, and email on the branded host.

White label affects presentation, not data ownership or source labels. Vendor estimates and measured facts must keep their provenance even when Tailwin’s platform name is hidden.

Client-safe delivery checklist

• Active organization is the intended client.
• Dashboard sources all belong to that client.
• Fee visibility matches the signed agreement.
• Public share token contains no internal-only widget.
• Brand, host, reply address, and PDF tested.
• Client member sees only the appropriate navigation and records.
• Act-into and proposal actions appear in the audit trail.

Workspace roles

Owners and administrators operate the workspace. Members have read-only access to overview, Rankings, site visibility/crawler evidence and Reports. Members cannot launch scans or crawls, change sources, publish content, send campaigns, manage visitors, use hiring/concierge controls, or edit workspace settings. Those controls are hidden, and direct requests are denied too.

Agency HQ and client-account navigation appear in partner/platform workspaces for owners and administrators. Switch back to the agency workspace for those operations. Client owners and administrators can operate their own Signal, Content, Local, Press, Reports, Tower and maintained Talent surfaces. Existing owner-only billing and platform-administrator restrictions still apply.

Your nearest membership in the organization hierarchy determines your role. A direct member role in a client account takes precedence over an inherited agency role; owning an unrelated workspace grants no extra access. Public report, approval and receipt links remain limited to the resource and action represented by their token. They do not grant a workspace role.