eProcureAI / Platform / For mid market companies

Segment

Too big for spreadsheets,
too sensible for a suite

Mid sized companies get offered two bad options. A suite built for global groups, priced and paced accordingly, or a point tool solving a quarter of the problem. There is a third answer.

One hundred to five thousand people. Usually run out of finance rather than a procurement team.

What fitsThe suite option
The situation

The middle is where software gets least attention

Procurement software is built for two markets. Very large organisations with dedicated platform teams, and very small ones that need little more than a purchase order form.

Companies between one hundred and five thousand people fall between them. Spreadsheets have stopped working, but there is no procurement technology function, no implementation budget measured in quarters, and nobody who wants to spend a year configuring anything.

So mid sized companies get offered a suite scaled down, which still assumes somebody will configure it, or a point tool that handles requisitions and leaves invoice matching, supplier records and budgets exactly as they were.

Opinionated is an advantage here

A highly configurable platform with nobody to configure it becomes a frozen platform. Where there is no platform team, sensible defaults that work on day one are worth more than flexibility nobody will use.

That is the design choice we made. The system has opinions about how a request should look, how routing should work and what a good approval chain contains, and you adjust rather than build.

Modular matters more than it sounds

Starting with one module and adding others without reimplementation is what makes the first purchase a small decision rather than a strategic commitment. Most customers start with intake and approvals and add two more inside the first year.

Why the options do not fit

Four mismatches mid market teams run into

Mismatch 1

Implementation measured in quarters

A suite deployment assumes a project team and a timeline you do not have. Three weeks is the number that fits.

RealityWeeks, not quarters
1
Mismatch 2

Configuration assumed

Flexible platforms need somebody to shape them. With no platform team, that flexibility becomes a liability.

RealityOpinionated defaults
2
Mismatch 3

Breadth you will not use

Paying for global multi entity capability when you have one ledger and one country is a common mid market complaint.

RealityModular pricing
3
Mismatch 4

Point tools that do not join up

Requisitions in one place and invoices in another means matching is impossible, which was half the reason to buy.

RealityOne record
4
What changes

Three things that make this size work

Live in weeks with your own team

Configuration, migration and testing are handled by an implementation specialist. The typical ask of your team is a few hours a week for about three weeks.

  • No project team required on your side
  • Specialist does the configuration with you
  • One training session per site
  • Live on the first module in about three weeks
ImplementationLive
TimelineAbout three weeks
Your effortHours weekly
Project teamNot needed
ConsultantsNone
WeeksRather than quarters

Run by one person in finance

Most mid market customers have no procurement function at all. One owner in finance sets thresholds, maintains the catalog and handles exceptions.

  • Rules changed by finance without a developer
  • Catalog maintained without specialist knowledge
  • Access granted by department rather than by ticket
  • IT involvement limited to single sign on
OwnershipLive
OwnerOne person in finance
DeveloperNot needed
ITSingle sign on only
Procurement teamOften none
One ownerRather than a function

Grows without a second implementation

Adding modules, entities or volume does not mean starting again, because everything reads the same record underneath.

  • Start with one module and add later
  • Multi entity available when you need it
  • No reimplementation as you grow
  • Historical data stays intact throughout
GrowthLive
Year oneTwo or three modules
Multi entityWhen needed
ReimplementationNever
HistoryIntact
Grows with youNot against you
Honest comparison

Where each option genuinely fits

This is the comparison we would give you on a call, including the cases where we are the wrong answer.

OptionFits whenStruggles whenTypical timeline
SpreadsheetsLow volume and genuinely simple approvalsVolume grows or the person who built it leavesAlready in place
Point toolOne narrow problem, and only oneYou need matching, budgets or supplier records tooWeeks
eProcureAIOne hundred to five thousand people, no platform teamYou need deep global multi entity governanceAbout three weeks
Enterprise suiteMany entities, dedicated platform team, transformation budgetThere is nobody to configure it afterwardsMonths

If you have a dedicated procurement technology team and complex multi entity governance, a suite is genuinely the better answer and we will say so.

How it grows with you

Six changes that do not require starting again

More modules

Added when justified

Most customers add two more inside the first year without any reimplementation.

TypicalTwo more
More volume

Same system

Volume growth does not change the deployment or require a different tier of product.

ChangeNone needed
More entities

Available when needed

Multi entity capability exists when you get there rather than being something you pay for now.

WhenYou need it
More people

Access by department

Adding headcount is a department choice, not a licensing exercise or an access ticket.

EffortOne choice
More suppliers

They onboard themselves

Supplier growth does not create work for your team because suppliers complete their own records.

Work createdMinimal
More scrutiny

Evidence already there

When an auditor arrives, the evidence exists as a by product rather than needing assembly.

ReadyAlready
Who does what

The short version of running this at your size

The right amount of software for this size is the amount somebody in finance can own alongside their actual job.

What your team does

One owner in finance, a few hours a week during setup, then exceptions.

The human partLive
Finance ownerSets thresholds and catalog
Finance ownerHandles exceptions
ITSingle sign on, once
Everyone elseRaises and approves
One ownerNot a function

What eProcureAI does

Implementation, configuration support and everything the system runs on its own.

The automatic partLive
Configure with youNot hand it over
Migrate suppliersAnd de-duplicate
Apply the rulesEvery request
Support the rolloutSame people throughout
Grow with youWithout reimplementation
No consultantsNo services package
0from signing to live on the first module
0in finance, rather than a procurement function
0start with one, add without reimplementing
0and no mandatory services package
FAQ

Questions people actually ask

What size company is this actually built for?
Roughly one hundred to five thousand people. Below that, spreadsheets may still be reasonable. Above that, particularly with many entities and a dedicated platform team, a suite may genuinely fit better.
Do we need a procurement team to run it?
No. Most customers of this size run it from finance with a single owner who sets thresholds, maintains the catalog and handles exceptions alongside their existing job.
How long does implementation really take?
About three weeks for the first module, including supplier migration and configuration. Your team spends a few hours a week on decisions rather than data entry.
Will we outgrow it?
Adding modules, volume, entities or people does not require reimplementation, because everything reads the same record. Multi entity capability is there when you reach that point.
Do we have to buy all the modules?
No, and we would talk you out of it. Most teams start with one or two and add more when there is a reason, without a new implementation.
What if we already tried procurement software and it failed?
Worth telling us why. The most common reasons are a request form that took too long and a rollout that tried to do everything at once, both of which are avoidable.
Are there mandatory professional services?
No. Implementation is included on the main plans and done by our own team, so there is no partner margin inside your quote.
When would you tell us not to buy?
When the volume does not justify it yet, or when your requirements point to a suite. Both happen, and saying so on the call costs us less than a deal that unwinds in month seven.

Tell us how you buy today

Thirty minutes and a straight answer about whether this is the right size of solution for you.

Book your free demo

Related: All solutions and The platform