Skip to content
Tayyab Hassan
← All case studies

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.

$20k/mo
Saved in subscriptions
17
Modules shipped
250
Daily users
4 years
Partnership
A 17-module ERP that 250 people use every day

The situation

Amazify had eighteen departments, each running on its own spreadsheets, shared drives and inboxes. Every number existed in three places and nobody could say which one was true. Month-end meant reconciling files by hand, and any question that crossed two departments needed a person to go and ask.

The business did not need "an ERP" in the abstract. It needed its own processes to stop depending on who happened to be at their desk.

What I built

A single internal platform, delivered as 17 modules, one department-facing workflow at a time, in the order the pain was worst. Each module replaced a specific set of spreadsheets rather than a textbook process, so adoption did not require anyone to relearn their job.

Across the platform:

  • One record, one owner. Every entity lives once, with a clear owner and an audit trail of who changed what.
  • Role-based access that matches the org chart. People see their own work first; managers see their department; leadership sees the roll-up.
  • Approvals inside the system. Requests stop living in email threads.
  • Reporting on live data. The numbers in a meeting come from the same place as the numbers in the system.

The modules cover finance, procurement, warehouse management, accounting, vendor management and sales data, among others, each one replacing either a set of spreadsheets or a paid tool.

How it was delivered

Shipping 17 modules at once would have failed. The rollout was sequenced:

  1. Map how the department actually works, not how the process document says it works.
  2. Build the narrowest module that removes the worst manual step.
  3. Put it in front of real users within weeks, not quarters.
  4. Fix what they complain about, then move to the next department.

Each department went live with its own training and a short written guide, so support questions dropped off quickly instead of landing on one person forever.

What it changed

250 people now work inside one system across 18 departments. Cross-department questions are answered by opening a record instead of chasing a person, and leadership reporting runs off live data rather than a weekly re-key.

The commercial result the client reports is over $20,000 a month saved in software subscriptions, the separate tools each department had been paying for now live as modules inside one platform.

What I would do next

Instrument the modules that still have manual steps left in them, and route the highest-volume ones to an agent-assisted flow, the same pattern described in the AI agent case study.

Summarize with AI

Screens

What it looks like.

A 17-module ERP that 250 people use every day, screen 1
A 17-module ERP that 250 people use every day, screen 2

Keep reading

Next step

Let's find the manual work in your business.

Thirty minutes. Bring one process that keeps breaking and we will map what it would take to automate it, whether or not you hire me.