Qualification, lifecycle and pipeline
Sales
What you capture, the stages you move through and the rules that gate them are configuration — which is why two businesses that sell completely differently run on the same system.
Configuration, not code
Qualification fields you define
Lane and volume for a freight forwarder; budget and location for a property consultancy. The same engine drives extraction, the order the agent asks in, the admin forms and the filters.
- One schema definition, four surfaces generated from it
- Two completely different businesses, zero bespoke code
Freight forwarder
Property consultancy
A pipeline with rules
A lifecycle that refuses illegal moves
Stages carry entry requirements. Dragging a card somewhere it cannot go is refused with the requirement named, rather than snapping back without explanation.
- Entry requirements are part of the stage, not tribal knowledge
- The refusal tells you what to capture next
Qualifying
Sundaram Textiles
24 TEU/mo · FOB pending
Quoted
Drop refused
Won
Move to Quoted refused — Incoterm is required to enter this stage
The rest of sales
Scoring you can read
Every contribution is recorded per rule, including the ones that did not fire. An opaque score gets ignored, and an ignored score is worse than none because it still takes up space.
Schema versions travel with the row
Edit your qualification schema and existing records keep the version they were captured under, migrating lazily on read. Nothing is orphaned.
Pipeline, tasks and meetings
Configurable stages with forecast weighting, follow-ups the agent can create, and meetings with outcomes.
Next best action
Ask a missing question, answer an objection, schedule, escalate. Surfaced for a person, not executed silently.
See it with data in it
The demo is the real product, seeded with two businesses that sell completely differently.