Marketing for ERP consultancies in the UK

¶01 The problem generic advice does not fit

Most B2B marketing advice is written for firms that sell a product with a defined price, a predictable sales cycle and a buyer who already knows the category. ERP consultancies sell none of those things, and the mismatch is not a detail.

The advice says: publish frequently, run paid campaigns, track conversion rates, nurture leads through a funnel. Each of those instructions assumes a pipeline that flows in a predictable direction. In an ERP consultancy, the pipeline is mostly referral-led, the sales cycle stretches to match the client's own budget and system decision timeline, and the buyer is usually a technical or operational leader who has already been burned by a previous implementation and is reading your content to find out whether you understand that, not to be converted.

That does not mean marketing does not matter. It means the marketing that matters looks different from the template, and the template is most of what you will be sold.

¶02 Long cycles and the buyer who is always waiting

An ERP consultancy's sales cycle does not begin when the buyer contacts you. It begins when the buyer's organisation decides something is broken enough to fix. That decision can take months. The conversation you have on the day someone reaches out is the last five percent of a process you were not in the room for.

What that means for marketing is this: the material that influences the decision is the material someone reads before they have a project. Articles that explain what a messy migration actually involves. A website that is clear about which kinds of firm you work with and, just as usefully, which kinds you do not. A search presence that means when a financial controller searches for answers to the problem they have right now, six months before they have a budget, they find you rather than a competitor.

The buyer is also technical. Not always a developer, but always someone who has sat in a system selection meeting, who knows that every vendor promises the integration will be painless and every implementation has at least one moment when nothing works. Hype does not merely fail to land here. It costs credibility. A prospect who reads a page full of transformation language and partner badges and nothing specific about how you work has learned that you probably write marketing like everyone else in the channel. They will keep looking.

The implication is that the most valuable marketing asset an ERP consultancy can publish is specific: the real questions that come up in pre-sales, answered directly. Not thought leadership in the abstract, but the article that a prospect could forward to a sceptical colleague and have it hold up.

¶03 Describing hard work without breaching confidence

ERP implementations involve the kind of access that companies treat as sensitive long after the project ends. The client who had the worst go-live, the one that produced the most useful lessons, is usually also the client most concerned about who knows it. The work you can talk about most freely tends to be the work that was most straightforward, which is precisely the work that is least interesting to a buyer who suspects their situation is complicated.

This is a real constraint, and pretending otherwise is not useful. But the constraint is narrower than most firms treat it. Permission to use a client's name is one thing; the ability to describe a problem type is another. A study that names no one but describes the challenge of migrating a firm whose chart of accounts has been manually overridden for nine years, who acquired a second entity on a different platform three years into the project, and who had no internal IT resource to speak of, is specific enough to be credible without identifying anyone.

The buyer reading that is not checking whether the named client is real. They are asking whether the firm writing it has seen this shape of problem before. The specificity is what signals yes. A case study that says "we delivered a cloud ERP implementation resulting in significant efficiency gains" signals nothing, because anyone can write it, including firms that have never managed a difficult project.

The practical approach is to write from the problem rather than the client, to agree with each client at project close what can be described and at what level of detail, and to treat that agreement as a publishing asset rather than a legal formality. Most clients will permit more than you expect if you ask at the right moment, which is when the project has gone well and they are still pleased with you.

¶04 Referral dependence and the partner tier system

Most ERP consultancies receive most of their work by referral: from existing clients, from the vendor's own channel team, from accountants and other advisors who know the firm. That is not a problem. It is a genuine signal of quality and it is the most efficient pipeline a services firm can have.

The vulnerability is that referrals are invisible when they stop working. A firm that has grown entirely on referrals for five years has no early warning system for a quiet quarter. The referrals slow, the pipeline thins, and by the time the absence is obvious there is a six-month lag before anything new can fill it. The firms that manage this well are the ones that treat marketing as pipeline insurance rather than pipeline replacement: something that keeps them findable between referrals, rather than something that turns on when referrals run dry.

The partner tier system introduces a second layer. SAP, Microsoft Dynamics, NetSuite, Acumatica and most other platforms run formal partner programmes with tiered accreditation: gold, platinum, whatever the current vocabulary is. Those tiers carry real weight inside the vendor channel, where a higher tier often means preferred lead referrals, co-marketing funds, and visibility in the vendor's own directory.

