Skip to content
GullySales

ERP software providers · Sales presentation and demo script writing

A demo script that lets the accounts head say yes before the owner does.

Demo script writing for an ERP provider is deciding which screens to show a manufacturer or distributor, in what order, and what to say as each one opens. GullySales writes the running order and the spoken words from your product material and your buyer notes, and your presales team rehearses and delivers them.

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

Realistic editorial illustration of erp software providers at work in India

What sales presentation and demo script writing means

A sales presentation script and a product demo script are written guides that tell a presenter what to say, show and ask at each step of a buyer meeting. GullySales writes the spoken words, the demo path and the answers to likely questions from your product knowledge, and hands over editable scripts your team can rehearse.

Last updated 14 Nov 2026.

For ERP software providers

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

  • “The demo is built for the wrong person”

    Presales builds a demo that thrills the owner with dashboards while the accounts head waits for the screen that shows a purchase invoice posting to the ledger. Nobody objects in the room. The deal simply goes quiet afterwards. A script that names who is in the room and what each person must see settles the order of screens before the session, not during it.

  • “A free custom demo becomes a bargaining tool”

    Prospects ask for a demo on their own items and ledgers, and some use it to bargain with another partner. The script decides how far custom preparation goes. It can use a few of the buyer's real items and one realistic ledger flow, and leave the rest on a standard dataset, so the buyer sees their own business without taking away a free implementation sketch.

  • “The feature tour loses the stores person”

    A demo that opens every menu in turn ends with a buyer who cannot say what was seen. The stores head cares about goods received, issues and stock statements, not the master list of modules. We write the demo around the everyday jobs of the people who will live with the system, and cut screens that do not serve a problem the buyer has named.

  • “Every presenter tells a different story”

    When two presales people and the founder all run the demo, the buyer hears different claims about migration, support and what is included. One script gives every presenter the same order, the same approved answers and the same moment to ask the buyer a question, so a second demo to the same company does not contradict the first.

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. Buyer-moment map

    A short note for each type of ERP buyer you meet, listing who attends, what each person decides and which problem the session must settle. The demo is built from this map, so the product serves the buyer's concern and not the other way round.

    Result: Each attendee type is listed with the one thing the session must show them.

  2. Demo running order and click path

    A step-by-step path through the product: which screen opens, what the presenter says, what the buyer should notice and where the presenter pauses to ask a question. Screens that do not answer a buyer problem are left out and kept in a spare list.

    Result: Your presenter can follow it screen by screen without improvising the order.

  3. Spoken presentation script

    The words for the slides that open and close the session: why the buyer is in the room, how an implementation runs, who leads it and what happens after signing. It is written in short spoken sentences, with cues for where a slide supports the point.

    Result: A presenter can read it aloud in one pass without stumbling over written phrasing.

  4. Script for the accounts head's questions

    A prepared sequence for the part of the session where the accounts head asks about ledgers, closing entries, reports and audit trails. It shows the screens and gives the approved reply to each doubt your presales team has recorded.

    Result: Each recorded accountant question has a screen and an approved reply attached.

  5. Answers to the hard questions

    Replies to the questions presales dreads: why a previous project elsewhere failed, what customisation costs after go-live, what happens at renewal. Each reply is marked with who at your firm approved it, and what the presenter must not claim.

    Result: No answer states a figure or a promise your management has not signed off.

  6. Custom-preparation rule for the demo

    A one-page statement of what presales prepares from the buyer's own data before a demo, what it asks in return and where preparation stops. It is written so a salesperson can send it to a prospect without negotiating each time.

    Result: A salesperson can quote the rule to a prospect and the limit is clear to both sides.

How the result is measured

  • Meetings where the presenter followed the agreed running order
  • Buyer questions raised that the answer sheet already covered
  • Follow-up requests recorded after a presentation or demo

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 script writing for ERP software 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.

