Sample advisory pack · Fictional business situation

Understand the delay before choosing the fix.

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 assessment

Fictional 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

What would help the team prepare quotes sooner?

The question

Where are requests waiting, and what should change before the team invests in new software?

The boundary

From a request arriving to a quote being approved. Pricing quality, sales conversion, fulfillment, and customer satisfaction are outside this sample assessment.

The initial recommendation

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.

7 of 12requests entered without an owner
7 of 12requests had an incomplete brief
4.5 daysmedian elapsed business days in the sample

Figures describe the twelve sample records below; they are not a business benchmark.

Time through the quotation process

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.

  1. 01

    Assignment

    Intake coordinator

    13 request-days

    A request waits for an owner.

    Proposed control

    Automatic routing to an owner, with unmatched requests kept in review.

  2. 02

    Clarification

    Request owner

    14 request-days

    The estimating brief is incomplete.

    Proposed control

    Minimum fields and a retained Needs information state.

  3. 03

    Estimating

    Estimator

    14 request-days

    The estimator prepares the quote.

    Proposed control

    A clear ready-to-estimate definition and handoff.

  4. 04

    Approval

    Commercial approver

    15 request-days

    A prepared quote waits for review.

    Proposed control

    Agreed approval rules and an overdue view.

What the sample cannot establish

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

What the sample requests show

Open a finding to inspect its records, proposed response, and questions to check with the team.

F1Seven requests arrived without an owner.

Observed in the sample

Seven of the twelve sample requests entered without an owner. Assignment waiting time is recorded separately from estimating work.

Records: Q-101, Q-102, Q-104, Q-106, Q-108, Q-110, Q-112

Interpretation

Define who receives each request and keep unassigned requests visible. Check why assignment was delayed before selecting a fix.

Verify before acting

Confirm who should accept a request, what happens during absence, and whether assignment timestamps are recorded consistently.

F2Seven requests had an incomplete brief.

Observed in the sample

Seven sample requests are marked as missing information. The sample records distinguish clarification time from estimating time.

Records: Q-101, Q-103, Q-104, Q-106, Q-108, Q-109, Q-112

Interpretation

Agree the information needed to prepare a quote and a route for collecting missing details.

Verify before acting

Review which missing details actually prevent a quote, what can be clarified later, and who contacts the customer.

F3Approval accounts for 15 of the 56 request-days.

Observed in the sample

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

Interpretation

Check which quotes need approval and how exceptions should be reviewed before changing the approval route.

Verify before acting

Confirm the commercial thresholds, delegated authority, escalation route, and the evidence an approver needs.

The underlying sample records

Download evidence CSV

Durations are elapsed business days within each stage. “Missing brief” is an authored flag, not a conclusion inferred from the time taken.

Twelve fictional requests, Q-101 through Q-112
RequestOwner at intakeMissing briefAssignmentClarificationEstimatingApprovalTotal days
Q-101NoYes22116
Q-102NoNo10124
Q-103YesYes03115
Q-104NoYes21126
Q-105YesNo00112
Q-106NoYes12216
Q-107YesNo00101
Q-108NoYes32117
Q-109YesYes01124
Q-110NoNo20114
Q-111YesNo00213
Q-112NoYes23128

03 / Requirements brief

What the quotation process must handle

Download requirements CSV

The default sample requires automatic assignment and change history (R1–R2). Each requirement has a responsible role and a check for accepting it.

R1MustFrom F1

Assign an owner automatically

Apply approved routing rules to assign each incoming request to one owner automatically. Requests that cannot be matched stay in the intake review queue.

Acceptance example

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 P1
R2MustFrom F1

Record changes to owners and status

Automatically retain who changed a request’s owner or status, the previous value, the new value, and the time.

Acceptance example

Reassign a request and change its status. Both changes appear in its history without a separate manual entry.

Responsible role: Process owner

Carried into P1
R3MustFrom F2

Define the minimum estimating brief

The team agrees required scope, quantity, timing, and customer-contact information before the pilot.

