ERP & CRM Systems

Software shaped around your business, not the reverse

Off-the-shelf ERP forces you to change how you work. For a large enterprise that trade-off can make sense. For a company of 5 to 100 people it usually means paying monthly for a system where you use a fraction of the features and fight the rest.

We build the system around your actual process — the one your team already follows, including the parts that only exist in someone's head or a shared spreadsheet.

What we build

• Inventory and stock systems — multi-warehouse, transfers, stock-taking, low-stock rules
• Order management — from enquiry through production to delivery, with status tracking
• CRM — customer records, communication history, follow-up reminders, sales pipeline
• Field-team apps — mobile-first tools for people who aren't at a desk, with offline tolerance
• Time and attendance — shift tracking, GPS check-in, hours reporting
• Reporting dashboards — the numbers your management actually asks for, not a generic template
• Document generation — invoices, delivery notes, contracts produced automatically

The technology

We build on React and TypeScript for the interface and Supabase for the backend — Postgres database, authentication, real-time updates and file storage. It can run on Supabase cloud or self-hosted on your own server, which matters if your data can't leave the country.

We've done both. For Stokomak we migrated a full stack to self-hosted Supabase on Hetzner — storage, realtime, edge functions and auth for 82 active users, with no data loss during the move.

Connecting to what you already have

A new system that ignores your existing tools creates more work, not less. We integrate with what's already running — POS systems, accounting software, WooCommerce stores, courier APIs and supplier feeds — so data flows instead of being retyped.

See Automations & Integrations for how we handle the connection layer.

How we scope it

ERP and CRM projects fail when they're specified in one giant document and built for six months before anyone uses them. We work in phases: the highest-value module first, in production and being used, then the next one.

That way you get value in weeks rather than quarters, and the second module is informed by what you learned using the first.

How we quote a system

Business systems vary too much for a published price to mean anything. A single-purpose internal tool and a multi-module system with inventory, orders and reporting are separate universes of work.

What we do instead is scope the first phase in detail and quote that fixed. You see real software in production within weeks, and the next phase is quoted once you've used the first one and know what you actually want from it. The scoping conversation is free.