Should you submit a proposal? Decide before you start writing
Decide whether to pursue a B2B service request: check essential conditions, preparation costs, your reason to compete and limits on further work.
Article language: English

In this article
A large request arrives on Friday. The response deadline is short, the client's brand is well known, and the attachments could easily fill a quiet weekend with no other interests. The team opens a proposal document. Only later does it ask whether it can deliver the entire scope and whether the proposal deserves several days from people also needed by existing clients.
It is worth deciding whether to participate earlier. In sales this is called a bid/no-bid decision: either prepare a response or decline to undertake that work. The aim is not to find a way to guarantee a win. It is to make a conscious choice to spend time on an opportunity that suits the company and has enough basis for a sound proposal. We consider the business choice involved in a B2B service request, not how to conduct a public procurement procedure.
Can you meet the conditions before assessing the opportunity?
In our fictional example, a studio receives a request for a website, content and subsequent support for many local teams. It can build the site and organise the content. It is unclear whether the expected support requires someone to be on call continuously, or whether the contractor must maintain every language version. These unknowns affect the ability to deliver, not just the appeal of a presentation.
First read the desired outcome, the important conditions and the selection method. Mark what is required, where an alternative is permitted and what you do not understand. Do not replace that work with a list of your company's strengths. You can have an excellent portfolio and still fail an availability condition for a particular service. That tells you about fit, not the worth of the entire team.
Business Queensland's analysis of a tender request separates questions about the request, the buyer and the supplier's own capability, including the cost of preparing a bid and the resources needed to deliver. It is guidance for a specific purchasing environment, not a statement of Polish legal procedure. We use its principle of assessing fit before committing further resources.
A condition you do not meet is different from one whose status is unknown. If the studio cannot provide the required scope, it can decline to participate or check whether a smaller option is allowed. If it does not know what the support clause means, it should ask through the proper channel. Filling a gap with an optimistic assumption does not confirm the ability to deliver.
When recognising a poorly matched assignment (in Polish), the limits of a promise matter. Here you also choose whether to invest in an extensive response at all. You do not need a complete concept to establish that no team is available for the required maintenance. At that point, it may be better to stop preparing the response than to use a finished presentation as a reason to promise more.
Why should the client choose this particular proposal?
Show the connection between the buyer's need and what your company can demonstrate. It is not enough to say that you are creative and committed. Have you done similar work? Can you explain a relevant limitation? Does the proposed method address what the client wants to assess? The reason should rest on evidence, not on your affection for a famous brand.
For our studio, that reason might be an ability to organise multilingual materials and hand over responsibility for updates. It still has to check whether that is what matters in this request. If the buyer primarily wants round-the-clock support, the studio's strength may not determine the choice. Explain that difference before planning an elaborate demonstration.
New Zealand Government Procurement asks suppliers considering a bid to think about the buyer's priorities, their own point of difference, and the time and cost of responding. It also notes the hidden cost of taking staff away from their regular duties. These are tips for suppliers in that system, not proof that knowing a client guarantees success in another process.
Do not assume the incumbent supplier always wins, but do not pretend every participant has the same context either. Record what you know about the buyer's situation and how you know it. A vague suspicion that a company is "only collecting prices" remains a suspicion. It may justify a specific question or caution, not an accusation presented as an established fact.
Use actual lessons from your own lost proposals. The article on analysing lost proposals (in Polish) explains how to collect them. If similar clients did not understand the maintenance approach, consider that in the assessment. Do not transfer the reason for one lost bid to every new request. A different scope and different criteria may require a very different proposal.
Do not invent a percentage chance of winning merely because a spreadsheet asks for a number. You can record reasons supporting participation, significant gaps and how certain you are about them. If the company really has comparable data, it may use it within appropriate limits. Without that data, a precise "37 percent chance" is above all a precise way of writing down a guess.
Do not let an overall score conceal a mandatory condition. In our example, a high score for an attractive client and a good portfolio cannot make up for a missing required on-call service. Separate such conditions from strengths that can be compared. Only then consider whether there is a confirmed way to close the gap before making a commitment.
If you use scores, keep the reason behind each one. Two people may enter the same number for very different reasons: one knows the client's need, the other likes its brand. A discussion of the evidence matters more than calculating an average. The note should let you return to a particular claim when new information arrives.
Include someone who would deliver the service. Sales may recognise the opportunity but not know a specialist's current workload. The delivery team may know the constraints but not understand that a smaller option might be possible. A joint assessment does not require an elaborate committee. It requires access to the information that determines this proposal and someone authorised to make the final choice.