Outside the channel, the weight is less obvious. A buyer who is not already navigating the partner programme does not instinctively know what a Gold partner designation means for their project. Translating that accreditation into language a buyer can use, what it means for staffing, for support, for what the vendor relationship can actually do in a difficult moment, is marketing work. The badge alone does not do it.

Conversely, a firm that is trying to climb a tier needs to demonstrate market activity to the vendor: certified headcount, published content, events attended, pipeline reported. Marketing that is built to serve the vendor's accreditation criteria and marketing that is built to serve the buyer are not the same brief. Both are legitimate. They are just different tasks.

¶05 What differs between ERP ecosystems

SAP, Microsoft Dynamics, NetSuite, Acumatica, Odoo, Sage and their respective ecosystems share the structural marketing problem described above. The sales cycle, the technical buyer, the confidentiality constraint, the referral dependence and the partner tier dynamic are present in all of them, in varying degrees.

What differs is the buyer community, the size of the typical implementation, and how the vendor positions itself.

SAP and Dynamics tend to sit in larger organisations with longer sales cycles, larger procurement committees and a stronger expectation of formal proposals and reference site visits. The content that matters in those ecosystems needs to hold up to technical scrutiny from multiple stakeholders, including people whose job is to find reasons to object.

NetSuite, Acumatica and Odoo tend to sit in the mid-market: faster decisions, fewer stakeholders, a buyer who is often a founder or a CFO rather than a procurement function. The content that works there is more direct and more willing to state a point of view. For the NetSuite-specific version of the provider question, including which kinds of agency do this work in the UK and what they each cost, see the dedicated article on marketing for NetSuite partners.

Sage sits in a different segment again: smaller firms, often with an accountancy practice in the referral chain, where the competitive dynamic is as much about practice management relationships as about inbound marketing. The buyers are less likely to be searching for an ERP consultancy and more likely to be introduced by someone who already knows them.

None of this changes the fundamental approach. But it changes the vocabulary, the examples and the specificity required. A supplier who can do the marketing mechanics without knowing the ERP context will need that context fed to them. A supplier who claims to know every ecosystem equally well should be asked to prove it with something they have published, not something they are proposing.

¶06 What a workable approach looks like

The approach that holds for most ERP consultancies is a narrow, consistent monthly rhythm rather than a campaign. One theme, worked properly, producing a small number of connected pieces from a single research and planning effort. That is achievable in a month where two consultants are on a go-live. Eleven items on a content calendar are not.

The production needs to happen away from the delivery team. The consultancy supplies context, judgement and approval. It does not supply the writing hours, because those are the hours that vanish first when a project goes wrong. An approval round that requires a director to review five documents in a busy fortnight does not happen. One document, one approver, one round, does.

The measurement needs to be real. Search visibility, qualified enquiries and the quality of the material in the pipeline are things that can be tracked and reported honestly. Rankings, lead volumes and specific pipeline values are not things a marketing supplier controls, and any supplier who quotes them as targets is either guessing or hoping you do not check.

Before committing to a supplier or a plan, find out what the current position actually is: what a buyer sees when they search for the kind of work you do, whether the site explains what you offer to someone who has not been referred, whether the content that exists is doing anything measurable. Most of the disappointment in these engagements comes from buying the wrong solution to the wrong diagnosis.

Artifexa is a founder-led Marketing Ops service in Swindon, UK. It is built for referral-led specialist firms, including ERP consultancies, whose senior people are billable and whose marketing has to run without consuming the delivery team. The one published track record in this specific space is Next Layer Consulting, a NetSuite consultancy, where a visibility audit score moved from 80 to 94 in under three weeks. That is a single data point and it is an honest one: it is the measurement available, not a performance guarantee.

The ERP experience at Artifexa is NetSuite, and the rest is reasoned transfer rather than a track record. If that distinction matters for your decision, it should, and it is better to know it now than to find it out later.

The full delivery model and prices, including a free Visibility Review, a priority fix sprint from £750, a one-month Pilot at £3,500, and ongoing Marketing Ops from £3,500 a month, are on the engagement menu. Month one is pay on delivery. There is a written review at month three against a named list of what should exist by then, and if anything on that list is missing, you stop and months four to six are never invoiced. That commitment is in writing, not a reassurance.