Loading…
Systems / Quote & Order Engine
PROVEN IN THE LABtime · money
Quote & Order Engine
From ping-pong quotes to a price and an order in one flow.
- What it is
- A guided quote-to-order flow: configure, see the price, pay, land in the cockpit.
- Typically gives back
- ~8–15 h/week of quote ping-pong
- Replaces
- Email quotes, spreadsheet prices, and a shop you do not need.
What it costs you without this
Calm arithmetic, not fear. Methodology.
Quote response: 2–3 days of email ping-pong before the customer knows the price.
Lab measurement
Follow-up time lost to re-reading threads: ~45 min per request.
Lab measurement
Details chased by hand before a number can even be given.
Lab measurement
No clean record of who asked for what — the next quote starts from zero.
Illustrative example
| Week | Month | At €40/h |
|---|---|---|
| 15 h | 60 h | €2,400/mo |
20 quotes × 45 min = 15 h/week × €40/h × 4 weeks
Illustrative composite example — 20 quotes × 45 min = 15 h/week ≈ €2,400/month at €40/h. Your scan gives the real numbers.
A firm like this
Van Dijk Installatie
9-person HVAC installer, Utrecht, ~35 quote requests/month
Without the system
- Quotes sit in email for 2–3 days while options are priced by hand.
- Invalid combinations (wrong vehicle + wrong film) are caught too late.
- Payment is a separate invoice chase after the yes.
With the system
- The customer configures the job in a governed catalog — impossible combos never appear.
- An open price is visible before checkout. Mollie takes the payment.
- The order object lands in the owner cockpit, not in a buried thread.
| Metric | Before | After |
|---|---|---|
| Time to a price | 2–3 days | Same session |
| Hours/week on quotes | ~15 h | Exceptions only |
| €/month at €40/h | €2,400 | Scan gives your number |
Illustrative composite example — not a real client
What is in the system
Only what we can point to. Missing pieces stay off this page.
Governed catalog
Options and dependencies are encoded so invalid combinations cannot be chosen.
You see: A configurator that only offers what you actually sell.
Nine guided screens
Welcome through checkout — 9 UI screens, 7 business decision stages.
You see: The customer finishes in one sitting. You are not the form.
Open price before pay
The price is shown before Mollie. No hidden call to “get a number”.
You see: A number you already approved in the rules.
Mollie checkout
Payment states (open, paid, failed, expired) are handled in one flow.
You see: Paid or not paid — not a maybe in WhatsApp.
Uploads in the flow
Logo and specs attach to the order, not to a later email.
You see: The file is on the order object.
Exception gate
A quote the rules cannot price routes to you. The system does not invent a price.
You see: A queue item: “needs your number”.
Order handoff
The finished order lands in the owner cockpit.
You see: One record instead of a thread.
167 active catalog rows (lab)
Lab catalog size measured from the production table (active rows).
You see: Proof the engine can hold a real catalog — yours will be yours.
How it works
- 1. Configure the offer in a governed catalog.
- 2. Show an instant price the owner can stand behind.
- 3. Let the customer check out.
- 4. Land the order in the owner cockpit.
In the build
- Governed catalog with impossible combos blocked
- Nine-screen quote path (lab pattern) mapped to your offer
- Mollie checkout with payment states
- Uploads attached to the order
- Exception queue — no invented prices
- Order visible in the owner cockpit
- Documentation, scans, handover
- Your repository from day one
Good to know
Usually no. The engine prices and takes the order. A shop rewrite is a different job — we will say so.
If every job is a one-off artwork with no repeatable options, a catalog will fight you. We will say that in the scan.
You. Rules are documented. The repo is yours from day one. Complex quotes wait for your click.
Works well with
Start with the scan
90 minutes. Written report is yours. Then a fixed price — or a clear no.