Three products · One project narrative
One project record.From first number to final draw.
Three comprehensive operating systems close the gap between the businesses that finance, build, and perform the work. Pro runs the investor record, GC runs the builder operation, and Crew runs the trade business—each with an embedded assistant and an explicit human approval rail.
Preview narrativeCurrent evidence shows three role-specific products and network workflows. A seamless cross-role handoff has not been demonstrated.
Three standalone operating systems
Built for each business. Connected around the work.
These are not investor add-ons or thin role dashboards. Pro, GC, and Crew each cover the full operating surface of their vertical. The Project Spine and contractor relationship layer explain how those independent businesses can coordinate without claiming an automatic handoff that has not been demonstrated.
The operating system for real estate investment.
Run deal flow, underwriting, budgets, capital, execution, portfolio reporting, and exit work from one investor record.
- Deal flow + underwriting
- Budgets + capital
- Execution + portfolio
The operating system for general contractors.
Control projects, estimates, costs, bids, subcontractors, field records, changes, draws, owners, and reporting.
- Projects + costs
- Subs + field records
- Draws + owners
The operating system for the trade business.
Connect leads and estimates to schedules, jobs, invoices, cash visibility, cost history, growth, and administration.
- Leads + estimates
- Jobs + crews
- Billing + cash
Groundbreak includes a connection layer for investor, GC, and trade relationships, with invitations, proposals, connected organizations, and selected project context visible at current connection points. Universal network coverage and end-to-end record continuity remain proof-needed.
One narrative · Three role-specific samples
Follow one project narrative through three operating systems.
One Project Spine narrative follows the story from deal assumptions through controlled construction work and invoice status. The evidence views use role-specific approved samples: Pro and GC show Desert Oak, while Crew uses a separate Mesa invoice sample. They demonstrate distinct working views—not a completed transfer or one shared source record.
- Narrative
- 1845 W Coronado Rd
- Scope
- Kitchen refresh
- Evidence
- Role-specific GRO-1126 samples
- 01Pro
Product view 01
Pro establishes project truth.
Start with the deal record: purchase and resale assumptions, a trade-level budget, risk inputs, and the evidence still needed before capital moves.
- Organize deal intake and what needs attention
- Compare scenarios and budget inputs
- Track procurement readiness without implying an order was placed
Needs reviewDeal / GB-26-014
Desert Oak Flip
1845 W Coronado Rd · Phoenix, AZPurchase$315,000Resale input$472,000Rehab budget$54,800Recorded actual$48,400Scope budgetSampleCabinets$19,800HVAC$11,200Flooring$9,800Electrical$7,600Procurement readinessProof needed5fixture line items
- Installed
- 1
- Ordered
- 1
- Bid received
- 1
Next decisionHuman reviewReview procurement states before treating the packet as a completed order record.
Deterministic sampleShipped surfaceProcurement proof-neededCurrent Pro deal and procurement states rebuilt from the deterministic Desert Oak fixture. Statuses demonstrate an inspectable workflow—not supplier execution or a completed handoff.
- 02GC
Product view 02
GC turns the plan into controlled work.
Project control keeps the signed scope, readiness blockers, budget state, subs, and owner-facing next actions in view as the build takes shape.
- See budget and readiness blockers together
- Coordinate subcontractor assignments and bid review
- Prepare owner updates and draw work for human review
2 blockersPortfolio / Needs attention
Desert Oak Flip
1845 W Coronado Rd · Deterministic fixtureReason
Scope and package coverage need GC review.
Open project signals are grouped here so the next manual action is visible without implying a completed handoff.
Review project →Contract value$620kContextSub assignments2ReviewBid responses1WatchBuy-list coverageProof needed3packages1receipt1documentDeterministic sampleShipped routeProof-needed journeyAuthenticated deterministic GC surface. Production-seeded project-level proof and an end-to-end Pro-to-GC artifact transfer were not demonstrated.
- 03Crew
Product view 03
Crew proves execution and closes the payment loop.
The current Crew record carries estimating, job context, invoice state, amount paid, balance, and due status. That is the proof shown here.
- Draft trade estimates and editable line items
- Connect job context to invoice and payment status
- Keep completed field-photo proof outside the claim until verified
New invoice ＋Invoices / Open
Invoice status
Separate sample trade-business recordINV-090 · QA-MARGIN-090
Mesa Kitchen Refresh
OverduePartialInvoice total$18,750Paid$6,000Balance$12,750Due May 24, 2026 · Net 15Open invoice →Excluded from proof: contradictory job-cost and margin values.
Separate sampleShipped statusField proof-neededSeparate Crew invoice-status sample used to prove paid amount, balance, and due-state visibility. It is not presented as a transferred Desert Oak record; contradictory margin data is excluded.
Evidence ledger
Every label sets a claim ceiling.
- Sample
- Sanitized or deterministic data used to show the current product surface.
- Shipped
- A route or workflow surface verified on the audited release.
- Preview
- A narrative or presentation direction, not proof of connected execution.
- Proof-needed
- Visible scaffolding or an incomplete journey that cannot support a stronger claim yet.
Not claimed: automatic ordering or payment, guaranteed accuracy or returns, completed bid/draw/field-evidence handoffs, or customer outcomes.
Enter where you work