ERP and business systems

Custom ERP

An ERP built around the way you already work

When a standard system would force you to change the process that sets you apart, we build the modules you need and nothing else: on a database you own, connected to the tools you keep.

Work orders

Planned 2

WO-214 · Staircase, oakMaterials reserved
WO-215 · Kitchen frontsWaiting for veneer

In production 2

WO-211 · Reception deskCNC · stage 2 of 4
WO-212 · Wardrobe setAssembly

Ready 1

WO-209 · ShelvingDelivery booked

When custom is the right choice

Your process is the product

Some companies are good precisely because they do one thing differently: the way a job is priced, the steps a product goes through, how work is scheduled across people and machines. A standard ERP handles those with workarounds. A custom one models them directly, so the screens match the words your team already uses and the rules are the rules you actually follow.

  • Only the modules you need, in the order you need them
  • A PostgreSQL database and a code repository in your accounts
  • Connected to accounting, the webshop and the CRM instead of replacing them
  • If Odoo covers the process well, we say so, because it is quicker to adopt

Quote from a bill of materials

Quote Q-0387

Reception desk · calculated from the bill of materials

  • 14 lines from stock and supplier price lists Materials
  • Cutting, edging, CNC, assembly Operations
  • Custom finish surcharge Rule applied
  • Proposed from workshop load Delivery date

A person checks the price before the quote is sent

What we deliver

Modules we are most often asked for

Work orders and production

Jobs broken into stages, with materials, people and machines assigned and progress recorded where the work happens.

Stock and materials

Items, locations and movements, with reservations per job and a warning before something runs out.

Quotes and pricing rules

Quotes calculated from bills of materials, operations and your own pricing rules, ready for a person to approve.

Planning and scheduling

A board or calendar that shows load per person, machine or team, and what moves when a deadline changes.

Reports

Open orders, stock value, job cost against quote and anything else you now assemble by hand each month.

Integrations

Invoice data to your accounting software, orders from the webshop, contacts from the CRM, files to shared storage.

How a project runs

The smallest useful system first

  1. 01

    Map the process

    We follow real jobs through the company and write down the data, the rules and the exceptions, in your team’s own terms.

  2. 02

    First module

    We design the data model, build the one module that removes the most manual work and put it into daily use.

  3. 03

    Extend

    Further modules are added one at a time, each going live before the next is started, with integrations alongside.

  4. 04

    Care

    We monitor, fix and adjust the system as the process changes. The code and the documentation stay with you.

What we build with

Application
Next.js, React, TypeScript, Node.js
Data
PostgreSQL, Role-based access, Audit log, Scheduled backups
Connected to
Your accounting software, Shopify, WooCommerce, CRM, n8n, Email

Custom ERP or a standard one?

Custom is a good fit when…

  • Your pricing, production or scheduling rules do not fit a standard system
  • You have tried a packaged ERP and kept working around it in spreadsheets
  • You need a few modules done precisely, not a wide system done roughly
  • You want to own the code and the database outright

Probably not for you when…

  • Your process is standard and Odoo would cover it with configuration
  • You need the full breadth of an ERP from the first day
  • Nobody can describe how the process works today
  • You want accounting and tax reporting rebuilt from scratch

Questions about custom ERP

Odoo or custom: how do you decide?

We map the process first. If Odoo covers it with configuration and a small amount of adjustment, we recommend Odoo, because it is quicker to adopt. If the core of your work would need heavy customisation to fit, a custom system is usually simpler to build and to live with. You get the recommendation in writing, with the reasons.

Who owns the code and the data?

You do. The code lives in a repository in your account, the database runs in hosting you control, and the documentation is written so another team could take over.

Does a custom ERP include accounting?

Not by default. Bookkeeping, tax reporting and fiscalisation stay in the accounting software you and your accountant already use, and the ERP passes invoice data to it. We look at changing that only if you ask, and only after confirming what the local requirements are for your case.

Do we have to specify everything up front?

No. The analysis defines the first module precisely and the later ones in outline. Each module is specified in detail just before it is built, using what the previous one taught us.

Can it start from our spreadsheets?

Yes. The spreadsheets usually describe the process better than any document. We use them to design the data model, then import what is in them so nothing is retyped.

What if we outgrow it?

Because it is ordinary code on an ordinary database, it can be extended, connected to other systems or migrated. Nothing is tied to a proprietary platform.

Show us one process. We will show you what it could look like.

The analysis is free, takes about an hour of your time, and ends with a written summary you keep.

Prefer to read first? See examples