Show clients what your outbound tests found.
Keep your sending tool. Bring your leads into RevenueOS, write or edit each message, approve or reject it, and keep a record of your decisions.
Built for outbound agencies and GTM teams.
Free to watch: connect, import, and read the register before anything sends. $499/mo when you activate a program: founding customer pricing, open to accounts activated before 2026-12-31 and locked for 12 months.
- Soft-cadence follow-up vs standard 3-stepEVIDENCE · FAVORABLE EFFECT ESTABLISHEDDECISION · PROMOTE
- Price-incentive opener vs plain askEVIDENCE · NOT YET DECIDABLEDECISION · RETIRE
- Social-proof opener vs capability openerEVIDENCE · NOT YET DECIDABLEDECISION · CONTINUE COLLECTING
In this example, each decision follows a preselected 1.15× threshold. Evidence and decision can disagree.
Illustrative example; these are seeded data, not customer results. The design-partner pilot includes a client readout.
TWO WAYS TO START
- Software · run it yourself
- Start on the Free Preview and pay only when you activate a program. The pilot’s volume threshold does not apply. Compare plans
- Design-partner pilot · optional, run with us
- For two or more client programs, each with 5,000+ monthly sends: a 90-day engagement with a client readout first delivered in week 6.
- Before any invoice, we run the sizing math to check whether your volume can prove a result. The design-partner pilot is scoped on a call, not in a checkout.
IN SHORT · RevenueOS is a proof layer for cold outbound, helping agencies and GTM teams review outbound messages and keep a record of human decisions. The design-partner pilot includes a client readout of outbound test evidence, including results that remain unresolved.
Opened two ops roles in three days. This program is testing the operations-scaling angle. Ranked above 41 other sends competing for today’s capacity.
Maya, I saw Halden opened two ops roles this week. Most teams hit that hire because routing is manual, not because headcount is short. Worth fifteen minutes on how the other three we work with sequenced it?
Seeded demo. Your own rows arrive without a draft: you write each message. No model scores live rows today.
The page you would show the client.
Each row is one message angle, tested against another angle in the same client program. Every row answers two separate questions, and the answers are allowed to disagree.
- EVIDENCE
- What the data supports so far: an established result, or not yet decidable.
- DECISION
- What to do with the angle: promote, retire, continue collecting or hold. Each decision is judged against a pass/fail bar written down before any data.
How to read the numbers
Each row is one angle under test. The band is the range of lifts compatible with the data so far. A band entirely above 1.0× rules out no effect at the stated 90% level, and a band that straddles 1.0× is unresolved. The gate is the pass/fail bar we wrote down before seeing any data. The two columns can disagree: an angle can be retired because it cannot clear the gate while the evidence about it stays undecided. The bands stay valid even when you check them weekly.
Measured here · angle lift: does one angle beat another?
SPECIMEN · SEEDED DEMO TENANT
SPECIMEN · SEEDED DEMO TENANT
SPECIMEN · SEEDED DEMO TENANT
reading a row · band: the lifts compatible with the data so far · gate: the bar fixed before any data · rows: collected of required, from the published table, or sized per tenant where the table publishes no cell. Where a row has a published cell, its target lift sets how many rows it needs. That is sizing only: the decision is judged against the gate alone, and the gate never moves.
Three jobs, one readout for your client.
Work through the queue, approve or reject each send, and keep a record of your decisions. The example ledger shows what the test evidence supports, including results that remain unresolved.
The most urgent row, first.
When you add or import leads, each one with a company or a title opens a row in the queue, up to a capped number in each batch, and the rest stay in your pipeline. The queue sorts by priority, then by the soonest to expire. You see who to reach and why the row is there, then write or edit the message before you approve it. No model scores live rows today.
a approve · r reject · e edit · u undo
Specimen · seeded demo tenant
Today · Tue 07 Jul12 pending
Dana Whitfield · Northwind Analytics
soft-cadence follow-up
0.91action confidence
Maya Okonjo · Halden Logistics
operations-scaling angle
0.67action confidence
Priya Raghavan · Coastline Freight
social-proof opener
0.58action confidence
the sort: all three share a priority and none is close to expiring. Confidence plays no part in where they sit.
seeded example. Action confidence is how strongly the model behind a suggestion backs its own proposed action. Treat it as a reading to weigh, never as a measured outcome probability. No model scores live rows today. Live rows show no number and ask for your judgment. The register never invents a number.
Every send carries a name.
Write or edit the message, then approve or reject it. The record shows who made the decision and when.
wine red marks a human decision; machine output never uses it
09:14 · one decision
Dana Whitfield · soft-cadence follow-up
→ email · draft reviewed
→ cleared to send · the decision is recorded with who made it and when
the same row after approval, now with a name on it
An example of the client ledger.
The example ledger shows each angle’s evidence state separately from its decision. Evidence may remain unresolved; continuing to collect is a valid outcome.
rungs: reply → positive reply → meeting
Dana’s angle, graded by the math
soft-cadence follow-up
EVIDENCE · FAVORABLE EFFECT ESTABLISHEDDECISION · PROMOTE
positive-reply · target 2× · cell B3 · rows 12,944 of 12,944 required · band [1.21×, 1.58×]
gate 1.15×
0.8×
1.0×
1.8×
In this seeded example, the lower bound clears the preselected gate, so the decision is to promote the angle.
The client readout
It shows what was tested, what the evidence supports so far (settled or not), what was decided, and what changes next. The design-partner pilot includes a client readout, first delivered in week 6. It is ready to forward to your client, and every number in it can be recomputed. Experiment enrollment and the proof engine are built but switched off in production today, so no customer program is being graded yet.
See a specimen readout · a seeded example of three programs, each read against its own holdout
We qualify you before we invoice you.
Design-partner pilot
design-partner pilot · san diego, ca · dated 07 jul 2026
$7,500 / 90-day pilot
flat · 90 days · credited toward year one
one fee for the whole book, up to fifteen programs
The pilot is $7,500 flat for 90 days. One fee covers a book of up to fifteen programs, and it is credited in full against year one if you continue. Larger portfolios are scoped on the call.
The engineer who built it joins every call.
We author your first angle book with you.
Your own claim ledger, from your own sends, in weeks.→ schedule a
A weekly readout where we tally objections and adjust the roadmap.
We preview the published anytime-valid floor on your numbers here, then confirm it in writing before the invoice. Anytime-valid means the band stays valid however often you check it.
The pilot operating threshold · checked here, before we ask who you are
Meets the pilot operating threshold.
On the call, we run the sizing math on your real volumes to see whether they can prove anything, before any invoice.
per program 6,000 against 5,000 (meets) · programs 2 against 2 (meets) · assumes your 2 programs share the monthly volume equally
Illustrative published sample requirement · cell A1, conservative 0.64% reply
21,928 rows needed
0.1% → 0.64% (holdout → proof reply rate)
rows count leads randomized into the proof and holdout cells, not emails sent, so the count does not change with volume
This is the conservative cell. A healthier reply rate needs fewer rows. The timeline at your volume goes in writing on the sizing call. published anytime-valid table · generated 2026-07-03 · cell A1 · the full table
There are two timelines. First learnings arrive in weeks. A statistically decisive verdict under the registered design needs the sample the table states, and how long that takes at your volume goes in writing on the sizing call. If it would run longer than a pilot, we say so before any invoice.
The pilot operating threshold is public: 5,000+ monthly sends per program, across 2+ programs. Checking it stores nothing and does not ask who you are. the pilot, on one page
G. MAHN · dated 07 jul 2026
Grant Mahn, Co-founder & CTO · the engineer on every pilot call
Max Gale, Co-founder & CEO
your countersign
no mail app? write directly: info@revenueos.app
Schedule A
The first six weeks of the 90 days
activities, not verdicts. Results take as long as they take.
Experiment enrollment and the proof engine are built but switched off in production today, so no customer program is being graded yet.
Connect Smartlead / Instantly / SendGrid + your CRM (HubSpot, Salesforce, or Copper). Every parser must prove itself on captured live events before anything sends.
We write angle book v1 together.
First sends approved from the queue (a approve · r reject · e edit · u undo).
Outcomes come in as typed rungs.
Claims are logged, each with its evidence state and its decision, settled or not.
First weekly readout delivered: ready for the client, recomputable, and yours to forward.
From Grant Mahn, Co-founder & CTO and the engineer on every pilot call, and Max Gale, Co-founder & CEO.info@revenueos.app
Straight answers.
Do we have enough volume for this to work?
The pilot operating threshold is 5,000 sends a month per program, across two or more programs. That is a commercial bar, separate from the published sample requirement below. Before any invoice, we run your real volumes through the minimum-n table, which gives the rows needed to detect 1.25×, 1.5×, or 2× lifts on a 2% positive-reply base, and we put the timeline in writing on the sizing call. If honest detection would take longer than a pilot, we say so, and the Proof Readiness Audit included in every paid plan re-runs the sizing each quarter, with a written memo.
(Exhibit A below is the minimum-n table. Try it with your numbers.)
Exhibit A · the published anytime-valid table, on your numbers
The numbers below come from the published table, generated by a script that simulates the product’s own proof engine, not from a textbook formula. This exhibit only selects a cell. It never invents a number.
① First, prove the outreach works · program incrementality: does outreach beat no outreach?
21,928 rows needed
0.1% → 0.64% (holdout → proof reply rate)
conservatively snapped to the published grid: your 1% reply rate → the published 0.64% reply rate.
rows count leads randomized into the proof and holdout cells, not emails sent, so the count does not change with volume
your volume: 4,000 sends a month per program against the 5,000 pilot threshold (short)
The timeline at your volume goes in writing on the sizing call.
② Then, prove one angle beats another · angle lift, at a 2% reply base
There are two timelines. First learnings arrive in weeks. A statistically decisive verdict under the registered design needs the sample the table states, and how long that takes at your volume goes in writing on the sizing call. If it would run longer than a pilot, we say so before any invoice.
These are the anytime-valid floors, conservatively snapped to the published grid, dated, and recomputable (α .1, a 90% band, safe to peek weekly). published anytime-valid table · generated 2026-07-03 · cell A1. the full table · your exact per-tenant table ships with the pilot (the pilot, the floor clause).
Why isn’t pricing tied to the lift you find?
If we took a percentage of the lift we report, we would earn more by reporting more lift, and you would have no reason to trust the number. The design-partner pilot is $7,500 flat for 90 days. One fee covers a book of up to fifteen programs, and it is credited in full against year one if you continue. Larger portfolios are scoped on the call. Every self-serve price is flat too, and none of them moves with the result. We charge for the audit, never for its outcome.
What if an angle does not clear the example’s gate?
The seeded example shows every row whether or not it clears its preselected gate. The ledger keeps evidence separate from the decision: what the data has established, and what the example’s preselected rule decided. At n=1,102, an angle can be retired because its band rules out the gate while the evidence remains undecided. That decision is not proof of no effect.
Why does a human approve every send?
Two reasons. Deliverability: 2026 complaint limits leave no room for unattended sending. Accountability: when a prospect gets an email, someone’s name is on that decision. The queue makes each approval take seconds (a approve, r reject), so review takes minutes a day, not meetings.
Where does our data go?
Into your tenant, and nowhere you haven’t signed for. The application keeps each tenant’s data separate, and database row-level security adds a second check on the tables that carry an isolation policy. A decision cannot be saved without its record of who made it and when, and both are written in the same tenant-scoped write. Processing runs on the subprocessors named in the DPA. Cross-client benchmarks are opt-in, aggregate-only, and never reported below a five-tenant floor. The consent clause is in the DPA from day one, not added after a book is signed.
(Exhibit B is the subprocessor list, as printed in the colophon, all under DPA: Clerk · Supabase · Stripe · SendGrid · Fly.io · Vercel · Anthropic · OpenAI · Upstash · Sentry · Grafana.)
Are you SOC 2?
SOC 2 is planned ahead of mid-market procurement. Pilots today receive the security-posture one-pager. It covers architecture, per-tenant isolation, and encryption. Pilots also receive the DPA, with the full subprocessor list and the pooling-consent clause included from day one.
current as of sep 2026; this answer will be revised on the record when soc 2 lands.
Where do replies live? Do you have an inbox?
In your sending tool, where they already are. Smartlead’s Master Inbox, Instantly’s Unibox, and the equivalent in whichever platform you run already centralize every reply, and that is where your team keeps reading and answering it. RevenueOS is send-side: it routes each send to a person to approve and keeps the record of that decision. Where your sending tool reports a reply, RevenueOS records it as a typed outcome (reply, positive reply, or meeting). We read the outcome, not the inbox, and we never ask you to move a conversation to us.
or send us your own question
Further questions
Contact us if you need more detail about any of these answers.
Grant Mahn, Co-founder & CTO, the engineer answering · san diego, ca · jul 2026
Max Gale, Co-founder & CEO
Check whether the design-partner pilot fits your book.
Enter your monthly sends and how many client programs you run. The sheet checks them against the pilot threshold here, before we ask who you are.