When customers can build it themselves, what makes you worth keeping?
AI makes "we could build it ourselves" a fair proposition. The answer starts long before the objection: discovery that can change the recommendation, and a relationship worth keeping.
I was asked a version of this question recently:
It is a fair challenge. AI-assisted development has made a first version of many applications much easier to produce. When the initial build can look like a fraction of the price, "we could build it ourselves" becomes a proposition worth exploring. The real comparison runs well beyond that first version, into integration, support and who owns the result once it is live. That opens the door to a more useful conversation.
On reflection, the work starts long before the objection. If we have not understood the customer, earned real buy-in and shaped something that fits their world, there is little substance behind the relationship to defend. The objection simply exposes that.
Business value can still be a fixed answer
Many software conversations now cover business value as well as features. That is progress. Yet a conversation can discuss efficiency, revenue and return on investment and still arrive at a predetermined answer: our product, used our way. The slides may change, but not the recommendation.
That gap is what interests me. Does what we learn about the customer shape the solution, or only the pitch? Off-the-shelf products can be exactly the right answer, and I am not arguing for bespoke software everywhere. What separates consulting from presenting is a willingness to be influenced. Sometimes that leads to recommending less, combining technologies or admitting a poor fit.
Discovery works both ways
Qualification has its place. Introductions, overview messaging and a standard demonstration help both sides decide whether there is a reason to continue. The risk is treating that early stage as if it had already done the work of understanding the customer.
Real discovery is mutual. The customer discovers what we can offer, and we discover their world. As trust builds, people start to share what has failed before, where colleagues may have concerns and what they personally hope the change will mean.
Most customers have a destination in mind. A good solution consultant helps them plot a credible course towards it, instead of handing over a product as a magic potion. When the ambition is still forming, the job is to help it take shape. Uncertainty calls for exploration, not pressure to buy.
This is where an account executive and a solution consultant earn their partnership. Together, they connect commercial priorities, stakeholder needs and technical possibilities. The result should be ideas the customer has helped shape and can confidently support, and a shared view of what success looks like. For the customer, it should feel like one joined-up conversation, not a sales discussion followed by an unrelated technical demonstration.
The measure is not the number of meetings. It is whether what we learn improves what we propose.
Let the answers shape the demonstration
Consider a customer asking for an AI agent to handle service requests. A standard demonstration might show a question answered and a task completed. Discovery asks where requests stall today, which exceptions consume the team's time and what a better experience would look like. It also asks what the agent may do on its own and who takes responsibility when it hands over.
The next demonstration should reflect those answers. Use an agreed scenario, with properly authorised customer data or realistic synthetic records. Show the awkward handover as well as the straightforward request, agree what would count as success and test it together.
Personalisation does not have to mean bespoke software. The customer should recognise their priorities in the proposal and see that their input made a difference.
A relationship worth keeping
Working in the open-source world taught me that customers should stay because of the value they receive, not because leaving is hard. Contracts give clarity. They should not be the main reason a relationship lasts.
That also shapes the solution consultant's role. The work continues through onboarding and beyond: making sure delivery and customer success inherit the reasoning behind the solution, checking whether the intended outcomes arrive and never knowingly overselling. The consultant need not own every activity to maintain continuity, but staying involved at agreed points helps. Nobody on the customer's side should have to explain their ambitions again from scratch.
We should judge that contribution through adoption, renewals, recurring revenue and customer advocacy, not only the initial signature.
So when a customer says they could build it themselves, the conversation can be an honest one. We can compare both approaches on business fit, outcomes and the full cost of implementation, integration, operation and change. That includes the less glamorous work: training, documentation, coaching, service-level commitments and clear ownership when something breaks. These need to be credible whichever route the customer chooses.
Sometimes the alternative really is better, and a trusted adviser should say so. The aim is to give the customer demonstrable reasons to stay, not simply reassurance that we listened.
The opportunity
As customers explore what they can build with AI, solution consultants can help them make better-informed choices. Product knowledge remains essential. Its value grows when we connect it with the customer's ambitions and stay involved long enough to see the outcome.
How does your organisation give discovery room to change the answer, and not only the presentation?