PacivaPacivaCONFIDENTIAL
The executive overview, 6 minutes

The agentic operating system for your professional and personal life.

Pax does the work, finds the work you can hand off, and gives you back the hours for the work only you can do. One assistant, one memory, every channel. Pax does the work. You approve.

PacivaJeremy Mays and Frederick TownesEight sectionsSeptember 2026
01 The thesis

An operating system can run the day itself.

The thesis below is the company's, as written. This overview walks it as an argument in three parts. The day can be run by a system that watches how your work actually moves. That system hands you only the moments that need your judgment; everything else it does, and you approve. And it gets measurably better every time you touch it, which is the personalization thesis the beta will test.

The thesis, as written

The next AI breakthrough is not another model. It is intelligence reliably accountable for getting work done. Paciva exists to manage the complexity between intent and outcome: what comes in, what matters, what is known or assumed, what may be done, and where intelligence should run. Work moves forward under your rules and returns only as a result, blocker, or decision, giving you time back without taking control away.

Paciva is the user-controlled execution layer between abundant intelligence and trusted outcomes. That is the destination. A new beta cohort is underway; the first saw limited usage of an earlier product variant. Product examples show the intended experience, not customer results.

How this overview walks it: three beats and a consequenceSection 01
01

It runs the day

An operating system that watches how your work actually moves and proposes the handoff from observed reality.

02

You keep the judgment

Pax does the work. You approve. Only the moments that need your call reach you, with the reason attached.

03

Every touch compounds

Every action is labeled behavior. The system gets measurably better each time you touch it, tuned to you alone.

Our bet is that connected context, screening and governed execution earn a place alongside the tools buyers already use.
02 The leak

Your day is spent coordinating work instead of doing it. Nobody is watching the leak.

Microsoft reports 275 daily pings for the top 20% of users by ping volume, with roughly two minutes between pings during work hours. That telemetry is distinct from its 31,000-person survey. Teams spend 50% more time in unnecessary meetings than on their highest priorities. Two leaks run at once: graymail has a modeled time value of $12,796 per employee per year, and the Collaboration Tax, the operational drag of meetings, tool switching and AI rework, has a separate modeled value of about $12,800. The leak persists for one reason: nothing in your stack watches how your work actually moves. That is the job an operating system exists to do.

The workday, splitMicrosoft WorkLab 2025, BLS
Coordinating: triage, meetings, app switching, interruptionsThe actual work
1.5 hrsa day on graymail triage
235working days
$36.30an hour, BLS
$12,796per employee per year, $3.2M a year at 250 people
Ticks illustrate incoming pings, not measured focus switches or a count to scale. The 275 figure covers the highest-volume 20%. ChatGPT and Claude offer memory; our differentiation thesis is screening and governed execution across connected work.
Two leaks, counted separatelyWe never add them
Graymail, the inbound slice
$12,796
per employee per year. $3.2M a year at 250 people.
Time assumption, BLS wage rate. 1.5 hours a day, 235 working days, $36.30 an hour.
The Collaboration Tax, the operational drag
$12,800
per employee per year. $3.2M a year at 250 people.
Modeled: $6,824 in wage-equivalent tool-switching time, plus $3,739 in unnecessary meetings and $2,232 untangling AI-generated work.
Why we do not add them. Both leaks draw on the same finite day, so summing them would double-count. For context, a separate survey reports about 60 percent of the workday goes to communicating about work, searching for information, and switching apps, not the job the person was hired to do.
60% work about workThe rest is the job
Work about work, Asana Anatomy of Work Index. These sources cover different samples and periods; this is context, not a validated ceiling. Categories may overlap within the collaboration scenario, and wage equivalents are not cash savings.
One number is what reaches the person. The other is what the organization pays to move work between people. Pax aims to address both, as an executive assistant for individuals and a chief of staff to organizations.
03 The product

One assistant across eight modes, entering another beta cohort.

The product direction spans eight modes, all the same Pax: the same memory, trust, and rules follow you from the front door to the calendar to multi step work running across your tools. Every mode obeys the same contract from the thesis: Pax does the work, and the moments that need your judgment come to you as one decision, not eleven threads.

