The system of record for builder finishing programs. It tracks every lot from plat to close — and everything that happens to it: buyer selections, quotes, purchase orders, delivery and install scheduling, and post-close warranty service. One thread instead of five tools.
Design consultants running selection sessions, purchasing agents issuing POs, warehouse and install coordinators running the calendar, and admins keeping the catalog and price book straight. Builders check their lots through the portal; crews use the phone-first field app.
Your admin invites a builder contact by email. They log in with their own credentials, scoped to their builder — any lot belonging to them is visible automatically, read-only, with your internal costs and margins hidden. Access is per-person and revocable, so nothing leaks through shared links.
Per module, per person: none, view, or edit. Role templates — Admin, Operations, Scheduler, Design Consultant, Read-only, Field — set sensible defaults in one click, and you can override any cell of the matrix. The nav hides modules set to none; edit controls disappear where someone's view-only.
Open any lot and you see its whole life on one line: plat → selections → quotes → purchase orders → install → close → warranty, color-coded by stage. Every order, schedule entry, and work order links back to the lot it belongs to — so "what's the status?" stops being a phone call.
Yes. Every finish category carries its own unit of measure, with waste factors applied when quantities are figured. Everything flows from plan dimensions into selections into orders — no naive area-times-price math.
That's the founding use case. We migrate lot registers, catalogs, price books, and plan libraries from legacy systems and spreadsheets during onboarding, community by community, so your team never runs two systems for the same lot.
Yes. Each client runs in its own workspace with its own catalog, plans, communities, pricing, and users. Builder portal users see only what their builder owns inside your workspace — never anything across workspaces.
Book a demo. If it fits, we scope a pilot on one community: load your plans, allowances, and catalog; bring your team on with role templates; invite your first builder. Expand when the thread proves itself.