Skip to content
GullySales

ERP software providers · Sales presentation and demo improvement

The owner called the ERP demo good, and the accounts team asked for another.

Sales presentation and demo improvement for an ERP provider is a review and rebuild of how presales and sales show the system, whether on a screen share or in the buyer's office. GullySales compares recent demos with what each buyer asked, then rewrites the running order, demo scripts and pre-demo checks around the buyer's problem.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

An assessor observes trainees practising a buyer conversation

What sales presentation and demo improvement means

Sales presentation and demo improvement is a review and rebuild of how your team presents and demonstrates in front of buyers, whether on a site visit, a screen share or a showroom floor. GullySales reads your recent decks and demos against what each buyer asked, then rewrites the structure, scripts and checks around the buyer's problem.

Last updated 14 Nov 2026.

For ERP software providers

Where it usually goes wrong, and what we would do.

  • “The demo walks the module menu”

    Sales, purchase, inventory, accounts, reports: the presenter moves through the product in the order it was built. The buyer came to see how a stock mismatch or a GST reconciliation gets resolved, and finds it near the end, if at all.

  • “One demo for three audiences”

    The owner wants a dashboard, the accounts head wants entries and closing, the stores person wants goods receipt and issue. A single presentation pleases the owner and leaves the others with doubts. Separate segments or sessions, each opened with that person's own problem, prevent the second demo request.

  • “The free custom demo turns into a bargaining tool”

    Presales spends days loading the prospect's items and ledgers, and the buyer shows the result to another partner. A scoped demo, agreed in advance with a sample of the buyer's data and named attendees, protects the effort and still feels personal.

  • “The sample company breaks in front of the buyer”

    The login has expired, the demo data was left in a half-finished state from the last session, or the screen share lags. A buyer evaluating a system that must run the books for years reads every glitch as a warning about support.

What we do

What we deliver for ERP software providers.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Review of recent demos against buyer enquiries

    We set the buyer's own words from the enquiry or call notes beside what your team showed, and mark where the demo parted from the question.

    Result: A marked-up record of recent demos showing where each missed the buyer's problem.

  2. Running order that opens with the buyer's problem

    A structure for the demo that starts with the situation the buyer described and shows the modules only as they solve it.

    Result: Each demo begins from a stated buyer problem.

  3. Demo scripts by buyer role

    Separate scripts for the owner, the accounts head, the stores or plant head and the external accountant, covering what to show and what to ask.

    Result: Presales has a script for each person likely to be in the room.

  4. Demo data set for each trade

    A clean sample company for the trades you sell to, such as garment makers or distributors, with a reset routine after every session.

    Result: Every demo starts from a known, tidy state.

  5. Scoped custom demo rule

    A written rule for when a customised demo is offered, what the buyer provides, who attends and what happens afterwards.

    Result: Presales effort is spent on buyers who have agreed the scope.

  6. Pre-demo check and follow-up recap

    A short checklist for access, connection and data before the call, and a recap note sent after, listing the buyer's questions and the answers.

    Result: Both the checklist and the recap exist for every demo.

How the result is measured

  • Demos and presentations reviewed against the buyer's questions
  • Buyer questions answered during the demo
  • Equipment and sample checks completed before meetings

Recorded as a baseline before work starts, so every later report has an honest comparison.

Who it is for

This is written for these ERP software providers.

  • ERP implementation partners for SAP Business One, Odoo or Microsoft Dynamics
  • Tally partners selling add-ons and customisation
  • Zoho partners and implementation consultants
  • Industry-specific ERP product companies
  • ERP providers for pharma and retail distribution
  • Manufacturing ERP and MRP software vendors
  • Construction and project ERP providers
  • Cloud ERP and SaaS accounting providers for small businesses

Before you decide

Agree the work. Know how to judge it.

Sales presentation and demo improvement for ERP providers: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

Bring questions from sales calls and examples of objections that delay a decision. Choose a subject expert who can check the substance, and identify evidence that can be published.

Make the scope clear

Agree the reader, buying question, format, and distribution route for each piece. Set the approval process and distinguish new research from rewriting material you already have.

Check the work in use

Ask a colleague to use the draft in a real buyer conversation. It should answer the question, support its claims, and make the next step clear without requiring a sales pitch to explain it.

Know when to change course

If the same unanswered question appears in several articles, improve the strongest page before commissioning another. More words are not a substitute for missing evidence.

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 ERP software providers. Anything missing is noted in the written scope, with who will supply it.