Eight modes, one memoryBeta product direction
BetaGreetingThe front door. A conversation that screens, replacing the form.
BetaBriefingYour day composed across work and personal, read or spoken.
BetaScreeningA public Pax that handles strangers end-to-end.
BetaMessagingEvery channel handled in place, one unified surface.
BetaPlanningGoals become tracked plans with owners and dates.
BetaSchedulingOwns the calendar end-to-end, context aware.
BetaOperatingMulti-step work runs across your tools, following your rules.
BetaDreamingThe off hours pass. Pax works the backlog and has it waiting.
Same assistant, same memory, every time. A new mode inherits your context, trust, and rules on day one. The inbox is one of eight surfaces, never the product.
The Dashboard, the command centerIllustrative example
Swipe sideways to explore the screen.
The Paciva Dashboard: today's workload, projects, the check-in queue, and Pax working in the background
What Pax is working on, what it drafted, what needs you. Today's workload, the projects it is tracking, and the check-in queue, on one surface. Example data; not customer-outcome evidence.
04 The operating system

The assistant is the surface. The operating system underneath finds the work you can delegate before you ask.

This is the first beat of the thesis made mechanical: an operating system can run the day because it watches how the day actually runs. Its recall runs beyond any human on the team, one pane across every connected tool, and a memory that does not walk out the door when a teammate does.

The operating loopAlways on
Observehow work actually moves
→
Discoverthe work you can hand off
→
Execute or proposeby action class
→
Reportwith the receipt
→
Learnfrom every touch
Documented process rarely matches reality; an entire industry, process mining, exists because of that gap. Pax does not ask you to configure workflows. It watches how work moves and proposes handoffs based on observed reality, which is why the proposals feel true and why configuring your own automation products stalls where Pax does not.
On the other hand: the Defense CenterIllustrative example
Swipe sideways to explore the screen.
The Defense Center: focus time recovered, work delegated, Gatekeeper escalations, messages Pacified, and one decision escalated for review
29.4 hours shielded since the last check-in, itemized by lane, every block with its reason, and one gray-area escalation waiting for a human call. Transparency is the product surface, not a report. Example data; not customer-outcome evidence.

On the other hand: the Defense Center

The operating system finds work and hands it off. The Defense Center blocks what should never have reached you and shows its work: every action with its reason, reversible ones undone in one tap, irreversible ones always gated. That ledger is what earns Pax the right to act for you.

The dial: Pacivity

One dial sets how boldly Pax acts: Suggest, Act and you approve, Standing autonomy. The confirmation gate is architecture, not policy. No waiver can move an irreversible action past it.

05 The moat

Personalization is a technical thesis. Adoption is the next test.

Every action inside Paciva is labeled behavior: who matters to you, what gets approved, which threads are dead, how you decide. Two mechanisms carry the argument, and the third beat of the thesis is also the clock: a system that gets better with every touch makes early seats sticky before the category consolidates, and makes every month of delay a month of calibration a rival never gets back.

The personalization curveReported technical result; validation details pending
Day 0
Day 90
8.5% to 0.41%

The reported technical result is 8.5% false positives on day 0 and 0.41% by day 90. Cohort size, dates, evaluation set and reproducible methodology are needed to validate this comparison. It does not establish customer retention, willingness to pay or paid adoption.

The corpus tunes the systemAggregate feedback transfers to every user. A competitor can rebuild this at the cost of running a communication product for years.
Calibration tunes to you aloneYour senders, your judgment, your waivers transfer to no one. A copier starts at day zero with every customer, and stays there for months.
The next beta tests recurring usage and trust in delegated work. Technical evaluation and commercial adoption will be reported separately.
06 The field

A crowded field. Our bet is governed work across channels.

Email assistants, general-purpose AI and automation platforms already cover parts of this job. Our differentiation thesis combines cross-channel context, screening, and execution under explicit user control. The beta must show why early-adopter knowledge workers and developers choose that combination over their existing tools.

