Why we tell prospects what we can't do

Some of our best partnerships started with us saying no to part of the request.

That runs against most sales advice. The revenue is real, the capability is close enough, and there's pressure to say yes. But in the impact sector, the vendor who names its limits is usually the one who gets trusted.

Nonprofits buy on trust, and they're right to

Corporate software sales often run on demonstration. Show the product, the buyer sees value, the deal moves.

Nonprofit buying is slower and more relational, for good reasons. A new system touches several teams. It changes how people do their jobs. There's rarely an IT department to catch problems. And the money comes from a finite pool that could otherwise fund programmes.

So the real evaluation happens before any feature comparison. Do these people understand how we actually work? Do they believe what we believe? Will they tell us what their tool can't do?

Many nonprofits have been sold solutions before and watched the promises fall apart in implementation. When we say "this won't fix your problem if your team hasn't agreed on how work flows," they hear it differently from a vendor claiming everything is possible.

Qualification protects both sides

We treat qualification as mutual protection. It keeps organisations from buying something they can't implement, and it keeps us from taking on work we can't deliver well. When both sides start a project with fuzzy agreements, someone pays later. Usually it's the programme participants and frontline staff who feel it first.

In practice, that means asking hard questions early.

• What's actually happening today? When someone says "we need better reporting", we don't open a demo. We ask what data systems exist, how information moves between them and where the current process breaks. Sometimes the problem lives in process design or role clarity, and software won't touch it.
• Who's in the room? A founder may feel the pain, but it won't stick without the people who'll use the system. We push for decision-makers, users and sponsors in early conversations. Weak internal alignment at the start tends to collapse during implementation.
• Is the budget realistic? For the work described, including implementation and the learning curve.
• Has the team done its own thinking? When an organisation hasn't built consensus internally, we'll suggest it does that first and come back. It feels like leaving money on the table. It protects everyone.

Vagueness is a warning sign

"We just need to go digital" usually means one of two things. Either the internal thinking hasn't happened yet, or the organisation isn't ready to invest in it. Rushing to a proposal feels productive. It also guarantees a later conversation about what the vendor promised versus what the organisation needed.

Enthusiasm and readiness are different signals. A prospect can be excited about working with us and still be unprepared to execute. Part of our job is telling the two apart.

Naming limits builds credibility

We say plainly where our experience is deep and where it's thin. When a request sits outside our core strengths, we say so, and often point to a partner who's a better fit or suggest another way to approach it.

That tells a serious buyer three things: we know ourselves, revenue isn't our only filter, and we care enough about the relationship to risk the deal. Nonprofits talk to each other. Word that you decline poor fits spreads. So does word that when you do take on work, you've thought hard about whether you can deliver.

Phase the work

When serious interest turns into a deal, we often propose a phased structure: a defined first phase, then a second once both sides have seen results. You can't predict everything upfront in a nonprofit implementation, and pretending you can is how budgets and relationships break.

Phasing lowers the commitment barrier for the partner and gives both sides a real test of fit. We'll also suggest a contingency buffer in budgets. Scope always holds surprises, and it's better to plan for them together.

Small frictions add up

Nonprofit deals rarely die from a clear no. They die from friction. A prospect can't find a phone number. An email sits for three days. The next step is ambiguous. Nobody's sure who the point of contact is.

Each one looks trivial. Together they open a gap between interest and action that widens with every exchange. So we make the basics non-negotiable:

• A named point of contact, never a general inbox.
• A calendar link in the first reply to any scheduling request.
• A one-line confirmation the same day a meeting is booked.
• A reminder the day before.
• An alternative time offered immediately when the first one doesn't work.
• A call instead of an email thread whenever something is objection-level important.

A 30-minute call resolves what a week of email can't, and it keeps the relationship collaborative.

Friction removal doubles as diagnosis. When you make the next step easy and the prospect still doesn't take it, that tells you something about fit or internal alignment. That's the moment for the harder conversation: is this the right time for you?

Sales is a preview of delivery

Prospects make an inference, and they're right to. If a team is organised about scheduling, it's probably organised about scope, timelines and outcomes. The same discipline shows up across the whole relationship.

By the time a partner reaches contract, the credibility work has already happened, in dozens of small interactions that showed we know how to work, we'll show up, and we'll be honest when something won't fit.

---

Previous: Technology has three jobs. Next: Problem first, tool last.