Choosing a B2B service provider: a brief that produces comparable proposals
Prepare a B2B service selection brief with outcomes, assumptions and acceptance, and compare scopes, maintenance and handover.
Article language: English

In this article
Three proposals, three different scopes and one table pretending to compare the same thing. Choosing a B2B service provider starts earlier: with a brief describing the problem, desired outcome and acceptance conditions. Without a common basis, the cheapest proposal may cover the least work, while a “comprehensive” one leaves the most room for interpretation. A good brief lets you ask useful questions before purchasing becomes an archaeological dig through attachments.
This procedure concerns preparing an enquiry for a service, such as website design, process analysis or market research. It does not settle legal contract terms or the rules of a particular procurement. It is a practical way to organise requirements, provider responses and acceptance checks. The examples are hypothetical, with no prices or results from real companies.
Describe the situation the provider does not yet know
Start with who needs to do what and what currently gets in the way. For a website it may be an unclear service scope and enquiries requiring repeated clarification. For a process it may be repeated manual checking of documents. “We need a modern solution” gives a provider no basis for proposing a meaningful scope.
Add observations and materials, and label assumptions separately. If you suspect a copy problem but have not conducted a test, say so. The provider can then suggest an investigation instead of pricing a diagnosis nobody has confirmed. In a premium website brief (in Polish), the goal and audience task are the starting point for further agreement.
Name the outcome and show how to check it
Distinguish an activity from a result. A workshop is an activity. An agreed process map including exceptions can be its result. A website project may include mockups, code, copy and public deployment, but not every proposal contains the whole set. State what must be handed over and how completion will be recognised.
An acceptance condition must be testable. “The website will be intuitive” needs a scenario: the visitor finds the service scope, distinguishes an option and sends an enquiry. “Automation works” also requires behaviour on errors or exceptions. You need not design the whole solution yourself to describe the tasks the final result should enable.
Separate requirements from favourite ideas
Mark essential conditions, elements for consideration and hypotheses needing a test. The provider can see where it has freedom and where a real constraint exists. If your company must use a particular system, explain why and the dependency's scope. Do not make a tool's name the goal merely because it looked good in a demonstration. Before naming a new build as the enquiry's only option, compare building your own system, buying a service and manual work (in Polish). Providers can explain differences more easily when the desired result is not equated with one method.
GOV.UK's introduction to choosing technology highlights the ability to change later, adaptation to needs and control of total cost. These are guidelines for UK public services. They inspire our questions about development and maintenance; we do not treat government requirements as obligations on a Polish company.
State your own constraints and dependencies
List existing systems, materials, approvers and deadlines arising from real events. Identify which content is ready and which must be developed. If the provider is to prepare translations, say who will check the meaning and the target material. This missing information does not disappear when an attractive quote arrives.
Check your team's availability. The project may require expert interviews, decisions about the offer and acceptance of successive versions. A provider cannot replace all of these roles. Record what the company will do and who coordinates it. An honest enquiry reveals dependencies instead of promising the provider that needed information will “somehow turn up”.
Agree a common response structure
Ask for proposed scope, stages, outputs, assumptions, exclusions and how changes will be priced. Add questions on maintenance and handover. The format should help comparison without forbidding a better method. Leave room for an alternative and an explanation of its effect on outcomes and costs.
- What exactly will be produced and in what form?
- What must the buyer provide or approve?
- Which assumptions affect scope and timing?
- What is excluded?
- How will we check each important stage's result?
- What will maintenance require after completion?
- How will scope changes and handover be charged?
Do not demand extensive unpaid solutions to the actual problem within the proposal. You can request an approach and an example of a similar result. If a meaningful quote requires a separate analysis, agree its scope. A paid diagnosis before a project (in Polish) should have its own output that helps the company decide on further cooperation too.
Check the service from the user's side too
The provider's finished product is part of the user's whole journey. A form, a message, a conversation and internal handling may belong to different people. Show these connections in the brief. Otherwise the provider may correctly deliver its piece while the company still cannot complete the customer's case.
GOV.UK guidance on commercial off-the-shelf products and services draws attention to the whole service journey and checking suitability for users. The document concerns UK public services. We set acceptance scope for the particular project rather than assuming that buying a ready-made solution removes the need to assess its use.
For a website use an acceptance checklist (in Polish). For an AI tool, provider evaluation before purchase (in Polish) can help. They are different scopes of work. Do not replace a detailed trial with a screen demonstration where everything looks good with data prepared by its author.
Compare scope before amounts
Break proposals down by the same outputs. Mark what is included, excluded and unclear. If one includes writing copy and another expects finished content from the client, account for your own work. Do not count it as a free resource simply because it is absent from the provider's invoice.

