By Sagar Shankaran, Founder of CallSphere
Twenty questions that separate viable AI projects from doomed ones, applied at the discovery stage in 2026.
Key takeaways
The 2026 data is clear: most failed AI projects failed at discovery, not at engineering. The team did not know what success meant, what data they had, what compliance applied, or what stakeholders needed. Building the wrong thing well is still failure.
This piece is the working list of 20 questions every AI project should answer at discovery.
flowchart TB
D[Discovery] --> B[Business: 1-5]
D --> U[User: 6-9]
D --> Tech[Technical: 10-13]
D --> R[Risk: 14-17]
D --> O[Org: 18-20]
flowchart TD
Q[Unanswered question] --> Risk[Project risk]
NoMetric[No metric] --> Drift[Goal drift]
NoData[No data] --> Stuck[Engineering stuck]
NoComp[No compliance check] --> Block[Late-stage block]
NoOwner[No owner] --> Cancel[Cancellation]
Each unanswered question is a future risk. Discovery surfaces them while they are cheap to handle.
For a typical project:
Total: 2-6 weeks for non-trivial projects. Skipping it doesn't save time; it shifts cost to engineering and beyond.
For "What is the measurable business outcome?":
The good answer is testable; the bad one is decoration.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
Some questions don't have crisp answers at discovery time. The discipline:
For client deployments, we run a 90-minute discovery call covering all 20 questions. Clients sometimes resist; we have learned to insist.
The clients who push back hardest at this stage are typically the ones whose projects have the most discovery gaps. The clients who answer cleanly typically have successful deployments.
flowchart TD
Red[Red flags] --> R1[Vague success criteria]
Red --> R2[No clear owner]
Red --> R3[Compliance "we'll figure it out"]
Red --> R4[Volume estimate is wishful]
Red --> R5[Timeline driven by external pressure not feasibility]
Each is a sign discovery is incomplete. Push back; do not start building until they are addressed.
Once discovery is complete, the project moves to:
The 20 questions are revisited at the end of pilot to confirm assumptions held.
If "AI Project Discovery: 20 Questions Before You Start Building" reads like a prompt for your own roadmap, it usually is. The teams winning the next two quarters aren't the ones with the loudest demos — they're the ones who have wired AI into the parts of the business that compound: pipeline coverage, NRR, CAC payback, and time-to-onboard. That means picking a bounded use case, instrumenting it from day one, and refusing to ship anything you can't measure within a single billing cycle.
The honest test for any AI investment is whether it compounds. Models, prompts, fine-tunes, and slide decks don't compound — they decay the moment a new release ships. What compounds is structured data on your actual customers, evals tied to revenue events (not BLEU scores), and agents that get better as more conversations land in your warehouse.
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
That's why the operating model matters more than the tech stack. CallSphere runs on 37 specialized voice agents, 90+ tools, and 115+ Postgres tables across six verticals — but the reason customers stay isn't the count. It's that every call writes to a CRM event, every event feeds a sentiment model, and every sentiment score routes the next call through an escalation chain (Primary → Secondary → six fallback numbers). The infrastructure does the boring, expensive work of making each interaction worth more than the last.
For most B2B operators, the right sequence is unambiguous: pick one funnel leak (inbound qualification, demo no-shows, win-back, expansion), wire an agent into it for 30 days, and measure ACV influence and NRR delta before touching anything else. Logos and category-creation slides are downstream of that loop, not upstream.
Q: Is there a meaningful risk of getting ai project discovery: 20 questions before you start building?
Most teams see directional signal inside the first billing cycle and durable signal by week 6–8. The factors that move the curve are unsexy: clean call routing, an eval set that mirrors real customer language, and a single owner on your side who can approve prompt changes without a committee. Setup typically lands in 3–5 business days on the standard plan, and there's a 14-day trial with no card so you can test the loop on real traffic before committing.
Q: What's the failure mode when ai project discovery: 20 questions before you start building?
Measure two things and ignore the rest at first: a primary outcome (booked appointments, qualified pipeline, recovered reservations) and a guardrail (containment vs. escalation, sentiment, AHT). Anything else is dashboard theater. The most common pitfall is shipping without an eval set — once you have 50–100 labeled calls, regressions stop being invisible and prompt iteration starts compounding instead of going in circles.
Q: How does this connect to ACV, NRR, and category positioning?
ACV moves when the agent influences deal velocity (faster qualification, fewer demo no-shows). NRR moves when the agent owns expansion-trigger calls (renewal, usage-spike, success outreach). Category positioning is downstream — buyers don't pay for "AI-native" framing, they pay for a reproducible motion. CallSphere pricing reflects that ladder: $149 starter, $499 growth, and $1,499 scale, billed monthly, with the same 37-agent / 90+ tool stack underneath each tier.
If any of this maps onto your roadmap, the fastest path is a 20-minute working session: book on Calendly. You can also poke at the live agent stack at realestate.callsphere.tech before the call — it's the same infrastructure customers run in production today.
Written by
Sagar Shankaran· Founder, CallSphere
Sagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
The Official MCP Registry hit API freeze v0.1. Smithery has 7,000+ servers, mcp.so has 19,700+, PulseMCP is hand-curated. We compare discovery, install, and security across the major catalogs.
How to convert vague stakeholder asks into agent specs engineers can build from. The 2026 templates and discovery questions.
The Agent Card spec is how A2A agents advertise capabilities and authenticate. The schema, the trust signals, and the registry options today for cross-vendor discovery.
A 40-point enterprise requirements checklist for evaluating AI voice agent vendors — SOC 2, SSO, RBAC, SLAs, and integrations.
Learn how to build an AI agent that coordinates subcontractors across trades, manages construction schedules, tracks budgets against estimates, and handles change orders for general contractors.
Learn how to build an AI agent that tracks construction project milestones, processes photo documentation, sends delay alerts to stakeholders, and generates automated progress reports.
© 2026 CallSphere LLC. All rights reserved.
Watch how CallSphere handles real customer calls, schedules appointments, and processes payments — live.
Try Live DemoBook a DemoCalculate Your ROI