ERP and enterprise software implementation partners · CRM
Keep every proposal, committee member and vendor lead in one place.
A CRM for an ERP partner holds opportunities, the people on each buying committee, the vendor who referred the deal and the documents sent. GullySales sets up the stages and fields and trains the team to keep them current.
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 ERP and enterprise software implementation partners
- Lead generation for ERP implementation partners
- Follow-up systems for ERP implementation partners
- SEO for ERP implementation partners
- Social media marketing for ERP implementation partners
- Content marketing for ERP implementation partners
- Buyer persona for ERP implementation partners
- WhatsApp marketing for ERP implementation partners
- Digital marketing for ERP implementation partners
Sales and marketing for ERP and enterprise software implementation partners, the overview.
Last updated 22 Oct 2026.
For ERP and enterprise software implementation partners
Where it usually goes wrong, and what we would do.
“Opportunities sit in the founder's inbox”
A proposal sent from a partner's mailbox is invisible to the rest of the firm. When the partner is on a project, no one follows up.
“The committee is tracked by memory”
A deal has a finance head, an IT head and an owner. The CRM should hold each name, role and last conversation.
“Vendor referrals go untagged”
If the source is not recorded, the firm cannot tell which vendor relationship deserves more effort.
“Support and renewal dates live in a spreadsheet”
Annual support contracts and upgrade windows need reminders, or the client drifts to another partner.
What we do
What we deliver for ERP and enterprise software implementation partners.
Every deliverable, what it covers for you, and the result it is there to produce. Nothing here is an extra.
A deal pipeline with the firm's real stages
Stages from first contact to shortlist, demo, proposal, reference check, negotiation and signature.
Result: The partners see where each deal stands.
Contact roles and committee fields
Fields for decision role, stance and last conversation, linked to each opportunity.
Result: Nothing hangs on one contact.
Source and vendor tracking
Fields recording the vendor, the adviser or the event behind each opportunity.
Result: The best channels are visible.
Document and reference log
Proposals, reference requests and tender documents attached to each deal.
Result: The next proposal begins from the last.
Support and renewal reminders
Dates and owners for each support contract and each client's next module.
Result: Live clients are followed up on purpose.
Team training
A session for consultants and sales staff on what to log and when.
Result: The CRM holds current data.
Tender and vendor-registration tracker
Each tender or vendor-registration form with its owner, the documents required, the submission date and the status, so the firm does not lose a deal because a certificate lapsed or a form went unsigned.
Result: Paperwork deadlines are visible to the team.
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
What an ERP partner should record on every opportunity and every client after go-live.
- System under evaluation
- The sales lead picks it from a list at the first call. It lets you see which products draw the most opportunities and which consultants to bring into the demo.
- Committee roles and stance
- The sales lead enters each person's role and whether they are a supporter, neutral or doubtful. It shows whose objection to prepare for before the next meeting.
- Referring vendor or adviser
- Filled when the opportunity is created. It shows which vendor account managers and accountants send projects that close, and which only send names.
- Documents sent and date
- The sales lead logs each proposal version, scope note and reference shared. It stops two people sending different scopes to the same buyer.
- Registration and approval status
- The bid manager records vendor registration, tender deadlines and pending forms. It stops a bid being lost to a missing document.
- Support contract and renewal date
- The delivery lead enters it at go-live. It lets the account owner raise upgrade and extra-user work before the contract ends.
Who it is for
This is written for these ERP and enterprise software implementation partners.
- SAP Business One and S/4HANA partners
- Microsoft Dynamics 365 and Business Central partners
- Oracle NetSuite and Oracle Fusion partners
- Odoo, ERPNext and open-source ERP implementers
- Zoho One and Zoho Creator implementation partners
- Industry-specific ERP firms for manufacturing, pharma or distribution
- HRMS, payroll and finance system implementers
- Supply chain, warehouse and procurement software partners
- Data migration and integration specialists
Not for
It is not the right fit if.
- The founders still run deals from their inbox and will not log them, so a CRM would stay empty
- You have not yet defined the stages of your own sale, and the system would carry the vendor's template instead
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
Map the sales process
We sit with the people who sell and write down how a deal moves from enquiry to payment, including where it stalls.
- 2
Agree stages, fields and owners
Each stage gets a name your team already uses and a proof that the deal has left it. We agree which fields are required at which stage, and who may change what.
- 3
Build on a copy
Pipeline, fields and views are built on a trial copy where the CRM offers one, or in a separate pipeline where the plan allows. Live work stays untouched.
- 4
Connect channels, then switch on automations
Channels are connected first. Each automation is then switched on separately, so a misfiring rule is easy to find.
- 5
Test with real deals
The people who will use the CRM run open deals through it. Gaps are fixed before the whole team switches over.
- 6
Switch over and trim
Once real use shows which fields stay empty and which stages nobody uses, those are cut and the handover record is updated.
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.
Which CRM should we use?
Should consultants log in as well?
How do we avoid a messy CRM?
Should the CRM hold client project data?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
What do you need from us?
What if we are not happy with the work?
More for ERP and enterprise software implementation partners
Everything else we would do for you.
Closest to this: leads and follow-up
Also for ERP and enterprise software implementation partners
Or start from the overview: sales and marketing for ERP and enterprise software implementation partners.
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.