A different moment from where a project starts
AI Quote & Estimate Automation captures scope before a project begins. This is later: work is already underway, and the client asks for something different — an added feature, a changed requirement, a different delivery date. Treating that request the same as new intake, or worse, acting on it from a verbal mention in a call with nothing written down, is where scope quietly drifts without anyone deciding it should.
What a change request actually needs to capture
- What specifically changed, in the client's own words, not a vague summary
- What it affects — timeline, cost, or both — assessed before work continues, not after
- A clear yes from the client on the new basis, not an assumed approval because nobody said no
- A record of what was agreed, so the next conversation doesn't start by reconstructing it
Why this is not the same as Client Approval Automation
Client Approval Automation tracks sign-off on something already finished and sent out. This is upstream of that — a request to change what's being built before it's finished, which needs an impact assessment and a fresh yes, not just a status tracker on a completed item.
What this does not do
It doesn't estimate the cost or timeline impact itself — that judgment stays with your team. It captures the request cleanly, prompts for the impact assessment, and records the client's decision, so the change is agreed on the record rather than assumed from a comment nobody wrote down.
Questions
Isn't this the same as taking a new enquiry?+
No — an enquiry is before a relationship exists. This is a change requested by an existing client on a project already underway, which needs different handling: an impact assessment against the current scope, not a fresh qualification.
Does it calculate the price or timeline impact automatically?+
No — that judgment stays with your team. It prompts for the assessment and records it, rather than guessing at a number.
What if the client just mentions a change verbally in a call?+
The tracked record is what the workflow acts on — capturing it in writing is part of what this exists to enforce, not an optional extra step.
Is this the same as Client Approval Automation?+
No — that page tracks sign-off on something already finished. This captures a request to change something still in progress, before it's finished, which needs an impact assessment first.