Leads, deals, contacts, activities
Selling from first touch to invoice: leads, staged deals, contacts, activities and touch sequences. It replaces the spreadsheet where reps keep customers in their heads: a deal knows its amount, its date and its next step, and an order is born from the card already linked — no re-entering the customer, prices or lines. The sales lead gets a screen of their own: plan vs fact per rep and a deal queue ranked by money at stake. Switch it off if you sell by orders with no pipeline.
/crm/sequencesThey read the same documents as your team, prepare the next action, surface exceptions and keep the decision trail inside the process.
You set the authority. Payments, goods receipts and shipments always wait for a person. Everything else, customer messages included, starts as a suggestion and runs on its own only once you allow it and verified results back it.
Choose an industry preset and start with realistic demo data; the team sees the target flow before migration.
Import or connect source data. Digital employees observe, draft and expose gaps while people confirm decisions.
For a typical 50-person company, the target is four weeks. Source quality, integrations and legal requirements can change it.
A module is more than screens. Digital employees work behind them: they prepare the decision and bring it to you instead of waiting for you to type everything in. Below — who exactly, what they do, and where their authority stops.
Moves deals through stages and drafts the next step for the rep
Sends nothing to a customer without your approval
Builds the sales lead's day: a money-ranked decision queue, not a report
Proposes who to review today; the lead decides
Every capability below is tied to an implemented product route. A reviewed product screenshot is shown when it exists in this language; otherwise the route is explained as a transparent work loop, never as invented UI.
The sales lead's screen: an action queue ranked by money at stake, each item paired with what happens if you skip it. Consequence figures are computed from data, never invented. The day starts with decisions, not reports.
/cockpit/rop
Stages, amounts and dates on one board. The digital seller moves the deal along, drafts the next step and brings it to you for approval — you decide instead of filling in cards.
/crm/pipeline
Scoring, a stage playbook, quote scenarios and the whole correspondence in one place. An order is born from the card already linked — no re-entering the customer, prices or lines.
/crm/opportunities
Email and call sequences, activities with reminders, a history per contact. No lead is forgotten: open touches sit in their own list.
/crm/sequences
Team KPIs: stage conversion, deal velocity, plan attainment. Not an average — you see who loses deals and at which stage.
/crm/kpis
Won and lost money by month, win share and deal cycle per manager. You see who piles up losses and when the team drags dead deals instead of closing them early.
/crm/win-loss
Where deals leak and where they stall: median days per stage against the pace of won deals, money sitting in each stage, and loss reasons with totals. The bottleneck is named before the month drops.
/crm/pipeline-flow
Stalled deals, missed promises, plan gaps, and the reasons behind wins and losses. Win/loss review runs on data, not memory.
/cockpit/ropYes. Start with one workflow and the data it needs. Add adjacent modules only when the operating process calls for them.
Digital employees watch product records, prepare the next action, surface exceptions and keep the decision trail. Their exact actions and authority gates are shown on this page.
Your team sets the authority. Payments, goods receipts and shipments always wait for a person's confirmation, at any trust level. Everything else, customer messages and ledger entries included, stays on suggestion or approval until you deliberately allow it to run on its own.
Start by exploring the process with labelled demo data. A live rollout needs checked source data, connected systems and agreed approval rules. We scope those prerequisites with your team before agreeing a schedule; creating a workspace is not a completed implementation.