CoConstruct replacement research¶

This documentation captures the public research and early product framing for a focused construction-management system inspired by CoConstruct.

At a glance¶

This is the starting point for defining a smaller, builder-focused product for builders who use only part of CoConstruct.

It is not an attempt to clone the entire old CoConstruct app, which was acquired and is now being merged into Buildertrend. The documentation separates evidence, product behavior, product direction and open discovery work.

Areas covered¶

1. Landscape and evidence¶

This area establishes what the market and incumbent products publicly say. It covers CoConstruct’s product positioning, Buildertrend’s acquisition and migration direction, the public go-to-market surface and the source material behind the claims.

Start with the public research overview. The public product and workflow, Buildertrend acquisition analysis and website and go-to-market analysis add detail. The sources page records the evidence base.

2. Product anatomy¶

This area describes how the system works as a product. It follows the connected commercial workflow from estimate through budget, selections, purchasing, change orders, scheduling, actual costs and client communication.

The public product and workflow gives the outside-in model. The authenticated product and workflow maps the contractor application, project modules, permissions, settings, reports and implementation implications.

3. Product direction¶

This area turns research into a possible starting point for a new product. It focuses on the smallest useful workflow for the local builders, the likely first-release boundary, differentiation hypotheses and scope risks.

Read product opportunity and scope for the current recommendation.

4. Discovery and validation¶

This area contains the questions that still need answers from the builder companies. It is where assumptions about users, accounting, permissions, migration, ownership and daily workflows become testable.

Use the discovery questions and validation plan before turning the proposed scope into committed requirements.

Suggested reading path¶

1. Read the public research overview for context.
2. Review the authenticated product and workflow for observed product behavior.
3. Read product opportunity and scope for the current product hypothesis.
4. Use the discovery questions and validation plan to prepare builder conversations.

Research conventions¶

• Verified fact means the claim is directly supported by a linked public source.
• Company claim means a metric or statement published by CoConstruct or Buildertrend; it is recorded as their claim, not independently validated.
• Inference means a product or market interpretation based on the evidence.
• Stakeholder context means information supplied in the project conversation and requiring validation with the prospective users.

Research date: 3 August 2026.