Your Oxford spinout closes the books on a grant calendar, and NetSuite has never heard of UKRI
For an Oxford research spinout, a custom ERP (Enterprise Resource Planning) runs £70,000 to £160,000 over 4 to 7 months. The reason off-the-shelf hurts here is that NetSuite, SAP and Microsoft Dynamics organise the world around fiscal periods and cost centres, while a Begbroke or Oxford Science Park spinout organises it around grant codes, work packages and burn against a UKRI or Wellcome award. Custom lets the chart of accounts and the funder report share one source of truth.
You took Innovate UK and a Wellcome translation award, hired six people, and your finance contractor maps every invoice to a grant work package in a spreadsheet because Xero only knows nominal codes. Then NetSuite gets pitched as the grown-up answer, and you discover its idea of a project is a billable client engagement, not a five-year award with eligible-cost rules, FEC overheads and a claim schedule.
Odoo and Dynamics can be bent toward this with custom fields and a consultant, but the bending never stops. Every funder has different eligibility, every claim wants a different cut, and the people doing it in Oxford are PhDs who notice the moment the overhead recovery is off by a fraction. The tool fights the way the money actually moves.
Where the off-the-shelf tools fall short
- Invoices map to nominal codes but funders want spend by grant work package, so finance re-keys everything before each claim
- FEC overhead recovery and eligible-cost rules differ per funder and live in a contractor's head, not the system
- Consumables and capital equipment bought against a specific award can't be traced back cleanly at audit
- Burn-rate against remaining grant runway is reconstructed by hand the week before a board meeting
Custom erp: what Oxford teams actually get
A custom ERP makes the grant the primary object, not an afterthought. Every purchase order, payroll line and consumable carries its award code and work package from the first click, so the funder claim and the statutory accounts reconcile automatically. For a spinout where a mis-stated overhead can trigger a clawback, that single source of truth is worth more than any module count.
- You hold three or more concurrent awards with different eligibility and claim formats
- Annual grant income is large enough that a clawback or mis-stated FEC is an existential risk
- Finance spends days, not hours, reconciling spend to awards before every board pack
- You expect to scale headcount and add awards faster than a spreadsheet workflow can absorb
- You run a single award and Xero plus a clean spreadsheet still closes in an afternoon
- You have no in-house finance-systems owner and won't hire one this year
- Your funders all accept the same standard claim format with no custom eligibility
- Cash runway is too short to absorb a four-month build before the next raise
- One ledger that produces both Companies House accounts and a UKRI or Wellcome claim from the same transactions
- Live grant runway per award so a CSO sees months of runway, not a stale month-old spreadsheet
- Eligible-cost rules encoded once, so a flagged ineligible expense gets caught before it hits a claim
- Audit trail that ties a £40,000 mass spec back to the award that funded it without a paper hunt
- Connects cleanly to inventory management software for reagents and your accounting software for statutory filing
- You become responsible for keeping funder rules current as UKRI and charity terms change year to year
- A six-person spinout may not have the headcount to own an internal ERP without a part-time finance-systems person
- If the company pivots or gets acquired, a bespoke grant-centric ledger may need rework to fit an acquirer's stack
- Initial discovery is slower because eligibility logic must be captured precisely, and detail-driven founders will scrutinise it
Feature priorities for Oxford teams
Oxford ERP: the full scope
The engagements Oxford teams bring us most often: SAP integration, Odoo development, Microsoft Dynamics 365, ERP migration, cloud ERP, manufacturing ERP and distribution ERP.
The honest cost picture for Oxford
| Project scope | Typical cost | Timeline |
|---|---|---|
| Grant-aware ledger MVP for one entity | £70,000 to £95,000 | 4 to 5 months |
| Multi-award ERP with claim-pack export and FEC logic | £100,000 to £140,000 | 5 to 7 months |
| Group rollout across spinout plus parent IP holding co | £140,000 to £160,000+ | 6 to 8 months |
Timeline: what happens, and when
Exactly what you get
A ledger where the grant award is a first-class dimension, not a tag. Every PO, payroll allocation and reagent purchase carries its award and work package, FEC overheads recover automatically per funder, and one click produces both your statutory accounts and a funder-ready claim pack. You also get runway dashboards per award and an audit trail that survives a UKRI or charity audit without a week of paper-chasing.
How to choose a developer in Oxford
Pick a team that asks to see a real claim pack before quoting and that can name the funders you hold. Oxford is full of capable shops, but grant accounting is a specialism. Ask for a reference from another spinout or research body, and make them walk you through how eligible-cost rules get encoded and updated. A detail-driven founder will spot a generalist within ten minutes, so let that instinct guide the shortlist.
- !They pitch NetSuite project accounting as a grant module without asking which funders you hold
- !No question about FEC overhead recovery or eligible-cost rules in the first call
- !They quote a fixed price before seeing a real claim pack you have submitted
- !They have never shipped finance software for a research or grant-funded organisation, ask for a reference
- !They treat funder reporting as a report you bolt on later, not a core data model decision
Most Oxford teams pricing erp end up comparing notes on internal tools, shopify, inventory management too; the systems share one data spine.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Can a custom ERP produce both our statutory accounts and our UKRI claim?
Yes, that is the entire point. When every transaction carries its award code and work package, the system derives both the Companies House accounts and the funder claim from the same data, so they always reconcile.
How is this different from NetSuite project accounting?
NetSuite projects model billable client work with revenue recognition. A grant is a multi-year award with eligibility rules, FEC overheads and a claim schedule. A custom ERP models that directly instead of forcing a grant into a project shape.
We are six people. Is an ERP overkill?
Possibly. If you hold one award and close cleanly in Xero, stay there. Custom ERP earns its cost when you carry three or more awards with different rules and reconciliation is eating finance days every month.
Who keeps the funder rules up to date?
You do, with the developer's support. Funder terms change yearly, so budget for a maintenance arrangement where eligibility logic gets reviewed each grant round.