
A 17-module ERP that 250 people use every day
One system replacing a decade of parallel spreadsheets at Amazify, built module by module across 18 departments without stopping the business, and maintained as their web partner for four years since.
For growing businesses
When departments run on parallel spreadsheets, the fix is not another tool, it is a system built around how your business already works. I build it module by module, in production, without stopping the business.
17modules
Shipped on one platform
250people
Using it every day
18depts
On a single system
~100hrs/mo
Manual work removed by one agent
Sound familiar?
None of these are a software problem yet. They are the symptoms that say one is coming.
The same number exists in three spreadsheets and nobody is sure which is right.
Approvals live in email and WhatsApp, so nothing can be audited later.
Month-end means a week of re-keying and reconciling by hand.
A question that crosses two departments needs a person to go and ask.
You evaluated an off-the-shelf ERP and the implementation quote was larger than the problem.
Every new hire needs a week to learn which file is the real one.
The real cost
Three costs, in the order businesses usually notice them, which is the reverse of how much they matter.
Re-keying, reconciling and chasing is work that never appears on a project plan, because it is spread thinly across everyone. It is usually the single largest line item in the business and the only one nobody has measured.
When the report is assembled by hand on a Monday, every decision taken on Thursday is three days old. The cost is not the reporting effort, it is the choices made with the wrong picture.
If a process lives in one person's spreadsheet and one person's head, it leaves when they do. A system is also the cheapest form of documentation your business will ever buy.
The deliverable
Approvals, reporting and access control all follow from that. Nothing follows without it.
Today
After
How I build
This is the sequence that produced a 17-module platform used by 250 people across 18 departments.
Department by department, including the spreadsheets. Those files are free requirements documentation written by the people doing the work, and they are more accurate than any process document.
The module roadmap starts with whatever costs the most hours today, so the system earns trust before it gets large. Nobody has to believe a roadmap; they can see the first module working.
Each module replaces a specific set of spreadsheets and goes live in weeks. If it does not beat the spreadsheet on day one, it gets fixed before the next one starts.
Every entity lives once, with a clear owner and an audit trail of who changed what, which is what makes a number mean the same thing in two departments.
People see their own work first, managers see their department, leadership sees the roll-up. Approvals happen inside the system, so they can be found again later.
Every department goes live with training and a written guide. The system belongs to your team, not to the person who built it, that is a deliverable, not a promise.
A typical roadmap
Indicative, not a template, the order comes from your map, not from mine.
One department stops re-keying. The business sees a working module before committing to the rest.
The handoffs around that module move inside the system, so the data stops being re-entered at the boundary.
Requests stop living in email. Leadership reporting runs on live data instead of a weekly assembly job.
Adoption is no longer a fight, by now departments ask to be scheduled rather than being scheduled.
Scope of one module
Not a prototype that someone else has to finish. If any of these is missing, the module is not done.
Be honest about it
If your processes are genuinely standard, buy the product and spend the money elsewhere. I will tell you that on the call.
| Custom build | Packaged ERP | Stay on spreadsheets | |
|---|---|---|---|
| Fit to your unusual processes | Built around them | Expensive customisation | Perfect, that is why they exist |
| Time to first working thing | Weeks | Months to a year | Already here |
| One source of truth | Yes | Yes, if adopted | No |
| Audit trail and approvals | Built in | Built in | None |
| Cost shape | One-off build, small running cost | Licence per user, forever | Hidden, paid in hours |
| Survives someone leaving | Yes | Yes | No |
| Who it suits | Processes that are genuinely yours | Standard processes, willing to change | Small teams, low volume |
Proof

One system replacing a decade of parallel spreadsheets at Amazify, built module by module across 18 departments without stopping the business, and maintained as their web partner for four years since.

A review-backed agent that reads, classifies and files the records a team used to copy by hand, with a human check on anything it is unsure about.
Getting started
Days 1–10
I sit with the departments and watch the work. You get a written map of every manual step and a ranked list of what it costs.
Days 10–20
We pick the first module together, and you get a fixed price, a fixed date and a module roadmap for the rest.
Days 20–90
The first module goes into real use with real data, gets fixed based on what people complain about, and the second one starts.
Investment
That is the starting point for a multi-department build, paid per phase rather than up front. You get a fixed quote after the mapping, before anything is built, and the mapping is useful even if you stop there.
What you get
Included
Questions
Off-the-shelf works when your processes are standard and you are willing to change them. Mid-sized businesses usually have one or two processes that are genuinely theirs, and that is exactly where packaged systems force expensive customisation, which you then maintain forever against an upgrade path that breaks it.
The first module is usually in real use within weeks, not at the end of a year-long programme. That sequencing is deliberate: it is what keeps the project from dying in month six, and it means you can judge the work before committing to the rest.
Migration is part of each module, not a phase afterwards. Each module launches with the existing data already in it, because a system that starts empty does not get used.
No. Modules go live one at a time, and the old spreadsheet stays available as a safety net until the department stops reaching for it. Nothing is switched off on a big-bang date.
That is partly the point of shipping something narrow first. A wrong assumption found in week five costs days to fix. The same assumption found at the end of a twelve-month programme costs the programme.
You do. The handover includes the code, the deployment, the documentation and the training. There is no part of the system that only works while you keep paying me.
Hosting and any third-party services, which for a system of this size is usually a small monthly figure rather than per-user licensing. Ongoing support from me is optional and priced separately.
Yes. I work across Gulf business hours from Dubai, with the same direct working relationship, no account layer between you and the person building the thing.
Next step
Thirty minutes to map the process that costs you the most hours, and an honest answer on whether custom is the right call.