parsons/ai consulting

Case study · own operations

A 22-product company. Zero staff.

Parsons Cloud is a platform of 22 AI-driven products used by real customers. It has one engineer and no employees. This is how the phones, the inbox and the money run anyway, and what it cost.

Summary

At a glance

ClientParsons AI LLC (the firm itself)
IndustrySoftware platform, consumer and small-business products
SizeOne engineer, no staff
EngagementBuild and run (continuous)
Timeline2025 – present
StatusLive. You can call it: (833) 700-7551

The problem

The challenge

A platform with billing, phone lines, email and support obligations, and one person to run it. Every inbound call, email and payment had to be handled correctly without a human sitting on it, and every dollar had to reconcile, or the company could not exist at this size.

Solution

What was built

Phone: an AI receptionist on the main line

Answers every call, identifies the caller and the need, books a slot on the calendar with real availability, or promises a callback. Voicemail transcribed and emailed. Calls logged with duration and outcome. Spam ended politely.

Inbox: an agent that drafts, a human that sends

Every email to the business addresses gets a drafted reply in the firm's voice within minutes. Nothing sends without approval. Vendor pitches get a one-line decline or no draft.

Billing: Stripe-backed, self-reconciling

Subscriptions, prepaid usage wallets, metered charges for phone minutes and AI, invoices and receipts, with a nightly tie-out between the ledger and Stripe. Exceptions alert the engineer; nothing silently drifts.

Operations: monitored, written up

Health probes, structured logs, cost audits, and incident write-ups when something breaks (something always eventually breaks). The write-ups are what turn one outage into zero repeats.

The boundary

What a human still does

Approves every outbound email. Takes the booked calls. Decides pricing. Reads the monthly numbers. Reviews exceptions the tie-out flags. That's the design: the machine does the entry and the chasing; the person does the judgment.

The economics

What it costs to run

$15/mothe platform account (the same one customers buy)
$3.99/mothe phone number, plus 3¢ a minute answered
~$0.01AI cost of a typical receptionist minute
0staff hours on inbound calls, email triage or reconciliation

The honest part

What went wrong

A deploy once wiped the routing for two customer domains for a day; nothing paged. The fix was a reconciler and an external probe, and a rule that a deploy cannot touch routes. Voice minutes were initially priced ten times above cost until a measurement said so. Both are written up internally and both changed how client work is built: monitor from the outside, measure before pricing.

Your company

Could this work for your company?

If you are one of the founder-led companies doing $2M–$50M a year and the phone, the inbox or the close is eating staff hours, the same three pieces apply, on your accounts, sized to your volume. The assessment tells you which one first.

Start with a 20-minute call.

You describe the problem. I tell you what I'd build, what it costs, and whether I'm the right person. No deck.