What does the opportunity to submit a response itself cost?
Break preparation down into people's work and materials: reading requirements, asking questions, defining scope, developing a concept, calculating, checking and submitting the response. Add external costs if they are actually needed. Do not count only the time of the person assembling the document. An expert's hour taken from a current project is still a cost, even if no separate invoice appears.
Business Queensland's guide to the main tender steps calls for planning the preparation cost, necessary information, resources and responsibilities before writing. It separates this work from producing the document later. We use that distinction without copying foreign deadlines or procedural rules into a private request.
Suppose for planning purposes that preparation takes several days from a small team. We give no invented price or outcome. The question is what other work those people will postpone. There may be a smaller, suitable request or an existing project awaiting acceptance. Compare real alternatives instead of treating time visible in a calendar as free.
Check the cost after a possible win too. The proposal may require a specialist or tool that is not available to the company by the expected date. Writing a good document does not itself ensure later availability. If the plan depends on a partner, confirm its role and ability to participate rather than listing a familiar studio as a ready team without a conversation.
Allow for your own registration as a supplier with the buyer if this model requires it. The article on supplier registration (in Polish) discusses the steps. Some steps may need information from several roles. Creating an account alone is not evidence that those steps are complete. Record the outstanding condition and its effect on the plan to start the service.
Set a limit for work on the response and identify who may approve an extension. The point is not to abandon the request automatically at the first difficulty. It is to make another decision when an extra concept, presentation or series of meetings appears. Otherwise, a small participation can quietly become a large project nobody consciously chose.
What will you do with an unknown that could change the decision?
Instead of choosing "yes" or "no" immediately, sometimes a limited check is worthwhile. For our studio that would mean asking about the support scope and language materials. Decide who will ask and when the team will return to the decision. The status should be clear: we are doing limited investigation, not preparing a full proposal under the pretence that the decision is still pending.
Use the question channel specified by the buyer. Do not seek informal confirmation that could contradict the documents or lack the proper authority. If the answer changes a requirement, record its content and scope. The actual rules on equal treatment or permitted contact require assessment of the applicable procedure, not guesses from a sales guide.
A common basis in the supplier-selection brief supplied by the buyer makes proposals easier to compare. The article on a supplier-selection brief (in Polish) discusses how to prepare one. As a contractor, check whether you can respond to that basis without adding unnoticed assumptions. If you propose an alternative, say what it changes. Do not describe a narrower scope as full compliance merely to get the document through its first reading.
If participating is intended to teach you about a new area, name that goal and set its limit. Do not retrospectively count the entire cost as priceless experience. You can consciously choose to try, but the attempt should have a question and a useful result even if you lose. A major brand in your inbox does not guarantee that value.
Do not confuse a proposal process with co-creating a service with a client (in Polish). Co-creation requires separate agreement on each side's contribution, tasks and limits on using materials. Preparing more unpaid concept variants does not become that model merely because both sides speak regularly.
How do you record the decision so you do not start again a week later?
A short note should state the decision, its reason, important assumptions and the next move. If participating, name the owner, the preparation limit and missing information. If declining, record a specific reason without labelling the client. If waiting, name the condition for returning. That way, the next invitation will not automatically trigger the same work from the beginning.
You can keep a simple set of questions for the team discussion:
- Can we deliver the required scope and demonstrate the necessary capability?
- Which important client need will our proposal address particularly well?
- What do we not know, and can we clarify it before committing more work?
- What will we postpone to prepare the response, and what will be needed after a win?
- What would justify changing this decision or increasing the work limit?
After the result, revisit the original reasons. A win does not prove that every earlier concern was unnecessary. A loss does not prove that deciding to participate was a mistake. Compare what was known before preparation with information obtained later. This helps improve the selection of requests without adjusting the story to fit the outcome alone.
If many unsuitable requests arise from how the offer is described, Aeneia Design can help clarify the scope, conditions for starting and contact route on the website. First, however, the company must establish which work it actually wants to accept. Stronger copy should not conceal an impossible promise.
A large proposal deserves work because the company has consciously chosen to prepare it, not because, after several days of work, closing the document feels like a waste. The second argument is persistent. The easiest time to limit its influence is before the file receives its first title, "Proposal_final".








