Most ERP problems start the same way. The spreadsheets stop coping, the accounting package can’t keep up, and the finance team is spending a serious chunk of every week reconciling numbers by hand. Then a second site opens, or an audit throws up a VAT discrepancy, and suddenly the lack of a joined-up system is a real cost rather than an annoyance.
The usual answer is a big off-the-shelf ERP. For some businesses that’s the right call. But plenty of UK firms end up bending working processes around the software, paying per-user fees that climb with every hire, and waiting a year or more for an implementation to land.
At ByteGears we build ERP systems around how your business already runs. The software is developed in the UK, you own it outright with no recurring licence fee, and you get support and compliance help from people in your time zone. We’re a small consultancy, so we’ll also tell you honestly when off-the-shelf is the better-value option.
Where off-the-shelf ERP falls short
Packaged ERP works well for standard workflows. The friction tends to show up here:
- Per-user pricing that scales the wrong way. Most cloud ERP charges roughly £40 to £240 per user per month depending on role and edition. Fifty users is manageable. Two hundred users on the same model rarely is, and the bill never stops.
- Rigid workflows. Approval chains, commission structures and multi-stage manufacturing routes are often hard or impossible to change without paying the vendor or a certified consultant.
- Reporting that doesn’t match how you think. Pre-built reports rarely line up with your actual KPIs, and custom report development through a vendor is slow and expensive.
- Weak UK compliance. Making Tax Digital, CQC, FCA and Ofsted requirements are frequently handled with workarounds rather than built in.
- Integration gaps. Vendor APIs cover the popular tools and leave your legacy or specialist systems stranded, so staff re-key data between them.
- Long, risky implementations. Mid-market rollouts commonly run 4 to 6 months and enterprise suites 12 to 24, and budget overruns are routine.
- Lock-in. Once your data and custom logic live inside the platform, leaving is expensive enough that you stay even when the fit is poor.
None of this is hidden malice. It’s what happens when one product has to suit thousands of different businesses. The cost shows up as manual workarounds, duplicate systems and a finance team that doesn’t fully trust the numbers.
When SaaS is enough, and when custom is the right call
We’d rather you spend money well than spend it with us. A configured SaaS ERP is usually the sensible choice when your workflows are standard, your team isn’t large enough for per-user pricing to bite, and the vendor’s compliance certifications cover what you need.
A custom build earns its place when:
- You have proprietary workflows, complex approval chains or costing rules that no amount of configuration will reproduce.
- Per-user licensing has become a real constraint on growth.
- You need to connect several legacy or specialist systems that vendor APIs don’t reach.
- Your sector has compliance demands, in healthcare, financial services, education, food or regulated manufacturing, that packaged ERP only handles generically.
- You need something live in weeks, not a year-plus implementation cycle.
- No single vendor covers all your requirements, so you’d be stitching products together anyway.
What we do differently
We start with your processes. We map how you actually work, including the bits that don’t fit a template, then build software that supports it instead of forcing a rewrite of workflows that already do the job.
You pay once. You own the system and the source code. No per-user fee, so growing the team doesn’t grow the software bill.
We phase it deliberately. A core finance and operations release goes live first, so you get value early rather than waiting for the whole suite. Manufacturing, CRM and analytics follow once the foundation is solid.
It connects to what you already run. Accounting, ecommerce, payroll, CRM, carriers and HMRC, built as proper APIs with retry logic and audit logging rather than fragile scripts.
UK compliance is part of the build. GDPR-grade data handling, Making Tax Digital VAT submission, audit trails, and whatever your sector adds on top.
Support comes from our team here. Implementation, training and ongoing help from the UK, with no time-zone gap when something needs attention.
What we usually build in
A first release typically covers the operational core, then later phases add depth. The exact mix depends on your business.
Finance. General ledger, accounts payable and receivable, bank reconciliation, multi-entity consolidation and multi-currency where you need it.
Purchasing. Purchase requisitions with approval routing, purchase orders, goods receipt and three-way matching against PO, receipt and invoice.
Sales and order processing. Quotes, sales orders, deliveries and invoicing, with online, in-person and wholesale orders running through one interface.
Inventory. Stock receipts, issues, transfers and counts, multi-warehouse and bin-level tracking, and FIFO, LIFO or weighted-average valuation.
Manufacturing. Bills of materials, work orders, production scheduling and job costing with variance analysis.
Dashboards and reporting. The KPIs you actually track, P&L, balance sheet and aging reports, drill-down and a custom report builder, so you’re not stuck with whatever a template allows.
Automated workflows. Approval chains, escalations, stock replenishment and notifications driven by your own rules, including conditional routing such as orders above a threshold needing director sign-off.
CRM. Contacts, accounts, opportunities and activity tracking, shaped around how your sales and support teams actually work.
User management and audit trails. Granular role-based permissions and a full log of who changed what and when.
Mobile access. Warehouse, field sales and approvals on any device, with role-based permissions.
How a project runs
We work in four phases:
1. Discovery and planning (2-4 weeks). We sit with your team, watch how things work now, map the data and integrations, and agree what the first release must cover.
2. Development (8-16 weeks for the core release). Our UK developers build it with modern frameworks, and you review working software as it comes together rather than waiting for a big reveal.
3. Migration, testing and deployment (2-4 weeks). We import your chart of accounts, master data, opening balances and transaction history, reconcile it against the old system, run proper QA and user acceptance testing, then roll out in phases.
4. Training and support (ongoing). We train staff by role and identify super-users to act as first-line support, then stay involved after launch.
Migration is the part that most often runs over, usually because legacy data has more duplicates and gaps than anyone expects. We treat that as a known risk and surface the problems early. We only take on a handful of clients at a time, so each one gets proper attention.
What it costs
Custom development is a larger upfront cost than signing a SaaS contract. The case for owning the system is about the five-year picture, not the first invoice:
- No per-user licence fee. This is the big one. SaaS cost rises with every hire; a custom system doesn’t.
- No paid-for customisation cycle. Workflow and report changes are part of owning the software, not a vendor change request.
- Less manual work once approvals, reconciliation and replenishment are automated.
- No duplicate systems or workarounds once everything runs through one platform.
- An architecture that bends as the business changes, instead of a platform you’ve outgrown.
We won’t quote a guaranteed payback date, because it depends on your team size, growth and how much manual process you’re replacing. As a rough guide, a phased build often pays for itself fastest for firms growing past the point where per-user pricing starts to hurt. Every project is priced on what you actually need, and the first consultation is free with a clear, no-obligation estimate.
Where this works
Custom ERP earns its keep where the workflows are specific enough that a template gets in the way:
Manufacturing — bills of materials, production scheduling, work-in-progress and job costing, quality and defect tracking, supplier lead times and UKCA traceability
Wholesale distribution — multi-warehouse stock, inter-site transfers, batch picking, tiered pricing, volume discounts and credit limits
Retail and ecommerce — real-time inventory across stores, your own site and marketplaces, POS settlement, returns and demand forecasting
Professional services — project costing, resource planning and utilisation, milestone and time-based billing
Construction — project tracking, subcontractor and CIS handling, materials and cost management
Healthcare and care — patient and episode-of-care costing, CQC record-keeping, safeguarding alerts and staff vetting
Hospitality — reservations, staff scheduling and procurement
Charities and nonprofits — restricted fund accounting, grant tracking, donor management and programme reporting
Food production — batch tracing, recipe costing, allergen and HACCP records, shelf-life management
Because each build is bespoke, you get the workflows and compliance your sector needs without paying for, and training people on, a pile of features you’ll never touch.
Common Questions About Custom ERP Systems
How does custom development cost compare to SaaS ERP?
A custom build is a larger upfront cost, but it has no per-user licence fee. With a SaaS platform, per-user pricing runs roughly £40 to £240 per user per month depending on role and edition, so the bill climbs every time you add headcount. Most firms reach a point, often around 50 to 100 users or a few years in, where owning the system outright works out cheaper over a five-year view. We are honest about this: if you have a small team on standard workflows, SaaS may well be the better-value option, and we will say so.
What's the typical development timeline?
A first usable version, covering core finance, purchasing, sales and basic inventory, usually takes 8 to 16 weeks. Adding manufacturing, supply chain, CRM and integrations in a second phase typically adds another 4 to 8 months. We deliberately phase the work so you are not waiting a year or more before anything goes live, which is a common complaint with large vendor implementations.
How do you handle data migration from our old system?
Migration is usually the part that runs over, so we plan it properly. We import your chart of accounts, master data (products, customers, suppliers, employees), opening balances and two to three years of transaction history, then reconcile it against your old system before go-live. Legacy data almost always has duplicates and gaps; we surface those early rather than discovering them on launch day.
Can you integrate with our existing systems?
Yes. Common integrations include accounting platforms (Xero, QuickBooks, Sage), HMRC for MTD VAT submission, ecommerce (Shopify, WooCommerce, Amazon), payment processors (Stripe, Worldpay), CRMs, payroll, and carriers like DPD and Parcelforce. We build these as proper APIs with retry logic and audit logging, rather than brittle one-off scripts.
What about data security and compliance?
Every build includes UK GDPR handling: encrypted data at rest and in transit, role-based access, full audit trails of who changed what and when, and right-to-erasure workflows. We build to HMRC Making Tax Digital requirements for VAT, and can support sector rules where relevant, such as CQC record-keeping in care, FCA reporting in financial services, or HACCP traceability in food production.
What happens after go-live?
We train your team by role: finance, operations, warehouse and reporting users each get focused sessions, and we identify super-users who become first-line support. The handover includes documentation and the full source code, so you are never locked in. After the initial support period you can take updates on a maintenance plan or run the system yourself.