We crossed 100 paying customers in January. It felt like a milestone worth marking — not with a press release, but with an honest audit of what we've learned. What follows is our attempt to compress two years of customer conversations into the patterns that actually matter.
Who our customers are
The breakdown by sector: healthcare and clinics (26%), professional services and consulting (22%), hospitality and restaurants (18%), education and training (16%), logistics and local services (12%), other (6%). The breakdown by company size: under 50 employees (38%), 50–200 (41%), 200–1000 (17%), over 1000 (4%).
The size distribution surprised us. We expected to be a mid-market product. We're used more heavily by small businesses than we anticipated — because small businesses feel the pain of repetitive customer calls most acutely. An eight-person clinic with 80 appointment calls a day has a problem that a 200-person hospital could throw a receptionist at. They can't. AIVA is their receptionist.
The use case breakdown is even more revealing: 71% of our customers use AIVA primarily for appointment booking, 63% use it for Q&A (hours, prices, services, availability), and 42% use it for both. These numbers are why we rebuilt our positioning around Q&A and booking — that's what customers actually needed from us.
The one thing every successful customer has in common
I've been thinking about how to say this clearly, because I've seen it enough times now that I'm confident it's real.
Every customer who succeeded fast gave AIVA access to their actual systems.
This sounds obvious. It isn't, in practice. Most businesses' first instinct when deploying an AI agent is to give it a FAQ document and a service list — essentially, the same information they'd put on their website. AIVA works with this. It answers questions. It's useful.
But the customers who went from "useful" to "transformative" — the ones who cut their booking call volume by 80%, who freed up their front desk entirely, who stopped missing calls after hours — all of them connected AIVA to live systems. Their booking calendar. Their patient management system. Their appointment database.
The difference is: a customer who says "do you have slots on Friday?" gets either a generic answer or a real answer. The generic answer ("yes, we're usually open Fridays") is technically accurate and completely useless. The real answer ("Friday has 11 AM and 3 PM available — shall I book one for you?") completes the transaction. Same question. Completely different outcome based on whether AIVA has access to live availability.
AIVA is only as good as the systems it has access to. Every "AI is overhyped" story I've heard from a failed deployment traces back to an AI that was given information instead of access.
What failed, and why
The deployments that failed (we've had nine customers churn) broke into three categories.
FAQ-only deployments (4 customers): Described above. AIVA became a slightly better search engine for their website content. Not worth the setup cost for what it delivered. The fix is always the same: connect it to your booking system or calendar.
Wrong escalation configuration (3 customers): These teams set AIVA's escalation threshold too low — essentially, AIVA routed everything to a human at the first sign of complexity. The result was no meaningful reduction in workload. AIVA's value is handling the repetitive volume — "can I book tomorrow?", "what are your hours?", "how much does it cost?" — so humans can focus on the conversations that actually need them. If you escalate the simple stuff, you've added a system that creates more work, not less.
Insufficient tuning time (2 customers): Both churned in weeks two and three. AIVA requires a calibration period — typically two to four weeks — where you're watching real conversations, adjusting how it handles edge cases, teaching it your specific service offerings and booking rules. Two customers expected day-one performance without that investment. Their feedback was that AIVA "didn't understand their customers." It didn't, yet. The customers who stayed through calibration saw performance improve dramatically by week four.
The surprise
The finding I didn't expect: the strongest predictor of a successful AIVA deployment isn't the company's size, sector, or technical sophistication. It's whether the person setting it up actually talks to their own customers.
The businesses that succeeded fastest were led by owners or managers who had personally handled booking calls or customer questions. They knew exactly what customers said, how they phrased things, what caused confusion. They configured AIVA based on real understanding of their customers, not assumptions.
The businesses that struggled were often managed by people who hadn't done that legwork. Their mental model of a customer inquiry was a clean FAQ lookup. Real customers ask "do you have anything tomorrow morning?" not "query availability for date: tomorrow." An AI configured by someone who doesn't know the difference will reflect that gap.