ERP software providers · Buyer persona

Write down every person who can approve, block or live with your ERP.

A buyer persona for an ERP provider is a written profile of each person in the buying group, from the owner who signs to the accounts head who tests the system on a real month-end. GullySales interviews your closed and lost deals and turns them into profiles your presales and marketing teams both use.

Tell us what you needor call +91 80958 58589

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 buyer persona means

A buyer persona is a plain description of the kind of customer who actually buys from you. It includes what they search, what worries them and who else they ask before deciding. GullySales builds this from real enquiries and past sales rather than a generic template, then uses it to write every page and advert.

Also for ERP software providers

Sales and marketing for ERP software providers, the overview.

Last updated 5 Oct 2026.

For ERP software providers

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

“The signatory is rarely the sceptic”
The owner or managing partner signs the cheque and enjoys the dashboard demo. The accounts head, the stores in-charge and the external chartered accountant carry the risk of a bad cutover. A persona sheet that covers only the signatory misses the person who quietly stalls the file.
“Each trade buys for a different reason”
A garment exporter wants size and colour variants handled. A pharma distributor worries about batch expiry and returns. A fabricator asks about job work and material issue. One generic profile for manufacturers erases the very detail that makes a prospect feel understood.
“A family business has a second decision-maker”
The next generation joins and pushes for software, while the founder trusts the old ledger. Both belong in the persona, along with the question each asks first, because your follow-up has to satisfy the person who is hesitating, not the one who is keen.
“Past failure shapes the conversation”
Some prospects arrive having abandoned an earlier implementation or a half-used Tally add-on. Their persona should record what went wrong, who got blamed and what they now fear, so your discovery call begins with that history instead of a feature tour.

What we do

What we deliver for ERP software providers.

Every deliverable, what it covers for you, and the result it is there to produce. Nothing here is an extra.

Interviews with won and lost buyers
Structured conversations with customers who signed and prospects who walked away, covering who joined each meeting and what changed their mind.
Result: You can read the real reasons behind your last several decisions.
One profile per role in the buying group
A page each for the owner, the accounts head, the stores or production lead and the external CA, with their goals, worries and favourite questions.
Result: Your team knows what each person needs to hear before a demo.
Trade-specific variations
Short notes that adjust each profile for the industries you implement for, such as distribution, process manufacturing or project work.
Result: A pharma buyer and a fabricator are no longer pitched the same way.
Objection and proof map
A table matching each role's usual objection to the answer, document or reference call that settles it.
Result: Presales picks the right proof for the right person.
Persona-driven page and message briefs
Briefs for your website, emails and WhatsApp messages written from the profiles instead of from the feature list.
Result: New content addresses a named person with a named worry.

Show 2 moreShow fewer

How the result is measured

Enquiry match to persona
Conversion rate by persona
Content aligned to persona

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

Read the full B2B and B2C buyer persona development page

Who is asking

The people in an ERP buying group and what each wants to see before agreeing to a demo.

Owner of a family-run factory: Wants to know what happens to the business if the person who set up the system leaves. Asks about support terms, the next generation's comfort and what other factories in the trade did.
Accounts head who will test the system: Asks to run a real month-end and a GST return on sample data before agreeing. Distrusts a demo that shows only a dashboard.
Chartered accountant who advises the owner: Wants to know that the books will still tie to the returns, who maps the ledgers and whether the provider has handled the same trade before.
Stores or plant manager: Wants barcode, batch and stock movement shown on a floor-level flow, and asks how many extra entries a shift will need at first.
IT person with a failed project behind them: Asks what went wrong elsewhere and what you do differently: who owns the scope, how data is cleaned and what happens when a promised report is missing.

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

Not for

It is not the right fit if.

You have not interviewed any buyer, won or lost, and the profiles would be copied from a template
The firm sells to a single trade through one introducer, and the committee never changes

How it works

How the buyer persona 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
Understand the current view
We start with how your team currently describes the customer, since the gap between belief and reality is the finding itself.
2
Audit past enquiries and sales
We look at recent enquiries and closed deals to see who actually bought, not who was assumed to buy.
3
Interview customers and staff
Structured conversations with recent buyers, held as talk about the last purchase and not a questionnaire. We ask what happened before they called, who else was involved and what they compared. Customers agree before we contact them, and their answers are reported without names.
4
Build the personas
Findings are written into short, usable persona documents rather than a long report.
5
Apply to your marketing
We show where each persona should change a page, an ad or a script you already have. The sales team reads the drafts and says which ring true. A persona they do not recognise is rewritten.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 0, foundation. 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.

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.

Tell us what you need

How do we build personas without inventing them?

Start from your own deals. Interview customers and lost prospects, read your CRM notes and call recordings where consent exists, and write only what repeated conversations support. Anything you cannot trace to a real deal stays out of the profile.

Should we write a persona for the external CA?

Yes, if the CA influences the choice. They rarely use the software daily, but they review its reports and may recommend a rival. Record what reassures them, such as clean exports, audit trails and familiar return formats.

Do we need a separate persona for each industry?

Keep one core profile per role and add a short trade note for each industry you serve. That keeps the work manageable while still reflecting how a batch-tracked pharma buyer differs from a job-work manufacturer.

What do we do when a persona does not match a real buyer?

Change the persona. A real buyer who surprises you is the best evidence you have, so note the surprise in the CRM, tell presales and rewrite that profile. A persona that never changes has stopped being used.

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.

What if we are not happy with the work?

Tell us and the plan changes. Everything is reported against the baseline, so a number that is not moving is visible to both sides. The term is in your written scope, and the refund and cancellation policy sets out the rest.

From the blog