Signal
Inbound call · 18:42, after hours
Voice AIExample run
- ContextContact recognised — known patient
- 10:3014:15DecisionIntent: reschedule — availability loaded
- Action10:30 Tue confirmed on the call
Outcome
Calendar and CRM updated
We build AI systems that compound.
Strategy, software and automation built as one connected growth system.
Voice AI · example run
- Input
After-hours call
- System
Intent understood and the appointment booked
- Outcome
Calendar and CRM updated
Voice AI: After-hours call to Calendar and CRM updated.
What we build
AI voice systems that qualify, support and convert without losing context.
- Inbound and outbound agents
- Qualification and routing
- CRM and calendar integration
Hi, do you have anything Tuesday morning?
We do. 10:30 works. Shall I book it for you?
That would be great, thanks.
Selected work
View all workSelected systems.
01SaaS Products · 2026
Football Intelligence OS

- Challenge
- Clubs without a performance department have no reliable picture of a player.
- System
- One operations layer where attendance, wellness and match data build a living player profile.
- Status
- Built
02Voice AI · 2026
University IVR audit engine

- Challenge
- A phone tree has no API or sitemap. It can only be mapped by dialling, listening and pressing each option.
- System
- A voice agent that walks every branch live, then scores caller friction across the paths it genuinely reached.
- Status
- Built · 39 institutions audited
03SaaS Products · 2026
Artizyn

- Challenge
- Commission-based trade marketplaces push artisans off the platform the moment a relationship forms.
- System
- A two-way marketplace earning from subscriptions instead of commission, with matching, messaging, reviews and payment inside it.
- Status
- Built · 19 trades
How Keeel thinks
One signal, four stages, and every one leaves something behind.
- Journey map
- Enquiry lands
- No reply until morning
- Caller books elsewhere
- Agent boundary
- if known contact
- then skip qualification
- escalate anything else
- Build state
- Agent logic
- Calendar + CRM
- Escalation to a human
- Event stream
- call.received
- booking.created
- escalation.raised
Built for handoff
The engagement ends. The system keeps working.
A working product
Deployed and usable — not a deck or a disconnected prototype.
Your code, your infrastructure
Repos, accounts, docs and credentials stay with you from handoff.
A measurable loop
Events and dashboards are built in, not added at the end.
Surfaces we deploy into
- Telephony and voice
- CRM and pipeline
- Calendars and scheduling
- Payments and billing
- Data warehouse and events
- Ad platforms
- Internal tooling and APIs
- Web and product analytics
Next step
What should your next system improve?
Two answers is enough to start. We'll come back with where a system would help — and where it wouldn't.