Custom-built AI for your procurement · Buy or build

Buy or build procurement software?

Standard software provides existing functions. Custom software can fit your workflows more closely but requires development and maintenance capacity. Here we compare cost, time and demands on your IT team.

It feels like every second IT department says it can build this itself with Power Automate, and often that is true. I build with the same tools, and the difference lies in the time to the first running process and in who operates it afterwards. An agent module costs €3,000 to €5,000 one-time with me and operation starts at €350 a month.

The sober comparison

No sugar-coating in either direction. Both routes have their place, just not for the same job.

CriterionBuy standardBuild it yourself
Time to first resultWeeksMonths to quarters
Fit to your processesYou adaptExactly your process
Cost in year onePredictable, recurringHigher, one-time
Cost over five yearsKeeps runningMaintenance, not license
Load on your ITLowConsiderable
Where data sitsWith the vendorIn your environment
Vendor dependencyHigh without an exportLow, with documentation
Further developmentThe vendor's roadmapYour priority, your budget

Green marks the structural advantage, not the right choice for you.

The dividing line that actually matters

Not "buy or build", but: where is your problem a solved problem, and where is it your own?

Buy when it is analysis

Existing modules cover price comparisons, supplier analysis and evidence management. First check whether their functions meet your requirements.

Build when it is your process

Specific approval chains, category rules or contract workflows may need custom development. Check what can be configured in standard software and what cannot.

And build where you already pay

Microsoft 365, Power Automate, your ERP: licenses you already hold. An agent inside them is not an extra system, not an extra login, not an extra place for your data.

Plan for maintenance from the start

Data upkeep and normalization need clear ownership. Documentation and cover should be in place even if the original developers leave the team.

The line items missing from the calculation

Both routes carry costs that are not in the first quote. Ask about them, including with us.

When buying

Implementation fee, data migration, seat tiers, price increases at renewal, and a charge to export your own data.

When building

The colleague who built it and leaves. Documentation nobody wrote. Rework after every ERP update.

With both

The months in which nobody can say reliably where your money is leaking, the most expensive item of all.

That is why every engagement with us starts with a fixed-price proof of value instead of an annual contract.

What procurement leaders ask us here

You sell both, are you even neutral?

No, and we do not claim to be. The difference: we earn on both routes, so we have no need to talk you into one. And in several cases we advised against a build because a module already answered the question.

Our IT says they could build this. Are they right?

Usually yes, technically. The question is whether that is the best use of scarce internal developer days, and who maintains it in three years. That is exactly why we build agents in your environment and hand them over documented.

How do we start without committing?

With an export from your ERP and a fixed-price proof of value. Afterwards you know which part of your problem should be bought and which built, even if you choose neither.

Let us settle it on your case

Name two or three categories and your biggest friction, and in 15 minutes I will tell you which part a module solves and which part has to be built.

We respect your privacy

We use cookies to give you the best possible experience on our website. You can change your preferences at any time. Learn more