Skip to main content
Skip to main content
Money · Planned EarnCommand OS architecture

Keep actual results separate from plans and projections

Money OS is designed to record revenue, expenses, goals, forecasts, scenarios and time ROI while keeping Actual, Forecast and Target visually distinct.

This capability is part of the planned EarnCommand OS architecture and is not available to use yet.

Designed to

  • Record revenue and expenses per income stream.
  • Track goals, forecasts and scenarios without blurring them into actuals.
  • Calculate Time ROI and portfolio-level comparisons.
  • Support AI CFO interpretation while preserving labels and caveats.
Problem

Money decisions are distorted when labels are mixed

A pipeline deal, forecast and target can be useful, but none of them is recorded revenue. Money OS is designed around that separation.

  • Costs and hours are not tied to the stream that caused them.
  • Targets are treated like results.
  • Forecasts become emotionally persuasive even when they are only assumptions.
Design intent

What Money OS is designed to do

Planned EarnCommand OS architecture

Revenue

Confirmed income events recorded as actual only when they happen.

Planned EarnCommand OS architecture

Expenses

Costs connected to streams, projects and campaigns.

Planned EarnCommand OS architecture

Income Streams

Each stream visible on its own and as part of a portfolio.

Planned EarnCommand OS architecture

Goals

Targets tracked separately from actual results.

Planned EarnCommand OS architecture

Forecasts

Forward-looking scenarios labelled as forecast.

Planned EarnCommand OS architecture

Scenarios

What-if models built from explicit assumptions.

Planned EarnCommand OS architecture

Time ROI

Returns compared with the hours required.

Planned EarnCommand OS architecture

Portfolio

Allocation choices across several streams.

Planned EarnCommand OS architecture

AI CFO

Future interpretation of financial patterns with inspectable reasoning.

Typical workflow

How the work flows

The sequence below describes planned workflow structure, not active product functionality.

  1. 01

    Record actuals

    Revenue, expense and time entries are captured.

  2. 02

    Assign streams

    Each entry is tied to the work that caused it.

  3. 03

    Set targets

    Goals are visible but separate from results.

  4. 04

    Model forecasts

    Scenarios use assumptions and are labelled.

  5. 05

    Review decisions

    Use the money picture to improve or reallocate effort.

Inputs and evidence

What information it uses and what records it creates

Information it uses

  • Revenue and expense entries recorded by the user.
  • Pipeline outcomes from Sales & CRM.
  • Time invested per stream or project.
  • Goals, forecasts and scenario assumptions.

Records and evidence created

  • Actual revenue and expense records.
  • Target and forecast records.
  • Scenario assumptions.
  • Margin and Time ROI calculations.
  • Portfolio review notes.
Financial labels

Actual, Forecast and Target stay distinct

The interface is designed so recorded results, planning projections and desired goals do not collapse into one number.

Actual: recorded revenue, expenses or hours

Forecast: projected future outcome

Target: goal the user is aiming for

Connected system

How Money OS connects to other modules

EarnCommand OS is designed as one operating system. Each capability passes context and evidence to another part of the loop.

Illustrative example

A labelled example scenario

Illustrative example

Illustrative example

  1. Actual
  2. Forecast
  3. Target
  4. Scenario
  5. Decision

Illustrative example: a business owner sees actual revenue from one service line, a forecast for a second line and a target for the quarter, with each label shown separately before choosing what to improve.

Trust and data philosophy

Evidence stays labelled

The system is designed to show where information came from before it informs a decision.

  • A forecast is not revenue. A pipeline deal is not revenue. EarnCommand OS is designed to keep planning assumptions separate from recorded results.
  • Actual values come from confirmed records.
  • Forecasts and scenarios remain estimates.
  • AI CFO output is interpretation, not financial advice.

Data labels

ActualUser ProvidedExternal EvidenceCalculatedAssumptionEstimateAI RecommendationUnknown

Relevant next step

Once money is visible, the next question is what constraint to improve.

FAQ

Questions about Money OS

More answersRead the full FAQ

Start with the full operating loop

The first step is understanding how each capability connects before any account or workflow is opened.

EarnCommand OS supports better-informed decisions and execution. It does not guarantee earnings.