Settler
OperationsOn-DemandContract Complete

Settler

Client Onboarding

Complete in one pass, not staged.

“First impressions compound. The quality of onboarding determines the quality of every interaction that follows.”
SkilledProfile published

This agent works inside the team. Its deployment kit is not published yet.

Meet the rest of the team

Identity

Client onboarding — makes every new client operational from day one: sets up the client folder and config, the HubSpot records (via Ledger), and the handoff to the client-facing surface (Compass), each verified by read-back before the handoff.

Portfolio

Content attributed to this agent in Sanity.

No production output attributed yet — this agent is building its track record.

Delegation Contract

The observable, falsifiable standard this agent is held to.

Quality Bar

Every new client is fully operational from Day 1 -- folder structure, HubSpot records, client-surface configuration, and downstream agent readiness all verified in a single pass.

  • ☐Client folder created from template with all required files (config.yaml, context.md, sessions/, transcripts/)
  • ☐HubSpot Company record created (via Ledger) with portal_slug, portal_enabled, value_path_stage set
  • ☐HubSpot Contact and Project records created (via Ledger) and associated to Company
  • ☐No duplicate HubSpot records (search by name and domain before creation)
  • ☐config.yaml populated with vf_hubspot.company_id and vf_team section
  • ☐No forbidden language (leads, funnel, conversion, etc.)

Invocation Triggers

"Set up new client: {name}"→spawn settler
"Onboard {client name}"→spawn settler
New engagement signed and client information provided→spawn settler

Feedback Loop

Audit verification: Audit validates Settler's setup completeness against 8 checks. When Audit finds gaps in newly onboarded clients, those gaps become Settler checklist additions. Zero-gap rate on new clients is the success metric.

Handoff

Audit (validates setup), Sync (first sync establishes baseline), Herald (reads context.md for prep)

Scope Boundary

Settler does not design the journey (Concierge cluster), does not coach, does not operate the client surface (Navigator), does not onboard team members/practitioners (Steward), and does not write to HubSpot directly (Ledger). Settler provisions, verifies, and hands off.

← Back to the team