Recordings or notes of recent demos
Recordings are best, but notes by the presales lead will do. We cannot judge the demo from the deck alone. If no demo has been recorded, we ask to sit in on two before any rewrite. Bring the demos that went well along with the ones that stalled, because the contrast between the two teaches more than either alone.
The original enquiries behind each demo
The comparison needs the buyer's first message or call notes. Pull the email, the form entry or the CRM note for each demo. Without them we compare the demo with what the salesperson remembers, which changes the result.
A demo environment you can reset
Rehearsal needs a system you can restore to a clean state. Tell us whether your demo instance can be refreshed and who does it. If resetting is difficult, the data set work is delayed until the environment is fixed.
A consultant for each trade's data
The data for a pharma distributor must look right to one. Name a consultant who has worked with each trade and can fill the sample company. Without them, the data sets are generic and the demo loses what makes it fit. If two trades share a consultant, we start with the trade that has the larger open pipeline and add the other afterwards.
A decision on the custom demo rule
Say when a buyer may receive a customised demo, who approves it and what the buyer must supply first. Without a rule, we draft one for your approval, and the free request will continue to be handled case by case.

How it works

How the sales presentation and demo improvement 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. 1

    Gather recordings and slides from recent demos

    We ask for the recordings, slide decks and notes of the last eight to ten demos, along with the enquiry that led to each. If recordings do not exist, the presales lead walks us through the demo from memory. We watch or read them as the buyer's accountant would. Nothing is judged yet; the aim is to see what the buyer was shown. Where a demo ran as a screen share, we also note whether the buyer's accountant was on the call or only the owner.

  2. 2

    Set each demo against the enquiry

    For each demo we place the buyer's original question beside the first ten minutes of what was shown. We mark where the demo started with the module menu, where it answered the question and where it never did. The presales lead and the sales head review the table with us, and disagree with it where they must.

  3. 3

    Rewrite the running order around the problem

    The new structure begins with the buyer's problem in their words, shows the shortest path through the system that solves it, and keeps modules the buyer did not ask about for the end. We write scripts for the owner, the accounts head and the stores person. The presales lead rehearses the first one and corrects the language. The accounts head's script, for instance, opens on a month-end close and not on the dashboard.

  4. 4

    Build the demo data for each trade

    A sample company that breaks in front of a buyer costs the deal. With a consultant we prepare a data set for each trade you sell to, with the items, price lists, party names and opening stock a buyer in that trade recognises. We run each path once before it is used. You decide which trades earn a data set first. Each set is stored with a note of the reset steps, so a second consultant can restore it on the morning of a demo.

  5. 5

    Rehearse and record the first new demos

    Presales and a salesperson give the new demo to us as if we were the buyer, and we record it. We stop at each place a buyer might interrupt. The pre-demo checklist grows from what went wrong: login tested, data reset, questions confirmed the day before. You agree which checks are mandatory.

  6. 6

    Start the feedback form and read the first results

    After each live demo the salesperson and the buyer's contact answer the same short form: was the problem understood, what was missing, what should the next meeting cover. We read the forms with you against the earlier pattern of repeat demos and custom requests, and decide which part of the script to change.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.

  1. 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.

  2. 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.

  3. 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.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

We already have a standard presentation. Why change it?
A standard presentation is a good start. We look at whether it opens with the product or the buyer's problem, and whether it works for the accounts head as well as the owner. The fix may be the order, not new slides.
Do you build the demo environment itself?
We design the demo data set, the script and the reset routine. Your presales team loads it into your product, since only they know its settings. We do not alter your software.
Can this stop buyers asking for free customised demos?
It cannot stop the request. It gives you a written scope so that the effort goes to buyers who have agreed to provide data and bring the right people, which changes who asks and how seriously.
Will the new demo be shorter?
Likely yes, since it stops covering modules the buyer did not ask about, but length is not the measure. The test is whether the buyer's own problem is shown working before the meeting ends. Some demos run longer because the buyer wants to try a second problem. We set the structure; you and the presales lead decide how long to spend with each buyer. A short test settles it: ask three recent buyers what they remembered from the presentation. If the answers are about the company and not their problem, the deck is the first thing to change.
Do we need to record demos with the buyer's consent?
Yes, ask first and say what the recording is for. Some buyers will agree, and some will not want their data on a recording at all. Where they refuse, your presales lead writes notes instead. Check with your own adviser how recordings should be stored and who may see them, and never keep a recording that shows a buyer's real ledgers.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.
What do you need from us?
Your brief, and a conversation. After that, access to whatever this work touches, such as your website, your accounts or your enquiry record, and time with the people who handle your enquiries.

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.