14+ years building on WordPress / Replies in under 5 hours
AI & Technology 2 min read · Updated July 2026

Beyond the Technical Pitch: Solving the “AI Gap”

AK
Ajay Khandal
WordPress Developer
Beyond the Technical Pitch: Solving the “AI Gap”
TL;DR

Instead of leading a sales call with pricing, this discovery script uses four questions about repetition, friction, bottlenecks, and missed leads to uncover where a business is actually losing money. Each answer points to a specific AI-driven fix, like a RAG-powered support agent or automated lead follow-up, that a developer can pitch as a solution rather than a generic service. The goal is shifting the conversation from what a project costs to how much it saves or earns the client.

Discovery calls built around question-based selling outsell technical pitches for a simple reason: a prospect who names their own problem out loud sells themselves on the fix. The five questions below are a version of that, tuned specifically for finding where AI actually pays for itself in a client’s business.

The 5-Question Discovery Script

Use these five questions in your next intro call. They are designed to move the conversation from “How much do you cost?” to “How much money can you save me?”

1. The “Repetition” Question: > “What is the one question your team has to answer ten times a day?”

2. The “Friction” Question:

“Where do you see the highest drop-off in your customer journey?”

3. The “Bottleneck” Question:

“If you doubled your traffic tomorrow, what part of your business would break first?”

4. The “Leakage” Question:

“How many leads did you miss last month because your team was offline?”

5. The “Who Else” Question:

“Who else would need to sign off on something like this?”

  • The Gap: This one isn’t about a specific AI feature, it’s about not losing the deal in week six because the real budget-holder was never in the room. Ask it early, before you’ve already built a proposal aimed at the wrong person.

Depth matters more than speed on these calls. A rushed 20-minute call tends to surface surface-level answers and closes at a fraction of the rate a longer, unhurried conversation does, the extra time is usually what gets a prospect from a vague complaint to a real, specific “Leakage” or “Bottleneck” answer you can actually price against.


Moving from “Hourly” to “Value-Based” Pricing

If you find a “Leakage” gap that is costing a client $50,000 a year in lost leads, charging $15,000 to fix it isn’t “expensive”—it’s a 300% ROI.

This isn’t a new idea. Ron Baker has spent decades arguing professional firms should sell intellectual capital, not time, and the same logic applies to AI project pricing: you’re not billing for the hours it takes to wire up an integration, you’re pricing what the fix is worth to the client. See how to sell “intelligence as a service” at scale for the bigger version of this pitch beyond a single project.

In your proposal, don’t list “hours worked.” List Expected Outcomes:

  • Outcome: “Capture 20% of previously lost after-hours leads.”
  • Outcome: “Reduce manual support tickets by 45%.”

Conclusion: Become the Solution Architect

The “AI Gap” is everywhere once you know how to look for it. By using this discovery script, you position yourself as a partner in their growth, rather than just another line item in their budget.

Frequently asked questions

A discovery call is the first conversation with a prospect, focused on questions that uncover their actual problem before any pitch happens. Done well, the prospect names their own pain point out loud, which makes the eventual solution feel like their idea, not a sales pitch.

Price the outcome, not the hours. If a fix saves or earns a client $50,000 a year, a $15,000 project fee is a 300% return, not an expensive line item. List expected outcomes in the proposal (leads captured, tickets reduced) instead of hours worked.

Ask about repetition (what question does staff answer constantly), friction (where do customers drop off), bottlenecks (what breaks under more traffic), leakage (what leads get missed when the team is offline), and who else is involved in the decision. Each answer points to a specific, sellable AI fix, or in the last case, protects the deal from stalling on a decision-maker you never identified.

Value-based pricing means charging based on the value a project delivers to the client rather than the hours it takes to build. Ron Baker's Implementing Value Pricing is the standard reference on this for professional services, and it applies directly to AI and web development projects.

A technical pitch leads with features and hourly cost, which invites price comparison against cheaper alternatives. A discovery-question approach leads with the client's own stated cost of the problem, which reframes the project as a return on investment instead of an expense.

Because deals commonly stall late when the person on the call turns out not to be the actual budget-holder. Asking "who else would sign off on this?" early surfaces that before you've spent time building a proposal aimed at the wrong person.

Longer than feels efficient. Rushed, sub-30-minute calls tend to surface only surface-level answers, while longer, unhurried conversations are what actually get a prospect from a vague complaint to a specific, priceable problem.

AK

Written by Ajay Khandal

WordPress Developer — building, fixing and speeding up WordPress sites.

Work with me →