Simple Growth
The CRM that reads your Microsoft 365 calendar, not your data entry.
For VPs of Sales and RevOps at Microsoft Solutions Partners and B2B services firms that want a CRM native to Microsoft 365 from day one. Complements Dynamics 365 Sales for organizations that have it.
HubSpot bolts onto Outlook with a plugin. Salesforce is its own world that your Microsoft estate has to be taught about. Simple Growth is Microsoft-native from the first sign-in: calendar events with an external attendee become activities against the right company and deal, Teams Phone call records are ingested and analysed, and meeting briefings arrive before the meeting rather than after it. Drafted quote lines and proposals carry the confidence and reasoning behind them, and a person sends them.
How to get Simple Growth
Available on requestRunning in production and taking new customers. There is no self-serve trial or purchase on this one yet, so access is set up with us directly.
Where this stands
- Availability
- Available on request
What it costs
$89 per seat per month
Growth plan
Annual billing shown, monthly available, minimum five seats.
Published pricing. There is no self-serve checkout for this product yet.
Routes that are not open
- Direct trial with Simple Intelligence Not open yet
- Direct subscription from Simple Intelligence Not open yet
- Microsoft Marketplace Not published yet
- Sponsored subscription for member companies Not open yet
The CRM is only as good as the data entry nobody does.
A rep takes four external meetings a week and logs one of them. The call that changed the deal happened in Teams and left no trace. By the time a forecast is assembled, the pipeline reflects what people remembered to type on a Friday afternoon, and the manager reviewing it knows that, which is why the review takes two hours and produces a different number than the system holds.
Read the calendar instead of asking for the update.
Simple Growth reads the Microsoft 365 calendar the team already lives in. A meeting with at least one attendee outside your domain is treated as a sales meeting, its attendees are matched to contacts, and the activity is written against the company and the open deal. Teams Phone call records come in the same way. The record fills itself from work that already happened rather than from a form somebody has to remember.
The agent drafts. A person sends.
The outbound agent cannot dispatch a message until it has passed five simulated conversations, and it refuses to run at all if its adapter is not configured for that workspace. Quote lines and proposals arrive drafted, with a confidence value and the reasoning behind them, and somebody accepts them. Nothing here sends on your behalf because a scheduler fired.
What works today, and what does not.
Simple Growth is live on Azure with its own pricing and legal pages. Access is arranged with us rather than started from this site, because the product has no mechanism that ends an evaluation. What is otherwise unfinished is on the outbound edges: CRM connectors that verify a connection but do not yet sync, and a Marketplace listing that is built but not published.
Working today
- Companies, contacts, deals, activities, notes, and a pipeline you configure. A new workspace starts on a six-stage pipeline named "B2B SaaS" that you can rename, reorder, or replace.
- Microsoft 365 calendar capture: an event with at least one attendee outside your domain is classified as a sales meeting, attendees are matched to contacts, and the activity is rolled up to the company and the open deal without creating duplicates on a re-run
- Teams Phone call record ingest against the customer tenant, matching numbers in E.164 form to contact records, with call analytics on top
- Meeting transcripts and a briefing prepared before the meeting rather than a summary after it
- Quotes and proposals with the AI provenance columns available on drafted lines, proposal rendering, and a share link for the buyer
- A statement of work that renders, shares, accepts by click under a configurable threshold and by typed or drawn signature above it, and takes a deposit through a secure checkout on acceptance
- An outbound sales agent with a five-simulation gate, drafted email and in-product chat steps, inbound reply capture, and intent classification
- Microsoft-funded engagement matching against a fifteen-engagement FY27 catalog across six solution clusters, with an eligibility panel on the company record
- Entra ID sign-in, per-tenant isolation, assigned-only visibility per the portfolio rule, and an MCP server exposing twenty tools that writes an audit row per call
Not yet
- The CRM connectors are not yet a two-way sync. Salesforce, HubSpot, and Dynamics 365 connect and verify the connection read-only. The sync framework behind them is built and tested in the repository, including field ownership, a conflict queue, and a cross-system write log, but it is not switched on for customers, and the Dynamics connector defaults to off so that no unattended job writes into a production CRM by accident.
- Simple Council receives token usage from this product for cost governance. It is best effort and it is switched off when its endpoint is unset. It does not sit in front of customer-record writes, and nothing on this page should be read as saying it does.
- The in-product agent can pause for write approval, but that pending approval is held in process memory for five minutes and belongs to the session that started it. It is a confirmation prompt, not a durable approval queue that survives a restart.
- The Azure Marketplace fulfilment path is implemented and the pricing page shows a Marketplace column, but the offer is not published. This cannot yet be bought through a Microsoft agreement or drawn against a Microsoft consumption commitment.
- The AI provenance columns exist on drafted records but nothing forces them to be populated, so a blank means unknown rather than human-authored. Treat it as a record of what the model claimed, not as a guarantee of coverage.
- There is no self-service evaluation with an end date. The product has no trial column, opens no checkout at registration, and does not gate sign-in on workspace status, so an evaluation started here would have nothing to close it. Access is set up with us and the term is agreed in that conversation. Audited 2026-08-22 against the repository.
- Copilot and desktop surfaces are planned. Today this is a web application you sign into.
- Enrichment and dialer connectors each need their own vendor registration and customer consent before they do anything, and an unconfigured one stays visible as unconfigured rather than pretending to work.
Verified against the product on 2026-08-20.
The teams this was built for.
Getting the pipeline to match what the team actually did
External meetings and Teams Phone calls land as activities against the right company and deal without anyone logging them. The forecast conversation starts from what happened rather than from what got typed, and the gap between the two stops being the meeting.
Walking into the call already briefed
A briefing is prepared before the meeting from the history on the record and the transcript of the last one, so the first five minutes are not spent reconstructing where things stood.
Getting from a verbal yes to a signed, deposited SOW
A quote becomes a proposal, a proposal becomes a statement of work, the buyer opens a share link, signs above the threshold you set, and the deposit is taken at acceptance. The signed scope then imports into Simple Projects as the plan rather than being retyped.
Finding which accounts qualify for Microsoft funding
Companies are matched against the FY27 Microsoft-funded engagement catalog on segment and workload signals, and the eligibility panel sits on the company record where the person working the account will see it.
From the first sign-in to a deal that updates itself.
Sign in with the Microsoft work account
Simple Growth is a multi-tenant Entra ID application. The tenant on the token scopes every later query, so there is no separate user directory to keep in step with the one you already run.
Connect the calendar and the phone
Microsoft Graph consent lets the product read calendar events and, where Teams Phone is in use, call records. Classification of what counts as a sales meeting is a rule you can read rather than a black box: at least one attendee outside your own domain.
Let the records fill themselves
Attendees are matched to contacts, contacts roll up to companies, and companies roll up to the open deal. Re-running the sync updates the same activity rows instead of stacking duplicates, which is the difference between a capture job you trust and one you turn off after a fortnight.
Work the deal, with drafts to accept or reject
Quote lines, proposals, follow-up drafts, and next-action suggestions arrive with the confidence and reasoning attached. The outbound agent stays in observe-only until it has passed its simulation gate and its channel is configured.
Close it and hand it to delivery
The statement of work is signed and the deposit taken in the same flow, and the signed scope imports into Simple Projects as a drafted plan. The contract does not get retyped by whoever is free on Monday.
What it does between the first meeting and the signature.
Activity capture that survives a re-run
Calendar events are fetched from the Graph calendar view, classified, and written as activities keyed so that a repeat sync updates rather than duplicates. Meetings with no external attendee are left alone, because an internal stand-up is not a sales touch and a CRM that thinks it is stops being readable within a month.
Calls as first-class history
Teams Phone call records are read under an application permission against the customer tenant and matched to contacts by number in E.164 form. Transcripts and call analytics sit on the same timeline as the meetings and the emails, so the deal history is one list rather than four systems.
An outbound agent with a gate in front of it
The engagement loop refuses to dispatch unless the agent is active, its channel adapter is configured for that workspace, and it has passed five simulated conversations. Inbound replies flip the conversation out of the sequence and get classified rather than continuing to send at somebody who already answered.
Quote to signature to deposit
Quote totals, proposal rendering, and SOW margin are computed server side. Acceptance is a click below a configurable contract value and a typed or drawn signature above it, defaulting at ten thousand, and the deposit percentage is a deployment setting rather than a hardcoded number. The buyer never needs an account to sign.
An agent surface that is scoped and recorded
The MCP server exposes twenty tools across companies, contacts, deals, activities, notes, and pipeline reporting. Tenant scope and capability checks are enforced inside the server rather than trusted from the caller, and each call writes an audit row carrying the token cost of the ones that use a model.
Where the records live, and who can see them.
Postgres, tenant scoped in the query layer
Every domain table carries a tenant id and the filter is composed into queries rather than left to each route to remember. Customer, contact, deal, and quote history are durable business records, so this is a persistent store with vector search alongside it, not an ephemeral one.
Assigned-only visibility by default
A non-admin member sees the records they own or are assigned to. Administrators see the workspace. The rule is a shared server-side fragment composed inside an already tenant-scoped query, so it is not something a new screen can forget to apply.
Microsoft permissions you can read off the page
Calendar capture reads the signed-in user calendar view. Call record ingest uses an application permission scoped to call records against the customer tenant. Both are consented by an administrator in your own directory and both can be declined without breaking the rest of the product.
Runs on Azure, in the SIG subscription
Azure Container Apps behind Front Door, secrets in Key Vault reached through a managed identity, and session cookies scoped and marked secure per host. No AWS, no Google Cloud, no third-party platform-as-a-service in the path.
What it connects to, and what is still a connection test.
A name here is a system this product is built to work with, not a promise that the connection is live in your tenant. Where a connector carries a status label, that label is the current state. Anything that needs its own vendor registration, its own consent, or its own approval says so, and nothing on this page can be taken as available until it is confirmed for your tenant.
Microsoft
CRM (connection verification today, sync in development)
Finance and data (each needs its own vendor registration and your consent)
Across the portfolio
For your own systems
Reading data from an external system is not a way to sign in. Customer identity stays with Microsoft Entra ID, and no data source on this list authenticates a person.
Where each of these claims comes from.
What it costs.
- Up to five seats included
- The outbound agent with drafted artifacts
- Proposals, signing, and SOW
- Connection verification for one CRM
- Everything in Starter Pack
- AI-drafted statements of work
- Goals and OKRs, read and write
- Deeper Microsoft Graph surface including Teams cards and send-on-behalf
- Everything in Growth
- Single sign-on through Entra ID
- A custom domain through Azure Front Door
- A portability clause with no exit fees
- A named contact and an agreed response time
How access works.
- How access starts
- A conversation first. We scope the evaluation with you and provision the tenant ourselves.
- Evaluation length
- Agreed when the evaluation is scoped, up to 45 days for a standard evaluation. A longer guided pilot is approved case by case.
- Payment details
- None collected to begin an evaluation.
How ICM informs Simple Growth
Simple Growth runs sales development conversations. The design point is that the agent stops at the moment a real person replies, and that nobody can start it running without deciding to.
Built, and verified against the product code
-
Context in
One prospect, one channel
A conversation pins to exactly one channel: email, in-product chat, Teams, LinkedIn or SMS. The external thread identifier is carried as an opaque value the engine does not interpret.
Gated
-
Retained or discarded
The thread and its delivery state
Messages keep direction, position in the sequence, and what the mail system said back: delivered, bounced, and the bounce reason. That is the working set. The rest of the customer record is not pulled into the loop to send a follow-up.
Gated
-
What the agent proposes
A sequenced message and a read of the reply
Outbound steps follow the sequence. Inbound messages get classified as positive, neutral, negative, out of office, or an unsubscribe, and that classification decides whether the loop answers, escalates, or closes.
Gated
-
Human review a person decides
An operator switches it on, and takes the reply
An agent reaches ready only after five simulated conversations pass at high confidence, and it still sits there until an operator activates it by hand. When a prospect replies the conversation flips to a state that needs a human, and the record names who took it.
Gated
-
Permitted effect
Only an active agent sends anything
The scheduler runs the engagement loop for active agents and ignores every other state. Draft, simulating, ready and paused all send nothing.
Gated
-
Evidence recorded
Activation is audited, drafts are marked
Turning an agent on writes an audit row. Conversations and messages the agent produced are flagged as generated, so a person reading the thread later can tell which side of it was drafted.
Gated
-
Failure and refusal
Bounce and unsubscribe are terminal
A permanent delivery failure and an opt-out both end the conversation rather than feeding a retry. Disqualified is a state an operator sets, not one the agent awards itself.
Gated
These labels describe each step of this workflow on its own. They are not the availability of the product, which is the status shown at the top of this page.
This describes how the workflow is built. It is not a statement about availability, which is the status shown at the top of this page. ICM informs how context, review and evidence are designed here. It does not replace this product's database, its tenant isolation, its Entra identity, its audit tables, or its authorisation checks.
Methodology note
ICM was developed by Jake Van Clief and David McDermott. Simple Intelligence Group did not originate the methodology.
Simple Intelligence Group applies relevant ICM principles to context, provenance, traceability, human review, and workflow design.
Participation does not imply certification, endorsement, partnership, or an official ICM Architect designation.
What sales leaders ask first.
Does it sync with Salesforce or Dynamics 365 today?
It connects and verifies the connection read-only. It does not yet run a production two-way sync, and the Dynamics connector ships switched off so that nothing writes into your CRM without a deliberate decision. The sync framework behind it is built, with field ownership, a conflict queue, and a cross-system write log, but built is not the same as switched on and this page will not pretend otherwise. If two-way sync is a condition of buying rather than a preference, raise it in the first conversation.
What exactly does it read from Microsoft 365?
The calendar view for the signed-in user, and where Teams Phone is in use, call records under an application permission scoped to call records. Both are consented by an administrator in your own directory. Declining either leaves the rest of the product working, you just lose that capture path.
How does it decide what counts as a sales meeting?
At least one attendee outside your own domain. Internal meetings are ignored, because a CRM that logs your own stand-up stops being readable within a month. The rule is a single readable check rather than a scoring model you cannot inspect.
Can the agent email a customer on its own?
Not until somebody has put it there. It refuses to dispatch unless it is active, its channel is configured for your workspace, and it has passed five simulated conversations. A reply from the prospect takes the conversation out of the sequence and gets classified rather than continuing to send at someone who already answered.
Is Simple Council checking the agent before it writes?
No, and it would be convenient to say otherwise. Simple Council receives model token usage from this product for cost governance, it is best effort, and it is switched off when its endpoint is unset. It does not sit in front of writes to your customer records. Governance in Simple Growth today is the visibility rule, the audit rows on agent tool calls, and the fact that a person accepts the drafts.
Can we start an evaluation ourselves from this page?
No, and the reason is worth stating plainly. Simple Growth has no mechanism that ends an evaluation: there is no term held on the workspace record, and nothing restricts the surface when one runs out. Publishing a self-service trial button over that would be promising an end date the product cannot keep. So access is arranged with us, the length is agreed in that conversation, and one of us is accountable for it. Your records stay yours and stay exportable either way.
Can we buy it through our Microsoft agreement?
Not yet. The Marketplace fulfilment path is implemented and tested against the Partner Center subscription states, but the offer is not published, so there is no transactable listing and no consumption commitment eligibility to claim. Purchase today is direct.
Ten questions worth answering before you move CRM.
A short readiness checklist for sales and revenue leaders. It runs in the page, stores nothing, and prints if you want to take it into a meeting.
Before you move CRM.
None of these need a product to answer. If most of them are uncomfortable, the problem is that the record depends on people remembering to write it, and that is worth fixing whoever you buy from.
Nothing here is stored or sent. Tick boxes to work through it, or print the page and take it into the meeting.
What it connects to across the portfolio.
Simple Growth is the revenue layer of SimpleOS. A qualified lead from Simple Marketing becomes a deal here, the signed scope becomes a plan in Simple Projects, and the hours worked against that plan return through Simple Time as the invoice.
How to start
-
Available on request Open
Running in production and taking new customers. There is no self-serve trial or purchase on this one yet, so access is set up with us directly.
Request access -
Direct trial with Simple Intelligence Not open yet
This product has no self-serve trial yet. Ask us and a person will set access up.
-
Direct subscription from Simple Intelligence Not open yet
There is no direct checkout for this product yet. Where a trial exists it converts to a paid subscription inside the product.
-
Microsoft Marketplace Not published yet
There is no transactable listing for this product yet, so it cannot be bought against a Microsoft agreement today.
-
Sponsored subscription for member companies Not open yet
The member sponsorship program is not open for this product yet.
Questions about evaluation length, extensions, or sponsored access are answered on the get started page.
Ask for access and we will agree the term with you.
Once you are in, connect one calendar and see how much of last month's activity was never recorded anywhere. That answer is useful whether or not you buy anything.