Jarvis

The problem

Busy operators don’t want another dashboard — they want to call someone who already knows their calendar, their ad spend, and their inbox, and have things handled. Human chiefs of staff cost six figures. The question: can that experience be built as software, with real telephony, not a chat window?

The build

An AI chief of staff with an actual phone number. Azure Communication Services provisions real telephony, bridged to ElevenLabs conversational voice, with Claude (via Azure AI Foundry) as the reasoning brain behind the conversation.

Why serverless (91 Azure Functions): a personal assistant’s workload is bursty — calls, syncs, and scheduled jobs, not steady traffic. Functions price and scale to that shape.

Why Cosmos DB with per-user partition keys: every user’s data is physically partitioned — tenant isolation enforced by the database layout itself, not by hoping queries remember a WHERE clause.

Why usage metering from day one: AI credits and voice minutes are real marginal costs. Metering is wired into the platform with Stripe three-tier billing, because an AI product without cost controls is a liability with a UI.

Around the brain: Meta Ads sync every four hours, Gmail and Google Calendar integration, Entra CIAM auth, App Insights observability, and the whole platform defined in 1.5k lines of Bicep.

Honesty note: themed voice presets, no Marvel branding; field-level encryption and automated secret rotation are known roadmap items.

The method beat

Widest-stack proof: voice, telephony, payments, ads, email, calendar, and multi-tenant isolation — one spec, one builder, one running system.