We make CRM simpler. We remove bloat with sharp insights and tooled methods. If that is the conversation you want to have about your Salesforce estate, this page is where it starts — with a Quickstart if you want an expert to show you what the analysis surfaces, or with a demo, a guided walkthrough of the analysis on the demonstration estate, if you want to see it first.
A guided walkthrough of the analysis on a real five-org estate.
A couple of hours with one of our experts, on your own org.
Prefer email? Write to contact@stoodcrm.com. We answer in French or English, usually within a working day.
What a Quickstart is
Every Stood engagement starts as a Quickstart: a couple of hours of work with one of our experts, walking the first steps on one of your own orgs. Two hours is two hours — it is a capability showcase, not an audit and not the whole arc: a first scan, the shape of the analysis, the insights it turns up on your own metadata, and a straight answer on what your event logs can and cannot support. No project plan, no deliverable, read together with your analyst or your partner’s consultant.
What matters is what comes after: a first scoped project — three orgs over three months is a common shape. Security comes first — a read-only permission set and appropriately scoped user access, prepared with your admins before the first scan, so the access Stood Flows uses says what the tool is. Then the scans, the insights walked through with your team, and governance agreed: who reads the analysis, who raises and owns issues, and how those issues feed your architecture and licensing decisions. The first project produces a baseline, a qualified worklist and a rhythm — and the installation itself: installers and the license key are provided as part of scoping it.
Then the rhythm continues, monthly for most customers, and the technical-debt curve bends measurably from snapshot to snapshot. The rhythm is yours: it runs whether or not you buy services from Stood. Services support the practice; they are not the practice. A one-off assessment is possible; the value compounds with continuity.
What the first project needs from your side
Three things, none of them exotic, all prepared together in the first sessions:
- Salesforce CLI (
sf, v2) on the analyst’s machine. Stood Flows reads through it and never holds credentials of its own; installation takes a few minutes if it is not already there. - A Salesforce user with read permissions on the objects and metadata under analysis — a dedicated read-only user through a read-only permission set is the clean configuration, and the one we prepare first with your admins. No admin write access, no connected app, no OAuth grant to a third party. The security page states the full architecture your security team will want to review.
- A first target org. We offer a full or partial sandbox for the opening scan if that is easier to authorise; production works just as well — safe by construction, read-only at three layers — and is where the usage numbers are real. Your call, either way.
The first scan runs metadata first, then usage — typically a couple of minutes, with heavy orgs continuing in the background. When it finishes, the Mapping view shows your business processes as swimlanes, stage by stage, with per-stage active/total counts: the first honest picture of which processes are real. From there the project works through structure, usage and licensing with your analyst or your partner’s consultant.
What the first conversation covers
- Scope. Which orgs, which business processes, what question the analysis has to answer first.
- Security preparation. What the read-only permission set contains and how access is scoped — and, where team sharing is wanted, the GitHub repository or S3 bucket it will run on, under your own publisher and reader roles.
- Governance. How insights become qualified issues, who owns them, and the rhythm afterwards.
- Partners. Whether the first project runs with your existing integration partner — it often should; the partners page describes the delivery model.
If you are still at the reading stage, the methodology and security pages answer most of what a first call would.