Custom web applications

What it is

Software shaped around a process that already exists: a client portal, a quoting calculator, a submission and review queue — with its own data model, permissions and record of what happened.

Why businesses need it

A quote model, an approval chain or a document handover rarely fits a generic product, and the gap ends up in spreadsheets and email threads where the record is lost.

What MIWEBX delivers

• Client and partner portals built around an existing service
• Quoting, costing and eligibility calculators with the rules exposed
• Multi-step workflow applications: submission, review, approval, handover
• Operational dashboards over data no reporting tool has access to
• Document-collection and data-entry tools that replace shared sheets
• Add-ons to a platform whose vendor will not build the feature

Core features

• Roles and permissions modelled on who performs each step
• Status history and audit trail held on every record
• File upload, versioning and retention rules per document type
• Calculation rules an authorised user can edit and re-run
• Bulk actions and imports for work staff already do in sheets
• Notifications and digests tied to state changes, not to a schedule alone

Technical capabilities

• Domain model written down before the schema; each screen maps to one aggregate
• Permissions enforced in the query layer and re-checked on every mutation
• Long-running work moved to a job queue with retries and visible progress
• Validation shared between browser and server from one typed definition
• State changes appended to an audit table rather than overwritten in place
• Tests built from the client's own edge cases, kept as fixture data
• Staging seeded with production-shaped volumes before the first user session

How we build it

• Walk the process with the people running it and write down every state a record passes through
• Model the data and the permissions, then agree the screens against that model
• Build the thinnest slice that crosses the whole flow and put it in front of the users
• Round out the workflow, import the existing records and add the audit trail
• Run the application and the old method in parallel, then retire the spreadsheet
• Hand over source, schema notes and the plan for the next iteration

Technology stack

• React
• TypeScript
• Node.js
• Fastify
• PostgreSQL
• Prisma
• Redis
• Docker

What you receive

• The application, deployed on infrastructure the organisation controls
• Schema, migrations and the imported data with a note on what did not map
• Roles and permissions explained per team
• A plain-language description of every workflow rule the build encodes
• Source repository, pipeline and the agreed next iteration

Business benefits

• The process keeps its record instead of leaking into email threads
• Staff stop maintaining the same fact in three spreadsheets
• Rules a manager can read and change, rather than a formula nobody understands
• Work in progress is visible without anyone asking for an update