For deadlines, check the start point and dependencies. “Four weeks” could mean from signing, receiving materials or approving mockups. This illustrates different definitions, not a recommended project length. Agree the meaning before comparing dates. A calendar does not read the footnotes for you, although it will readily show a delay.
Organise questions without changing the rules halfway through
Collect important clarifications in one place. If an answer changes scope, give the same information to all invited providers. Then you compare proposals made on a common basis. The aim is not formality for its own sake, but being able to explain differences later.
Distinguish a question about the brief from an individual alternative. A provider may propose a different delivery model; record which requirements it meets and which assumptions it changes. Do not squeeze it into the same table cell without comment. A different method can be valuable, but needs evaluation against the goal, not a prize for the most impressive process name.
Check capability on a task close to the commission
Ask the provider to explain its approach to a short scenario connected with the project. For a website it might be accepting a form; for process analysis, identifying an exception; for market research, assessing conflicting sources. The question should test reasoning and responsibility boundaries. It need not require a finished solution to the real problem without agreed payment.
For prior work, ask about the provider's role, scope and permission to use the material. Do not expect confidential documents from another customer. An anonymised process description or prepared exercise may be enough to discuss method. Separate what was shown from conclusions about the whole team. One excellent presentation does not automatically answer who will do your task.
Also check how the partner speaks about limitations. Can it identify missing material, an assumption and the point of decision? Does it promise an outcome dependent on actions outside its control? Honest clarification can be more useful than agreement with every point of the brief. The choice should lead to workable cooperation, not a contest for the longest list of assurances.
Recognise when the enquiry itself needs improvement
If proposals describe entirely different outcomes, examine the brief before judging their authors. Perhaps the task combines investigation with a finished implementation without defining the boundary. Perhaps nobody knows who supplies content. Collect recurring questions and improve the common basis. Do not try to create comparability by arbitrarily adding missing scope to somebody else's offer.
After material clarification, allow time to revise proposals. The provider needs to know which assumption changed and which version of the brief it is answering. Record the document identifier and date. This simple protection helps prevent one party pricing the original task while another evaluates an expanded version agreed in a conversation with someone else.
Sometimes the right result is to postpone selection and commission limited investigation. Define its output, cost and condition for deciding on further work. Do not make analysis an unlimited waiting room. The company should receive material that enables a choice, even if the answer is that the current scope is too broad and the offer and internal responsibilities must be agreed first.
Practise comparing three hypothetical proposals
A company commissions a service website. The first proposal covers design and code, the second also copy, the third adds post-publication support. This invented scenario has no prices. The team first separates the outputs, checks its own capacity to prepare text and determines the maintenance needed. Only then does it assess a comparable version of the whole job.
Two proposals lack an account and source handover description. The company asks the same questions, using the code and access acceptance package (in Polish). It does not assume that “deployment” automatically means full control of services. The clarification enters the agreed scope before it becomes an urgent need after cooperation ends.
Plan the end of cooperation at the start
Ask about export, documentation, account ownership and further use of materials. Legal details require assessment of actual terms, but operational needs can be clearly described. The company should know how the next person will run the project and what remains dependent on a paid service or the provider's access.
For an AI solution, add a provider exit plan (in Polish) and data retention rules (in Polish). For a multilingual offer, check versioning of materials (in Polish). Exit conditions are part of assessing fit, not a pessimistic addition that spoils the beginning of a relationship.
Pass the agreed scope to the people doing the work
After selection, do not leave the brief only in the purchasing folder. The project lead needs the approved proposal, clarifications and open conditions. Check that the provider's delivery team knows the same agreements discussed during selection. Otherwise a useful clarification can disappear between presentation and the first task.
At the start, walk through one output and its acceptance together. Confirm materials, approver and how to request a change. There is no need to renegotiate the entire commission. The aim is to check shared understanding: what is produced, on what basis and when the other side can say the stage is complete. Such a conversation often reveals a gap that is easier to fix before delivery starts.
Close the selection with explicit reasons
Record the selected scope, important differences, rationale and open conditions. Do not reduce provider assessment to a single number without explanation. If a higher cost was accepted for a particular result, name it. If something is outside scope, identify who will complete that part.
After selection, connect the brief with the internal services catalogue (in Polish): who supplies materials, approves and accepts work in your company? You can relate the Aeneia Design scope to the website's goal and present constraints.









