How it works
A loop, not a project.
You don’t commission a system and wait for it. We agree a change in a session, it’s built, it goes live, and the next session starts from there. Design, Build and Operate are one service, run by one team, and one monthly fee covers all three.
DesignJonathan Pincassessions and specification
AI writes the code. The hard part is knowing what to build.
An ERP system encodes decisions about your business: how stock is valued, when revenue is recognised, who approves what, and what happens when an order goes wrong. Get those right and the software follows. Get them wrong and no amount of code will save it.
Jonathan meets you regularly, normally once a fortnight. You walk him through how the business really works, including the exceptions and workarounds that never make it into a requirements document, and together you decide how the system should handle them. Often that means questioning how something is done today, not just copying it. He brings twenty years in ERP, from large platforms such as NetSuite to Pakk, his own ERP and ecommerce platform, across accounting, inventory, ordering, logistics and compliance.
Sessions run on a meeting tool we built for this. An AI assistant follows the conversation, already knows your system as it stands, and keeps a shared list of what’s been agreed. Nothing is marked as agreed until Jonathan confirms it. Afterwards, the decisions become a precise written specification in your business’s own language, and over time those specifications become a complete record of why your system works the way it does.
UK requirements, including Making Tax Digital, are part of the design from the start rather than added later.
BuildAllan Clarkthe pipeline and every build
A platform built for ERP, not for everyone.
Allan, an engineer and computer scientist for decades, runs the pipeline that turns each agreed specification into working, deployed software, on a platform we’ve built and maintain: a deliberately chosen technology stack, and an automated pipeline engineered for ERP.
The pipeline turns each specification into a structured build plan and holds the AI to automated quality checks it can’t talk its way past. Independent AI reviewers then audit every piece of work without seeing how it was produced. Nothing reaches your system until it passes. Changes go live shortly after they’re agreed, not at the end of a project phase, and as AI improves, so does the pipeline.
- SpecificationAgreed in a session
- Build planBroken into steps
- AI buildCode generated
- Quality gatesAutomated checks
- Independent reviewAI reviewers audit the work
- LiveIn the running system
| Technology | Why it’s there |
|---|---|
| Go | Fast and dependable. It compiles into a single self-contained program, so there’s little to go wrong. |
| SQLite | Among the most thoroughly tested software ever written. Your whole database is one file you own, supported until at least 2050. |
| React and TypeScript | The most widely used interface technology, so developers who can work on it are easy to find. |
| Open source | Throughout. No vendor lock-in, no subscriptions underneath, and nothing stopping another developer taking over. |
OperateThe teamJessica Perez on support and testing
Run for you, properly.
Once your system is live, keeping it running is our job. You don’t need an IT department or a hosting contract of your own, and the people looking after it are the ones who built it. Jessica is your first port of call: she has set up and run small businesses herself, and knows what it costs when a system gets in the way of the day.
- Hosting
- Professional servers in European data centres, with encrypted connections as standard.
- Backups
- Multiple independent copies, kept over different periods and in separate locations, including off-site. No single failure can take your records with it.
- Monitoring
- The system is watched continuously, errors are logged, and problems raise alerts. We usually know about an issue before you do.
- Updates
- Features, fixes and security updates go live through the same pipeline, without disruptive upgrade projects.
- Incidents
- Handled by the team that built your system and knows your business, not a support queue reading from a script.
- Support
- Questions and problems go to Jessica, who knows your system and works with the rest of the team to resolve them.
- Client testing
- Jessica works through changes with you as they arrive, so you know each one does what was agreed.
Getting started.
There’s no long discovery phase before anything happens. The first release follows the first sessions.
- 1
First call
A call with Jonathan about your business: what isn’t working, what you’ve tried, and what good would look like.
- 2
First sessions
Regular sessions begin, normally fortnightly. The first ones map how your business runs today and agree what the system should do first.
- 3
First release
The first agreed specification goes through the pipeline and goes live. From then on, each session starts from the system as it stands.
What’s included.
From £1,500 a month + VAT
Design, Build and Operate together, never à la carte.
Run by the three people who built Pakk and ran it together for ten years.
- 26 sessions a year, normally fortnightly, each up to 90 minutes, plus the specification and build that follow.
- Every build and release, through the pipeline’s quality gates and independent review.
- Hosting, backups, monitoring, updates and support. Hosting and backups are charged at cost, with no markup.
- A 12-month term.
- You own your code, specifications and data from day one, and get the full codebase if you leave.
Questions.
Can we buy just the build, or just the hosting?
No. Design, Build and Operate are one service. The specifications agreed in sessions are what the pipeline builds, and the team that built your system is the one that runs it. Keeping them together is what lets a change go live shortly after it’s agreed.
What does it cost?
From £1,500 a month + VAT, on a 12-month term. That covers 26 sessions a year, the specification and build that follow each one, and running the system. Hosting and backups are charged at cost on top, with no markup.
How quickly do changes go live?
Shortly after they’re agreed in a session, not at the end of a project phase. Each change goes through the pipeline’s automated quality checks and an independent review before it reaches your system.
What do we own?
Your code, your specifications and your data, from day one. Your data sits in a single database file that belongs to you, and if you leave, you get the full codebase.
What is it built on?
Go, SQLite, React and TypeScript: proven, open-source technology throughout, with no licence fees underneath and no vendor lock-in. Every system is built from the same tested modules; the platform page lists them.
Who do we deal with day to day?
Jonathan runs your sessions and writes your specifications. Allan runs the builds. Jessica handles support and tests changes with you. Meet the team.
Can we rely on a small team?
Yes, and you’d be in safe hands. The three of us spent ten years building and running Pakk, an all-in-one commerce and operations platform with double-entry accounting at its core, handling millions in client turnover. Jonathan has twenty years in ERP, including large platforms such as NetSuite. Allan has decades of experience as an engineer and computer scientist. Jessica has set up and run small businesses herself. And you own your code, specifications and data from day one, so you’re never locked in to us.
Start with a call.
Tell us what isn’t working, and we’ll tell you how the first sessions would go.
Or email info@frictionlesserp.com.