Platform · Coming Soon
Simple Ops

Simple Ops
The planned home for the operational products, not a product itself.

For Operations leaders evaluating more than one Simple Intelligence product who want to know whether they will eventually be one thing.

Six of the products in this portfolio cover work that most organizations run as one continuous operation: winning the work, planning it, doing it, billing it, marketing it, and administering the tenant underneath. Buying six things that behave like six things is a worse outcome than buying one. Simple Ops is the decision to organize those six under a single name and a single lifecycle. It is a decision, not a release. Nothing has been built under the name, nothing is for sale under it, and every one of the six is bought, signed into, and used on its own today.

Web Planned Copilot Planned
Get product updates How it works
Where this product is

Simple Ops on the same scale as everything else here

Every Simple Intelligence product is placed on one five-stage scale, so a stage means the same thing on this page as it does on any other. Nothing here is a schedule.

  1. Now

    Planned

    Scoped and specified. Not being built yet.

  2. Not started

    Building

    Under active development.

  3. Not started

    Validation

    Built, and being tested against real work before anyone outside is let in.

  4. Not started

    Early access

    Open to a reviewed group, with onboarding run by a person.

  5. Not started

    Available

    Open to anyone who qualifies, without waiting for a review.

Simple Ops is a decision about how these products fit together. It is not software you can buy, and there is no date.

This is where the product sits, not what you can do with it today. What you can do is the button at the top of this page, and it is worked out separately from evidence about the product rather than from this scale.

Why this exists

The problem this name is meant to solve.

A services organization does not experience time tracking, project delivery, pipeline, service desk, campaigns, and tenant administration as six separate concerns. It experiences them as one operation with six views into it. Sold as six products, the seams between them become the customer's problem to manage.

What was actually decided.

On 2026-07-17 the portfolio was reduced from roughly forty product ideas to roughly twelve, and six of the operational applications were grouped under the name Simple Ops. That grouping is the whole of the decision. It set a direction for how the products are organized. It did not start a build, set a date, or create anything a customer can acquire.

What that means if you are buying today.

Buy the product that solves the problem you have. Each of the six has its own page, its own way in, and its own stage of readiness, and none of them depends on Simple Ops existing. If the suite is built, the products you are already using are the ones it is built from.

What is inside

The six products Simple Ops is planned to bring together.

Each one is its own product with its own page, its own way in, and its own stage. Nothing here is a bundle you buy in one go.

Simple Time

The Microsoft 365 timesheet that closes the billable-hours leak.

Trial access

Simple Projects

Project delivery that starts at the signed scope of work.

Available on request

Simple Growth

The CRM that reads your Microsoft 365 calendar, not your data entry.

Available on request

Simple Service

ITSM on Microsoft 365, without the ConnectWise tax.

Available on request

Simple Marketing

Marketing automation built for the Microsoft 365 partner channel.

Available on request

Simple Admins

Tenant administration from a Teams chat, with a seam before every write.

Coming soon
Readiness

What exists under the name Simple Ops today.

Simple Ops is a decision recorded in the portfolio log. There is no Simple Ops repository, deployment, sign-in, or schema.

Working today

  • The grouping is decided and recorded, so the six products are being designed with the same conventions
  • All six products underneath it are independently reachable, each with its own page and its own access path

Not yet

  • There is no Simple Ops application, sign-in, tenant, or bill
  • There is no cross-product single tenant or single invoice, and no work has started on one
  • There is no announced date, and no date will appear here until one is approved
  • Simple Ops is not the same thing as SimpleOS, which is a separate planned shell with its own page

Verified against the product on 2026-08-24.

Two names, two things

Simple Ops and SimpleOS are not the same.

The names are close enough that treating them as interchangeable would be easy and wrong. They describe different things and neither is available.

Nothing on this list is available today. This is the product we intend to build, written down so you can tell us whether it is the right one, and it will change.

Simple Ops is the grouping

It names which products belong together and are designed to share conventions. It is an organizing decision about the portfolio.

SimpleOS is the shell

It is the planned composition experience: one place approved products can be used together. It has its own page and its own separate status.

Neither is purchasable

Both are planned. Nothing on either page can be bought, started, or signed into, and neither has an approved date.

The products are real

The six products underneath are the part that exists. What they can and cannot do today is stated on each of their own pages.

If a future version of this page describes Simple Ops as software you can run, it has drifted from what was decided.

Who stays accountable

A planned suite changes nothing about who approves what.

Every Simple Intelligence product stops at a human approval before it changes a customer system, and grouping products under one name does not create a shortcut between them.

Approvals stay per product

The approval seam in each product is the one that governs it. There is no suite-level authority that can act across products, because there is no suite.

Your data stays where it is

Each product holds its own records in its own tenant-scoped database under its own stated storage posture. No Simple Ops store exists, so nothing has been pooled.

Nothing is migrated without sign-off

If products are ever consolidated, the portfolio rules require data migration with matching row counts, verified checksums, a retained rollback database, and explicit sign-off before any cutover.

Failures escalate per product

Detection, recovery, and escalation are the responsibility of the product you are using, and are described on that product's page.

Evidence

What backs the claims on this page.

Nothing has been built under the name Simple Ops.
In the build There is no Simple Ops application, database, sign-in, tenant, or deployment. The name exists in the portfolio decision record and in no running system.
The six products it is planned to group are separately available today.
In the build Each is its own application with its own tenant, its own sign-in, and its own page on this site. How far along each one is, is stated on that page rather than here.
The grouping is a recorded decision, not a schedule.
In the build The portfolio decision of 2026-07-17 named which products belong together. It set no date, no scope, and no build order, and no date has been approved since.
No customer data has been pooled across the products.
In the build Each product holds its records in its own tenant-scoped database under its own storage posture. There is no shared store, so there is nothing for records to have been pooled into.
Storage posture
None of its own. Each product underneath keeps its own storage posture.
Certification target
None. Certification applies to shipping products, and this is a plan.
Distribution
Status
Coming Soon
Industries
Cross-Industry
FAQ

The questions this page exists to answer.

Can I buy Simple Ops?

No. Nothing has been built under the name and there is nothing to purchase, trial, or sign into. The products it is planned to group are each bought on their own.

When will Simple Ops be available?

There is no date. No schedule has been approved, and a date will not appear on this page until one is.

Is Simple Ops another name for SimpleOS?

No. Simple Ops is the grouping of operational products. SimpleOS is the planned shell they would be used through. Both are planned, and they are separate.

Will the products I use today be discontinued or renamed?

Each product keeps its own page, its own URL, and its own way in. Some module names were reserved for a future suite, for example Simple Revenue for Simple Growth and Simple Tenant for Simple Admins, but no product has been renamed and none of those names is in use.

What happens to my data if the products are consolidated?

Nothing moves without a verified migration. The portfolio rules require row counts to match per table, checksums to verify, compliance ledgers to be copied in full, the source database to be retained as a rollback, and explicit sign-off before any cutover.

Where this sits

The rest of the portfolio.

SimpleOS Coming Soon The planned shell where the products a customer already has are used together. Simple Atlas In Development The layer that holds the authority an agent is deliberately not given.

There is nothing to start here.

Simple Ops is a plan. If one of the six products underneath solves a problem you have today, start there. If you want to be told when the suite becomes real, ask for updates.

Get product updates See the portfolio