Where three days of proposal time actually goes

Ask a sales director how long it takes their team to get a proposal out and you will usually be given a number in days. Ask them how many hours of work is in one and the number will be very much smaller. Almost nobody notices the discrepancy, because the two figures are held in different parts of the conversation: the days are the customer's experience and the hours are the team's.

The gap between them is where the recoverable time is, and it is considerably larger than the drafting time that everyone focuses on.

The anatomy of three days

Here is the shape of it in most organisations I have seen, in the order it happens rather than the order anybody would design.

• -Finding the last one. Somebody searches for a comparable proposal. It exists. It is in a folder belonging to a person who has since left, or in an email thread, or on a laptop. This takes anywhere between ten minutes and a day, and it is entirely invisible in any reporting.
• -Waiting for a number. The pricing requires someone in finance, operations or product to confirm something. That person is not waiting for this request. Elapsed time here is frequently longer than every other step combined.
• -Assembling what already exists. The company boilerplate, the case references, the team biographies, the certifications, the terms. All of it is written down somewhere. None of it is in one place.
• -Actually writing. The part everybody thinks the three days consists of. It is usually two to four hours, and the good salespeople do it quickly because they have made the argument before.
• -Formatting. Making it look like the last one looked. This takes longer than writing it, which is a sentence worth reading twice.
• -Review. One or two people must read it. They are in meetings. The document sits.

Why this matters more than the hours suggest

If you look only at hours, a proposal is a modest cost and it is tempting to leave it alone. Looking at elapsed time changes the picture in three ways.

Proposals that arrive late arrive to a decision that has moved. In a competitive situation the first credible document frames the comparison, and the ones that follow are read against it. Being third in is a materially worse position than being first in, regardless of quality, and the interval that determines the order is mostly composed of waiting rather than of work.

The delay is where opportunities are quietly declined. When a proposal takes three days, a team will not write one for anything below a certain deal size. That threshold is never written down and nobody decides it deliberately, but it exists, and every opportunity underneath it goes unanswered. Reduce the interval and the threshold falls, which does not save money but does add revenue that was previously uneconomic to pursue.

It is the clearest signal a buyer receives about how you operate. Customers cannot assess your delivery before they have bought anything. What they can assess is how you behaved during the sale, and a document that arrives on the day the requirement was understood says something about the organisation that no slide in the document itself can say.

Which four fifths are recoverable

Not all of it, and it is worth being specific about which parts move.

Search and assembly move almost entirely. Where previous proposals, pricing structures, case references and boilerplate sit in a single accessible place, an assistant trained on that material produces a complete first draft of the assembled sections in minutes. This is the single largest recoverable block in the process and it is the least contentious, because nobody believes that locating a document is skilled work.

Formatting moves entirely. A template applied by a system rather than by a person. This is unglamorous and it removes more elapsed hours than the drafting improvement does.

Writing moves partially. A first draft arrives immediately, which is useful, but the part that wins the deal - the specific paragraph about why this client's particular situation requires this particular approach - still requires the person who had the conversation. That paragraph should get more attention rather than less, and in practice it does, because there is now time for it.

Waiting for a number does not move at all. This is an organisational problem, not a technology one. If pricing requires a human decision from someone with other priorities, no tool changes that. The honest answer here is that the dependency should be examined separately: either the salesperson can be given the authority to price within a band, or they cannot, and if they cannot then the delay is a deliberate control rather than an inefficiency.

Review does not move either, and should not. A proposal is a commitment, and the review step is the one part of the process that is not worth compressing. What does change is that a reviewer receives a cleaner document and spends their limited attention on the argument rather than on the typography.

How to establish your own number

Before changing anything, measure two things for the last ten proposals your team sent.

First, the elapsed time: the date the requirement was understood against the date the document was sent. Second, the hours actually worked, from whoever worked them, which requires asking rather than inferring. The ratio between those two figures is the finding, and in most organisations it is somewhere between four and ten to one.

That ratio is also the honest basis for any claim made afterwards. A team that halves its drafting time and leaves a three-day pricing dependency in place has changed a number that nobody outside the team can see. A team that takes elapsed time from three days to one has changed something the customer experiences, and that is the change worth making the case for.