Skip to content
Home For whom What I offer Platforms & CMS Lab Writing About Contact
NL EN

A proposal takes three days, two and a half of them spent searching.

With a bespoke request the work does not start with writing but with searching: which proposal looked like this, what is technically possible, and what does it cost now. Those three questions sit spread across a project folder, an ERP and the memory of two colleagues. Below is what that costs, what a system can take over, and where it stops.

An example, not a client case. The situation recurs in real work; the numbers are an illustration.

A clipboard with a technical drawing on it and a single red hex bolt resting on top.

01 · Today and after

What changes

How it goes 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.

What the system does

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.

02 · The arithmetic

What it costs while it stays manual

Run the sum with your own numbers. It is about the order of magnitude, not these three figures.

Worked example

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.

03 · The boundary

What it does not do

  • It sets no price and grants no discount.
  • It sends nothing to the client.
  • If a requirement appears in no earlier proposal, it says so and stops.

Does this sound familiar?

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.

This example leads to:

The Scan
Request sent.

Thanks. I read it myself and usually reply within one working day.

This check keeps spam out and usually passes on its own.

Usually a reply within one working day