Custom ERP development
Custom ERP development for operators who buy and stock across many sites
Safock is a custom ERP development company that builds procurement, inventory, operations and finance modules into one system designed around your processes and sites. We build for multi-site operators, such as school groups, clinic networks, contract caterers, retailers and construction firms, whose sites still buy and stock on separate spreadsheets. Controls are enforced in the database, every action lands in an audit trail that cannot be edited, and the system connects to the accounting software you keep.
/ The problem
What this fixes
- 01
An ERP that fights your process
Large ERPs assume a standard way of working. Every difference becomes a customisation, a workaround or a spreadsheet next to the system.
- 02
Sites and teams on separate spreadsheets
Each site or department keeps its own records, so head office sees spend and stock late and has to reconcile by hand.
- 03
Controls that only live in the screens
If approval rules are enforced only in the user interface, an import or integration can route around them.
/ What we build
Custom ERP development, built for your systems
- 01
Procurement and approvals
Requisitions, approval chains, purchase orders, goods receiving and three-way match before payment.
- 02
Inventory and transfers
Stock per site or store, reorder levels, transfers between locations and a single item master.
- 03
Operations modules
Production, scheduling, service or project modules shaped to your workflow, added in phases.
- 04
Finance links and reporting
Invoices, payments and spend reporting, connected to your accounting system rather than replacing it.
- 05
Controls and audit trail
Rules enforced in the database and an append-only log of every action, ready for audits.
/ How it works
The detail behind it
Built on what we run ourselves
Bollard, Safock's own procurement and inventory software for multi-site operators, covers requisitions, approvals, purchase orders, goods receiving, three-way match, inventory and transfers, and an append-only audit trail. Its controls are enforced in the database, so no screen, import or integration can bypass them.
Bollard was designed around five ways money leaks from multi-site purchasing: sites buying without approval, suppliers billing above the agreed price, invoices for goods that never arrived, a separate spreadsheet per site, and stock piling up at one site while another runs short. Each module closes one of those gaps.
Custom ERP projects start from the same foundations and add the modules your operation needs, one site or department at a time.
How custom ERP development rolls out, one site at a time
ERP projects carry the most risk when every site and module switches at once. We go live with one module at one pilot site, fix what the pilot reveals, then roll out across the business. Your existing systems keep running until each part is proven.
Bollard's own rollout shows the pattern. Days 1 to 3 are discovery, days 4 to 7 import the catalog and vendors, and days 8 to 14 take one pilot site live before the rest of the network moves over. A custom ERP takes longer than rolling out an existing product, and the pilot-first order stays the same.
- Discovery across the processes and sites in scope
- First module live at a pilot site
- Rollout to the remaining sites and teams
- Further modules added in later phases
What drives the cost of a custom ERP
Cost follows the number of modules, the number of sites, the depth of the approval chains, the systems to connect, such as your accounting software or an existing ERP, and the item and vendor data to clean and import. Procurement and inventory for one region is a smaller build than production, finance links and many sites. We scope it in discovery and send a fixed quote with milestones, and every launch includes 30 days to 3+ months of support.
/ How we work
From first call to a system your team runs
- 01
Discovery
We start with your workflows, goals, and constraints, so we solve the problem you actually have.
- 02
Proposal & architecture
A clear scope, timeline, milestones, and system design, with honest pricing before any build starts.
- 03
Agile delivery
Short sprints with regular demos, so you see working software early and can steer as it takes shape.
- 04
Launch
Deployment, optimization, and security hardening are included. Nothing ships unless it is safe and secure.
- 05
Support & growth
30 days to 3+ months of support after launch, with long-term maintenance available as you grow.
- 06
Your team, enabled
Documentation and training so your people can operate and extend the system on their own.
/ Proof
Work that shows how we build
- usebollard.com

Our product / Procurement and inventory for multi-site operatorsBollard
Our own procurement and inventory software for multi-site operators: seven modules, controls enforced in the database, and an append-only audit trail.
- AI assistant on live data
- Database-enforced controls
- Append-only audit trail
14 daysPath to a first live site
- mavick.si

Our product / Textile manufacturingMavick
Our AI operating system for textile factories: one agent per department, cited answers, and human approval before any change to a live system.
- Department-scoped AI agents
- Human approval before writes
- Answers with citations
32Department templates
- Client workProfessional services, software developmentClient work / Professional services, software development
A software development agency
One internal platform for a development agency, covering deal, project, time, invoice and Stripe settlement, in place of four SaaS tools.
- Postgres row-level security
- Idempotent Stripe webhooks
- Deal-to-settlement workflow
Read the case study
/ FAQ
Questions buyers ask us
Should we build a custom ERP or buy one?
Buy if a standard ERP fits your processes with light configuration. Build, or build modules around an existing system, when your processes are distinctive, when you run many sites that buy and stock differently, or when licence and customisation costs outgrow the value. We recommend honestly during discovery.
Can a custom ERP work alongside our accounting system?
Yes. We connect the ERP to the accounting system you already use and send it approved invoices, payments and journal entries, so it stays the place your finance team closes the books. Purchasing, stock and approvals move into the new system, while the chart of accounts and month-end routine stay as they are. Where the accounting tool has no usable API, we agree a scheduled export format instead.
Can you use Bollard instead of building from scratch?
If your needs are procurement and inventory across many sites, Bollard may already cover them with its seven modules, and we can extend it. If you need production, scheduling or finance modules as well, we build custom modules around it or start fresh. Either way you get a recommendation and a fixed quote after discovery, before any build work begins.
How long does custom ERP development take?
It depends on the modules, the number of sites and how clean your item and supplier data is. We take one module live at a pilot site first, so your team uses the system on real purchases early, then roll out site by site. Bollard reaches its first live site in 14 days because its modules already exist. A custom build takes longer, and the proposal sets its milestones.
/ Related
Often paired with
- /01Custom software development
Custom software development
CRMs, ERPs, portals and internal tools shaped to your process, with access rules in the database and code you own.
- CRMs shaped to your sales process
- ERP and operations modules
- Client, vendor and partner portals
- /02Custom CRM development
Custom CRM development
A CRM built around your pipeline and client lifecycle, from lead to invoice, connected to your tools and owned by you.
- Pipelines and deal management
- Client and contact records
- Quotes, projects and invoicing
- /03Business process automation
Business process automation
Redesign and automate complete processes across your systems, with approvals, exceptions and an audit trail.
- Process mapping and redesign
- End-to-end workflows
- Exception handling
- /04Systems integration and API development
Systems integration
We connect payments, Google Workspace, Microsoft 365, ERPs and CRMs with APIs and webhooks that stay correct under real traffic.
- Payment gateway integration
- Google Workspace and Microsoft 365
- ERP and CRM connections
/ Next step
Tell us which part of your operation runs on spreadsheets
Tell us what you are working on. You will speak with a founder, and you will leave the call with a clear next step, even if that step is not us.
Prefer writing? Send us a brief and a founder will reply.