This is a live client system that replaced a manual quote-and-invoice step that previously required staff review on every order. A structured intake collects what is needed to price the job before it will submit. The system composes a fee from map data and several job factors, shows the requester a clear quote before they commit, and, once the order is accepted, issues the invoice to them without anyone on staff touching it. The client and their region are not named here.
The constraint that made this worth building
This was not a firm with a broken process. It was a firm with a working process that could not run without a person standing in the middle of it, on every order, all day.
Every order stopped at a human before it could be priced
A request came in, someone read it, someone worked out the fee, someone wrote back. The step was reliable because the person doing it was good at it. It was also the ceiling on how many orders could be taken in a day, and the reason nothing happened on a weekend.
Requests arrived without the facts needed to price them
Free-text requests leave out the things that determine the fee, because the requester does not know which things those are. That produced a second round trip before pricing could start: ask for the address details, ask what the job actually involves, wait, ask again.
The pricing rules lived in somebody's head
The rules were consistent, which is not the same as written down. Consistency that depends on one person’s memory drifts when that person is away, and it cannot be explained to a client who asks why their fee is what it is.
Invoicing was a second manual pass over the same facts
After the work was agreed, someone re-entered the agreed fee into an invoice and sent it. Any transcription step between an agreed number and a billed number is a place where the two can differ, and the difference is usually found by the client.
The pricing decision model, layer by layer
This is how a quote is composed. Each layer can only adjust what the layer above it established, and that ordering is what makes a fee explainable when a client asks how the number was reached.
| Order | Input layer | Where it comes from | What it decides | If it is missing or out of range |
|---|---|---|---|---|
| 1 | Service requested | An explicit selection at the top of intake | Which fee model applies at all, and therefore which questions get asked next | Nothing else is shown until this is answered |
| 2 | Location | An address captured at intake and resolved against map data | Whether the job is inside the served area, and the travel component of the fee | An address that cannot be resolved, or falls outside the area, routes to a person instead of quoting |
| 3 | Job characteristics | Structured intake fields, chosen from defined options rather than typed as prose | The base fee band the rest of the calculation adjusts from | Intake will not submit; the requester is asked for the missing characteristic rather than quoted from a guess |
| 4 | Complexity factors | Intake answers, plus attributes already known about the location | Adjustments applied on top of the base band | Falls back to the standard case and flags the order for review rather than silently under-quoting |
| 5 | Timing | The turnaround the requester selects | Whether an expedite applies to the composed fee | Standard turnaround, with no expedite |
| 6 | Quote presented | The composed figure from layers one to five | Whether an order exists at all, because acceptance is what creates it | No acceptance means no order, no work scheduled, and no invoice |
| 7 | Invoice issued | The accepted quote, carried forward unchanged | The amount billed and the document that reaches the requester | There is no re-keying step, so the invoice cannot drift from the accepted quote |
What the requester actually experiences
One intake, asked in an order that makes sense
The requester answers what the service is, where it is, and what the job involves. Later questions depend on earlier answers, so nobody is asked about circumstances that do not apply. The form is the pricing interview, conducted by the form.
The address is validated before anything is priced
An address that cannot be resolved is caught while the requester is still there to correct it, not an hour later by email. Locations outside the served area are told so immediately rather than quoted and then declined.
A number before a commitment
The requester sees the fee, and what it covers, before agreeing to anything. This is the change that mattered most to the firm. A client who has seen a figure and accepted it does not open the engagement by negotiating it.
Acceptance is what creates the order
Nothing exists in the firm’s queue until the quote is accepted. That keeps enquiries out of the work pipeline and means every order in the system has an agreed fee attached from the moment it appears.
The invoice issues itself to the requester
Once the order is accepted, the invoice goes to the requester carrying the accepted figure, without a staff member producing it. This is the step that replaced a manual quote-and-invoice pass that previously required staff review on every order.
Anything unusual still reaches a person
Out-of-area addresses, jobs whose characteristics fall outside the model, and anything the system would have to guess at go to a human rather than being quoted. Automating the routine cases is only defensible if the edge cases are visibly not automated.
Where this sits in the firm's day
- structured intake form design — The intake refuses to submit until it holds enough to price the job, rather than being an inbox somebody has to interpret.
- document generation and delivery — The quote and the invoice are generated from the same accepted figure, so there is no transcription step between them.
- custom application development — The pricing model is application logic with its own rules and states, not a spreadsheet formula wired into a form.
Is this a fit for your business?
A good fit when
- Every order in your business currently stops at one person for pricing
- Your fee depends on where the job is as much as what it is
- Your pricing rules are consistent but have never been written down
- Quoting and invoicing are two separate manual passes over the same facts
Probably not a fit when
- Every job is genuinely bespoke, priced by judgement with no repeating pattern underneath
- You want published rate-card pricing on a website and nothing behind it
- Nobody is willing to have the pricing rules made explicit
What to have ready
- A sample of real requests as they arrive today, including the messy ones
- Whoever prices the work, for a couple of hours, with permission to say how they actually decide
- Your current invoicing route, so the issued invoice lands where accounting expects it
Questions we get asked
What happens when the system cannot price something?
It routes the request to a person rather than producing a number it is not entitled to produce. Out-of-area addresses, unresolvable locations, and job characteristics outside the model all take that path. A quoting system that never admits it does not know is one that will eventually quote something badly.
Can the firm still override a quote?
Yes, before acceptance. What the firm cannot do is have the issued invoice quietly differ from the quote the client accepted, because the invoice is generated from that accepted figure rather than re-entered. If a fee needs to change after acceptance, that is a visible action rather than an edit nobody sees.
How long does something like this take to build?
The build is rarely the long part. Extracting the pricing rules from the person who holds them, and getting agreement on cases they have always handled by judgement, is what sets the timeline. We usually spend the first stretch writing down rules that already exist and having them argued over.
Why is the client not named on this page?
Their fee structure is a competitive matter and this page describes how it is composed. Naming the firm alongside that description would tell their competitors more than it tells you. If you want to talk to someone who has been through this build, we can arrange it privately with their permission.
Related
- mobile construction estimating and field operations platform
- notice operations and evidence platform
- workflow automation services
- selected product, application and workflow projects
Tell us what the process looks like now and we will map what a system would need to do. No obligation, and you keep the map either way.