Groundbreak

Groundbreak GC / General contractors

The operating system for general contractors.

Groundbreak GC brings projects, estimates, budgets, bids, subcontractors, field records, change orders, draws, owner communication, reporting, and growth operations into one comprehensive builder operating system.

Choose a GC planExplore the system

Proof boundaryThe assistant reads permitted GC records and queues drafts for approval. Current proof does not demonstrate completed cross-role handoffs or autonomous execution.

Groundbreak GC/Project control

Portfolio / Needs attention

Desert Oak Flip

1845 W Coronado Rd · Deterministic fixture
2 blockers

Reason

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$620kContext
Sub assignments2Review
Bid responses1Watch
Buy-list coverageProof needed
3packages
1receipt
1document
Product-native viewResponsive HTML composed from current product states.

01 / Operating system

The complete working surface

Control the business and the build from one place.

GC connects the portfolio command center to the daily construction record—so estimating, cost, subcontractor, field, owner, and back-office work stay legible as conditions change.

  1. 01

    Portfolio command

    See active projects, readiness blockers, budget movement, draws, subcontractor coverage, and buy-list signals.

    • GC dashboard
    • Project portfolio
    • Attention queue
    • Readiness signals
    Shipped
  2. 02

    Estimating + cost

    Build estimates and keep budget, commitments, billing, projected cost, and variance context together.

    • Estimate lifecycle
    • Trade cost lines
    • Budget review
    • Variance context
    Shipped surface
  3. 03

    Subs + bids

    Organize assignments, outreach, responses, exclusions, leveling, award controls, and payment-readiness context.

    • Sub directory + assignments
    • Bid invitations + responses
    • Side-by-side leveling
    • Coordination workspace
    Shipped surface
  4. 04

    Field execution

    Keep the project timeline and daily operating record attached to the work.

    • Tasks + timeline
    • Daily logs + notes
    • Documents + photos
    • Project readiness
    Proof-needed
  5. 05

    Financial + change control

    Review portfolio and project financials while keeping change, draw, buy-list, and reporting work explicit.

    • Financial dashboard
    • Change orders
    • Draw workflow
    • Reports + exports
    Shipped surface
  6. 06

    Owner + client trust

    Prepare owner updates from current project records and organize client-facing project context for review.

    • Editable owner updates
    • Client portal surfaces
    • Draw support context
    • Explicit send controls
    Proof-needed
  7. 07

    Network + growth

    Maintain connected contractor relationships and run the public-facing business around the project pipeline.

    • Connection inbox + graph
    • Capabilities website
    • Owner/developer leads
    • Profile, billing + settings
    Preview

02 / How the work moves

Each chapter connects the operator decision to the record that stays in view.

  1. 01

    Win + plan

    Move from estimate to a controlled baseline.

    Keep the opportunity, trade scope, estimate, exclusions, budget baseline, and readiness work visible before field execution begins.

    Record signalEstimate + baseline

    A prepared estimate or bid response is not represented as a completed award.

  2. 02

    Buy + coordinate

    Tie responsibility and cost to the package.

    Coordinate subcontractors, compare bid responses, track exclusions, and keep payment and compliance readiness beside the work.

    Record signalPackage coverage

    The system shows coordination state; it does not claim autonomous outreach, award, or procurement.

  3. 03

    Build + document

    Give field activity a durable project record.

    Keep tasks, timeline, daily logs, notes, documents, photos, changes, and cost context organized around the active project.

    Record signalProject attention

    Detailed project-route evidence remains labeled proof-needed until the current journey is rerun.

  4. 04

    Report + bill

    Prepare the owner and financial record for review.

    Draft owner updates, assemble draw context, review financials, and export reporting while preserving the human decision at every external boundary.

    Record signalOwner + draw workflow

    Prepared work is not represented as sent, approved, funded, or paid.

03 / AI-native operating rail

Context in. Reviewable work out.

A builder assistant grounded in the current project.

The embedded GC assistant can summarize the records that drive project control, then prepare supported changes inside a visible approval rail.

Ask from the current record

The assistant can read and summarize

  • Projects, budgets, draws, and change orders
  • Daily logs and readiness context
  • Subcontractors and compliance flags
  • Leads, insights, follow-up drafts, and connections
Route through approval

The assistant can prepare

  • Lead follow-up notes
  • Change orders and approval decisions
  • Owner-update drafts
  • Tasks and daily logs

Human-directedNothing executes autonomously. Drafts and decisions require explicit approval and the same permission checks as the manual workflow.

Inspect the product state

The builder view is a control surface, not a glossy dashboard.

The native composition follows the authenticated GC shell: project context, attention state, package coverage, and the next manual action remain legible at every viewport.

Groundbreak GC/Project control

Portfolio / Needs attention

Desert Oak Flip

1845 W Coronado Rd · Deterministic fixture
2 blockers

Reason

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$620kContext
Sub assignments2Review
Bid responses1Watch
Buy-list coverageProof needed
3packages
1receipt
1document
Deterministic sampleShipped routeJourney proof-needed

GC project-control view for the Desert Oak fixture. The data is deterministic and not proof that Pro transferred the project or that a production journey is complete.

Proof, with the edges left on

Control begins with visible exceptions.

  • Portfolio, project readiness, estimate, and budget state
  • Subcontractor assignment, coordination, and bid context
  • Tasks, timeline, daily logs, documents, and change control
  • Financials, draws, owner updates, reports, and relationship surfaces

Not claimedAutomatic Pro-to-GC transfer, completed bid award, autonomous dispatch or procurement, complete compliance vault, final draw package, owner approval, lender funding, or comprehensive network coverage.

04 / Project Spine

Standalone product. Connected context.

GC turns the plan into controlled work.

GC stands on its own for the general contractor business. On the Project Spine, it becomes the control record for scope, responsibility, field activity, cost change, and owner-facing work.

Product
Builder operating system
Spine role
Project control
Current proof
Deterministic route

Next working view

Crew owns the trade business and its billing record.

GC can coordinate the work while Crew serves the trade contractor. The public story does not imply that field evidence, invoices, or payments already cross that boundary automatically.

Continue the Project Spine

Groundbreak GC

Run the builder business from first estimate to final report.

Keep projects, costs, subs, field records, changes, draws, owners, reporting, and growth operations in one control plane.

Choose a GC planSee pricing