Monday starts with a question about the latest version
Imagine a business manufacturing products to order. The customer sends a drawing, a salesperson prepares a quote and a technical specialist adds the conditions. After a phone call, the quantity and deadline change. The next day, the customer accepts. But which version: Friday’s attachment or the revision sent in reply to a different message?
Sales considers the matter closed, while the person planning the work is only starting to gather the missing information. The difficulty is not producing another PDF. It is establishing which version commits the business, who approved it and whether delivery can begin on that basis.
What holds up the work?
Starting point
An enquiry without an owner
A message arrives in a shared inbox, but no one is responsible and no next action is scheduled. The lack of a reply only becomes apparent when the customer calls.
A calculation that changes after the quote is sent
The spreadsheet serves as both calculator and archive. A cost adjustment overwrites the data used to create the offer previously sent to the customer.
The sale is complete, but work cannot begin
Agreeing a price does not mean all details are settled. A drawing, material confirmation or delivery decision is missing, so operations has to reconstruct the conversation.
We design a record of decisions, not another inbox
The central element of the application is the sales case: customer, requirement, documents, owner and next step. A quotation has its own versions, and sending one locks that particular version against editing. A change creates the next version rather than rewriting the history.
We separate customer approval from readiness for delivery. The latter requires an agreed set of information. This prevents the system from handing over an order whose essential parameters are still being discussed.
What the new workflow could look like
Record the requirement and the next move
The enquiry enters a queue with an owner, a response deadline and a list of missing information. At the next contact, the employee can see the context, not just a filename.
Prepare a quotation with its conditions
The calculation includes line items, assumptions and an expiry date. An unusual discount or payment condition may require internal approval before the document is generated.
Record precisely what was approved
Confirmation identifies the quote version and how the decision was received. Partial acceptance or a change request leads to the appropriate next step rather than automatically closing the case.
Hand over a complete package
Operations receives the agreed scope, attachments, deadline and notes. If an ERP system is already in use, we establish which data to transfer through integration rather than creating a second order register.
The most important screen shows what needs attention
A business owner rarely needs another board full of colourful statuses. They need to know which cases are stuck, what is missing and who can make a decision. We therefore organise the operational view around the next action, while keeping the detailed history within each case.
- Salespeople see their enquiries and response deadlines.
- Approvers receive only the cases that need their decision.
- The delivery team sees the approved scope; access to margin information is defined separately.
Exceptions belong in the process
A customer may return to an expired quote, change the invoice recipient or order only some line items. The team must also be able to merge duplicate enquiries without losing messages. We establish when a case can be reopened and when a new quotation is required. A change history and an attachment confirming the decision help resolve questions later.
Let us start with one part that works.
A good first scope covers one type of enquiry, a simple calculation, quote versioning and handover to one person responsible for delivery. We select a path that occurs regularly and has clear acceptance conditions. An advanced pricing configurator, customer portal and further integrations can follow once this workflow has been tested in everyday use.
How will we know it is better?
This is a measurement plan, not a promised result. We agree the baseline before implementation.
Time to the first meaningful response
We compare the time from registration to a substantive reply, distinguishing an automatic acknowledgement from a salesperson’s response and accounting for working hours.
Completeness of the handover
We check how many accepted orders come back for missing information and which fields or documents most often prevent work from starting.
Cases without a next step
We monitor open matters with no owner or deadline. An increase in the number of quotations sent does not, on its own, show that the process is working better.
Questions worth asking
Do we have to replace our current CRM?
Not necessarily. First we check what is missing: the right CRM configuration, a connection to a calculator or a separate quotation module. An additional application makes sense when it fills a specific gap without creating another place to re-enter data manually.
Can the system send quotations automatically?
It can, if we agree those rules. During the first stage, it is often better to automate document preparation while leaving sending to an employee. Exceptional pricing, delivery commitments and non-standard conditions should have a clear approval path.
