An example, not a client case. The situation recurs in real work; the numbers are an illustration.
01 · Today
Someone digs through the project folder for a comparable proposal from last year.
The requirements from the request are checked by hand against what is technically possible.
Product information comes from the ERP, from a supplier pdf and from someone's head.
The first draft is written by whoever is busiest.
What comes out depends on who happened to write the proposal.
02 · The system
It reads the request and pulls the requirements out as a list.
It searches earlier proposals by content, not by file name.
It takes current prices and specifications from the ERP.
It puts a draft together with the source for each part alongside it.
It flags what it is not sure about, instead of inventing it.
8
proposals per month
16 hours
preparation per proposal
128 hours
per month, before anything is sold
Fill in your own numbers; this is a worked example, not a promise. How much a system can take over depends on the state of your product data. That is exactly what The Scan looks into.
A system like this does not stand on its own. That page shows how the work runs, what it costs and what you get back.
Describe in two sentences how it runs at your end. You will hear whether this works the same way for you, and if it does not, I will say so.