# Stood > Stood is a FinOps and complexity audit for Salesforce. Its product, Stood Flows, measures every Salesforce business process — structure, real usage and contract cost — so license waste, technical debt and savings get numbers anyone can audit. Built by Hway Digital SAS, France. ## Key facts - Company: Hway Digital SAS (France), brand Stood. Product: Stood Flows. Founder: Pierre Lecointre. - Category: Salesforce license optimization, CRM FinOps, technical debt and org complexity audit, multi-org Salesforce governance. - Unit of measure: the business process (object × record type), because a process has an owner and a budget. The complexity score is the plain sum of seven counts — stages, profiles, layouts, pages, flows, triggers and validation rules — with no weighting, so anyone can recompute it. - Usage is measured from writes (DML from Salesforce event log files), not logins. Licensing is read as a cascade: provisioned → assigned → logged in → any recorded operation → wrote to a business object. - Buffer and releasable seats are kept apart: the buffer (unassigned entitlement) is a negotiating position to size and time against the renewal; releasable seats are qualified rung by rung (no login in 90 days, read-only consumers, non-business activations). - Contract: the Salesforce Enterprise License Agreement (SELA) is reconciled line by line against the orgs that consume each line. Agentforce and Data 360 credit consumption is set against contract entitlement. - The product emits insights (each with a detection method and a remedy); people or agentic co-workers raise issues from them. Stood Flows never deactivates users or changes an org. - Architecture: desktop app for macOS and Windows reading through the Salesforce CLI. Read-only by architecture and by a least-privilege permission set on a dedicated user. No Stood cloud in the data path; analyses are local by default; team sharing runs on the customer's own GitHub repository or S3 bucket with publisher and reader roles. - Event-log depth (retention, hourly detail) is licensed on the Salesforce side (Event Monitoring, typically Shield), so write-based usage analyses depend on the customer org's own options. Structure, complexity, volumes and license assignment do not. - Pricing: from €950 per analysed org per month (Standard edition, no minimum duration, volume discounts). Enterprise edition packages a whole estate with a three-month minimum. Viewers are unlimited and free. - Engagement: a Quickstart (a couple of hours with an expert on the customer's own org), then a first scoped project (for example 3 orgs over 3 months), then a monthly practice that runs whether or not services are bought. - Figures shown on the site come from a synthetic demonstration estate and are illustrative, not customer results. ## Product - [Stood — home](https://stoodcrm.com/): FinOps and complexity audit for Salesforce - [Stood Flows — Salesforce org analysis by business process](https://stoodcrm.com/stood-flows/): Stood Flows measures every Salesforce business process — structure, usage, contract cost — so bloat, the license buffer and savings get numbers you can audit. - [Analyse — processes, structure, code and data](https://stoodcrm.com/stood-flows/analysis/): Map every Salesforce business process — stages, complexity, related objects, flows, Apex dependency trees and cold code — with counts you can verify. - [Usage & cost — Salesforce licenses, writes and the SELA](https://stoodcrm.com/stood-flows/usage-and-cost/): Measure real Salesforce license usage, writes not logins: qualify releasable seats, reconcile the SELA line by line and set Agentforce credits against the contract. - [Diagnostics — findings with named remedies](https://stoodcrm.com/diagnostics/): Nine named Salesforce findings, each with a detection method, a qualification test and a remedy — the Stood Flows diagnostic entry set, on one page. - [Govern — the estate, baselines and the practice](https://stoodcrm.com/stood-flows/governance/): Govern a multi-org Salesforce estate on evidence: eight portfolio scorecards, versioned snapshots and baselines, an issue backlog, a monthly practice. ## Guides and resources - [Salesforce license optimization — a practical guide](https://stoodcrm.com/salesforce-license-optimization/): How to optimize Salesforce licenses on evidence: read the contract, measure writes not logins, qualify releasable seats, size the buffer and track Agentforce credits. - [Customers — who Stood is built for](https://stoodcrm.com/customers/): Stood is built for Global Fortune 500 companies sustaining large Salesforce estates — multi-org by history, costs without a usage story. - [Methodology — how we measure a Salesforce org](https://stoodcrm.com/methodology/): The published method behind Stood Flows — from Salesforce business processes and volumes to structure, Apex, usage and cost, with the limits stated. - [Security — Salesforce analysis, no cloud in the path](https://stoodcrm.com/security/): Stood Flows analyses Salesforce with no cloud in the path — no Stood backend, local by default, sharing on infrastructure you own. In full. - [Pricing — Stood Flows editions and services](https://stoodcrm.com/pricing/): Stood pricing — Salesforce analysis from €950 /org /month, with volume discounts. Unlimited viewers, Standard and Enterprise editions. ## Blog - [Read your Salesforce data where it already lives](https://stoodcrm.com/blog/salesforce-data-warehouse-landing-zone/): 2026-10-08. Some records in the CRM were never a workplace. They are referentials — read far more than written — and the warehouse already holds what they need. Moving them upstream takes the seats with it. - [412 business processes. 168 saw a record move.](https://stoodcrm.com/blog/what-eight-orgs-look-like-when-you-count-them/): 2026-09-18. What a Salesforce estate of eight orgs contains once every business process, flow, Apex class, seat and pageview is counted rather than estimated. - [Headless one week, bundled the next](https://stoodcrm.com/blog/headless-one-week-bundled-the-next/): 2026-09-04. Claudeforce says the agent need not live in the Salesforce org. The new editions bundle more into it. Both call for control over every seat and credit. - [Multi-Org Salesforce Governance, Simplified](https://stoodcrm.com/blog/multi-org-salesforce-governance-simplified/): 2026-08-20. Managing a multi-org Salesforce portfolio across enterprise business units usually means flying blind. Technical debt, bloated automation, and unused licenses quietly accumulate inside every instance — until system performance degrades and licensing costs balloon. - [Controlling Value vs Costs for CRM (+AI) Activities](https://stoodcrm.com/blog/controlling-value-vs-costs-for-crm-ai-activities/): 2026-06-22. The shift to the Agentic era — anchored by platforms like Salesforce Agentforce and Data Cloud — introduces a massive paradigm shift for enterprise architecture: variable consumption costs. - [The 10 KPIs that actually tell you where your Salesforce org hurts](https://stoodcrm.com/blog/the-10-kpis-that-actually-tell-you-where-your-salesforce-org-hurts/): 2026-04-15. Salesforce orgs don't get complex. They accumulate. Org-wide averages hide everything that matters — the right level of slicing is the process, and that's where audit becomes action. - [The Inflection Point of Enterprise CRM](https://stoodcrm.com/blog/the-inflection-point-of-enterprise-crm/): 2026-03-26. Bloat is the bug. Complexity is the tax. The enterprise CRM stack is at a breaking point — and the pragmatic leaders who move first will own the next decade of speed. - [Beyond the Audit: Igniting the Salesforce Flywheel](https://stoodcrm.com/blog/beyond-the-audit-igniting-the-salesforce-flywheel/): 2026-03-12. Most Salesforce professionals treat an "audit" like a dental checkup — something you do once a year, dread the results, and promptly forget about until the next pain point. But a static audit is a relic of the past. - [Sovereign CRM for the Agentic Era](https://stoodcrm.com/blog/sovereign-crm-for-the-agentic-era/): 2026-03-03. For too long, CRM systems have felt like walled gardens — locking you into their infrastructure and deciding how your data lives. Sovereignty in the agentic era starts with knowing, and owning, what your CRM actually does. - [Visualization: The Key to Scaling Salesforce](https://stoodcrm.com/blog/stood-flows-visualization-scaling-salesforce/): 2026-01-13. In the world of Salesforce administration and RevOps, complexity is a silent killer. What starts as a streamlined CRM inevitably evolves into a sprawling labyrinth of record types, hundreds of picklist values, and aging automation. - [Stop Forcing, Start Composing](https://stoodcrm.com/blog/stop-forcing-start-composing/): 2025-11-14. Is your CRM working for you, or are you working for your CRM? For decades, the promise of a CRM was a single source of truth — which led to the rise of the monolithic CRM. - [How to Prevent Bloat in Your Enterprise CRM](https://stoodcrm.com/blog/fighting-the-invisible-enemy-how-to-prevent-bloat-in-your-enterprise-crm/): 2025-09-15. In the world of enterprise software, software bloat is the main enemy we face when trying to operate at scale. It's a silent force that gradually adds complexity, slows down processes, and frustrates users. - [Don't make AI your landlord, get ROI](https://stoodcrm.com/blog/dont-make-ai-your-landlord-get-roi/): 2025-09-09. The promise of AI is everywhere, and business leaders are shifting focus from whether to adopt it to how to scale it for tangible results. Yet a recent MIT study reveals that 95% of Generative AI pilots fail. - [Manifesto — Simplicity as a Service](https://stoodcrm.com/blog/manifesto/): 2025-06-10. The enterprise software game is broken — clunky, overpriced, and stuck in the 00s. Our manifesto: we make CRM simpler. We remove bloat with sharp insights and tooled methods. - [Enterprise Software Deserves Simplicity](https://stoodcrm.com/blog/simplicity-deserved/): 2025-05-19. Enterprise software, particularly CRM systems, has evolved from simple contact management tools into complex, feature-heavy platforms. A new approach emphasizes simplicity, openness, and adaptability. ## Optional - [About — Hway Digital, the company behind Stood](https://stoodcrm.com/about/): Stood is built by Hway Digital SAS, France. We make Salesforce CRM simpler: we remove bloat with sharp insights and tooled methods. - [Contact — start a Quickstart conversation](https://stoodcrm.com/contact/): Contact Stood to start a Salesforce Quickstart — a couple of hours with one of our experts, showing what the analysis surfaces. Or write to us. - [Partners — Salesforce analysis at scale](https://stoodcrm.com/partners/): Stood provides the tool, the method and expert support. Partners bring the delivery capacity to run analysis and transformation at scale. - [Documentation](https://stoodcrm.com/docs/): how each Stood Flows view works and where its numbers come from - [Apex analysis and packaging](https://stoodcrm.com/docs/apex/) - [Cost and reach](https://stoodcrm.com/docs/marketing-cloud-cost-and-reach/) - [Dashboard KPI definitions](https://stoodcrm.com/docs/dashboard-kpi-definitions/) - [DML analysis and event log files](https://stoodcrm.com/docs/dml-and-event-logs/) - [Enterprise and business units](https://stoodcrm.com/docs/marketing-cloud-business-units/) - [Field usages](https://stoodcrm.com/docs/field-usages/) - [Full analysis: run, pause, resume](https://stoodcrm.com/docs/full-analysis/) - [Hiding names and emails](https://stoodcrm.com/docs/hiding-names-and-emails/) - [History timeline](https://stoodcrm.com/docs/history-timeline/) - [I/O analysis and heavy consumers](https://stoodcrm.com/docs/io-and-heavy-consumers/) - [Install and connect](https://stoodcrm.com/docs/install-and-connect/) - [Integrations and source-DE usage](https://stoodcrm.com/docs/marketing-cloud-integrations/) - [Issues and epics](https://stoodcrm.com/docs/issues/) - [Licence keys](https://stoodcrm.com/docs/licence-keys/) - [Licensing](https://stoodcrm.com/docs/licensing/) - [Managed-package usage](https://stoodcrm.com/docs/managed-package-usage/) - [Marketing Cloud: overview and connection](https://stoodcrm.com/docs/marketing-cloud/) - [Methodology: backbone first](https://stoodcrm.com/docs/methodology/) - [Objects explorer](https://stoodcrm.com/docs/objects-explorer/) - [Objects, record types and lineage](https://stoodcrm.com/docs/objects-and-record-types/) - [Org permissions](https://stoodcrm.com/docs/org-permissions/) - [Refreshing a Marketing Cloud folder](https://stoodcrm.com/docs/marketing-cloud-refresh/) - [S3 access policies](https://stoodcrm.com/docs/s3-access-policies/) - [Security posture](https://stoodcrm.com/docs/security-posture/) - [SELA contracts](https://stoodcrm.com/docs/sela-contracts/) - [Settings: GitHub, offline mode, CLI paths](https://stoodcrm.com/docs/settings/) - [Sharing and roles](https://stoodcrm.com/docs/sharing-and-roles/) - [Team sharing over S3](https://stoodcrm.com/docs/team-sharing-s3/) - [The Flows view](https://stoodcrm.com/docs/flows/) - [The folder dashboard](https://stoodcrm.com/docs/folder-dashboard/) - [The KPI table, column by column](https://stoodcrm.com/docs/kpi-table/) - [The Marketing Cloud dashboard](https://stoodcrm.com/docs/marketing-cloud-dashboard/) - [Visits: what people look at](https://stoodcrm.com/docs/visits/) - [Volumes and complexity](https://stoodcrm.com/docs/volumes-and-complexity/) - [Your first audit](https://stoodcrm.com/docs/first-steps/) - [Blog RSS feed](https://stoodcrm.com/blog/rss.xml)