P
Perch · Onboarding

Onboarding & Customer Journey

The workstream behind end-to-end onboarding test runs — how a real customer travels from "finds us" to "in the product." Internal — pre-launch working drafts, real companies named. Bands and statuses are not final; confirm before external use.

Customer Journey Mind Map

every customer type

The full matrix the team makes product decisions against: one engine (role → what Perch does → their $ lever → the next question), then six anchor journeys — GC and sub, small to enterprise — each bent by who lands. Plus the role-bend (estimator vs owner vs field) and the trade-bend (Electrical / Concrete / Drywall — counts vs volume vs area), with the other 31 trades following the same spine.

Custom Onboarding Journeys

fresh design

The reimagined flow: email is the only ask, sub-agents research the company on capture, and onboarding becomes confirm-don't-ask + an instant role-specific value demo. Two tracks (self-serve = the agent sells; white-glove = research arms a human), four concrete persona journeys, racing three clocks: time-to-info, time-to-value, time-to-check.

Journey → Onboarding → Initialization

the model

The mental model behind it all: three related-but-distinct layers (find us → set up → use it), Brock's point that the last 4–5 steps are really initialization (where stickiness is made), the role overlay (each role uses Perch differently), and the sub-agent research that fires on first contact to pre-fill and steer onboarding.

Customer Journey — Funnel Map

whiteboard · digitized

The strategy-room whiteboard, mapped: the customer universe (GC × 1, Sub × 34 trades) with revenue bands that set the journey, the six acquisition channels, the two journeys (self-serve vs white-glove, gated by ACV), the 8-step onboarding flow, and the seven conflicts it surfaces against the test-client set.

Onboarding Test Clients

format-check batch

Real, verified Utah companies → exemplars we model mock-up customers on for end-to-end onboarding/sales test runs. v0 format-check batch: 3 GCs (S/M/L) + 5 trades × med/large + 1 self-serve micro. Scales to the full 34 trades once the bands and field set are locked.

Where this stands — open decisions

  1. Re-axis from price tier → journey. v0 segmented by Core/Pro/Enterprise; the funnel says cut by self-serve vs white-glove. Load-bearing.
  2. Re-band to the whiteboard. GC <$10M / $10–500M / >$500M · Sub <$10M / $10–100M / $100M+ (v0 used different thresholds).
  3. Self-serve coverage — one small example per trade (34×3) or a separate small set? Self-serve is under-represented in v0.
  4. Role day-to-day in Perch — define what each role actually does in-app (needs the real precon_web service list). (HO = homeowner — resolved: 3rd account type, not a track.)
  5. Revenue vs ACV — which gates the journey when they disagree?
Perch · internal onboarding workstream Pre-launch · confirm figures before external use