Acceptance example

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 P2
R4ShouldFrom F2

Keep clarification with the request

The missing detail, follow-up owner, and next review date remain attached to the request.

Acceptance example

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 P2
R5MustFrom F3

Apply agreed approval criteria

Only approved rules determine whether a quote needs review; exceptions remain reviewable.

Acceptance example

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 P2
R6ShouldFrom F3

Show stalled approvals

Pending approvals show an owner and an agreed review deadline, with a defined escalation route.

Acceptance example

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 P2

04 / Options and tradeoffs

Compare a manual pilot, configuration, and a custom build

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.

Default illustrative conclusion

Test configuration before a custom build.

Configuration ranks highest under the balanced sample priorities. Check automatic assignment and change history in the actual product before choosing it.

Balanced process improvement · illustrative ratings
CriterionWeightImprove the current manual processConfigure a shared business systemBuild a focused internal application
Intake and ownership30%2 / 54 / 55 / 5
Rules and traceability25%1 / 54 / 55 / 5
Speed to a small pilot20%5 / 54 / 51 / 5
Fit for unusual workflows10%1 / 53 / 55 / 5
Ease of maintenance15%4 / 54 / 51 / 5
Weighted score100%2.55 / 53.90 / 53.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.

Improve the current manual process

Test an intake template, named owners, and a shared status list with little setup. Assignments and history still depend on manual updates.

Validate before choosing

Confirm whether a pilot with manual assignment and recordkeeping is acceptable before relaxing R1–R2.

Configure a shared business system

Configure request fields, ownership rules, history, and approvals in a shared system.

Validate before choosing

Check automatic assignment, change history, permissions, exports, and integration access in the actual product and subscription tier.

Build a focused internal application

Build around unusual rules and interfaces, with responsibility for development, hosting, and maintenance.

Validate before choosing

Establish which requirements existing tools cannot meet, and who would build, operate, and maintain the application.

What the criteria mean
Intake and ownership
How well the approach supports required fields, clear ownership, and a working queue.
Rules and traceability
How well status changes, decisions, and exceptions can be reviewed.
Speed to a small pilot
Relative ease of setting up a small pilot; not a delivery-time estimate.
Fit for unusual workflows
Ability to accommodate genuinely nonstandard rules and interfaces.
Ease of maintenance
The work needed to operate and maintain the chosen approach; not a price estimate.

05 / Improvement roadmap

Test the changes before rolling them out

Download roadmap CSV

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.

  1. P1

    Start here

    Agree routing rules and record the baseline

    Process owner + sales operations

    • A process map with owners and routing rules
    • Automatic assignment and change history for the pilot
    • An intake review queue for unmatched requests

    Decision gate

    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

    Requirements: R1, R2
  2. P2

    After P1

    Pilot a complete intake-to-approval path

    Estimating + commercial leads

    • A minimum brief and clarification route
    • Approved decision rules and acceptance examples
    • A limited pilot with exception handling and a recovery plan

    Decision gate

    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

    Requirements: R3, R4, R5, R6
  3. P3

    After P2

    Review the pilot before extending it

    Business sponsor + process owner

    • A baseline-versus-pilot review using consistent definitions
    • Feedback from the people doing the work
    • A decision to adjust, expand, or stop, with named owners

    Decision gate

    The sponsor reviews the pilot evidence and agrees who will operate and support any wider rollout.

    Decide whether to adjust, expand, or stop

Define success before the pilot

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

Use the requirements with your team or provider.

The requirements and roadmap can guide an internal project, brief an existing provider, or form the basis of an implementation with us.

Inspect the sample materials

Evidence register CSV · fictional recordsRequirements brief CSV · rules and acceptance examplesImprovement roadmap CSV · dependencies and decision gates

CSV files contain the fixed sample. Printing includes your current comparison settings.

What keeps getting delayed or worked around?

Describe the delay, who handles the requests, and what you have tried. We can review the process before recommending changes.

Discuss an assessment