Services

Four service lines. Each dogfooded first.

We don't take on work we haven't already done in production on our own ops.

WhatsApp archiving

334,246 of our own messages, 85% auto-linked to clients, 65% to leads. Disappearing messages stay; deletes need the three-flag DPDP tool, not a button.

Typical engagement — Per-business setup, IMAP/sync wiring, ongoing operate-and-monitor retainer.

What's included

  • Tamper-evident SHA-256 hash chain
  • Auto-link to clients (85%) + leads (65%) by phone
  • 13,866 entities extracted (617 GSTIN, 1,477 PAN); ~1,131 @lid privacy IDs recovered

Cloud telephony

9+ versions in ~6 weeks against a live vendor integration. Sub-100ms inbound routing inside a 500ms budget.

Typical engagement — PBX selection, CRM integration build, smoke-test rollout, ongoing operate.

What's included

  • Sub-100ms inbound routing under a 500ms budget
  • Vendor-neutral CRM layer (Bonvoice today, swappable)
  • Recording → transcription pipeline at ~0.95 confidence on Malayalam-English

CRM customization (Perfex)

3 production Perfex modules, ~18,000 lines of PHP, covered by ~220 automated tests on the VPS post-receive hook.

Typical engagement — Module spec, build, automated tests on the post-receive hook, deploy.

What's included

  • 3 production Perfex modules, ~18,000 lines of PHP
  • ~220 automated tests on the post-receive hook
  • Rides Perfex's own AJAX layer — no third-party REST bolt-on

AI integration

Vertex AI fallback that dropped our extraction HTTP-503 rate from ~50% to ~0 (availability, not accuracy). JWT cache that dropped auth-mints ~75%.

Typical engagement — Discovery sprint, then a build engagement — Vertex AI, Claude, embeddings, knowledge graph.

What's included

  • Vertex AI fallback — HTTP-503 rate ~50% → ~0
  • Shared, content-addressed transcription (~$7/mo)
  • Knowledge writes ~23× faster after batched-upsert refactor
How we engage

Three steps, no surprises.

01

Discover

We map the workflow that's actually costing you time — and define the measurable outcome before any code.

02

Build

We ship in small, reviewable increments with automated tests, the same way we build for ourselves.

03

Operate

We deploy on infra you own, monitor it, and keep improving it — or hand over clean runbooks.

Have a workflow that needs building?

Tell us the workflow that's eating your team's day. We'll show you how we'd automate it — starting from how we run our own businesses.

30 minutes · no obligation · we reply within 1 business day