AIM System AI Infrastructure & Machines
Work

Production Work

Systems we've taken to production and still operate, and delivery for a UK client.

Each case study follows the same structure: the client, the problem, the constraints, the architecture, what AIM owned, the result and the evidence.

Engineer presenting results to a client team
15K+
Production calls processed
6.8K+
Calls answered
~45%
Connected / answered rate
3
Industries in production
Healthcare · Education · Hospitality
Case study · Healthcare · Production system

Apple Hospital: patient outreach on APEX Connect

In production
1 · Client

Apple Hospital · Healthcare · India · in production.

2 · Business problem

Reaching large patient lists for outreach while keeping the operational workload on hospital teams manageable.

3 · Constraints
  • · Multi-tenant platform shared with other institutions
  • · Per-tenant capacity limits
  • · Multiple communication providers
  • · Voice and WhatsApp in one flow
4 · Architecture · campaign flow
Patient list
Validation
Campaign queue
Voice workers
Retry engine
WhatsApp follow-up
Outcome reporting
Patient list → Validation → Campaign queue → Voice workers → Retry engine → WhatsApp follow-up → Outcome reporting
  1. Patient list — the hospital uploads the outreach list.
  2. Validation — numbers are checked before anything is dialled.
  3. Campaign queue — calls wait within the tenant's capacity limit.
  4. Voice workers — background workers place the calls.
  5. Retry engine — unanswered numbers are retried on a schedule.
  6. WhatsApp follow-up — a message reaches those the call didn't.
  7. Outcome reporting — every result lands in an automated report.
5 · What AIM owned
  • · Architecture
  • · Backend workers
  • · Telephony and WhatsApp integration
  • · Retry scheduling
  • · Tenant isolation
  • · Deployment and production operation
6 · Production result
15K+calls processed
6.8K+answered
~45%connected / answered
7 · Evidence
APEX ConnectPythonRedisPostgreSQLTelephonySTTLLMTTSWhatsApp Business API
Inside APEX Connect
Before

Outreach to large patient lists competed with the hospital teams' day-to-day workload.

After

Campaigns run on APEX Connect: queue workers place the calls, unanswered numbers are retried, WhatsApp follows up and outcomes are reported automatically.

Illustration of a cross-functional engineering team
Case study · Education · Production system

BIMTS College: a dedicated tenant

In production
1 · Client
BIMTS College · Education · in production.
2 · Business problem
Reliable communication workflows for student outreach, admissions activity and ongoing engagement.
3 · Constraints
Runs on the same platform as other institutions, with its own configuration and billing.
4 · Architecture
Isolated tenant → Campaign automation → Voice + WhatsApp → Outreach tracking
5 · What AIM owned
Tenant architecture, campaign automation, communication workflows, independent configuration and billing separation.
6 · Production result
A dedicated institutional communication environment in production within the same multi-tenant platform.
7 · Evidence
APEX ConnectWhatsApp Business APITelephonyCampaign automation
Illustration of connected desktop and mobile devices
Case study · Hospitality · UK delivery

Café Ciel at The OWO, London

Delivered
1 · Client
Café Ciel at The OWO, London · Hospitality · UK client.
2 · Business problem
A polished digital experience, needed within a compressed launch timeline.
3 · Constraints
Compressed timeline, rapid revisions and production requirements.
4 · Delivery path
Design → Implementation → Revisions → Deployment
5 · What AIM owned
Frontend implementation, responsive experience, content integration, iterative revisions and production deployment.
6 · Result
Delivered on schedule for a UK hospitality client.
7 · Evidence
“Ankit independently delivered a production digital experience for Café Ciel at The OWO, London, within a highly compressed timeline. He handled implementation, revisions, deployment, and technical execution with strong ownership and responsiveness throughout. We would confidently recommend him for future technical engagements.”
— Vedika, Café Ciel
More Than Individual Projects

Different industries. Different systems. One engineering approach.

Our engagements span:

AI & Automation

Voice workflows · AI orchestration · intelligent communication

Software Platforms

Multi-tenant applications · APIs · workflow systems

Cloud & Infrastructure

Deployment · queues · databases · observability

Digital Products

Web experiences · customer platforms · institutional systems

Engineering Across the Stack

One team from strategy to production.

Every engagement draws on the same layers of engineering, shaped to the system being built.

StrategyRequirements · Architecture · Technical planning
ProductUX/UI · Frontend · Backend · APIs
IntelligenceAI · LLM · STT · TTS · Automation
InfrastructureCloud · Containers · Queues · Databases · Observability
ProductionDeployment · Monitoring · Optimization · Operations
Selected Engagements

The range of our work.

HealthcareAI-powered patient communication
EducationInstitutional outreach infrastructure
HospitalityDigital product experience
AI & AutomationVoice and messaging workflows
Software PlatformsMulti-tenant systems and operational platforms
Cloud EngineeringProduction infrastructure and deployment
Workloads

How We Approach Different Workloads

High-volume communication

Campaign orchestration, queues, retries and capacity controls.

Multi-tenant platforms

Tenant isolation, independent configuration and scalable workflows.

AI-powered systems

STT → LLM → TTS pipelines with provider integrations and orchestration.

Digital experiences

Rapid implementation, iterative development and production deployment.

Institutional systems

Reliable workflows designed around operational requirements.

Process

From Requirement to Production

01

Understand

Business objectives, users and technical requirements.

02

Architect

System boundaries, APIs, infrastructure and workflows.

03

Build

Engineering across frontend, backend, AI and infrastructure.

04

Integrate

Connect communication providers, APIs, databases and external systems.

05

Deploy

Move the system into production with the required infrastructure.

06

Operate

Monitor, improve and evolve the system over time.

Planning something similar?

Tell us about the workload and we'll show you how we'd approach it.

Engineer celebrating a launch
Ready