Where the Sales Record Starts: From Enquiry to Quotation
In most small sales teams the enquiry lives in a notebook, the deal lives in somebody’s head, and the first real record is the quotation. AWRA now starts earlier — leads, a staged pipeline with weighted value, an activity log — and hands a won deal to a quotation. Where the seam falls now, what it gives back, and when a second system still earns its place.
Ask a sales manager what they need and they will describe a pipeline: enquiries at the top, deals moving through stages, a forecast at the bottom, and a nagging list of people who were supposed to be called back on Tuesday. Ask most operations systems what they hold and the answer starts later — at the quotation, when the deal is real enough to have a price and a document. The space between those two answers is where a great many software evaluations go wrong, and for a long time it was a space this product left empty too.
It no longer is. The record now starts at the enquiry: a lead with a source and an owner, a deal on a pipeline stage with a probability, a log of the calls and meetings against it, and a won deal that opens a quotation for its customer. This piece is about where that pipeline ends, where the transaction record begins, and why the two are still kept as different things.
CRM vocabulary, translated
What the words mean, and where each thing lives here
CRM term Here
Lead Built — the lead record
An unqualified enquiry — a name, a company, a phone number and an interest — with its source (walk-in, referral, WhatsApp, website and the rest), a status from new through contacted and qualified to converted or disqualified, an owner and an estimated value. A qualified lead converts into a customer and, if you want one, a deal.
Opportunity / deal Built — the deal record
A qualified chance with an amount, a stage, a probability, an expected close date and an owner. A deal that passes its expected close date while still open is marked overdue on the board and on the record.
Pipeline stage Built, and configurable
New, Qualified, Proposal, Negotiation, Won and Lost by default, each carrying a probability. Your organization renames, reorders and adds stages to match how it actually sells. Deals move across a drag-and-drop board.
Activity / next action Built — the activity log
Calls, emails, meetings, notes and tasks recorded against a lead or a deal, each with an optional due date. One that is past due shows as overdue on the record it belongs to.
Quotation Built — where the deal hands over
A real document with items, prices, discounts and a validity period. A won deal opens a new quotation for its customer, which is the moment the pipeline’s opinion becomes a priced offer.
Account Built — the customer record
Contacts, addresses, terms, credit limit, history. Converting a lead creates it, so the customer’s record begins with the enquiry rather than with the first invoice.
Forecast Weighted pipeline
Open value and weighted value — each deal’s amount times its probability — per stage and in total. Alongside it, accurate historic reporting on what was quoted, invoiced and collected.
One thing to keep apart while evaluating: the product also contains deals and attribution for AWRA’s own partner and reseller programme. That belongs to the partner portal. Your organization’s selling lives under CRM.
Where the seam falls now
Winning the work versus doing the work
In the pipeline
Relationship work — judgement, memory and persistence, now with somewhere to live
- Enquiries recorded as leads, each with a source and an owner.
- Qualification as a lead status — contacted, qualified, disqualified.
- Deals on stages, each with a probability and an expected close date.
- Calls, emails, meetings, notes and tasks logged against the lead or deal, with due dates.
- A reason recorded whenever a deal is moved to Lost.
From the quote onward
Transaction and fulfilment work — structured, costed, auditable
- Quotations with items, prices, discount control and validity.
- Conversion into an order and an invoice, with stock committed and costed.
- Credit limits checked against real exposure before the invoice stands.
- Delivery, receipt, payment, ageing and collections.
- Margin per line, per customer and per period, from actual cost.
The two halves still have different shapes, which is why they stay separate records. The left is opinion — a stage is a judgement and a probability is a guess — so moving a deal to Won posts nothing to the ledger and commits no stock. The right is documents, money and stock, where being approximately right is being wrong. The quotation is where one becomes the other.
What the pipeline gives back
A sales team with no pipeline loses four specific things. It is worth naming them, because each now has a place to be recorded — and it is worth being exact about how far each one goes.
- The follow-up has a due date. A call logged as a task against the deal carries the date it is owed, and goes overdue on that deal when it slips. Somebody still has to open the board each morning to see it.
- The conversion rate has a denominator. Every enquiry is a lead with a status and a source, so “how many people asked us” is a count rather than a guess, filtered by source and owner on the lead list.
- Loss reasons are captured. Moving a deal to Lost asks why, and will not move it without an answer, so a quote that went quiet and one lost on price stop looking identical.
- There is a forward view. Open and weighted value per stage turn “what does next quarter look like” into a figure the whole team reads the same way, rather than an opinion held by whoever knows the customers.
Weighted value is a forecast only as good as the probabilities on the stages, and those are your organization’s to set. A Proposal stage at 40% is a claim about your own history. Check it against the deals you actually won before you plan cash around it.
The old workarounds, retired
Before the pipeline existed, the usual move was to model deals as projects or tasks, because they have owners, statuses, due dates and boards. That always worked poorly — a project carries costing, time entries and billing that a prospect has no business having, and a board of “deals” among live projects made both lists harder to read. With a deal record of its own, there is no reason left to do it, and teams that did should move those pursuits across and close the pseudo-projects.
Best for most
The pipeline here, from the first enquiry
Record every enquiry as a lead, convert the real ones into deals, log the next action with a date, and let a won deal open the quotation. One system, one customer record, and the pipeline sits next to the stock and the credit limit it will eventually draw on.
If your selling lives in the inbox
A dedicated CRM alongside, joined at the customer
Right when email sequences, inbox sync and campaign tracking are the daily work of several full-time sellers. Accept the join is manual — a won deal becomes a quotation somebody raises here — and do not attempt a two-way sync you will spend a year maintaining.
Retire
Projects pressed into service as opportunities
This was a defensible stopgap when there was no deal record. Move those pursuits onto the pipeline and keep projects for delivery, where their costing and time entries belong.
Avoid
Quotations as the pipeline
Raising speculative quotations to represent deals is still the most corrosive improvisation: it pollutes your quotation conversion figures, your discount analysis and your document numbering with things that were never real offers. A deal is what holds a maybe; a quotation is a priced offer somebody actually made.
The one habit worth adopting today
Log every enquiry as a lead, including the ones you would disqualify in ten seconds. Those quick disqualifications are the denominator. Twelve weeks of leads against twelve weeks of won deals tells you whether you have a demand problem or a closing problem, which is the most consequential thing a small sales operation can know about itself — and the leads you skip because they were obviously wrong are exactly the ones that make the ratio honest.
What AWRA OpsHub does today
- Leads with source, status, owner and estimated value, converting into a customer and a deal.
- Deals on configurable pipeline stages — New, Qualified, Proposal, Negotiation, Won and Lost by default — with probability, expected close date and weighted value.
- A drag-and-drop pipeline board with open and weighted totals per stage, on the web and in the mobile app.
- An activity log of calls, emails, meetings, notes and tasks against each lead and deal, with due dates marked overdue.
- A required loss reason when a deal is moved to Lost.
- A won deal opening a quotation for its customer, and quotations with items, price lists, discount control and validity periods from there.
- Accurate historic reporting on quoted, invoiced and collected value, by period and by customer.
More we can add to your workspace
- Lead scoring — ranking leads by fit and engagement so the likeliest ones are worked first.
- Forecasting beyond the weighted pipeline — win rates learned from your own history, close-date slippage and a forecast by period.
- Reminders for CRM activities — the overdue call sent to its owner by email or in the bell, rather than waiting on the record to be opened.
- Email sync — messages to and from a lead filed onto its record automatically.
- Marketing campaigns, sequences and templated outreach to a list of leads.
- A conversion-rate report by source and owner, built on the lead statuses that are already recorded.
- A stored link from a won deal to the quotation raised from it, so deal-to-quote conversion reports itself.
If your selling is short and transactional — a customer asks, you quote, they buy — most of the pipeline is optional for you, and a lead per enquiry is enough. If your cycle runs over months with several people involved, the deal, its stage and its next action are the parts that stop work being forgotten.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsOur take
The record now starts at the enquiry: leads, deals on stages with a probability, an activity log, a required loss reason and a weighted pipeline, handing a won deal to a quotation. That covers what a small or mid-sized sales team actually loses without a CRM. What it leaves to you is discipline — opening the board each morning, and setting stage probabilities that match your real history. If your sellers live in their inbox and run sequences, a dedicated CRM alongside is still the right answer, joined at the customer. Whatever you do, do not raise speculative quotations to represent deals: that is what the deal record is for.
From the first enquiry to the paid invoice
Leads, a staged pipeline with weighted value, an activity log, then quotations, discount control, credit-checked invoicing, collections and true margin — one customer record from enquiry to payment.
See how sales worksFrequently asked questions
Is there a CRM or sales pipeline in AWRA OpsHub?
Yes. There are leads with a source, status and owner; deals on configurable pipeline stages (New, Qualified, Proposal, Negotiation, Won and Lost by default) with a probability and weighted value; a drag-and-drop pipeline board; and an activity log of calls, emails, meetings, notes and tasks. A lead converts into a customer, and a won deal opens a quotation for that customer. It works on the web and in the mobile app. The deals in the partner and reseller programme are a separate thing for AWRA’s partners.
What does the weighted pipeline actually tell us?
Each open deal’s amount multiplied by its probability, summed per stage and in total, alongside the plain open value. It is a forward view rather than a learned forecast: the probabilities are the ones your organization sets on each stage (or overrides on a deal), so it is as accurate as those numbers are. Check them against the deals you actually won.
Do we still need to use projects or tasks as a sales pipeline?
No. That was a workaround from before the deal record existed, and it always carried costing, time entries and billing a prospect should not have. Move those pursuits onto the pipeline and keep projects for delivery.
Should we raise quotations for every deal we are chasing?
No — and now there is no reason to. Speculative quotations pollute your conversion figures, your discount analysis and your document numbering with offers that were never real. A deal holds the maybe; raise the quotation from the deal when there is a real priced offer to make.
Does the CRM remind us about follow-ups or score our leads?
An activity carries a due date and shows as overdue on its lead or deal, and a deal past its expected close date is flagged on the board. A reminder that is sent to the owner, lead scoring, forecasting beyond the weighted pipeline, email sync and marketing campaigns are all things we can add to your workspace.
When do we still need a separate CRM?
When several full-time sellers work mainly from their inbox — sequences, email sync and campaign tracking are the daily work. Run it alongside and join at the customer: a won deal becomes a quotation somebody raises here. Do not attempt a two-way sync; you will spend a year maintaining it for very little.
