ERP and enterprise software implementation partners · Follow up systems
Keep a long ERP evaluation warm without chasing the finance head.
A follow-up system for an ERP partner is the set of agreed next steps after each meeting, demo and proposal during a long evaluation. GullySales designs it so the buyer hears something useful at each touch.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What follow up systems means
A follow-up system is the set routine for calling, messaging or emailing an enquiry more than once, since most buyers do not decide on the first conversation. GullySales sets the number and timing of follow-ups so an undecided buyer keeps hearing from you until they decide either way.
Also for ERP and enterprise software implementation partners
- Lead generation for ERP implementation partners
- CRM 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.
“The evaluation runs for weeks and the partner goes quiet”
Between a demo and a decision, the buyer talks to rivals. A partner who only reappears to ask for news loses ground to one who sends useful material.
“Every follow-up says just checking in”
A message that adds nothing is ignored. A message that carries a reference, a migration plan or an answer to a question asked in the demo moves the deal.
“Silent deals are never closed out”
A proposal without a reply stays open in the pipeline for months. Closing it with a clear message tells the firm and the buyer where things stand.
“After go-live, calls stop”
The project team moves to the next client and the live client hears nothing until a support issue arises.
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 touch plan for each stage
A set of messages for after a first call, a demo, a proposal and a reference check, each carrying something useful.
Result: The buyer receives value at every contact.
Reminders tied to the CRM
Tasks with owners and dates for each open opportunity.
Result: No proposal waits unread for want of a reminder.
A reference-sharing step
A routine for offering a client call at the right moment in the evaluation.
Result: Proof arrives when the committee is deciding.
A close-out message for silent deals
A short note that closes a quiet proposal politely and leaves the door open.
Result: The pipeline shows real deals only.
A post go-live review routine
A scheduled review with each live client and a written note of requests.
Result: Support and module work come from planned contact.
How the result is measured
- Follow-up completion rate
- Average number of follow-ups before close
- Enquiries closed after repeat follow-up
Recorded as a baseline before work starts, so every later report has an honest comparison.
What to capture or send
The moments in a long ERP evaluation where a useful message keeps the deal alive.
- After the discovery meeting
- A note listing what the buyer said about scope, plants and users, and the next step agreed. Let the buyer correct it, which also confirms you listened.
- After the product demo
- Send the answers to the questions you could not settle live, plus the consultant who would lead that area. A buyer waiting on a reply is already comparing.
- Proposal submitted
- A call to ask whether the committee has read it and who still has questions. Write down the objections and answer each in a one-page note.
- Reference offered
- Brief the reference client on what the buyer cares about, then ask the buyer for the questions they want answered. Record what was said.
- Deal gone silent
- A short close-out message that offers to pause and asks for a date to speak again. It gets an answer or releases the deal in your pipeline.
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.
- No one owns each deal in the pipeline, so the follow-up would go out from three people with three versions of the story
- The proposal itself is still unclear on scope, and chasing the buyer would only draw questions you cannot yet answer
How it works
How the follow up systems 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
Measure today's reply time
From your recent enquiries, we set the time each arrived against its first reply, using the call log, chats, form entries and portal panel. We also count the follow-ups each one got.
- 2
Agree targets and the sequence
We set reply targets and the follow-up sequence with your team, based on its real hours and workload.
- 3
Write the templates and first-call questions
The first reply, the quote follow-up and the last attempt are written in your voice and loaded as quick replies. The first-call questions are agreed with your best salesperson.
- 4
Set ownership, tasks and alerts
Named owners, cover for leave and CRM or sheet tasks go live. App alerts, such as IndiaMART's, are switched on for the right phones.
- 5
Track and adjust
Reply time and follow-up completion are reported against the baseline, and the routine is changed where it is not kept. How often you are reported to is agreed in writing.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 2, qualification. The audit comes before it, and sales management keeps it running.
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 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
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.
How often should we follow up?
What should a follow-up contain?
Should the sales head or the consultant follow up?
A buyer says the decision is delayed by the board. What do we send?
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.