Stood is priced per analysed org, per month — from €950 /org /month on the Standard edition, with volume discounts as the estate grows. There are no per-viewer fees: a licensed org can be shared with unlimited viewers, so the architecture board, the CFO and the delivery team read the same analysis without anyone counting seats. The license buys the fetch and the analysis; distribution of what you learn is free, because an analysis nobody reads removes no bloat.
Two editions
| Licensed by the org, never by the seat. | StandardStandard editionfrom €950/org /monthVolume discounts as the estate grows · no minimum durationLicensed per org, month to month. The full mapping and KPI analysis. | EnterpriseEnterprise editionGlobalpackageEverything in Standard, across the estate · 3-month minimumThe estate as one package, plus the event-log and contract analysis. |
|---|---|---|
| Processes and structure | ||
| Process mappingEvery business process as its stages, with the automations and rules that fire on each. Backbone and selected custom objects, no setup. | ✓Included | ✓Included |
| Volume and stage analysisRebalance stages against where records really sit, and find ghost records stranded on stage values that no longer exist. | ✓Included | ✓Included |
| Field usageSeparate the fields a process really uses from the ones its layout only asks for, and tell which of those you can delete rather than merely hide. | ✓Included | ✓Included |
| Complexity scoringRank processes by what their structure costs to maintain, on a plain sum of seven counts your architects can recompute. | ✓Included | ✓Included |
| Object analysisTell the related objects carrying real data weight from the relationships built and never adopted. | ✓Included | ✓Included |
| Automation, code and integrations | ||
| Flow inventory and scoringEvery active flow scored by step count and clustered by what triggers it, with Process Builder flagged as its own migration list. | ✓Included | ✓Included |
| Flow runtime and cold flowsHow often each flow ran, how long it took and how often it errored — and which are deployed but have never executed at all. | —Not included | ✓Included |
| Apex dependency treesWhat changing a trigger would drag with it, ranked by dependency weight rather than line count. | ✓Included | ✓Included |
| Cold class detectionWhich classes had no observed execution in the analysed window — the deletion and extraction candidates, from the org's own logs. | —Not included | ✓Included |
| Inbound and outbound call volumesWhich integrations actually call the org, against the set the architecture diagram says should. | ✓Included | ✓Included |
| Usage and licensing | ||
| Record activity datesLast created and last modified per record type — the simple read that names unused and empty processes as removal candidates. | ✓Included | ✓Included |
| DML audit from event log filesWho wrote to which business object, per profile and per licence type, over a stated window. | —Not included | ✓Included |
| Visit audit from event log filesWhat the read-only population opens — screens, paths, session length — as aggregates. No record ids, no URLs, no IP addresses. | —Not included | ✓Included |
| Licence and seat positionProvisioned, assigned and logged in per licence type and profile — the seat position, before anyone argues from an org-wide average. | ✓Included | ✓Included |
| Estate, contract and governance | ||
| Multi-org dashboards and KPI evolutionScorecards with deltas against a chosen baseline, so whether the debt is falling is a number with a date on it. | ✓Included | ✓Included |
| SELA contract reconciliationEvery line typed, priced and mapped to the org that consumes it, with unmapped lines flagged as questions carrying a figure. | —Not included | ✓Included |
| Issue trackingA qualified issue raised in February is visibly closed by July, or visibly still open. | ✓Included | ✓Included |
| Data residency | ||
| Level 1 · the analyst's machineThe analysis is local files that work with no connection at all. There is no Stood cloud to hold a copy of them. | ✓Included | ✓Included |
| Level 2 · your GitHub repositoryVersioned snapshots the team subscribes to, under Admin and Contributor roles you govern. | ✓Included | ✓Included |
| Level 3 · your S3 bucket, or a target you specifyThe same snapshots on storage your platform team chose, inside your own perimeter. | —Not included | ✓Included |
| Access and assurance | ||
| Licensed orgs, unlimited viewersEveryone who needs to read the analysis reads it — architecture board, CFO, delivery team — with nobody counting seats. | ✓Included | ✓Included |
| Read-only by constructionNothing in the application can write to the org, and nothing reaches Stood in any mode. | ✓Included | ✓Included |
| Beyond the Salesforce core | ||
| Solution design and system-of-systems graphsDesign the target state in the same tool that measured the current one. | —Not included | ✓Included |
| Marketing CloudExtends the same analysis to Marketing Cloud estates. | —Not included | Add-onAdd-on |
Viewers are unlimited and free on either edition. Both editions run the same security architecture. Backbone = Lead, Opportunity, Case, Campaign, Account, Contact, plus selected custom objects supporting key business processes.
The Standard edition is licensed per analysed org, month to month — add orgs as you need them, drop one when a project ends, and volume discounts apply as the count grows. Everything in it applies to every org you license: the mapping and KPI analysis, the dashboards and their deltas against a baseline, usage read from record activity dates, field usage per record type — which fields on a layout nobody fills in, and which of those you could actually delete — the licence and seat position per profile, and versioned sharing and issue tracking on your own GitHub repository. License three orgs and the dashboard spans those three.
The Enterprise edition changes two things. It is packaged for a whole estate rather than counted org by org, with a three-month minimum — one snapshot proves little; a baseline and two deltas prove a trend. And it adds the analysis that reads an org’s own logs and its contract: the DML audit from event log files, cold class detection, the SELA (Salesforce Enterprise License Agreement) reconciled line by line, solution design and system-of-systems graphs, and publishing to your own S3 bucket or a target your platform team specifies.
Both editions run the same security architecture.
Services
Every engagement follows the same arc: a Quickstart — a couple of hours with one of our experts, walking the first steps on your own org rather than the whole arc — then a first scoped project, three orgs over three months being a common shape, which establishes a baseline, a qualified worklist and a rhythm. The rhythm then continues, monthly for most customers, whether or not you buy services from Stood. The services below exist to support that practice, not to constitute it.
Expert sessions & support
Working sessions with our architects and analysts — KPIs, qualified issues and solution design where an engagement needs depth on the method — plus support and training for the people running the analysis as the practice establishes itself. Produces: a team that runs the analysis without us.
Tooled assessments
A scoped, tool-driven assessment of an org or an estate. We can run it, or work alongside your existing Salesforce partner — both are standard shapes, and the partner route is a feature of the engagement, not a fallback. Produces: the measured state of the estate as scoping input — for a renewal, a transformation proposal, or a governance reset. Where the scope is the SELA, the outcome is a defensible position at renewal: the seat buffer sized per org, its movement across snapshots, and the contract reconciled line by line behind it.
Advisory & transformation
The strategic end: turning qualified issues into an architecture and licensing plan, and supporting the programme that follows — simplification, re-platforming decisions, license renegotiation built on a buffer you can size and defend. We support the programme; you and your partners own it. See the partners page.
Agentic factories
A post-assessment capability, not an entry point. Where an analysis has surfaced custom development too heavy for the platform to keep carrying, Stood holds generic assets that can absorb it — deployed and operated on the customer’s own cloud, with backbone processes staying in Salesforce. Nobody starts here; the evidence has to come first.
Questions people actually ask
What counts as an org? Any org you fetch and analyse — production or sandbox each count as one. Most teams license their production orgs and one integration sandbox.
What happens when the term ends? Your analyses are local files on your machines — JSON and .sfschema. They remain yours: readable, archivable, diffable. The application stops fetching new snapshots; nothing you produced is held hostage, because none of it was ever on our servers.
Who counts as a viewer? Anyone reading a shared analysis of a licensed org — through team sharing on your own GitHub repository, on an S3 bucket or custom target on the Enterprise edition, as a reader under your own roles, or as exported files. Viewers are unlimited and never billed, on either edition.
Does the analysis need Shield or Event Monitoring? Not for structure, complexity, volumes, field usage or licence assignment — those come from metadata, the licensing objects and ordinary queries against your own records. The write-based usage analysis, cold-class detection and I/O ranking read event log files, and how much depth is available there is a property of your org’s own options rather than of Stood Flows. The scoping call establishes it, and a Quickstart answers it in the first hour.
What about procurement paperwork? A Data Processing Agreement, the subprocessor list and the security architecture document are available on request — the security page states the posture in full.
Can we start small? Yes. Start with a Quickstart, then a first project on one org, licensed on the Standard edition — no minimum duration — run the monthly refresh for a quarter, and move to the Enterprise edition when the event-log depth, the contract work or the estate packaging earns its case. The refresh rhythm is yours either way: it runs whether or not you buy services from us. Simpler CRM is the outcome the pricing is built around: the analysis pays for itself in the bloat it removes.