“Customers is available today. With the Orders module, orders sit on the same records: on the customer's timeline, in their buying history and in your sales reporting.”
6 things.
And what each one is for.
Accounts and contact relationships
Companies, people, contact points, custom attributes and relationship history stay linked, so one customer has one story rather than four half-versions of it.
Benefit Anyone picking up an account can see who matters and what has happened.
Proof: Accounts · contacts · relationship links · custom fields
Orders on the customer record
With the Orders module, each order shows on the customer's timeline next to calls, notes and deals. The customer record shows its confirmed order value for the last 30, 90 and 365 days, customers who look due to reorder are listed with the numbers behind it, and an order can be linked to a deal. Nothing is sent to anyone. This part arrives with the Orders module, which is taking pilot customers.
Benefit Sales can see what a customer actually buys before they call.
Proof: Timeline · order value by period · reorder list · order linked to deal
Lead capture and assignment
Your team types in each enquiry, from a phone call or a photo of a name card, and it lands in one list with a record of when and where it came from. Another system can add a lead through the API as a title, its source and a stage, connected by your developer. You set the assignment rules, and a lead matching no rule goes to an unassigned queue a manager can see rather than vanishing.
Benefit Nothing falls between two rules and disappears.
Proof: Manual · name card · API · owner · unassigned queue
Scoring and qualification
Lead scoring is a calculation from criteria you configure, not an opinion. The score recalculates when the data changes and you can open it and read the contribution of each factor.
Benefit A disputed score becomes a two minute conversation about a weighting, not an argument about trusting the software.
Proof: Configured criteria · factor breakdown · recalculation · audit trail
Configurable sales pipelines
Your stages, not a template's stages. A qualified lead converts into an opportunity carrying an owner, a stage, a value, a currency, a probability, an expected close date and its original source, without copying the contact or the company.
Benefit You can see what is in play and roughly when it is expected to land.
Proof: Stages · opportunities · value · expected close · won/lost
Activities and next actions
Calls, meetings, notes and tasks record against the customer with due dates and a named owner for the follow-up. Closing a deal requires a close date and a reason from a list written in your language.
Benefit After one quarter, why deals die stops being one person's opinion and becomes a number with deals attached to it.
Proof: Calls · meetings · notes · tasks · due dates · won/loss reasons
Four steps, in this order, every time.
- 01
Capture
An enquiry lands with its source and creation date.
- 02
Own
A rule assigns it, or the unassigned queue holds it.
- 03
Progress
The opportunity moves through your configured stages.
- 04
Learn
The won or loss reason you chose feeds the reports.
Thirty minutes, and you leave with three answers.
Whether a pilot fits the way your orders arrive, what we would set up, and what it would cost. Written down, so you can put it in front of a partner or a board.
Bring three things
- A few real orders, as they arrive today.
- Your product and price list, in whatever form it is in.
- Who takes and confirms orders now.
Leave with three answers
- Whether the pilot fits.
- What we would set up, and how.
- What it would cost, written down.