B2B procurement workshop / 5 MIN READ
Answer the market inquiry without inventing an offer
Prepare a useful information response that separates current capability, assumptions and approved commitments.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A market-information request can help a buyer shape future procurement. The supplier must answer clearly while checking what the request actually asks, how the information may be used and which statements require commercial or legal approval.
What you will leave with: A bounded RFI response map with evidence owners and disclosure checks.
Use this when
- A buyer requests capability information before issuing a tender.
- A sales team is asked for indicative delivery or pricing information with an incomplete scope.
This is not legal advice, a universal claim that RFIs are non-binding or a substitute for reading the particular buyer’s rules.
Identify the actual purpose and instructions
UK procurement guidance describes preliminary market engagement as preparation for procurement within its stated regime. Read the specific request before assuming it is an invitation to submit a firm offer.
Record the buyer’s questions, response format, permitted clarification route and submission conditions. Ask the appropriate owner to review terms about confidentiality, publication or use of submitted ideas. An informal label does not settle the legal effect of the document. If the request combines market research with contractual declarations, separate those parts and route them for qualified review before submission.
Describe capability at the right level of certainty
For each requested capability, distinguish available now, available with agreed configuration, dependent on another party and merely planned. Link a relevant internal evidence owner rather than copying optimistic language from an old proposal.
Explain limitations that would affect the buyer’s planning. A demonstration environment may show a possibility without establishing production readiness. Avoid naming a customer or sharing their confidential implementation details without permission. Where evidence cannot be disclosed, offer an approved description of the capability and its boundaries instead of inventing a reference or implying that an unverified claim has been independently assured.
Keep indicative estimates tied to assumptions
If the buyer requests a cost or delivery indication, state the scope assumptions and missing inputs that make it provisional. Have the authorized commercial and delivery owners review the answer. Use a clearly described basis rather than a precise-looking number unsupported by the available brief.
Do not turn a request for information into an unapproved discount, delivery guarantee or product-roadmap promise. Where a meaningful estimate cannot yet be made, explain which information would enable one. Answer the question as far as the evidence permits rather than filling every blank with a confident value merely to appear easy to work with.
Review disclosure and preserve the submitted version
Assemble a final response register showing each question, answer owner, approval and relevant limitation. Check the intended recipient and approved submission route. Ensure attachments match the response and contain no unrelated customer records or hidden working notes.
Save the exact submitted version and any receipt under the agreed process. If a later tender appears, review the new requirements independently rather than assuming the earlier response fixes the scope or gives preferential standing. Track any promised follow-up with an owner. A useful RFI response helps the buyer understand the market while preserving a truthful account of what the supplier actually knows.
Make the reasoning concrete.
A fictional public-sector buyer asks a software supplier whether a future integration could be delivered and requests a planning estimate. The integration has been discussed internally but has no approved delivery plan.
Describe the idea as committed capability
Opening: Provide a firm date to make the response look competitive.
Hypothesis: The answer appears complete.
Risk: The buyer may plan around a promise the supplier cannot authorize.
Describe the present boundary
Opening: Explain the dependency, current status and information needed for a reviewed estimate.
Hypothesis: The buyer receives useful planning information.
Risk: The response may reveal that the supplier is not ready for this requirement.
The supplier answers the capability question honestly and has the commercial owner review the conditional estimate. The response follows the buyer’s instructions and makes no claim that the RFI itself guarantees a later opportunity.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Purpose
What decision is this information intended to support?
Rules
What submission, disclosure and contractual conditions apply?
Capability
What is available, dependent or only planned?
Estimate
Which assumptions and approvals bound the indication?
Record
Where is the exact submitted response and follow-up ownership?
Watch for the wrong conclusion.
- Treating every RFI as legally identical.
- Presenting roadmap ideas as currently available capabilities.
- Sharing customer examples without checking disclosure permission.
Your next action
Map one RFI into questions, evidence owners and approval needs before writing the response.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- Cabinet Office: Guidance on preliminary market engagement →Primary UK procurement guidance · Supports: Within its stated procurement regime, preliminary engagement helps prepare for procurement; the supplier response worksheet is original editorial analysis.