A controlled commercial experiment

Decide whether demand-driven commerce is worth implementing, before implementing it.

The Request Readiness Sprint examines one repeated Catalogue Blind Spot in your business, models the relevant capability and constraints, prototypes the future decision process and ends with a written recommendation to expand, revise or stop.

Apply for a Sprint Start with one enquiry instead

The Sprint is successful when it produces a deliberate decision, even when that decision is not to implement.

Fit

This is worth doing for some businesses and a waste of money for others.

A good fit if

  • You regularly receive enquiries the published catalogue cannot express.
  • Those enquiries arrive by phone and email rather than through the website.
  • They are currently handled manually by sales or technical staff.
  • You can share examples of real customer enquiries, redacted as needed.
  • Someone in the business can say what it is genuinely able to deliver.

Not a good fit if

  • You sell a fixed catalogue with no configuration, modification or made-to-order capability.
  • Your catalogue already answers essentially every request you receive.
  • No one internally can approve what the business is able to deliver.

If the second column describes you more accurately than the first, say so and we will tell you not to buy it.

How it runs

Four stages, each with a named output.

  1. Stage 1

    Collect the pattern

    • You share a representative set of real customer enquiries, redacted as needed.
    • We identify the repeated Catalogue Blind Spot rather than treating each enquiry as unique.

  2. Stage 2

    Model capability and constraints

    • We draft a Capability Map of what the business can deliver beyond the catalogue.
    • We draft a Constraint Record of the rules that govern it.
    • Your owners validate both. Nothing is treated as approved until they do.

  3. Stage 3

    Prototype the decision

    • One real enquiry becomes a Structured Opportunity.
    • That opportunity becomes a prototype Decision Record: outcome, owner and reasoning.

  4. Stage 4

    Recommend

    • A written Pilot Decision Brief setting out what the evidence shows.
    • A recommendation to expand, revise or stop.

Price

€2,000

One price, fixed scope, no retainer and no obligation to continue. If the Pilot Decision Brief recommends stopping, the engagement ends there and you keep every deliverable.

€2,000

Credited in full against implementation if you decide to proceed.

Customer enquiries you shareA representative set
Catalogue Blind Spot1 repeated pattern
Capability MapDrafted and validated with you
Constraint RecordDrafted and validated with you
Final decisionExpand, revise or stop
Implementation creditFull Sprint price credited

  1. Opportunity Ledger sample

    A structured record of what customers requested, including incomplete, rejected and unresolved demand.

  2. Capability Map

    The governed products, materials, dimensions, modifications, methods and approval paths available behind the catalogue.

  3. Constraint Record

    The rules that determine what can be offered, under which conditions and with whose approval.

  4. Prototype Structured Opportunity

    One real enquiry translated into a commercially evaluable object.

  5. Prototype Decision Record

    The proposed evaluation, outcome, owner and reasoning for that opportunity.

  6. Pilot Decision Brief

    The evidence-based recommendation to expand, revise or stop.

The Sprint is successful when it produces a deliberate decision, even when that decision is not to implement.

Apply for a Sprint

Questions

The things worth asking before applying.

What if the recommendation is to stop?

Then that is the deliverable, and it is a successful Sprint. You will have a written account of which demand exists, what the constraints are and why implementation is not currently justified, which is considerably cheaper to learn now than in a six-month build.

How does this relate to the founding-partner programme?

The Sprint is a paid engagement that decides whether implementing this is worth it. A founding partnership is a different arrangement: we take three per sector, they receive credits toward consulting and platform fees, and in exchange we get a working relationship we can learn from. If you think you would be a good founding partner, apply for that instead. It costs you nothing and it is a bigger commitment on both sides.

Do we get a working integration?

No. The Sprint produces documents and a prototype decision path, not deployed software. Implementation is a separate decision the Sprint exists to inform.

Do you need access to our systems?

No. The Sprint runs on the enquiries you share and on your experts' knowledge of what the business can deliver. No ERP, PIM or production system access is required.

How much of our people's time does it take?

A few hours from whoever can say what the business is able to deliver, mostly validating the draft Capability Map and Constraint Record. We cannot produce those without them: capability that no one has approved is not capability.

What happens to the enquiries we send you?

They are treated as another company's confidential material. Remove names, prices and sensitive project details before sending. We will delete them on request, and we will not use them as public examples without asking you separately.

Apply

Tell us about the pattern, not about your company.

Three steps. Describe the request your team keeps handling by hand, answer two or three questions about it, then tell us where to reply. We answer either with a proposed Sprint or with a reason not to run one.

  1. Describe the request
  2. Two or three questions
  3. Where to reply

Write it as you would describe it to a colleague. Redact names, prices and confidential project details.