Your CRM doesn't know what your operations know.

Weighted composite of five factors recomputed on every relevant event. The defaults: payment behavior 30 percent (timeliness + consistency vs. agreed terms), volume trend 25 percent (growing / stable / declining on rolling 90-day window), communication recency 15 percent (days since last meaningful interaction), credit utilization 15 percent (% of credit limit currently outstanding), and revenue concentration 15 percent (relative exposure of total book). Weights are configurable per tenant in Settings. ClientHealthService recomputes on payment.received, order.created, communication.added, and a few other events — never on a schedule. The score drives the badge color in Directory, the alert priority in Overview, and the segment filters in Pipeline.

No by default. Sales sees revenue and the negotiated sell-side pricing but not the manufacturer buy cost. Finance and Admin see full margin. This is enforced at the field level, not the screen level — the same client profile page renders different fields for different roles, and the API returns different JSON shapes depending on who is asking. The role taxonomy is Admin, Manager, Operations, Finance, Sales, Viewer with the matrix specified in the platform docs. Custom roles with bespoke field-level access are available on Business and Enterprise tiers.

Yes. A client can be parent, child, or standalone — the relationship is optional and can be added at any time without re-keying historical data. ABC Corp as a parent can have ABC Europe and ABC Americas as children, each with their own orders, contacts, addresses, and per-product pricing. The parent rolls up: combined revenue across all entities, consolidated AR view, group-level pricing agreements that flow down to children unless overridden, and a parent-level health score that aggregates child scores by revenue contribution. Reports can be run at parent level or child level. Procurement teams negotiating group contracts use the parent view; ops teams shipping to a specific subsidiary use the child view.

DealService calls OrderService.createDraftFromDeal() which pre-populates an order in the Orders section with everything the deal already knows: products and quantities from the deal’s line items, the client’s negotiated pricing per product, the client’s default Incoterm and currency, the client’s preferred shipping address and payment terms, the assigned salesperson and account owner, and a link back to the deal so pipeline reports stay connected to operational outcomes. The sales rep clicks once to confirm. Time from Won to draft order: under 30 seconds in production benchmarks. This is the single feature that gets Sales adopting the platform instead of working around it — the moment when their work flows into operations without re-keying.

Yes. Native importers for Salesforce, HubSpot, Pipedrive, and Zoho map accounts, contacts, opportunities, pipeline stages, deal owners, and historical activity. The importer preserves stage history so your conversion analytics stay continuous — your Q3-to-Q4 win-rate trend doesn’t reset on the migration date. CSV import covers everything else with column mapping, type inference, and preview-before-commit. Most teams complete migration in a single afternoon. For teams with very large pipelines (5000+ deals) we offer a managed migration that runs in parallel with the legacy system for a 2-week reconciliation period before cutover.