Asset 20 8 2
Does AI recommend your business? Run the free check →

Join 15,000 business owners, marketers and entrepreneurs. The Sunday newsletter you'll be annoyed only arrives once a week.

Write for Us ERP: ERP Blog Guest Post Guidelines

Yes, ERP guest posts are accepted on this blog. The ideal writer is an ERP consultant, implementation lead, finance or operations manager, or systems analyst who can explain one decision about choosing, rolling out or running an ERP system in a small or growing business. We decline vendor promos, feature lists copied from brochures and posts with no rollout experience behind them.

Search for ERP guest post guidelines and much of what comes back isn't an ERP blog at all, so writers end up pitching blind. Most ERP pitches we see read like a vendor's product page. What this blog wants is the view from someone who has lived through a rollout: how a growing company knew it had outgrown spreadsheets and accounting software, what a consultant asks before recommending any system, how a team cleaned its data before the migration rather than after.

My readers are business owners and operators, and many of them are one hire away from needing a single system for stock, orders and finance. They already compare options in my guides to ERP software for small business and NetSuite alternatives. An ERP post has to help them choose and roll out a system without losing a quarter to it.

60-second ERP guest post check

A strong submission can answer yes to all five points:

  • Do you choose, implement or run ERP systems for your own or client businesses
  • Can you explain one decision with the trade offs, not just the features
  • Does your opening answer the reader's question in the first two lines
  • Have you kept vendor promotion and affiliate links out
  • Would an owner of a growing business follow it without a consultant on call

Read the guidelines and submit your guest post.

What we publish

  • Signs a business has outgrown spreadsheets and basic accounting tools
  • Choosing an ERP: the questions to ask before any demo
  • Data clean up and migration lessons from real rollouts
  • Training staff so the new system gets used
  • ERP for manufacturing, wholesale and ecommerce businesses
  • Cloud ERP compared with on premise, for smaller teams
  • Integrations with CRM, ecommerce and payroll tools
  • What goes wrong in year one and how teams recover

If your post could be published on any ERP site with the logo swapped, it is not for us.

What we look for in ERP posts

These are the ERP topics that land, and the version of each that gets turned down.

TopicWhat gets acceptedWhat gets declined
SelectionThe questions you asked and why one system wonA ranked list of vendors with no criteria
ImplementationA rollout you led, with what went wrongA generic project plan template
Data migrationHow you cleaned and moved data, step by stepAdvice to just import everything
TrainingHow you got staff to use the systemTelling readers to read the manual
IntegrationsConnecting ERP to tools a team already usesA promo for one connector

Whatever the topic, the post has to be checkable. These are the rollout facts an ERP editor wants to see, ideally in the pitch itself:

  • The type of business and its rough size
  • Which functions moved into the ERP: stock, orders, finance, or a mix
  • How long the rollout ran, in plain terms
  • What was migrated, and what was deliberately left behind
  • One thing that went wrong, and what the team did about it

Consultants often work under NDA and can't name the client. That's fine. Describe the business by type and size instead (a family wholesaler, a small food manufacturer) and keep every other detail specific. A real rollout with no client name beats a famous name with no detail.

What we don't accept

  • Vendor promos or posts that only mention one product
  • Feature lists copied from a brochure or comparison site
  • Rollout advice from someone who hasn't run a rollout
  • Thin posts under 800 words with no first hand experience
  • Previously published posts republished from another site

Most of these declines have a fix, so here's what to change before you pitch again:

  • Only one product mentioned. Set out the criteria you judged against, name the systems you compared, and say what the winner couldn't do. Naming a vendor is fine when the post explains why it won or lost.
  • Brochure feature lists. Swap the list for the one decision the features fed into, and the trade off you accepted.
  • No rollout behind the advice. Write from the part you did run, whether that's selection, the data move or training, and leave the rest out.
  • Republished posts. Write a new piece on a narrower question from the same project rather than reworking the old one.

A simple test for vendor fairness: if the vendor would happily repost your article on its own blog unchanged, it has no trade offs in it, and it will be declined.

What you get

  • Your article in front of an engaged audience of business owners, marketers and founders
  • One relevant, contextual link back to your own site
  • A byline and the credibility of an established, high-traffic blog
  • Editorial help to make the piece as strong as it can be before it goes live

How to submit

Send your pitch or draft through the contact form. Include the topic, the one specific problem the post solves, and a line on your first-hand experience with it. One idea per pitch works best. You will hear back on whether it is a fit before you write the full draft.

Before you press send, run your pitch past this list:

  • It names the decision the post helps a reader make
  • It states your role in the rollout: buyer, project lead, consultant or user
  • It gives the timeline in plain terms
  • It says what you'd do differently next time
  • The title has no vendor names in it

What a strong ERP pitch looks like

A weak pitch says "I want to write about the top ten ERP systems for businesses." A strong one says "I led the ERP rollout at a small manufacturer, and I want to show the three questions that knocked two vendors out, how we cleaned our product data before go live, and what we'd do differently with training." The first could be written by anyone with a search engine. The second names a type of business, a decision with a cost attached and a lesson another owner can copy, which is exactly what this blog's readers come for.

