Skip to content
Interface language: English
Imperium / Signal

The client fits your sector, but the assignment does not fit your company: when to decline

Check capacity, boundaries and timing before accepting B2B work, and explain a refusal or useful narrower scope clearly.

Article language: English

Aeneia concept image: a gold-toned, leaf-shaped ornament with iridescent insets rests on dark blue fabric.
In this article

The enquiry looks ideal: a familiar industry, a sensible product and a contact who can explain the need. Only in the third conversation does it emerge that the customer expects round-the-clock system operations, while the company designs and launches systems. Both have been talking about an online store. Each meant different work.

An unsuitable assignment need not mean an unsuitable customer. It may require capacity, time, conditions or responsibility outside the company's actual offer. Recognise the distinction before making a promise. The answer may be to decline, offer a smaller scope or check a condition separately. None should be replaced by an enthusiastic “we'll somehow make it work”.

Industry is only the start of a fit

Imagine a small studio that designs online stores. An office-equipment manufacturer asks for a new sales site and continuing support for order enquiries, stock updates and night-time responses. The studio can build the site but has no team to perform all those activities. This is a fictional example of identifying scope.

The US Small Business Administration’s business-planning guide recommends researching potential customers, demand, market size, location and competition. This is general small-business planning guidance, not a criterion for accepting a particular assignment or a legal assessment of its terms.

In the example, “a manufacturer selling B2B” fits the studio's experience. That does not establish readiness to operate its store around the clock. Separate design, technical maintenance and day-to-day operations. Each scope needs its own basis for delivery. Industry familiarity does not create a team available at two in the morning.

Compare the customer's task with the result of your service too. Their main difficulty may be unclear availability information rather than the appearance of the store. A new website may be part of the answer, but it needs data and a way to update it. Recognise this before treating the enquiry as an ordinary design refresh.

Check delivery capacity before the appeal of the brief

Identify the conditions on which accepting a commitment depends. Can the company do the work? Does it have time and the right people? Can it provide the required checks? Can the customer supply materials and decisions needed for delivery? The answers concern this order, not a general ambition to grow.

Lack of availability differs from lack of competence. A studio may know how to design a store but be unable to start at the requested time. It may also have a free slot and be unable to provide 24-hour support. A later start may help in the first case; changing the date alone does not solve the second.

Do not present planned learning as existing readiness. A company can consciously develop a new scope, but needs suitable conditions and an honest agreement. The customer should understand what is known, what needs a trial and what cannot currently be confirmed. “We have e-commerce experience” is too broad when the question concerns a different part of delivery.

For deadlines, use the principles for passing a promise from sales to delivery (in Polish). The person speaking with the customer needs confirmation of scope and availability. An attractive enquiry makes it tempting to shorten that check for speed; correcting the promise later may be harder than asking clearly now.

Consider whether a gap can reasonably be filled before accepting the commitment. Bringing in a suitable provider may be possible, but needs their confirmation and a clear role. Knowing someone with the right skill does not create an available team. Check that dependency before presenting a partner's name as established capacity.

Also identify the required contact pattern. A customer may need responses outside the studio's working hours. That is a difference in conditions, not a flaw in the customer. Check whether both parties can accept an alternative. Do not agree to continuous availability on the assumption that out-of-hours requests will probably be rare.

A narrower scope should still deliver a useful result

In Shape Up, Ryan Singer distinguishes a time budget for a solution from an estimate and discusses shaping the problem before a commitment. This is a product-development method, not a ready-made service-sales instruction. Here it prompts a narrower question: what useful part fits the actual constraints?

The studio might offer design and launch with a defined handover. Round-the-clock operations remain a separate need the customer must address another way. The reduced scope makes sense only if it gives a useful result and both parties understand who handles the remaining work. It should not conceal a missing link.

Check dependencies in the smaller option. If the new store must show availability, someone still needs to provide current data. If the studio does not manage stock, agree the source and responsibility for updates. Deleting a task from the quote does not make the whole service stop needing it.

A useful outcome can also be a discovery scope: examining the existing site and material needed for a later decision. Do not call it a completed implementation. Explain what the customer receives and what it does not yet confirm. The smaller commitment then remains specific instead of being a polite cover for declining.

Aeneia conceptual photography

