Most businesses don’t go looking for procurement software until something forces the issue. The spreadsheet that ran purchasing for years now has five people editing it and nobody trusts the numbers. An audit turns up a gap. A duplicate order or a supplier invoice that should never have been paid gets noticed too late. By the time procurement reaches your desk, the question isn’t whether to fix it, it’s whether to rent a tool or own one.
We build procurement systems around the way your team already buys things, rather than asking them to relearn purchasing to suit a vendor’s templates. We’re a UK development team focused on automation for SMEs and mid-market businesses. That means no per-user subscription that climbs with headcount, no awkward workarounds for VAT or Making Tax Digital, and support on UK hours from people who know your build.
To be straight about it: not every business needs custom procurement software. If you have a handful of suppliers, simple approval chains and standard accounting integrations, an off-the-shelf tool will probably serve you well and cost less. This page is about the businesses for whom that stops being true.
Where off-the-shelf procurement software falls short
Off-the-shelf procurement tools are mature and many of them are good. The friction tends to show up in specific places:
- Rigid approval workflows. Most tools route approvals on a single spend threshold. Real authorisation rules are messier: a £40k IT purchase in one cost centre needs different sign-off than £40k of raw materials in another. Teams end up working around the system in email or a side spreadsheet.
- Per-user pricing that punishes growth. Pricing scales with headcount. Once a lot of people raise requisitions, adding users gets expensive fast, and you end up rationing logins.
- Hidden costs beyond the subscription. The quoted price rarely includes implementation, data migration, per-integration setup fees, training, or the premium support tier. Add-on modules for sourcing or contract management are charged separately.
- Weak integrations with what you already run. Xero and Sage are usually fine. A legacy ERP, a warehouse system, or a proprietary finance tool often isn’t, and sync runs nightly rather than in real time, which leaves finance reconciling by hand.
- Generic compliance. GDPR logging and audit trails are there, but UK public procurement rules, NHS framework purchasing or FCA vendor due diligence usually need custom configuration the vendor charges for.
- Supplier portals suppliers won’t use. If the portal UX is poor, suppliers quietly go back to email and the e-invoicing benefits never materialise.
The bigger cost is usually invisible on the invoice: the spreadsheets people keep on the side, the rekeying between systems, and the IT time spent gluing things together.
What we build instead
Approval logic that matches your real rules
This is usually the deciding factor. We build conditional routing on the combination of spend amount, cost centre and procurement category, so a high-value engineering purchase and a routine office order follow different chains. Delegation covers people who are away, and approvals escalate automatically if they sit unactioned too long. Budget holders can adjust routes themselves without calling a developer.
Three-way matching that catches the errors
The system matches the purchase order, the goods received note and the supplier invoice, flags anything that doesn’t reconcile, and routes exceptions to the right person rather than letting a wrong invoice slide through to payment.
Budget control that holds in real time
Cost centre budgets are checked at the point a requisition is raised, counting open POs and delivered-but-uninvoiced commitments, not just what has already been paid. Spend can’t quietly run past its limit and surface at month end.
Integrations built for what you actually run
Xero, QuickBooks Online and Sage connect through documented APIs for purchase order, invoice and payment sync. Heavier systems such as NetSuite, SAP or Microsoft Dynamics involve GL mapping and multi-entity work, and we scope that honestly. Where a system has no usable API, we use secure file exchange or EDI rather than pretend otherwise.
One investment, not a forever bill
You pay for development once instead of renting access per user, per month. There are no module paywalls, no per-integration fees and no licence cost that climbs as you hire. The code is yours.
UK compliance built in from the start
UK VAT handling, digital record-keeping for Making Tax Digital, GDPR measures and an immutable audit trail are part of the design, not a configuration job bolted on later. For regulated sectors we can build in public procurement rules, NHS framework purchasing or FCA vendor due diligence.
Modular so it can grow
The architecture is built in pieces. When you need a supplier portal, a new approval chain or a different reporting view, we add the module instead of rewriting the system.
A UK team you can actually reach
Support runs on UK hours, in English, with people who know your build. No tier-one script readers, no overnight delays.
Features we typically build in
Every project is different, but these are the building blocks most procurement systems need:
- Self-service purchase requisitions with budget checks at the point of raising
- Conditional approval routing by spend, cost centre and category, with delegation and escalation
- Rule-based purchase order generation, PDF output and automatic email to suppliers
- Three-way matching between PO, goods received note and invoice, with exception handling
- Supplier master records covering contacts, tax IDs, payment terms, categories and risk tier
- Supplier performance history and contract records, including renewal dates
- Cost centre budget tracking against open POs and uninvoiced commitments
- Reporting dashboards with spend by supplier, category, cost centre or team
- Document storage for contracts, warranties, invoices and compliance files
- Role-based access with segregation of duties and granular permissions
- An immutable audit trail logging every change with user, timestamp and reason
- Automatic UK VAT handling and MTD-compatible digital records
- Mobile approvals and delivery tracking for buyers and budget holders on the move
How a project actually runs
Discovery and planning (2-4 weeks)
We spend time with the people who use procurement every day, buyers, approvers and the finance team. We map your real approval rules, list the data we’ll need to migrate and identify which integrations are simple and which are not. The output is a scoped plan with clear success measures, not a generic statement of work.
Development (around 8-14 weeks for a core build)
Developers build in short cycles with regular review sessions, so you see progress and can adjust direction before things harden. We start with the procure-to-pay core, requisitions, approvals, PO generation, three-way matching and one accounting integration, because that is where most of the value lands.
Migration and testing (2-4 weeks)
Legacy supplier data is the part teams underestimate. It tends to be full of duplicates, inconsistent supplier names and missing tax IDs, and cleansing it is real work. We handle extraction, de-duplication and mapping, then your team runs user acceptance testing on a real environment before anything goes live.
Rollout, training and support
We roll out in phases, often piloting with one department first rather than a single big-bang switch. Training is split by role: a couple of days for administrators, shorter sessions for approvers and budget holders, and brief guidance for anyone raising requisitions. After launch we stay on for fixes, tuning and the inevitable “can it also do this” requests.
A core procure-to-pay build usually lands in the 3 to 4 month window. A supplier portal, strategic sourcing or multi-entity support extends it. Integration count and the state of your legacy data are the main variables, not the build itself.
What it costs, honestly
Custom development costs more upfront than signing up for a SaaS tool. The honest comparison isn’t sticker price against sticker price, it’s total cost over three to five years.
SaaS procurement tools quote a subscription, then add implementation, data migration, per-integration setup, training, a premium support tier and add-on modules for sourcing or contract management. Per-user pricing means the bill grows as you hire, and multi-year contracts often carry early-exit penalties. None of that is dishonest, it’s just rarely on the first page.
With a custom build you pay once for development. After that:
- No per-user fees that climb with headcount
- No module paywalls when you need something the vendor decided is a premium tier
- No per-integration charges
- No vendor lock-in, because the code is yours
- No forced migration when you outgrow the original system
Where it lands depends on the feature list and how many systems you’re integrating with. We give a proper estimate after discovery, not a figure from a marketing page. Whether ownership wins financially depends on your headcount, number of sites and integration count, and we’ll tell you plainly if a SaaS tool would serve you better.
Where custom procurement software is worth it
It’s worth being specific about who this suits. A custom build earns its place when:
- Approval logic is genuinely complex — conditional rules across cost centre, category and amount that no template handles cleanly
- You need to integrate with a legacy ERP or proprietary finance system that no SaaS vendor supports without expensive middleware
- You operate across multiple entities or sites where per-user or per-location pricing makes SaaS more expensive than ownership at scale
- You carry sector-specific compliance — NHS framework purchasing, FCA vendor due diligence, food and pharma traceability
- Procurement volume is high enough that SaaS API rate limits or batch syncing slow your operation
- Vendor independence matters — you want full data control and no multi-year contract dependency
If none of those apply, an off-the-shelf tool is probably the sensible call, and we’ll say so.
Sectors we build procurement systems for
The mechanics of procurement vary a lot by industry, and that is exactly where custom rules and approval logic matter:
- Manufacturing: raw material ordering with reorder points tied to consumption, bill-of-materials purchasing, and supplier quality and certificate tracking
- Construction: project-level POs tied to cost centres, milestone-based approvals, subcontractor onboarding with insurance and licence checks, and hard caps per project phase
- Healthcare: medical supply procurement with par levels, supplier credentialing, and audit trails that stand up to NHS framework and CQC scrutiny
- Retail and hospitality: centralised purchasing across many sites with a local supplier mix, food and beverage ordering tied to inventory levels
- Public sector: competitive tender processes, framework agreement purchasing, social value scoring and the full audit trail transparency rules demand
- Professional services: project-specific purchasing linked to client billing and cost recovery
- Facilities management and logistics: maintenance parts, fleet and fuel procurement coordinated across multiple sites
- Charities: clear accountability and reporting for donor- and grant-funded spend
A generic tool has to flatten these differences. The reason custom works here is that it doesn’t have to.
Common Questions About Custom Procurement Management Software
How does a custom build compare on cost with procurement SaaS?
Custom costs more upfront. The trade-off is what stops compounding: per-user fees, per-location charges, module add-ons for sourcing or contract management, and per-integration setup fees. SaaS total cost of ownership is rarely the sticker price once implementation, data migration, training and annual increases are counted. Whether ownership wins over a three to five year horizon depends on your headcount, number of sites and integration count. We give a proper estimate after discovery, not a figure from a marketing page.
When is off-the-shelf procurement software the better choice?
Often. If you have a small supplier base, straightforward approval chains, standard accounting integrations and no unusual compliance burden, a SaaS tool like Precoro or Procurify will likely serve you well and cost less. Custom earns its place when approval logic is genuinely complex, you need to integrate with a legacy ERP no vendor supports cleanly, you operate across multiple entities where per-user pricing punishes scale, or you carry sector-specific compliance such as NHS procurement governance or FCA vendor due diligence. We will tell you honestly which side of that line you fall on.
What's the typical development timeline?
A working procure-to-pay system, requisitions, approval routing, PO generation, three-way matching, supplier records and one accounting integration, typically takes around 3 to 4 months. Adding a supplier portal, strategic sourcing or multi-entity support extends that. The biggest variable is rarely the build itself; it is the state of your legacy supplier data and how many systems need to sync. We scope a realistic timeline after discovery.
Can you integrate with our accounting and ERP systems?
Yes. Xero, QuickBooks Online and Sage have well-documented APIs and connect in a couple of weeks for purchase order, invoice and payment sync. NetSuite, SAP and Microsoft Dynamics are heavier work because of GL mapping and multi-entity structure. Where a supplier or legacy system has no usable API, we fall back to secure file exchange or EDI rather than pretend an integration exists.
How do you handle approval workflows that don't fit standard templates?
That is usually the reason a business outgrows SaaS. We build conditional routing on your real rules, for example spend above a threshold in a given cost centre and category requiring two named approvers, with delegation when someone is away and automatic escalation if an approval sits too long. Budget holders keep admin control to adjust routes without a developer.
What about data security and compliance?
Builds include UK GDPR measures: role-based access, segregation of duties, encryption in transit and at rest, and an immutable audit trail that logs every change to a requisition, PO, invoice or approval with the user, timestamp and reason. We handle UK VAT correctly and keep records digitally for Making Tax Digital. For regulated sectors we can align with ISO 27001 and Cyber Essentials, and build in NHS framework or FCA vendor due diligence requirements where they apply.
Do you provide training and support after launch?
Yes. Training is split by role: a couple of days for administrators, shorter sessions for approvers and budget holders, and brief self-service guidance for anyone raising a requisition. After go-live we stay on for fixes, tuning approval rules and the inevitable "can it also do this" requests. Your team retains admin access for routine changes.