Revenueos

RevenueOS

A revenue department for one business. It reads your website, ads, leads and mailbox, turns what it finds into a short list of actions, does the ones you approve, and measures what changed.

Connect once. Everything runs free. Pay when you agree with the result.

Free forever to run by hand, including the web panel. Running continuously on a schedule is $99/month , and only after it has measured a result you agreed with, plus 14 days.

Start Pro · Pricing · Talk to a human (or email hello@revenueos.com.au )

Runtime proof · Architecture · Security & approval · Integrations · Community vs Hosted · Capabilities

---

What it does

1. Connect once. Give it your website. It fills in the rest and labels every guess.
2. Discover. It reads the site, the ad exports or ad accounts, the lead lists and the mailbox, and writes what it finds as actions.
3. Approve. Nothing changes until you approve an action.
4. Execute. It deploys the site fix, pauses the wasting campaign, sends the email, books the call, raises the invoice, publishes the post.
5. Measure. It re-reads the live account and records before → after next to the action.
6. Pay. Nothing is charged until it has measured a result you agreed with.

Try it on your site in one command

uvx revenueos demo https://yoursite.com     # nothing to install; or: pip install revenueos && revenueos demo …

No account, and nothing is kept: the demo builds a workspace in a temporary directory and deletes it before it exits. It is not offline, though. The pages it reads go to whichever model you have configured, and only --no-llm keeps the run entirely local. Here is the whole output on a neutral domain, verbatim:

RevenueOS demo — Example Domain (https://example.com)

1 pages crawled · ad/analytics tags: none · booking link: no · phones: none seen

1. MISSING DESCRIPTION — https://example.com Page has no meta description. → RevenueOS writes the fix as a deliverable you approve, then re-checks the page.
2. THIN PAGE — https://example.com Only ~127 characters of body text were extracted. → RevenueOS writes the fix as a deliverable you approve, then re-checks the page.
3. NO SITEMAP — https://example.com No sitemap.xml was discovered at the host root or under the site path. → RevenueOS writes the fix as a deliverable you approve, then re-checks the page.
4. NO CANONICAL — https://example.com The homepage declares no canonical URL. → RevenueOS deploys this fix itself once the site is connected (git or WordPress), then re-checks it.

4 finding(s). Everything above runs free, every day, once connected: pip install revenueos && revenueos init --from https://example.com && revenueos serve You pay only when you agree with a measured result.

On a real business the same command also reads the homepage for tappable phone numbers, LocalBusiness schema, booking links and ad tags (Meta Pixel, Google Ads, GA4).

To run it from CI instead, add one step and read the job summary:

- uses: unempyd/revenueos@main

with: url: https://yoursite.com

Connect once

revenueos init --from https://yoursite.com   # the site fills the questionnaire; every inference is labelled

revenueos serve # TODAY / RESULTS / Connections / Spend on http://127.0.0.1:8791

A connection is an account you authorise once: Stripe, Google (Search Console, GA4, Calendar, Ads), Meta Ads, a git-hosted site, WordPress. Every connection is read-only until you turn on allow changes for it, and every change still waits for your approval on TODAY. See docs/integrations.md.

How it works

Four rules hold that picture together, each enforced in code and covered by tests:

• Workers never send, publish or spend. They only write actions.
• Only an approved action reaches an executor, and an executor that changes a connected account also needs that connection's allow changes switch. It refuses in a plain sentence otherwise.
• An outcome is pending until there is evidence, measured or no_effect from evidence, and unmeasurable with a note saying what would measure it. No metric is ever synthesised.
• A deliverable that was produced but not published is reported as produced, never as a win.

The longer version is in docs/architecture.md.

What the customer sees

The run above and the brief below are from a live run against a real company's public web presence, read-only, with no email sent to anyone. Nothing in them is mocked.

Workers

revenueos orchestrator runs the workers on a schedule (data/automations.json). revenueos serve is the same surface as a web panel, with password sessions, onboarding, the brief and the results ledger.

What is proven, and what is not

That table says what the code does, which is not the same as what has been watched doing it. The evidence is uneven, and it is worth knowing which row you are relying on. Dates and transcripts: docs/proof.md and docs/integrations.md.

| GA4 | not read | no GA4 property is confi