Where the Sales Record Starts: The CRM Boundary
The earliest sales record here is a quotation. Everything before it — the enquiry, the follow-up, the deal you are chasing — has no home, and that is a boundary rather than an oversight. Where it sits, what it costs you, and when you genuinely need a second system.
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 an operations system what it holds 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, in both directions.
So this piece is about a boundary rather than a feature. It exists, it is defensible, and it costs you something specific.
CRM vocabulary, translated
What the words mean, and where each thing lives here
CRM term Here
Lead Nowhere
An unqualified enquiry — a name and a phone number and an interest. There is no record type for this. It lives in a notebook, a WhatsApp thread or a spreadsheet, and it does so in almost every business this size regardless of what software they bought.
Opportunity / deal Nowhere
A qualified chance with a value, a stage and an expected close date. No entity, therefore no stages, no pipeline view and no weighted forecast.
Pipeline stage Nowhere
The columns a deal moves through. Nothing models this for sales. Worth noting the near-miss: projects and tasks have statuses and boards, and people do sometimes press them into service — see the honest assessment further down.
Activity / next action Partly
No sales activity log. Tasks exist and can be assigned with due dates, which covers "call this person Tuesday" if you are willing to run it outside a sales context.
Quotation Built, and this is the entry point
A real document with items, prices, discounts and a validity period. The first moment a prospective sale becomes a record — which is later than a CRM would start and earlier than an invoice.
Account Built — the customer record
Contacts, addresses, terms, credit limit, history. Strong on the post-sale side, and it begins life when somebody becomes a customer rather than when they become a prospect.
Forecast Historic only
You can report accurately on what has been quoted, invoiced and collected. You cannot forecast from a weighted pipeline, because there is no pipeline to weight.
One thing to ignore while evaluating: the product contains deals, attribution and stages for the partner and reseller programme. That is a different system for a different purpose and it is not a CRM you can use for your own selling. It will show up in a search and it is not the answer.
Where the seam actually falls
Winning the work versus doing the work
Before the quote
Relationship work — unstructured by nature, and the part that is not here
- Enquiries arriving by phone, WhatsApp, walk-in and referral.
- Qualification — is this real, can they pay, do we want it.
- Follow-up cadence and the discipline of calling back when you said you would.
- Competitive intelligence and the reason you lost the last one.
- A forecast built from judgement about deals that have not happened yet.
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 seam is honest because the two halves genuinely have different shapes. The left is judgement, memory and persistence, and its data is soft — a stage is an opinion. The right is documents, money and stock, where being approximately right is being wrong. Systems that try to span both usually end up weak at the half you actually get audited on.
What this costs you, specifically
It is worth being concrete, because "no CRM" sounds abstract until you name the four things you lose. All four are real and none of them are fatal.
- Nothing chases the follow-up. The deal that dies because nobody called back on Tuesday dies invisibly, and it is the single largest silent loss in most small sales teams.
- No conversion rate. You know what you quoted and what you won. You do not know what you were asked for, so the ratio that would tell you whether your problem is lead volume or closing ability is unavailable.
- No loss reasons. A quotation that goes quiet is indistinguishable from one lost on price, and those two require completely different responses.
- No forward view. Reporting here is historic and accurate. A weighted forecast is not available, so "what does next quarter look like" remains an opinion held by whoever knows the customers.
Notice that the first and third are process losses rather than data losses. They are fixable with a habit and a shared sheet. The second and fourth are genuinely unavailable and stay that way until something records enquiries.
The tempting workaround, assessed honestly
The obvious move is to model deals as projects or tasks. They have owners, statuses, due dates, boards and comments. It looks like a pipeline if you squint.
It works, poorly, and it is worth knowing why before you invest three weeks in it. A project is a unit of delivery, so it carries costing, time entries and billing that a prospect has no business having; a board of "deals" sitting among live projects makes both lists harder to read; and nothing links a won deal to the quotation that actually won it, so you maintain the connection by naming convention. For a team tracking a handful of large opportunities that is a reasonable trade. For twenty small deals a week it is worse than a spreadsheet, because the spreadsheet does not pretend to be part of the operational record.
Best for most
A shared sheet for the pipeline, this system from the quotation on
One sheet, six columns — customer, contact, what they want, value, next action, next action date. Sorted by next action date and read every morning. It costs nothing, it is honest about being a list rather than a system, and it fixes the follow-up loss which is the expensive one.
If you have a real sales team
A dedicated CRM alongside, joined at the customer name
Right once you have three or more people whose whole job is selling, or a sales cycle measured in months. 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.
For a few large deals
Projects pressed into service as opportunities
Defensible when you track five or ten significant pursuits, each with real internal work behind it. Keep them visibly separated from delivery projects and expect to maintain the link to quotations by naming convention.
Avoid
Quotations as the pipeline
The most common improvisation and the most corrosive: raising speculative quotations to represent deals. It pollutes your quotation conversion figures, your discount analysis and your document numbering with things that were never real offers, and it destroys the one clean sales metric you actually had.
The one habit worth adopting today
Record the enquiry count. A tally on paper — how many people asked us for something this week — costs nothing and unlocks the conversion rate that the missing pipeline denies you. Twelve weeks of tallies against twelve weeks of quotations 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 thing almost none of them do know.
What AWRA OpsHub does today
- Quotations with items, price lists, discount control and validity periods — the entry point of the record.
- Customer records with contacts, addresses, terms, credit limits and full trading history.
- Tasks with owners and due dates, usable for follow-up if you accept they sit outside a sales context.
- Accurate historic reporting on quoted, invoiced and collected value, by period and by customer.
- Attachments and notes on the records that do exist, so correspondence has somewhere to live from the quotation onward.
More we can add to your workspace
- A lead or enquiry record. The unqualified contact has no home at all.
- An opportunity or deal entity, and therefore no stages, no pipeline board and no weighted forecast.
- A sales activity log — calls, meetings and emails against a prospect are not recorded anywhere.
- A loss reason capture on a quotation that goes nowhere.
- Conversion-rate reporting — the numerator exists today, and the denominator arrives with the pipeline entity.
- An email integration, sequences or templated outreach.
If your sales cycle is short and transactional — a customer asks, you quote, they buy — the pipeline half is worth very little to you and you should not buy a CRM to fill it. If your cycle runs over months with several people involved and a real risk of forgetting, that half is the expensive one, and a second system alongside is a better answer than a workaround inside this one.
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 starts at the quotation, and everything before it — leads, deals, stages, activities, forecast — genuinely does not exist. For short transactional selling that is fine, and the fix is a six-column sheet read every morning plus a tally of enquiries so you can finally calculate a conversion rate. For a real sales team with a months-long cycle, run a proper CRM alongside and join it at the customer, manually, without attempting a sync. Whatever you do, do not raise speculative quotations to represent deals: it destroys the one clean sales metric you have in exchange for a pipeline view that was never worth it.
Strong from the quotation onward
Quotations, discount control, credit-checked invoicing, collections and true margin — with a plain statement that leads, deals, stages and forecasting are outside this system rather than buried in a menu.
See plans & pricingFrequently asked questions
Is there a CRM or sales pipeline in AWRA OpsHub?
No. There is no lead record, no opportunity or deal entity, no stages, no pipeline board, no activity log and no weighted forecast. The earliest sales record is the quotation. The product does contain deals and attribution for the partner and reseller programme, but that is a different system for a different purpose and is not a CRM you can use for your own selling.
What exactly do we lose without a pipeline?
Four things. Nothing chases a follow-up, so deals die invisibly when nobody calls back. There is no conversion rate, because you know what you quoted but not what you were asked for. There are no loss reasons, so a quote that went quiet looks identical to one lost on price. And there is no forward view — reporting is historic and accurate, forecasting is not available. The first and third are fixable with habits; the second and fourth are genuinely unavailable.
Can we use projects or tasks as a sales pipeline?
You can, and it works poorly. Projects carry costing, time entries and billing that a prospect should not have, deals mixed among live projects make both lists harder to read, and nothing links a won deal to the quotation that won it, so you maintain that by naming convention. Reasonable for five or ten large pursuits; worse than a spreadsheet for twenty small deals a week.
Should we just raise quotations for every deal we are chasing?
No — this is the most damaging improvisation available. Speculative quotations pollute your conversion figures, your discount analysis and your document numbering with offers that were never real, which destroys the one clean sales metric you had. Keep the quotation meaning what it says: a priced offer somebody actually made.
When do we actually need a separate CRM?
When three or more people sell full-time, or when the cycle runs over months with a real risk of forgetting who owes whom a call. 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.
What is the cheapest useful thing we can do right now?
Tally enquiries. A mark on paper each time somebody asks you for something, counted weekly. That single number is the missing denominator: twelve weeks of tallies against twelve weeks of quotations tells you whether you have a demand problem or a closing problem, which is the most consequential thing a small sales operation can know and the thing almost none of them do.
