Construction Data Insights
The Quote That Never Gets Re-Typed
AAA's salespeople quote, get approval, and hand work to the crews inside one system, where the quote the customer sees, the number the manager approves and the schedule the crews work are the same record.
01
The challenge
Industrial services is a repeat-relationship business. AAA's sales team quotes work for property managers, schools, food manufacturers and logistics operators, often while standing on the customer's site, and the same account produces a steady stream of quotes, revisions and won jobs over years.
That pattern makes the sales process easy to get wrong in a specific way: the quote, the approval and the handover to the crews live in three different places, and every hand-off between them is a chance to re-type something. A quote built in a document, approved over email and re-keyed into a scheduling system keeps everyone busy and keeps nobody certain that the number in the proposal, the number the manager approved and the number the crews are scheduled against are the same number.
There's also the question of what a quote means after it's sent. In most systems an order is either won or lost, and reality is messier: quotes get revised, customers go quiet, work gets re-scoped. When every non-win is recorded as a loss, the win rate stops meaning anything.
And quoting has its own rhythm. Site photos, scope lines, pricing, terms, the customer's purchase order. The faster that comes together, the more quotes a salesperson can put in front of customers while the conversation is still warm.
02
The solution
The whole sales cycle lives on one order record inside AAA's Dynamics 365.
A salesperson opens an order and everything about the deal is on it: the customer and site, the market, the proposal type, the activity timeline with every email, note and call behind the quote. Where the work will run, they capture the requirements while quoting: site, equipment, staffing, high risk, subcontractors, safety and environmental. That's the part that usually gets lost between sales and operations, captured at the source instead.
The proposal is generated, not assembled. The scope the salesperson authors prices the quote, and the system produces the branded proposal document with photos included, rendering the pricing box as a live preview first so the salesperson sees exactly what the customer will see before it commits. A quote goes from scope to a finished document in seconds, which means it can happen in the car park rather than the office.
Approval is a button. Requesting it sends the approver an email that states the order, its value and who's asking, and the approval or rejection lands back on the salesperson with the rejection reason attached. The order status moves with the decision: to be quoted, submission created, checked, ready for sending, pending. Each state is a column on the sales board, so the whole team can see what's moving and what's stuck.
Closing an order uses an honest vocabulary. Won and lost, but also superseded, when a revised quote replaces the one before it, and withdrawn, when the customer steps away. Each close takes a reason code, so the win rate reports real competitive outcomes instead of every non-win counting as a loss.
And the handover to operations is gated. Before a won order moves to the crews, the schedule has to match the quote. If reality needs more than was sold, that gap goes one of two named ways, absorbed as a management override or sent back to sales as a variation, and whichever it is, it's recorded with the decision.
03
The results
A quote is assembled, priced and previewed in seconds rather than an afternoon, and a salesperson can put a finished proposal in front of a customer while still on site.
The approval loop runs itself. Approvers receive the value, the order and who's asking, and salespeople receive the outcome, with the reason on a rejection. Nobody checks their sent folder to work out where a quote is sitting.
Nothing is re-typed between stages. The scope the salesperson writes is the scope that prices the quote, prints the proposal, and hands the crews their requirements, site notes and equipment list.
The pipeline is a single view. Every live order sits on one board from first quote to won, with age and value visible, so nothing stalls silently and nothing is forgotten.
And the win rate means what it says. Superseded quotes and customer withdrawals are recorded as what they are, so the reports show how the team performs in front of a customer, not how many quotes died in a mailbox.
The delivery journey
How the transformation took shape
01
The journey
The sales app has been built alongside AAA's team, and the design conversations worth recording are about behaviour, not software.
One was about what approval means. The first instinct is an email to a manager with the proposal attached. But an email carries no state: it can't tell you whether the order has changed since it was sent, and the answer comes back as a reply that has to be applied by hand. Routing approval through the order itself, with the value on the request and the outcome on the record, turned it into a step instead of a conversation.
Another was about closing. The natural instinct is won or lost, and it took a deliberate decision to add superseded and withdrawn as first-class outcomes with their own reasons, because otherwise the reports would quietly lie about how the team is actually performing.
And one was about the boundary with operations. It's tempting to hand a won order over the moment it's approved. The balance gate exists because the crews schedule against the quote, and if reality needs more than the quote allows, that decision deserves a name attached to it, made while the quote is still the reference point.
Underneath all of it sits a longer arc. The quoting system started as the thing AAA needed and keeps being refined around how the team actually sells. The app is now the way a quote happens rather than a tool beside it.
02
Implementation strategy
- One order record from first contact to handover. The quote, the approval, the requirements and the outcome live on the same row, so nothing is re-keyed between stages and nothing disagrees.
- Generate the document, don't assemble it. Proposal documents come out of the system from the scope and pricing already held, so a salesperson quotes on site and the customer sees a finished proposal.
- Show the pricing box before it commits. The proposal's pricing is rendered as a preview first, because a document the salesperson hasn't seen is a document that goes out wrong.
- Route approval through the system. Approvers receive what's being approved, salespeople hear the outcome, and rejection comes back with the reason. Nobody chases.
- Close with an honest vocabulary. Won, lost, superseded, withdrawn, with a reason for each, so the win rate reports what actually happened.
- Gate the handover to operations. A won order moves to the crews only when the schedule matches the quote, and a mismatch has two named paths, absorb it or re-quote it, both recorded.
03
Long-term impact
The quote is a record rather than a document. Every proposal, revision and outcome sits on the order, so the history of an account is readable years later, including why work was priced the way it was.
Win and loss became trustworthy. With superseded and withdrawn separated out and a reason on every close, the win rate is a number the business can act on, and the reasons are a catalogue of what customers actually say.
The handover to operations carries no translation loss. The crews schedule the quoted hours against the quoted scope, and any gap between what was sold and what gets delivered is a recorded, named decision.
And salespeople spend their time selling. The system takes the assembly work, the chasing and the re-keying, and what's left is the part only they can do: standing in front of the customer.