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.
Start with the question you came with.
Not sure which? Get your two-minute readiness brief Browse all 12 products in 4 groups
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
- Simple Time The Microsoft 365 timesheet that closes the billable-hours leak. Available on request
- SimpleOS Delivery 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
- SimpleOS Desk ITSM on Microsoft 365, without paying for modules nobody opens. Available on request
- SimpleFlow The checker and approval layer over the agents and workflows your team builds in Copilot Studio. Coming soon
- SimpleOS Reach Marketing automation built for the Microsoft 365 partner channel. Available on request
- SimpleForge Zero-retention AI infrastructure for firms whose client data is not allowed to rest anywhere. Coming soon
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.
Operational products
6 products
The software a team runs its day in.
Marketing, pipeline, delivery, time, service, and the Microsoft 365 admin copilot beside them. Each one is a product on its own terms with its own page, its own status, and its own way in.
SimpleOS Reach
Marketing automation built for the Microsoft 365 partner channel.
Simple Growth
The CRM that reads your Microsoft 365 calendar, not your data entry.
SimpleOS Delivery
Project delivery that starts at the signed scope of work.
Simple Time
The Microsoft 365 timesheet that closes the billable-hours leak.
SimpleOS Desk
ITSM on Microsoft 365, without paying for modules nobody opens.
Simple Admins
Tenant administration from a Teams chat, with a seam before every write.
Microsoft 365 Copilot declarative agent, not yet installable.
Platform and integration
4 products
Microsoft-native platforms for governed AI and workflow automation.
Simple Ops is the planned operational suite. SimpleOS is the planned shell and composition experience. They are two different things rather than two names for one. Alongside them sit the governed platform tier, the integration runtime, and the regulated inference surface. Grouping these on one heading is not a claim that the products share a database, share entitlements, run under one orchestrator today, or are being merged into a single product.
Simple Ops
The planned home for the operational products, not a product itself.
SimpleOS
The SimpleOS family has working products. Its shared shell is still planned for customers.
SimpleFlow
The checker and approval layer over the agents and workflows your team builds in Copilot Studio.
SimpleForge
Zero-retention AI infrastructure for firms whose client data is not allowed to rest anywhere.
Governance
1 product
Evidence a reviewer can follow.
Policy, approval, and the evidence trail for AI agents and the systems they are allowed to touch.
M&A execution
1 product
Tenant-to-tenant IT integration.
Governed planning for Microsoft and VMware estate integration through a merger, acquisition, or divestiture.
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.
- Marketing hands a qualified lead to Growth Planned
- Growth hands a signed scope to Projects Gated
- Projects hands delivery work to Time Gated
- Approved time becomes billable 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.
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.
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.
Simple Council
Review AI governance decisions with an evidence trail. Production, access arranged. What is built and what is pending.
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.
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.
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.
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.
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.