Treat the call as a workflow
The engineering scope extends beyond generating speech: call management, conversation context, and human handoff need to work together.
VoiceGrid.
A conversation is just the beginning.
Built from scratch and scaled a healthcare voice-agent platform, owning the frontend, backend, deployment, and ongoing operations.
1,000+ calls / day during pilots
VoiceGridWORKFLOW PREVIEW
BUILT AROUND THE CONVERSATION
A voice. A next step.
Connect Converse Review
The work behind the product.
Healthcare calls are part of a larger operational workflow. The platform brings call management, voice conversations, human handoffs, and operational review into one product.
What I owned.
- Built the complete product from scratch, across architecture, frontend, and backend.
- Built conversation orchestration for inbound and outbound voice agents and human handoffs.
- Owned deployment, scaling, and ongoing production management.
- Built evaluation, failure handling, and observability into the platform, and continued improving it in production.
How the product flows.
The main stages of the product workflow, from start to outcome.
- 01Call
- 02Conversation
- 03Handoff / outcome
- 04Review
The details that matter.
Keep people in the loop
Human handoffs are part of the product. The interface should make the conversation and next action understandable to an operator.
Make behaviour inspectable
Evaluation and observability belong alongside orchestration, so a team can examine behaviour and improve the workflow over time.
Software in use.
VoiceGrid handles more than 1,000 calls per day during healthcare pilots. I own the product from its initial build through deployment, scaling, and ongoing operations.
The public product website.
KEEP EXPLORING
Ask me about this build