Loading Gridfused0%
Back to Blog
Business|Analysis|November 13, 2026

When Sales Adds Another Priority to an Already Full Roadmap

Make the new customer request visible alongside the commitments your engineering team is already carrying.

João Dezembro · 5 min

More in Business

A new priority arrives. The work already promised has not disappeared.

A prospect asks for a capability your product does not yet provide. Sales wants to say yes. Your engineering team is already preparing a customer reporting change and working through a reliability issue affecting an existing workflow.

This is a hypothetical company, but the decision is familiar: where would the new work fit, and what happens to the commitments already on the roadmap?

The answer is not necessarily to reject the opportunity. It is to decide which promise the company is prepared to make after the people doing the work have examined the tradeoff.

Make the existing promises visible

Start with the work already in progress. For the reporting change, what did the customer understand it would receive and when? For the reliability work, what impact is the team trying to reduce? Who is needed to finish each one?

Some work may be a firm commitment. Some may be an internal target that can move. Some may still be under investigation. Those differences matter when you decide what can change.

Ask the engineering leader what the team is actually carrying, including support and necessary operating work. A roadmap with empty space on a slide does not establish that the relevant people have time available.

Understand what the new customer needs

Then speak with sales about the new request. What does the prospect need to accomplish? Is the requested feature the only acceptable way to do it? Which part matters for the decision to buy, and what is still an assumption?

A prospect might ask for an automated export because someone currently copies data into another system. A limited export, a temporary process or a later delivery might address the immediate need. The customer may also have a real constraint that makes those options unsuitable. The company needs to ask rather than guess.

Keep an exploratory discussion distinct from a promise. The prospect deserves a clear answer, including what the team still needs to investigate.

Ask engineering what would change

Ask engineering to compare the options against the existing work. A small interface change may depend on a data decision, a supplier or testing that is not visible in the request. It may also turn out to be simpler than expected because part of the capability already exists.

Look for the people and dependencies that overlap. If the same engineer must finish the reporting change and investigate the export, the team needs an explicit sequence. If different people can do the work without creating another constraint, there may be room for both.

Do not turn an early estimate into a guarantee. Identify the uncertainty that could change the decision and agree on who will resolve it.

Choose the tradeoff in business terms

Put the alternatives in front of the person who can authorize the customer and business consequences. The company might keep the current roadmap, offer a narrower capability, move an existing commitment after a customer conversation, or invest in the new request and accept a different risk.

The decision should describe what each option asks the company to do. Moving reliability work may leave an existing customer exposed for longer. Delaying reporting may affect a promised outcome. Declining the request may mean losing a prospect. These are possible consequences to examine, not facts about every roadmap change.

A technical leader can prepare the options and explain the work. The founder or another authorized owner decides the commercial tradeoff. Neither should have to guess what the other has accepted.

Tell the people affected

Once the company chooses, update the people who depend on the answer. The engineering team needs one current priority, the prospect needs a response, and any existing customer affected by a change needs the appropriate conversation.

Keep the reason visible too. If the team is investigating a narrow export before committing to the full feature, record who owns the investigation and when the company will return with an answer. If a commitment needs to change, follow the actual agreement and the people authorized to discuss it.

A new request can be the right priority

The new opportunity may deserve to displace something else. A roadmap is allowed to change when the business learns something important. The question is whether the company understands the change before it makes another promise.

A hiring or capacity problem may also be real. Looking at priorities does not prove the team has enough people or the right skills. If the work cannot be covered under any acceptable sequence, identify that separate constraint rather than disguising it with a new date.

Make one plan the team can use

Before adding the request, ask what outcome the customer needs, what the team would have to do and which current commitments would move. Bring the options to the people who can accept those consequences.

Then give sales and engineering the same answer. The team can make progress on a changed plan when it knows which work has actually been chosen.

Explore CTO as a Service

Learn how technical leadership can connect customer commitments with engineering decisions.

João Dezembro

João Dezembro

Founder & Managing Director

Founder of Gridfused Technologies. Software architect and engineering leader focused on building reliable products, systems, and AI-enabled operations.

November 13, 2026

5 min

Filed under

Categories