Ask the recipient whether the narrower result still meets the need. They may have sought one provider precisely to avoid coordinating several parties. A correctly described website project may therefore still not match their intention. Narrowing is a proposal to consider, not a way to rescue every sales conversation automatically.

If a condition is unknown, postpone the offer for a short check. State who will supply the information and what it will enable. Do not call waiting acceptance of the assignment. Both sides need to know whether they are still discussing the possibility of cooperation or an already confirmed scope; their planning depends on the difference.

Explain what you can take on

An honest refusal can be brief and factual. In the example: “We design and launch stores, but do not provide 24-hour order support. We can discuss the website once it is clear who will run day-to-day operations.” This describes the company's capacity. It does not judge the customer's needs or management.

You need not attach a catalogue of internal problems. The customer does not need your holiday schedule or a story about a difficult previous project. They need the boundary of the offer. If a check could reopen discussion, name it. If you do not plan to provide the scope, do not promise future availability merely to soften the ending.

An assignment already under way needs separate assessment. Changes should be agreed through the proper channel, considering existing agreements. This article concerns a new scope before acceptance, not legal advice on declining. Ending an existing offer calls for a separate look at winding down a service for customers (in Polish).

If you know a suitable provider, you can suggest where to look without promising that person's availability. A B2B referral partnership (in Polish) needs its own rules. A referral must not sound as though the other company has already confirmed the scope or timing; the recipient still needs the appropriate conversation.

When declining because of timing, say only what is actually known about future availability. Offer a checked possibility or agree when to talk again. There is no need to reserve unconfirmed time merely to preserve contact. The customer may need another provider because their deadline matters more than a preference to work with you.

If an important condition changes after the conversation, reassess the scope. The customer may drop 24-hour support or provide its own team. The earlier reason for refusal may no longer apply to the new proposal. That does not mean automatic acceptance: the remaining conditions and ability to deliver still need confirmation.

Repeated questions that receive a refusal can improve the offer. Choose one and see whether the present page communicates the boundary. If not, correct the specific description. If the reader understands but deliberately seeks different work, extra paragraphs may not resolve the difference; a factual answer in conversation is enough.

The website can set up a better question

Examine how the offer describes the service before contact. “Comprehensive e-commerce support” might mean website design, logistics, catalogue operation or communication with buyers. If the company performs only a chosen scope, name it clearly. A broad phrase can attract conversations that cannot lead to a suitable proposal.

Show a typical use, result and starting conditions. The customer should recognise whether the company can help and what is needed for first contact. Describe boundaries naturally alongside the service process. Half the page need not become a catalogue of refusals, nor should the customer need a complete specification before a conversation.

Compare claims with evidence for B2B offer promises (in Polish). If you show a project, explain your own role sufficiently for the reader to understand your competence. Participating in a large store project need not mean operating its whole business. Readers should distinguish the team's result from the work your company actually performed.

If similar enquiries recur, check where readers came from. A service name, an old project description or a sentence in the form may suggest a broader scope. Correct the source of the ambiguity. You need not immediately change the whole offer or treat every refusal as a reason to launch another business line. If a new option is genuinely under consideration, examine new demand and shifts between existing services (in Polish) rather than judging by the number of similar questions alone.

Record the decision without labelling the customer

After the conversation, record the specific mismatch: expected support scope, timing, a missing input condition or responsibility outside the offer. “Difficult customer” gives no such knowledge. It may cause a colleague to reject a later, entirely different enquiry from the same company without proper assessment.

Compare cases with reasons B2B offers are lost (in Polish). Declining a mismatched scope and losing a suitable proposal are different situations. One number labelled “lost opportunities” can obscure both. A useful record helps identify whether offer content, availability or enquiry qualification needs attention.

When an enquiry is narrowed, preserve what the new proposal excludes where it is needed for the next conversation. A colleague should know the customer originally asked for broader support. Otherwise the excluded task may later reappear as an assumed part of the work. The reason for the boundary preserves the meaning of the agreement.

For a new suitable option, revisit a supplier-selection brief (in Polish) from the customer's perspective: do they understand the result, their contribution and how it will be assessed? If discussion changes the earlier scope, preserve the agreement using service-project change principles (in Polish). A company can decline one task and still conduct an honest discussion about another. The customer should leave knowing what can support the next choice.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear