Work
Case studies, with the caveats left in.
Each one states its deployment status, how its client is identified, what was measured and how, and what is still unproven.
Voice receptionist and patient admin for a specialist practice
A voice receptionist built to answer and book calls, with day-before reminders, a consent capture flow and a morning digest for the practice team.
Read the case studyConnected Business operations simulator
A working model of how requests move between customers, departments and management: reference numbers, routing, approvals, SLA timers, escalations and reporting.
Read the case studyMore case studies are added when the evidence behind them is ready to publish and the client has authorised it.
What the status labels mean
- Production deployment
- Running for a real business, handling real work.
- Controlled pilot
- Live with real users, but within a deliberately limited scope.
- Tested prototype
- Built and tested, but not in daily use.
- Interactive demonstration
- A working demonstration with fictional data, not a deployed product.
- Concept architecture
- A designed architecture that has not been built.
We use the strongest label the evidence supports and no stronger. A prototype is never described as a production deployment.
Trusted to build what others shouldn't see.
A system that gives a business an advantage is often one it would rather keep to itself.
So we treat client information, commercially sensitive workflows and the details of how a system is put together as confidential by default. Where a client has not authorised publication, we do not publish.
When public disclosure is not appropriate, we show how we engineer through anonymised case studies the client has agreed to, our own working demonstrations, and evidence that can be shared without breaking a confidence.
A client's system is built to serve their business, not our marketing.
Confidentiality is a working standard, not proof of results. No client is named on this site today; each case study states how its client is identified and what was actually measured.
Illustration: an engagement brief where the client name, commercial terms, workflow rules and credentials are redacted, while the sector, an authorised architecture summary and measured outcomes with their method are shown.
Tell us where the work piles up.
Fifteen minutes on a call or WhatsApp. You describe the job that keeps landing on a person. We tell you honestly whether a system should do it, and what that would take.