ERP & CRM Systems

A custom CRM starts at $18,000, currently $11,500 under our launch offer until 31 October. Most land between $18,000 and $45,000 depending on how many workflows it covers and how many systems it connects to. A simpler client portal starts at $10,000. You get a firm fixed number after the two-week discovery stage, because a number given before anyone has mapped the process is a guess wearing a suit.

ERP modules start at $25,000, and a system spanning sales, operations and inventory typically lands between $40,000 and $90,000. We do not take on full ERP replacements above $150,000. Because we build in modules, you can start with the one that hurts most rather than committing to everything at once.

Ten to twenty weeks for most projects, depending on module count. A single module can be live in ten. A system spanning sales, operations and inventory is closer to twenty. Because we build in modules, you can go live with the most urgent piece first rather than waiting for the whole thing.

Use the platform if it fits. Honestly. It is cheaper up front, faster to deploy, and somebody else maintains it. Build custom when one of these is true: the platform cannot support a process that is central to how you compete, per-user licence costs have grown enough that a build pays for itself within two to three years, you need something the platform roadmap will never cover, or you are stitching four subscriptions together to do one job. Bring the question to the scoping call. You will get an honest answer even when the honest answer means no project for us.

Often, yes, and it is frequently the cheaper answer. We can build on top of what you already run, add the modules the platform will not, and connect it to your other systems. Tell us what you have at the scoping call and we will price both routes so you can compare them side by side.

You do, both, completely. The code sits in your repository from the first commit, not ours. No licence fee, no per-user charge, nothing you need our permission to change. Move to another team whenever you like and everything they need is already in your hands.

Yes, and it is inside the project price rather than an extra. Spreadsheets, older databases, exports from whatever platform you are leaving. We clean and validate as we go and give you a reconciliation report before switchover so you can confirm the numbers match.

This is the most common reason custom systems fail, and it is the reason stage one puts us in front of the people who will use it daily rather than only the person paying for it. Systems built with the users tend to get used. Systems built at them tend not to. Two recorded training sessions are included, and we build in a feedback route so early complaints reach someone who can act on them.

Wherever you need it. We work across regions and build to the data location rules that apply in your market or sector. If you carry specific residency or sovereignty obligations, raise them during scoping and we will architect for them from the start.

Thirty days of support included at no cost, covering anything not working as specified. After that you can take a monthly retainer from $900, or take the system fully in-house. Both are genuinely fine. The documentation and handover are identical either way, because we would rather you stay by choice than by dependency.

You can. You pay for the stages completed, and you keep everything produced up to that point: the scope document, the designs, the code written so far, in your repository. There is no penalty clause and nothing is held back.

A written update every week and a shared board you can open at any time without asking us for a status report. If something slips you will hear it from us in that week's update, not at the end. Going quiet is the single most common complaint about development agencies and it is the easiest one to avoid.