Win Better Work with a Strong Go/No-Go for Consulting Proposals

My firm will sometimes get calls from businesses under intense financial pressure looking for RFPs and other contracting proposal opportunities as a quick win. But when this happens, teams end up ignoring whether they're positioned to win, financially positioned to complete the contract, or effectively execute the work. When companies are under immense pressure to hit looming revenue targets or are experiencing sudden cash flow issues, such as losing a major client, it becomes incredibly difficult to maintain a disciplined go-or-no-go line on proposals.

So I tell my clients who are making bid decisions to keep an eye on the ROI. They might look at an RFP and absolutely love the project, and it might seem like the perfect scope of work for your team, but if the overall budget is too small, it simply won't be worth the massive effort required to pursue it. If they do win a contract, they're still typically looking at a 90-day cycle: getting awarded and initiating the work before actually receiving the first payment. It's something that clients would absolutely see more clearly if they weren't under the pressure of a looming revenue target. Ultimately, my advice is to find a mechanism — whether it's a process, a third-party advisor, or a pre-scheduled automation— that will keep you grounded and focused on making strategic, big-picture decisions.

The most difficult aspect of the discipline of proposal generation is the uncertainty that comes with having fewer and fewer potential customers for the proposal. When a company has a revenue goal, they will often fall into the trap of attempting to improve that goal by doing more than what the current company can provide, e.g., providing services outside their expertise or ability. This leads project teams to justify such projects, even if they are poor fits, as "growth opportunities." In reality, these projects cause margins to decrease and take the best resources away from higher value work that creates a scalable business.

To resolve this situation, we established the "Core Alignment Filter." If a project causes us to change our infrastructure, tech stack, or hiring model to accommodate one customer, it is a "No-Go." This discipline forces us to say "no" to the distraction, thus maintaining our delivery speed and focus on our primary areas of expertise.

It is much easier to account for a revenue miss for one month than it is to recover from a project that destroys your highest-performing employees. You will only be uncomfortable with discipline when you are in a state of desperation; upholding that discipline will keep your best employees around for the long term.

Chris here -- I run Visionary Marketing, a specialist SEO and Google Ads agency.

March arrives. Pipeline's thinner than you'd like. You get an inquiry. Budget's reasonable. And suddenly a discipline question becomes a survival question: is this the right client, or just any client?

The honest answer? When revenue targets loom, it's hardest to hold the line because saying no means admitting you might miss target. So you pitch. You win. Six weeks later you're drowning trying to deliver something you never should've committed to.

I have one rule that's saved us from exactly this disaster: if you can't articulate, in one sentence, the specific measurable result you'll deliver to this client, don't pitch it.

Not "improved conversions." Not "better SEO." Specific: "increase high-intent search traffic to the homepage by 34% in six months." You either know what you're delivering or you don't. If you don't, the project's going to be chaos.

When pipeline was terrible -- genuinely bad, not just "not ideal" -- I had to decline three inquiries that had budget and timeline. Each one was tempting. None had a clear one-sentence outcome we could actually deliver. I knew if we pitched them, we'd win on optimism and burn out delivering on ambiguity.

The disciplines I enforced: write the sentence before the proposal. If the sentence sounds generic, the project's generic. If it sounds measurable, you might have something. If you can't write the sentence at all, you're selling desperation, not a solution.

Two of those declines came back six months later as better-defined projects. One stayed gone. All three were the right calls because the alternative was bad delivery, churn, or both.

The harder revenue pressure gets, the tighter your criteria need to be, not looser.

Define an Ideal Client Profile that captures industry, size, buying style, budget fit, problem urgency, and cultural traits. Translate each trait into weighted criteria and a simple scoring scale. Require a minimum total score and minimum scores on must-have traits before advancing.

Pull evidence from public data, discovery notes, and past projects to avoid guesswork. Record scores in a central system so trends and bias can be tracked. Start by drafting the Ideal Client Profile and building a one-page scorecard today.

Set stage-gates that move an opportunity from lead to bid only after clear checks by sales, delivery, finance, and legal. Give each gate specific exit criteria such as scope clarity, margin target, and contract red flags resolved. Use short, timed reviews so the process stays fast and focused.

Stop or reshape deals that fail a gate rather than pushing risk downstream. Capture gate outcomes to learn which checks best predict profit and success. Stand up the first stage-gate and publish its exit criteria this week.

Build a risk matrix that scores threats by likelihood and impact across delivery, legal, financial, and client dynamics. Define red, amber, and green thresholds that trigger actions such as no-go, mitigation, or executive sign-off. Tie each risk to a named owner and a dated mitigation plan before proposal work begins.

Make the matrix part of the approval record so exceptions cannot slip through. Review results after projects to refine thresholds and common mitigations. Draft the matrix and set the stoplight rules now.

Make executive sponsorship a hard requirement for any bid over a set size or risk level. Confirm that the sponsor has budget control, decision power, and time for regular governance. Validate access through scheduled steering meetings, direct feedback on scope, and alignment on success metrics.

Treat weak or proxy sponsorship as a no-go, not a soft risk to manage later. Use a short sponsor charter to set roles and escalation paths before writing the proposal. Ask for sponsor access now and hold the line if it is not granted.

Map delivery capacity by role, skill, and location using a rolling heatmap for the next two quarters. Feed the map with confirmed projects, likely wins, vacations, and training time to reveal real availability. Test each pursuit against the heatmap to see if the start date and staffing mix are feasible.

Model options such as shifting timelines, subcontracting, or re-sequencing work to protect quality and margin. Block proposals that would overload key roles or create risky handoffs. Stand up the capacity heatmap and link it to the go or no-go check this month.