Control Systems for Inbox Operations

Bring your own data. We license you the synthesizer that learns on it.
Generic view · share signals for personalization

1 · What we observed about you

We don't know your business yet — which is exactly the point of the audit. Most teams come to us when their inbox has quietly become the operational nervous system of the company, and the patterns that matter most are now invisible inside thousands of threads.

Our work is to make those patterns visible. We treat your inbox the way a control engineer treats an industrial process: instrument it, find the loops, define the boundary conditions, and stand up a synthesizer that learns on your data and reports back in your voice. Your data stays in your tenant. The model learns. You keep the blueprint regardless of whether you deploy.

2 · The boundary loop we apply

Our work isn't generic automation. It's a closed-loop drill-down into the specific shape of your operations. The audit produces six things that compound on each other:

Operational cost / function
Anchored to your subject matter, not industry averages.
Unit economics at 1x / 10x / 100x
With stated assumptions, so the model holds at scale.
Leverage points
3–5 places where small effort moves big numbers.
Attractors
Why current outcomes keep recurring. Mechanism, not metaphor.
Collapse points
Where the system breaks, with early signals you can watch.
Next pilot move
One concrete action that chains back to the goal.

3 · Scope — in and out

In scope: inbox triage, draft replies in your voice, cross-thread synthesis, compliance gates on every send, pattern detection across customers, audit log on every action.

Out of scope (without separate engagement): calendar management, social posting, voice/phone, marketing automation, model fine-tuning on your data. We do these for clients but they are not part of the standard deployment.

4 · The audit

The audit is the start. It is a paid deliverable. We spend 2–3 weeks instrumenting your inbox, mapping the operational loops, defining the boundary conditions, and producing a written blueprint that names exactly where synthesis would change unit economics.

You own the blueprint regardless of whether you deploy with us. If you do deploy, the audit work carries forward and the deployment cost reflects that.

5 · Forward-deployed shape (if you deploy)

Deployment is not a SaaS subscription. It is a forward-deployed engagement: Murphy's synthesis layer running in your tenant, plus a real human point of contact on our side who knows your org chart by name. The synthesizer learns continuously on your data. The human keeps the relationship honest.

6 · How it actually works

Murphy's synthesis layer reads your inbox in your tenant — your data never leaves your boundary. We use a closed-loop LLM provider with circuit-breaker fallback so a model outage doesn't take you down. Every action is gated by a posture toggle you control: OFF, ASSIST (drafts only), or AUTONOMOUS (within risk bands you set). Every decision is logged with reasoning. You can roll back any change in one command.

7 · Security & compliance

Your data stays in your tenant. We do not pool training data across customers and we do not fine-tune on your data without a separate paid engagement. The platform runs against GDPR (7/7 passing), CCPA (4/4 passing), and is on a SOC 2 trajectory. The legal pages are live:

Privacy Policy · DPA · Sub-processors · Breach Notification

8 · Pricing shape

Pricing is anchored to your org chart. Tier 3 Business starts at $799 per month when advanced synthesis becomes load-bearing. Tier 6 Forward Deployed runs $1,000 to $5,000 per seat per month at org-chart scale, where every person on the chart gets a synthesizer that knows their function. The range exists because every org chart is different.

We invite you to start with the audit. The audit is a paid deliverable — a blueprint document that maps your operational shape and names where synthesis would change unit economics. You own it whether or not we deploy. If you do deploy with us afterward, the deployment is discounted because the audit work carries forward.

9 · Timeline

Week 1: instrumentation, signal gathering, first boundary-loop pass.
Week 2–3: drill-down on the 3–5 leverage points, draft blueprint.
Week 4: blueprint delivered, deployment scope priced.
Month 2 (if deploying): synthesizer wired in your tenant, posture set to ASSIST, drafts visible to your team.
Month 3: posture moves to AUTONOMOUS within agreed risk bands. Forward-deployed engineer reviewing weekly.

10 · Rollback & exit

You own your data. If you leave, your data leaves with you and your tenant is destroyed within 30 days. Every Murphy-applied change is snapshotted before it is made, so any individual decision can be reverted in one command. There is no model lock-in: your blueprint is a document, not a proprietary file format.

11 · Who you'll work with

Your engagement is led by a named human on our side — by default, the founder of Inoni LLC (Corey Post) — plus Murphy itself running synthesis underneath. A throat to choke and a system that doesn't sleep. This is the forward-deployed engineer pattern, applied to inbox operations.

12 · What you'll actually receive

From the audit: a written blueprint document (~30–60 pages), the instrumented inbox map, and a working pilot of one synthesis loop in your tenant. From deployment: the synthesizer running in your tenant, weekly review cadence with the forward-deployed lead, monthly substantive report, and the audit log every action is recorded in.

Request a white-glove audit Talk to a human first
Inoni LLC · Privacy · DPA · Sub-processors · Breach Notification