CRM and ERP Development
A CRM holds the people; an ERP holds the things; the business lives in the gaps between them. The lead that became an order was re-typed; the order that became a delivery was re-typed again; the delivery that became an invoice waited for someone to notice. Most of what we are asked to build is the connection between those steps.
We build CRM and ERP systems around the way a particular business runs, and we connect them to what already exists: the online shop, the accounting package, the warehouse scanner, the WhatsApp channel customers actually use. Before writing code we will say whether a product you can buy would do the job.
The parts, built in the order that pays back first
Nobody needs all of these on day one. Discovery puts them in order by how much re-typing each one removes.
Leads and pipeline
Every enquiry from the website, the chat, the phone and the shop in one list, with a stage, an owner and a next action that is overdue when it is overdue.
Quotes and orders
A quote built from your price rules, turned into an order with one action, with the approvals your margins require.
Stock and purchasing
What is on the shelf, what is promised, what is on order. Reorder points that raise a purchase order for a person to approve.
Production and jobs
Work orders, stages and the people on them, so a customer's "where is it?" has an answer.
Delivery and field work
Routes, proof of delivery and a mobile app for the people who are never at a desk.
Customer service
Tickets from email, chat and WhatsApp against the customer's history, with a chatbot that answers the routine questions and hands the rest to a person.
What it connects to
The value is in the joins. These are the connections most builds include.
Online shop
Orders from WooCommerce, Shopify or Magento arrive as orders, not emails. Stock and prices flow back the other way.
Accounting
Invoices and payments posted to the ledger you keep, by API or file exchange. The accountant stops re-keying.
Mobile app
A small app for sales visits, deliveries or stock counts, working offline and syncing when it can.
Chat channels
WhatsApp, web chat and email as one queue, with automation for order status, appointment reminders and document requests.
Partners and marketplaces
Supplier portals, courier APIs and marketplace feeds, each with a log of what was sent and what came back.
The systems you keep
Old applications stay in service while the new system takes over one function at a time. See software modernisation for how.
How a CRM or ERP build runs
Four stages. Stop after whichever one you like and keep what exists.
Discovery
We sit with the people who do the work and map the process as it is, re-typing included. You receive a scope, a data model, a module order and a cost range.
First release
The one module that removes the most re-typing, built in two-week cycles, used by real staff while the old method still runs beside it.
Next modules
Each added when the previous one is in daily use, with its integration and its migration of data.
Running it
Hosting, monitoring, backups and changes, on a retainer with us or handed to your team with the documentation to do it.
What we build it with
Boring on purpose. Another team can maintain it.
- Application
- PHP / LaravelNode.js.NETPython / Django
- Front end
- ReactVue.jsTypeScript
- Mobile
- FlutterReact Native
- Data
- PostgreSQLMySQL / MariaDBRedis
- Integration
- REST and webhooksQueuesShop and courier APIs
What a CRM or ERP costs
Our rates are published. Pick the role and move the sliders for an indicative budget.
Rate card
| Role | Hourly | Monthly* |
|---|---|---|
| Frontend / WordPress | $30 | $4,800 |
| Backend / API | $32 | $5,120 |
| Full-stack | $35 | $5,600 |
| Mobile (React Native / Flutter) | $35 | $5,600 |
| DevOps / Cloud | $40 | $6,400 |
| AI / Automation engineer | $45 | $7,200 |
| QA / Test engineer | $25 | $4,000 |
| UI / UX design | $28 | $4,480 |
*160 hrs/month full-time. Rates are indicative for planning, in USD (other currencies are converted at an indicative rate), and depend on seniority, contract length and timezone overlap. Longer engagements and multi-role teams are discounted — ask.
Build it, or buy one?
Building makes sense when
- Your process is the reason customers choose you, and products bend it into their shape.
- You have tried a product and the gaps live in spreadsheets and WhatsApp groups.
- You need the shop, the warehouse and the customer history to be one record.
- A person on your side can spare a few hours a week for questions.
Buy a product instead when
- Your process is standard and a product fits with configuration alone.
- You need it live next month.
- Nobody in the business has time to be involved.
- The budget covers the build but not the years of change after it.
Before you commit
Should we buy a product and customise it instead?
Often, yes, and we will say so at discovery. A build makes sense when the product is being bent so far that the customisation costs more than the software.
Can you connect it to our shop and our accounts?
Yes. Shops expose APIs; most accounting packages offer an API or a file exchange. Each connection is logged so a failed sync is visible, not silent.
Can staff use it on the road?
Yes. A mobile app for the few things field staff need, working offline and syncing later, is usually a small part of the build.
What about the chatbot?
It answers routine questions from your own data, order status, opening hours, document requests, and hands anything else to a person. It never moves money or changes an order on its own.
Can you take over a CRM or ERP someone else built?
Yes. We start by reading the code and the data and writing down what it does; then we agree the first fix. The first weeks go on investigation, not new features.
What does it cost?
Each role on the job is billed by the hour at its published rate. Discovery gives a cost range for the first module so you decide with numbers in front of you.
Tell us where the re-typing happens
What your business sells, which systems you run today, and where the same information is entered twice. No customer records or credentials; we sign an NDA before those change hands. We reply within one business day.