Access to a demo environment
A working copy of the product with sample items, ledgers and users. We write the click path against what the screens really do. Without access we write from sheets and recordings, and your presenter finds the mismatches in the live session.
Recordings or notes from past demos
Whatever shows how demos run today and where buyers lost interest or asked questions. They tell us which moments matter. Without them, the order is built from assumptions, and your presales team will correct the first draft screen by screen.
The questions your presales team dreads
A list of the objections that stall deals, such as data migration, failed projects, custom changes and renewal charges. We write replies to the real doubts. If the list is missing we write for common doubts, and the script feels less exact.
A decision on how much custom preparation to give
How many of the buyer's own items and which ledgers presales will load before a demo. It protects your team's time and sets a limit prospects can understand. When it is undecided, every salesperson sets a different limit and the weakest is exploited.
A presenter who will test the script
Someone from presales who reads the draft aloud and tells us where the words do not sound like speech. A script that has not been spoken always has sentences that fail aloud. Their corrections are worth more than any further drafting.

How it works

How the sales presentation and demo script writing 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

    Read your product material and demo recordings

    We read your product sheets, any existing slides and recordings of past demos, and the demo environment if you give access. We list what the product shows well, what it does not show clearly and which claims are made without support.

  2. 2

    Name who is in the room and what they decide

    We write a statement for each buyer type: the owner, the accounts head, the stores or plant head and sometimes the IT contact. It says what each decides and what the session must leave them able to do next. You approve it before the script is built.

  3. 3

    Set the running order

    We outline the sequence of moments for the presentation and the demo, each tied to a problem the buyer has named, and mark where the presenter stops to ask. You approve the outline before any spoken wording is written, because changing order later changes everything.

  4. 4

    Write the spoken script and demo narration

    We draft the words for each slide and each screen in plain sentences. Cues show when to click, when to pause and when to hand a question to the buyer. Every claim is checked against the product as it stands today and not as planned.

  5. 5

    Prepare the answers for the hard questions

    With your presales lead we write replies to the doubts that stall deals: failed projects, customisation costs, support and renewal. Each reply is read by whoever at your firm owns the commitment, and unsupported lines are cut.

  6. 6

    Read the next demos against the starting notes

    After your team has used the script, you share what happened: which screens drew questions, where attention dropped and which buyers moved forward. We read these against the buyer notes recorded at the start and revise the order. Rehearsal and delivery stay with your presenters.

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.

Do you write the slides as well as the script?
No. We write what the presenter says and the order of the session, with cues where a slide supports a point. Slide design and building the deck belong to pitch deck development and presentation design. The script can be written first so the designer works to a settled argument.
Can the script cover a demo on the buyer's own data?
Yes. It names which items and ledger flows are loaded from the buyer and which stay on the standard dataset. That keeps the demo personal without turning it into a free implementation. The preparation rule is written down, so every salesperson applies the same limit to every prospect.
Will you script the answer about a failed implementation elsewhere?
We write the reply from facts your own team supplies: how your projects are led, how data is checked and what the buyer is asked to provide. We do not write a promise nobody can keep. If your implementation head will not approve a statement, it is removed and the presenter is told what not to say.
Is one script enough for all our buyers?
One shared spine, with branches for the main buyer types. A manufacturer, a distributor and a trading firm each care about different screens, so the order shifts while the opening and close stay fixed. We agree the buyer types at the start and write only for those you actually meet.
Do you train the presenters?
No. Training and rehearsal sit with your presales team. We write for speech and ask a presenter to read the draft aloud, because sentences that read well on a page can fail in the mouth. Coaching and observation of live demos fall under sales presentation and demo improvement, if you want that as well.
What do we do when the product changes?
The script lists the product facts each section relies on. When a module or report changes, the list shows which lines to revise. We can rewrite those sections as a separate piece of work. Without that list, a changed screen leaves old words in the presenter's mouth, and buyers notice the mismatch.
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.

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.