The question
Where are requests waiting, and what should change before the team invests in new software?
Sample advisory pack · Fictional business situation
Quote requests are waiting in a team’s inboxes and spreadsheets. Does the team need new software? Review twelve sample requests, the proposed requirements, and three approaches to improving the process.
Open the assessmentFictional assessment with sample records and illustrative option ratings. The recommendations show an approach to the problem, not a client result or a verified software comparison.
01 / Assessment brief
Where are requests waiting, and what should change before the team invests in new software?
From a request arriving to a quote being approved. Pricing quality, sales conversion, fulfillment, and customer satisfaction are outside this sample assessment.
Agree who receives each request and what the estimating brief must contain. Then test the routing and approval rules in an existing or configurable system.
Figures describe the twelve sample records below; they are not a business benchmark.
The four stages below account for 56 elapsed request-days across the sample. These are summed durations across requests, not 56 calendar days or staff-hours.
Intake coordinator
13 request-daysA request waits for an owner.
Automatic routing to an owner, with unmatched requests kept in review.
Request owner
14 request-daysThe estimating brief is incomplete.
Minimum fields and a retained Needs information state.
Estimator
14 request-daysThe estimator prepares the quote.
A clear ready-to-estimate definition and handoff.
Commercial approver
15 request-daysA prepared quote waits for review.
Agreed approval rules and an overdue view.
Elapsed time does not establish the cause of a delay, the effort required to remove it, or a financial benefit. A real assessment would check timestamp definitions, request complexity, operating hours, and the explanations of the people doing the work.
02 / Evidence and interpretation
Open a finding to inspect its records, proposed response, and questions to check with the team.
Seven of the twelve sample requests entered without an owner. Assignment waiting time is recorded separately from estimating work.
Define who receives each request and keep unassigned requests visible. Check why assignment was delayed before selecting a fix.
Confirm who should accept a request, what happens during absence, and whether assignment timestamps are recorded consistently.
Seven sample requests are marked as missing information. The sample records distinguish clarification time from estimating time.
Agree the information needed to prepare a quote and a route for collecting missing details.
Review which missing details actually prevent a quote, what can be clarified later, and who contacts the customer.
Eleven sample requests include time waiting for approval. The sample does not include quote value or risk, so it cannot show which approvals were necessary.
Records: Q-101, Q-102, Q-103, Q-104, Q-105, Q-106, Q-108, Q-109, Q-110, Q-111, Q-112
Check which quotes need approval and how exceptions should be reviewed before changing the approval route.
Confirm the commercial thresholds, delegated authority, escalation route, and the evidence an approver needs.
Durations are elapsed business days within each stage. “Missing brief” is an authored flag, not a conclusion inferred from the time taken.
| Request | Owner at intake | Missing brief | Assignment | Clarification | Estimating | Approval | Total days |
|---|---|---|---|---|---|---|---|
| Q-101 | No | Yes | 2 | 2 | 1 | 1 | 6 |
| Q-102 | No | No | 1 | 0 | 1 | 2 | 4 |
| Q-103 | Yes | Yes | 0 | 3 | 1 | 1 | 5 |
| Q-104 | No | Yes | 2 | 1 | 1 | 2 | 6 |
| Q-105 | Yes | No | 0 | 0 | 1 | 1 | 2 |
| Q-106 | No | Yes | 1 | 2 | 2 | 1 | 6 |
| Q-107 | Yes | No | 0 | 0 | 1 | 0 | 1 |
| Q-108 | No | Yes | 3 | 2 | 1 | 1 | 7 |
| Q-109 | Yes | Yes | 0 | 1 | 1 | 2 | 4 |
| Q-110 | No | No | 2 | 0 | 1 | 1 | 4 |
| Q-111 | Yes | No | 0 | 0 | 2 | 1 | 3 |
| Q-112 | No | Yes | 2 | 3 | 1 | 2 | 8 |
03 / Requirements brief
The default sample requires automatic assignment and change history (R1–R2). Each requirement has a responsible role and a check for accepting it.
Apply approved routing rules to assign each incoming request to one owner automatically. Requests that cannot be matched stay in the intake review queue.
A request matching a routing rule receives the expected owner without manual assignment. An unmatched request is flagged and cannot move to estimating until an owner is assigned.
Responsible role: Sales operations
Carried into P1Automatically retain who changed a request’s owner or status, the previous value, the new value, and the time.
Reassign a request and change its status. Both changes appear in its history without a separate manual entry.
Responsible role: Process owner
Carried into P1The team agrees required scope, quantity, timing, and customer-contact information before the pilot.
Given a request missing a required field, the request is retained in Needs information and is not marked Ready to estimate.
Responsible role: Estimating lead
Carried into P2The missing detail, follow-up owner, and next review date remain attached to the request.
Given clarified information, the owner can update the brief without creating a second request or losing the earlier context.
Responsible role: Request owner
Carried into P2Only approved rules determine whether a quote needs review; exceptions remain reviewable.
Given examples above, below, and at an approval threshold, the route matches the signed-off policy and records the decision.
Responsible role: Commercial lead
Carried into P2Pending approvals show an owner and an agreed review deadline, with a defined escalation route.
Given a test approval beyond its agreed deadline, it appears in the overdue view and follows the approved escalation process.
Responsible role: Approver
Carried into P204 / Options and tradeoffs
Change the priorities to see how the ranking responds. Ratings run from 1 to 5; a higher score means a stronger assumed fit. Actual software capabilities must still be checked.
Turn off the filter to explore a pilot with relaxed R1–R2 requirements. The default requirements remain documented above.
The interactive comparison could not load. The default illustrative comparison remains below.
Default illustrative conclusion
Configuration ranks highest under the balanced sample priorities. Check automatic assignment and change history in the actual product before choosing it.
| Criterion | Weight | Improve the current manual process | Configure a shared business system | Build a focused internal application |
|---|---|---|---|---|
| Intake and ownership | 30% | 2 / 5 | 4 / 5 | 5 / 5 |
| Rules and traceability | 25% | 1 / 5 | 4 / 5 | 5 / 5 |
| Speed to a small pilot | 20% | 5 / 5 | 4 / 5 | 1 / 5 |
| Fit for unusual workflows | 10% | 1 / 5 | 3 / 5 | 5 / 5 |
| Ease of maintenance | 15% | 4 / 5 | 4 / 5 | 1 / 5 |
| Weighted score | 100% | 2.55 / 5 | 3.90 / 5 | 3.60 / 5 |
Score = sum of rating × weight ÷ 100. With the R1–R2 filter on, the manual approach is excluded before ranking. Eligibility is assumed here and must be verified in a real evaluation.
Test an intake template, named owners, and a shared status list with little setup. Assignments and history still depend on manual updates.
Confirm whether a pilot with manual assignment and recordkeeping is acceptable before relaxing R1–R2.
Configure request fields, ownership rules, history, and approvals in a shared system.
Check automatic assignment, change history, permissions, exports, and integration access in the actual product and subscription tier.
Build around unusual rules and interfaces, with responsibility for development, hosting, and maintenance.
Establish which requirements existing tools cannot meet, and who would build, operate, and maintain the application.
05 / Improvement roadmap
The proposed phases move from routing rules to a complete pilot, then a review. Each phase has a check before proceeding; dates depend on the agreed scope.
Start here
Process owner + sales operations
Sample requests reach the expected owners, unmatched requests remain in review, and changes are recorded. The team agrees how elapsed time will be measured.
Before testing the full quotation process
After P1
Estimating + commercial leads
The agreed acceptance cases pass. Operators can handle incomplete requests, reassignment, and approval exceptions without losing records.
Test with a limited set of requests before extending access
After P2
Business sponsor + process owner
The sponsor reviews the pilot evidence and agrees who will operate and support any wider rollout.
Decide whether to adjust, expand, or stop
Record request volume, complexity, ownership, brief completeness, stage times, and rework before the pilot. Use the same definitions during the pilot so the team can compare the results.
The assessment handover
The requirements and roadmap can guide an internal project, brief an existing provider, or form the basis of an implementation with us.
CSV files contain the fixed sample. Printing includes your current comparison settings.
Describe the delay, who handles the requests, and what you have tried. We can review the process before recommending changes.