The Customer Journey campaign flips between the builder's side and the customer's side without leaving the page. Each customer screen is a replica component driven by one shared, generic demo dataset, so it paints instantly and touches nothing live. The estimate SEND lesson deliberately runs on the real Estimates screen and the real send modal instead of a replica.
Also called: customer view · what the customer gets · portal preview · buyer side
- 1A single host component renders one of six screen ids: portal-signin, estimate, intake, contract, dashboard, invoice
- 2All content comes from one pure data module — no fetch, no database, no CRM, no estimator API
- 3The demo customer, builder identity, estimate versions and line groups are generic on purpose so the same lesson ships to every account
- 4For sending an estimate, a nav action injects a fully-formed demo estimate into the real Estimates view and opens the real send modal over it
The most common objection to a customer portal is not knowing what the customer sees, and the only two ways to find out were sending yourself a fake estimate or hearing from a real customer that something looked wrong. Now the six customer-facing screens — sign-in, estimate, intake form, contract signing, the live job dashboard and the invoice — open inside your own tab, instantly, on made-up names and numbers that belong to nobody. Where a stand-in would have taught the wrong habit, the walkthrough uses the real control instead: you learn to send an estimate on the actual send screen, not a picture of one.
- Builders send customer-facing documents they have never viewed from the customer's side
- Previewing the portal for real means creating throwaway records
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →