The catalogue

Every product, and where each one stands.

Each card states its availability. The products in production say so, and the ones not open yet say that instead.

The thread is the operating pattern, not the product boundary. Each Simple Intelligence product applies it to a different part of complex operations.

That covers time and billing, project delivery, revenue operations, marketing, service management, governance, integration, Microsoft 365 administration, and other complex operational systems the portfolio has products for.

These are software products you license and run, not consulting engagements or custom builds. One identity model, one security posture, one design language across all of them.

Every product stands alone. They are also the pieces SimpleOS is designed to compose into, which is the direction the portfolio is heading rather than something on offer today. SimpleOS is coming soon.

Selected products

Explore all products

12 products, in 4 groups. One Microsoft stack.

Each product stands alone and composes with the rest, though how far that composition is built differs from one pair to the next. They share one identity model, one security posture, and one design language. This is the portfolio as it stands today rather than the whole of what is being built, and each card says where that product stands.

Built to be adopted alongside Microsoft.

Sign-in runs through your Entra tenant, so access follows the directory and the conditional access policies you already enforce, and the products run on Azure. Storage is tenant-isolated, and the posture is set per product and stated on that product's page rather than promised across the portfolio.

What that means for a security review

Operational products

6 products The software a team runs its day in.

Platform and integration

4 products Microsoft-native platforms for governed AI and workflow automation.

Governance

1 product Evidence a reviewer can follow.

M&A execution

1 product Tenant-to-tenant IT integration.

From a campaign to revenue evidence

In sequence: SimpleOS Reach, then Marketing hands a qualified lead to Growth (Planned), reaching Simple Growth, then Growth hands a signed scope to Projects (Gated), reaching SimpleOS Delivery, then Projects hands delivery work to Time (Gated), reaching Simple Time, then Approved time becomes billable (Available), reaching Approved billing evidence.

  1. Planned
  2. Gated
  3. Gated
  4. Available

A person approves twice on this path, once in SimpleOS Delivery and again in Simple Time. What they review, what invalidates an approval, and how a failed handoff is detected and recovered are set out with the full diagram.

How each handoff works, and how far each one is built

Find the products built for your industry.

Thirteen industries. Every product is tagged to where it actually fits, so you only see what's relevant. Pick yours.

Financial Services
Microsoft Cloud for FSI, made shippable.
8 products →
Private Markets
Operating leverage for the GP and the LP, on Microsoft 365.
8 products
Real Estate
Brokerage, ownership, and asset management, agentic on M365.
8 products
Healthcare
Microsoft Cloud for Healthcare, with a decision trail your compliance officer can read.
8 products →
Manufacturing + Industrial
The OT-IT bridge for the modern plant, on Azure.
7 products →
Professional Services + IT
The operating system for services-led businesses on Microsoft 365.
10 products →
Public Sector + Defense
Evidence an assessor can read, not a binder you rebuild.
7 products
Media + Entertainment
Revenue and production velocity for modern media.
7 products
Energy + Utilities
Asset-heavy operations, agentic.
7 products
Education
Operations for institutions that run on Microsoft.
7 products
Architecture + Construction
From bid to closeout, orchestrated.
7 products →
Nonprofit organizations
Software for mission-driven operations.
7 products
Cross-Industry
The Microsoft 365 wedges every operation needs.
11 products

Governance your reviewers can examine.

Built to be adopted alongside Microsoft. Review the access model, approval controls and evidence for the product you plan to use. Check its current limits before connecting it to regulated work.

Microsoft identity, Azure runtime

Sign-in runs through your Entra tenant, so access follows the directory and the conditional access policies you already enforce. The products run on Azure. Storage is tenant-isolated, and the posture is set per product and stated on that product's page rather than promised across the portfolio.

Provenance designed into domain records

AI-generated domain records are designed to carry an AI-generated marker, confidence, and reasoning. Each product page states what that product implements today.

An evidence layer: Production, access arranged

Simple Council provides a policy engine and a hash-chained evidence ledger for actions routed through its own surfaces. Live Agent 365 interception and Microsoft Purview integration are not available. Customer-tenant validation is pending.

Live in controlled early access; applications reviewed one organisation at a time; customer-tenant validation pending.

Product-specific agents, with availability stated clearly.

Copilot and Teams are possible entry points, not proof that a product agent is available. Each product page identifies its current surfaces, access requirements and limits.

Governance plane

Simple Council

Review AI governance decisions with an evidence trail. Production, access arranged. What is built and what is pending.

Planned agent surfaces

Check each product's current surface

Product-specific Copilot agents are part of the portfolio direction. Each product identifies what is available, in development or planned. A web application or Teams tab does not establish that a Copilot agent is installable.

Opinionated where it matters.

AI-assisted development. Human-approved releases. We use AI in development and require tested changes and human release approval. That build process is separate from the human review controls inside each product.

01

Microsoft-native by default.

Microsoft identity and Azure hosting are our architectural defaults. Each product states where it runs, which data it retains and what connects to your tenant. Customer-hosted execution and SIG-hosted software are different deployment models.

02

Multi-tenant from day one.

Every product is built with tenant isolation as an architectural assumption, not a retrofit. One code path serving every customer tenant, zero single-tenant carve-outs.

03

Agents with audit, not autonomy.

Where a product writes a domain record with AI, that record is designed to carry an AI-generated marker, a confidence value, and the reasoning behind it. Multi-step workflows declare a human review point before anything reaches production.

How the audit behaviour is qualified

Where a product embeds an MCP server, its tool calls write to a per-tenant audit table, and that write is deliberately best-effort so a failed audit never breaks a customer's read. Those implementations vary by product. A customer-facing MCP capability is not treated as available here until tenant scoping, authorization, and durable audit behaviour have been verified for that product. There is no unrestricted portfolio-wide MCP server, and there is not going to be one: each product's tool server is scoped to one tenant and audited inside that product.

04

Foundry-routed, with BYOL planned where regulated.

Model access routes through Azure AI Foundry by default, which is a default and not an enforced invariant: a product may call a provider's own endpoint directly for a specific feature.

Which models, and where BYOL stands

The models behind Foundry are Azure OpenAI and other Azure AI Foundry models rather than a consumer chat service. Bring-your-own-model licensing as a regulated-workload commitment, where the routing is enforced rather than configured per tenant, is the design direction and belongs to SimpleForge, which is coming soon. Each product page says which of these apply to that product.