Slices of the work, against the jobPublished positioning; scope requires buyer-task validation
Superhuman
Email-focused experience; provider support varies.
Fyxer
Email and calendar assistance; LinkedIn and screening scope not verified.
Town
$55M pre-launch: no LinkedIn and no inbound screening in its published surface.
Viktor
$75M reported funding. Named agents inside Slack or Teams; individual assistance is explicitly not the focus.
Paciva
Gmail, LinkedIn, and Slack on one surface. Screening, briefing, scheduling, planning, operating, personal life.
Microsoft already supports Gmail connections in Copilot, and ChatGPT and Claude offer memory. Provider access alone is not a moat. We must earn preference through reliable completion, permissions and screening; LinkedIn access remains a platform-terms and integration risk.
The same screen, every channelIllustrative example
Swipe sideways to explore the screen.
The unified messaging surface: LinkedIn, Gmail and Slack in one place, each thread scored and either handled, held for review, or Pacified
LinkedIn sits beside Gmail and Slack on one surface. The same scoring, the same screening, the same ledger, whichever door the stranger knocks on. This illustrates the cross-channel experience. Example data; not customer-outcome evidence.
07 The model

Priced like software. Valued like labor. Expands with the work.

Our first buyers are early-adopter knowledge workers and developers. Pricing is proposed and untested: $300/month founding access, grandfathered, and $3,000/month list, plus metered usage. The next beta tests recurring value and conversion before we claim a repeatable acquisition model.

Priced like software, valued like laborProposed pricing and founder value assumptions
$2,500/month
Founder compute-capacity value estimateOne M5 MacBook Pro at full utilization for a month. Value depends on workload and utilization; this is not measured customer savings.
$300 / $3,000
Proposed founding / list monthly pricesCompute capacity plus incremental time saved supports the value hypothesis. Avoid counting the same work twice; validate willingness to pay and usage economics in beta.
01Recruit early-adopter knowledge workers and developers
02Run the next beta and measure activation and recurring usage
03Test paid conversion and measure onboarding and support effort
04Test personal expansion as a separate purchase hypothesis
05Evaluate implementer partners as a channel; validate incentives and acquisition cost
The initial acquisition plan targets early adopters directly and tests implementer partners. Market scenarios in the brief are assumptions, not customer forecasts; the immediate milestones are repeat usage and paid conversion.

We are raising $2M.

Use of funds: acquisition, compliance, compute, and hiring. The next system and beta-to-paid transition are the focus. Terms and planning detail are in the full brief, alongside the market model.

See the ask in the brief
08 Built by two people

Built by two people. A new beta is underway.

Our own engineering runs on autonomous agents with governed review, measured by accepted merges and review gate pass rate rather than raw PR count. The first external cohort saw limited usage of an earlier variant. The new cohort is the next test of engagement and paid demand; internal engineering usage is separate evidence.

Built by two people using the thing they are sellingThe meta story

Jeremy Mays

Product and marketing

Two decades across B2B and B2C growth on brands including American Express, Comcast, Four Seasons, Koch, Sotheby’s, Guaranteed Rate, Affectiva and the Los Angeles Police Department. $120M in new ARR driven in 2.5 years, scaling a team from 1 to 24.

Frederick Townes

Product and engineering

Created W3 Total Cache, running on tens of millions of sites. Founded W3 EDGE, serving Coca-Cola, Microsoft, Sony, and Staples. Led product at Remine across roughly 60 MLS markets and 1.2M professionals. COO through acquisition at Hyperlift.

implementreview gatemergeobserveapproveship
Our internal engineering workflow applies the thesis to our own work. Agents do the work, the review gate is our judgment moment, and the build compounds the same way a user’s calibration does.

The evidence is in the full brief.

Example product walkthroughs, reported technical results and their evidence gaps, market assumptions, the beta plan, and the ask. Pax reads along and answers what is still open. It takes a name and an email at the door.

Open the full brief

Rather see it than read about it?

Thirty minutes with the founders, Pax running live on real inbound. No slides.