Custom management software

What it is

The one-off build for a process packaged software will not hold: a case desk, a production schedule, an inspection routine, a fee or allocation model. Built to the shape of the work, and deliberately kept editable by whoever inherits it.

Why businesses need it

Packaged software asks the business to bend around it. When that process is the reason customers arrive, bending costs the advantage. When the process is merely awkward, custom work is the wrong spend — and saying so is part of the job.

What MIWEBX delivers

• Process discovery and a written model of how the work actually moves
• A web application for the team, with a role and a queue for each step
• Retirement of the shared drive, whiteboard or sheet that became software
• Validation placed at the point where the mistake is made, not at reporting
• Feeds into the accounting, mail and tooling the system has to work beside
• Continued change as the process itself moves

Core features

• Screens organised by the task, not by the tables underneath
• Statuses and handoffs defined so work cannot sit in limbo
• Bulk actions for the steps people repeat through the day
• Printable and exportable output for the documents the process produces
• Notification by mail or message when work lands on someone
• Configuration an administrator can change without a release, where that is safe

Technical capabilities

• A small, conventional stack chosen so a local developer can take it over
• Schema documented with the reason each table exists
• Tests around the rules that cost money when they break
• Configuration held in the database or the environment, not baked into screens
• Migrations run as reviewed code rather than edited directly on a server
• Error and usage logging that names the record involved, not only the request
• A maintenance note listing what to change when the process changes

How we build it

• Shadow the process for a day before writing a specification.
• Agree the vocabulary: every record, status and role named once.
• Build the shortest path that replaces the worst part of the day.
• Put it in front of the real users and change what they refuse to use.
• Add the reports, permissions and feeds the system now makes possible.
• Hand over the repository, the documentation and a maintenance plan.

Technology stack

• React
• Next.js
• TypeScript
• Node.js
• PostgreSQL
• Prisma
• SQLite
• S3-compatible storage

What you receive

• The application running on infrastructure the client owns
• Source repository with migration history, tests and a readable README
• Written process model reflecting the rules as they now stand
• Administrator training so routine changes do not come back to us
• A support and change plan for the period after launch

Business benefits

• The system follows the process instead of the reverse
• No licence paid for functions that were never used
• Changes take days because the code was written to be changed
• Know-how held in the system rather than in one experienced person