Start with an enquiry, not a prediction
An opportunity is a particular potential purchase, not the entire customer relationship. Give it a short description, a responsible colleague and the next action. A customer who asks about two services may have two opportunities. Avoid filling a pipeline with names that have no actual enquiry or agreed follow-up.
Use five stages as a starting example
These stages are an illustrative working routine, not mandatory AkuCRM defaults. Adapt them to the way your business actually sells and define what must be true before an opportunity moves.
- New enquiry: a person has contacted the business about a specific need. Next action: respond and clarify.
- Need confirmed: the scope and the customer’s next decision are understood. Next action: agree what information or proposal is needed.
- Quotation or proposal shared: the customer has received the agreed offer. Next action: confirm receipt and arrange a suitable follow-up.
- Decision pending: a specific decision remains. Next action: record the outstanding question and agreed date.
- Closed: record the actual won or lost outcome. If no decision has been made, do not call it a win.
Agree evidence for each movement
“They seem interested” is difficult for a colleague to act on. “Customer confirmed the required service and requested a quotation” explains why the opportunity advanced. Keep evidence short and factual. If the scope changes or a decision is delayed, update the next action rather than moving the opportunity forward simply because time has passed.
Separate an overdue action from a sales stage
An opportunity can be in Decision pending and also have an overdue follow-up. Treat stage and action date as separate questions. Otherwise the pipeline becomes a mix of buying decisions, staff reminders and vague statuses. Review overdue promises, opportunities without a next step and handovers between colleagues each working day.
Example: a small wholesale order
A fictional wholesaler receives an enquiry about stock for a shop. The team confirms quantities and delivery requirements, shares a quotation and agrees when the buyer will decide. If the buyer asks to change the quantities, the next action is a revised quotation with a named owner and date. The example demonstrates a process; it is not an AkuCRM customer testimonial or a promise about revenue.
Run a short weekly pipeline review
Ask what changed, what was promised and what blocks the next decision. Record losses honestly and use reasons only when the customer actually provided them. Do not invent conversion percentages for stages or add forecast value to orders that do not have a defensible amount.
- Review open opportunities with the responsible colleague.
- Check the last meaningful customer conversation.
- Confirm one next action and due date.
- Close completed or declined opportunities using the actual outcome.
- Look for repeated questions that could be answered with a clearer proposal or guide.
Apply the routine in AkuCRM
Use AkuCRM’s customer records and sales-pipeline workflow to keep the shared context together. Check your plan’s pipeline and user capacity on the pricing page. Before purchase, ask for a demonstration of stage setup, permissions and the particular reports or connected channels you need. This guide describes a management routine; it does not claim every step is automated.
Feature availability and limits depend on your plan and configuration. Ask for a demo to confirm the workflow your business needs.
