Business process consultants · CRM
Keep every enquiry, scope and partner introduction where the next step is visible.
A CRM for a process consultancy records each enquiry against the flow it concerned, the role of the enquirer and the step that comes next. GullySales works on a layout that fits how you sell and on filling it from the enquiries you already hold.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Also for business process consultants
- Lead generation for business process consultants
- Follow-up systems for business process consultants
- SEO for business process consultants
- Social media marketing for business process consultants
- Content marketing for business process consultants
- Buyer persona for business process consultants
- WhatsApp marketing for business process consultants
- Digital marketing for business process consultants
Sales and marketing for business process consultants, the overview.
Last updated 14 Nov 2026.
For business process consultants
Where it usually goes wrong, and what we would do.
“The sales cycle has long gaps”
An owner enquires, goes quiet while the quarter closes, then calls again. Without a record of the flow discussed and the question left open, the second call starts from zero and the buyer notices.
“Each enquiry has more than one person”
The owner raises it, the finance head reviews it and the ERP partner has a view. A record that holds only one name loses the other two, and the proposal goes out without answering the person who objects.
“Partner referrals need their own trail”
An accountant or software reseller who sends you a client expects to hear what happened. If the referral is not logged against the partner, the next introduction depends on memory and the partner stops sending them.
“A process consultant should not run on a messy sheet”
Selling the idea of written, owned procedures while your own pipeline sits in chat messages undermines the pitch. Your own workflow is the first sample a careful buyer may ask about.
What we do
What we deliver for business process consultants.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A pipeline built for scoped projects
Stages from enquiry to first meeting, scope, proposal, decision and kick-off, each with a clear exit.
Result: Every enquiry sits at a named step.
Fields for flow, role and source
Plain fields recording the flow concerned, who enquired and which route brought them.
Result: You can sort the pipeline by flow or by partner.
A partner view
A list of referring accountants, resellers and quality consultants, with each introduction and its outcome.
Result: You can report back to a partner in one message.
Next-step discipline
A rule that no record is left without a dated next action.
Result: Nothing sits without an owner or a date.
Import of existing enquiries
Past enquiries moved from sheets, email and chats into the CRM.
Result: The first day starts with a full pipeline, not an empty one.
A tool recommendation
A note on whether a simple spreadsheet, a low-cost CRM or a larger tool fits the size of the practice.
Result: You choose software against need, not a sales demo.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
The fields a process consultancy needs on every enquiry and scoped project.
- Flow the enquiry is about
- Picked by whoever takes the first call. Lets you see which flows bring enquiries and which you win.
- Role of each person on the enquiry
- Added as new people join the conversation. A finance head and an owner on the same enquiry want different things.
- Source and introducing partner
- Entered at the first contact. Shows which software and accounting partners send work, and which need a note.
- Scope sent and what it covers
- Attached by the consultant who wrote it. Prevents the next call from re-explaining scope the owner already has.
- Next step and the date it is due
- Written by whoever last spoke to the owner. In a long sales cycle this is the field that keeps a quiet enquiry visible.
- Reason for a lost or parked enquiry
- Picked from a short list plus a free line. Shows whether you lose on scope, on fee or to a software vendor.
Who it is for
This is written for these business process consultants.
- Trading and distribution firms with order, dispatch and billing handovers
- Small manufacturers with job cards, purchase and stores
- Hospitals and clinics with admission, billing and insurance claims flows
- Educational institutions with admissions, fee collection and records
- Logistics and transport operators with booking, trip and payment cycles
- Real estate and construction firms with approvals, billing and vendor payments
- Service companies with ticketing, field visits and invoicing
- Companies preparing for an ERP, an audit or a funding round
Before you decide
When this may not be the right fit.
- You have only a few live enquiries and the practice head remembers each one without a record.
- No one has been asked to write the next step after a call, and the tool would be filled once and then left.
Before you decide
Agree the work. Know how to judge it.
CRM for business process consultants: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from business process consultants. Anything missing is noted in the written scope, with who will supply it.
- Every open enquiry and proposal
- The record should start with live work. Gather open enquiries, proposals sent and projects awaiting approval from email, sheets and notes. A pile of forwards is acceptable. Missing items will not appear and the pipeline will look smaller than it is.
- A list of referring partners
- ERP and accounting partners are a source of enquiries, and the CRM should track them. Give us their names, firms and the enquiries they sent. If you do not track them, say so, and we start the list from the enquiries you can recall.
- A decision on who else sees the record
- Only you can say whether colleagues or associates may see proposals and rates. A short list by name is enough. Without a decision, we limit the record to you and add people one at a time.
- Your habits for notes after a call
- The record works if notes are entered when a call ends. Tell us how you take notes now, on paper, on a phone or in email. We shape the entry to fit. If you resist entry, we reduce it to three fields.
- A budget for software, if any
- Free sheets or low-cost tools may do. Say what you are willing to pay. If no budget is set, we recommend a spreadsheet design and hold the paid tool until the pipeline needs it.
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Trace one project from enquiry to invoice
We take a recent project and trace it from the first email through scoping, proposal, approval and invoice, asking who touched it and where notes were kept. You supply the emails, the proposal files and any notes from the scoping call, and tell us who at the client made the decision. The trace shows the gaps, such as a proposal sent by one person and chased by none, a call note kept only in a notebook, or a partner who introduced the enquiry and never heard what became of it.
- 2
Define the pipeline for scoped projects
We write the stages a consultancy actually has: enquiry, scoping call, proposal sent, clarification, approval, project start. You rename them to your words. Each stage gets one next action, so no enquiry sits without a step, and a stage that waits on the buyer carries the question we are waiting for, written beside the record.
- 3
Add fields for flow, role and source
We add fields for the flow concerned, the role of each person on the enquiry, the source and any partner who introduced it. You cut fields you will not keep. A record with several people on one enquiry is allowed from the start.
- 4
Import the old enquiries into a test copy
We bring your enquiries from email and sheets into a test copy, and you check a dozen records against the originals. Mismatches show where our rules are wrong. We correct them and repeat the import before loading everything.
- 5
Set the partner view and next-step rule
Partners who refer work need their own trail, so we build a view of enquiries by partner. We also agree a rule that every record carries a next step and date. You try the rule for a few enquiries and tell us what annoyed you, whether a field was missing, a date was awkward to enter or a stage name did not match how you speak of the work.
- 6
Switch over and compare the open enquiries
On the switch we retire the old sheet and compare the open enquiries and proposals in the CRM with the counts taken at the start. You trace any gap to a person or a date. Ownership of the record is written down.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Do we need a CRM with so few clients?
Which CRM should a consultancy use?
Will it take long to set up?
How do we move our old enquiries into the CRM?
How many enquiries justify a CRM?
What happens to the CRM if an associate leaves?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for business process consultants
Related work to consider.
Closest to this: leads and follow-up
Also for business process consultants
Or start from the overview: sales and marketing for business process consultants.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.