That's also how an editor reads a pitch. Two questions decide it: does the writer show a decision with a cost on both sides, and could a business owner act on it without hiring a consultant? A pitch that ranks vendors without saying what they were ranked on fails at the first read.

If your angle is data clean up, outline the order you worked in. An editor wants to see a sequence like this, filled in with what you found at each step:

  1. List every record type you're moving: customers, suppliers, items and open orders
  2. Remove duplicates and dead records
  3. Agree one naming rule for items
  4. Load a test batch
  5. Have the people who use the data every day check it
  6. Then do the real move

Worked illustration (invented business and numbers, not a real submission): a 25 person wholesaler moved stock, orders and finance off spreadsheets over six months. It migrated 4,000 item records, left five years of closed orders in the old files, and found in the test batch that the same product carried three different names. A pitch built on that would read: "We cleaned 4,000 product records before go live. Here's the naming rule that fixed our duplicates, and why we left old orders behind." Every number in it is one the editor can ask about.

The angles that get accepted fastest

  • The moment a business needs an ERP and not just better spreadsheets
  • Questions to ask in an ERP demo that vendors don't expect
  • Cleaning your data before migration, not after
  • Getting staff to use a new system in the first month
  • ERP for a small manufacturer: what matters and what doesn't
  • Connecting ERP with ecommerce and CRM without a mess
  • Choosing an implementation partner
  • The year one problems nobody warns you about

To turn an angle into a pitch, write it as a title. A few examples of the shape that works:

  • The three demo questions that knocked two ERP vendors out for us
  • Cleaning product data before go live: the spreadsheet we used
  • Why we kept payroll out of the ERP rollout
  • Month one after go live: how we got the warehouse to scan, not write
  • Choosing an implementation partner: the reference call questions that mattered
  • Cloud or on premise for a team of 15: what we weighed

If you pitch year one problems, tie each one to a real case and the fix: staff working around the system, data that drifted after go live, reports nobody trusts, integrations that break after an update. A list of warnings won't get through; one problem, traced from cause to recovery, will.

If you've only got one strong rollout behind you, pitch the data clean up angle first. It's where step by step detail matters most, and that's detail only someone who did the work can give.

Looking for more places to pitch? The sites that accept guest posts page helps you build a shortlist of blogs in your niche.

Frequently asked questions

Can I write about a specific ERP product?

Yes, when the post explains a decision and its trade offs from real use, including what the product couldn't do. Posts that mention only one product, or read like its product page, are declined.

What if I can't name my client?

Describe the business by type and size and keep the lesson specific. A pitch can be accepted without a client name as long as the rollout detail is real: what moved, how long it took and what went wrong.

Do you accept CRM, accounting or business software guest posts too?

Yes, but CRM, accounting and wider software pitches suit the manufacturing and digital transformation pages, or the software pages on the site. Every pitch reaches the same editor, and the same rule applies: lived experience, balanced and free of promotion.

How long should a guest post be?

Most accepted posts run between 1,200 and 2,000 words. Length matters less than usefulness: a tight 1,200 word post with one clear lesson beats a 3,000 word overview every time. Use short paragraphs, clear subheadings and at least one real example.

Can I include a link back to my own site?

One contextual link back to your own site is fine when it is relevant and helps the reader. Posts written purely to build a backlink with no real value for the reader are not published.

Do you accept previously published content?

No. Every submission must be original and not published anywhere else first, including your own blog, Medium, LinkedIn or a guest slot on another site. Republished or lightly reworded content gets declined, and we check before anything goes live.

Can I use AI tools to help write my guest post?

You can use AI to help with research or tidying your draft, but the experience, examples and opinions must be yours. Posts that read like generic AI output, with no first-hand detail, are declined.

Do you accept sponsored or commercial partnerships?

Commercial and partnership enquiries are handled separately from editorial guest posts. If you are a brand or agency wanting to work together rather than pitch an article, say so in the contact form and you will get the right details back.

How long does a decision take?

We aim to come back to you within a few working days. If the pitch is specific and clearly written, with the result in the first line, the decision is much faster.

Do you edit guest posts before they go live?

Yes. Every accepted post gets an editorial pass for clarity, structure and accuracy, and you may be asked for an extra example or a missing number. The aim is to make your piece as useful as it can be, not to change your voice.

Can I pitch more than one idea?

Yes, but send them one at a time or as a short numbered list with one line each. The strongest pitch goes first, and a single clear idea with a real result almost always beats several vague ones.

How do I submit a ERP guest post?

Send your pitch through the contact form with the topic, the specific result or lesson you will cover, and a line on your own experience choosing, implementing or running ERP systems. One idea per pitch works best, and you will hear back before you write the full draft.

If your pitch is really about running a factory or a wider change of systems, it may sit better on the manufacturing write for us or digital transformation write for us page.

Brands and agencies: sponsored posts and link placements on this blog are handled separately from editorial guest posts. See how to work with me or email [email protected].