Pilot in development, not field-proven: a daily view of construction attention, owners, next actions, blockers, and source freshness.
Planned capabilities · Not a delivered suite
Start with construction. Build the connected office carefully.
Start with a founder-led workflow conversation. Construction software is a controlled pilot in development, not field-proven. The broader modules below describe future vision, not delivered features or supported integrations.
Product direction
Planned capabilities around the work that already exists.
The first job is not to force a new system. The first job is to understand source truth, handoffs, risk, and where automation can safely remove drag.
Future vision: a pool-builder CRM connecting lead intake, customer history, follow-up, estimate context, and job handoffs.
Planned: versioned commercial records for calculator assumptions, options, pricing notes, documents, and review state.
Planned: proposal approval, signed-state protection, and change-order controls. No supported DocuSign integration is claimed.
Pilot in development, not field-proven: construction source state, next action, owner, blockers, and freshness. Each source requires a separately approved scope.
Planned: finance handoff visibility for estimates, invoices, payments, and deposits. No supported QuickBooks integration is claimed.
Planned: reviewed customer updates, closeout prompts, and communication controls; not an available automated messaging service.
In development: a shared PipeDream brain on Databricks for evidence-backed advice, separate from the CRM. Customer isolation and field behavior require verification before use.
Implementation principle
Automate the office without making the company brittle.
The design must separate internal assistance from external action. Customer messages, contract changes, finance writes, and AI-generated outputs require gates, source labels, and human ownership.
01Map the current systems and where each one owns truth.
02Identify retyping, duplicate work, stuck handoffs, and owner-memory dependencies.
03Build automations around approval gates, not around wishful thinking.
04Leave behind operating evidence that staff and buyers can understand.
Start a conversation
What’s getting in your way?
Tell us about your pool company and the work that keeps landing back on your desk. We’ll talk about whether there’s a useful next step together.