Before the estimate
Start with a useful project brief.
Collect site details, the requested work, photos or documents, and the questions the estimator needs to resolve.
Project details change. Keep the client’s request, the scope under discussion, and the team’s decisions together—from the first inquiry through the next handoff.
Discuss your project workflow See a scope changeFrom conversation to project brief
Try adding one more room to this fictional inquiry. The new request becomes visible without turning it into an approved commitment.
The client’s request
A second room. A different finish. One more detail that can change the work.
This updates the example only.
Requested work
Confirm the site details, finishes, and project timing with the client.
EstimateNot preparedScope, price, and timing need confirmation.
No quote issued. No message sent.
Around the work you already do
Choose a process that creates repeated chasing or rework. Shape the setup around the people, tools, and decisions involved.
Before the estimate
Collect site details, the requested work, photos or documents, and the questions the estimator needs to resolve.
As the work develops
Bring client requests and team updates back to the project, with a clear person responsible for the next review.
At the next milestone
Organize agreed decisions, outstanding documents, and follow-up so the next person knows what is still needed.
Make additions and open questions visible. A client asking for more work is the start of a discussion.
Let the responsible person assess the site, resources, and estimate before making a new commitment.
Define how confirmed decisions reach the office, project lead, or subcontractor—and who handles missing information.
A practical first step
Walk us through an inquiry, an estimate handoff, or a scope change. We’ll agree a useful first workflow and test it with your team.
See how setup worksBefore you start
Project intake is one starting point: collect the request, site details, available documents, and questions for the estimator. A change-request or client-update process can also be a good fit. We choose the first scope with your team.
No. The example records additional requested work and flags it for review. The team needs to agree the scope, price, and timing before a quote or approved plan changes.
We can map who needs which information, where it lives today, and how handoffs should work. Specific connections, access, and responsibilities are confirmed for the proposed setup.
We can discuss workflows for job updates, document requests, approvals, and follow-up around billing. Each needs a defined source of information, responsible person, and action scope. Start with one, then expand as the team is ready.
Start with the process that takes too much of your team’s day.
Map your first workflow