$1,800
Entry scope. Core build, one role set, standard reports and exports.
View this packageMost companies outgrow their spreadsheets long before they replace them. A web platform built to your own process puts the same data in front of everyone who needs it, with permissions that match how the business is actually organised.
| Queue | Open | Overdue | Owner |
|---|---|---|---|
| Approvals waitingAbove branch limit | 7 | 2 | Finance |
| Client requestsSubmitted this week | 34 | 5 | Accounts |
| Documents to verifyUploaded by clients | 18 | 0 | Compliance |
| Reports scheduledMonday, 09:00 | 6 | 0 | Automated |
This is the baseline every platform starts from. What makes it yours is the process modelled on top of it, which is written down in the scope before anyone writes code.
Users, roles and per-screen permissions, enforced on the server rather than by hiding buttons. A branch manager sees their branch, an owner sees all of them, and neither can reach the other's data by editing a URL.
The entities your business runs on — clients, jobs, assets, applications, whatever the domain is — with validation at the point of entry so bad data never reaches the database.
The stages a record moves through, who may move it, and what must be true before it can advance. Approvals above a limit wait for a named person instead of proceeding quietly.
Files attached to the record they belong to, with type and size checks, stored outside the web root so a direct link cannot expose them to someone who should not have them.
Every list filterable, sortable and exportable to CSV or PDF, and fast on a large table because the query is indexed rather than because the table is small today.
The figures management actually asks for, on one screen, each one clickable through to the records behind it so a number can always be explained.
Email and WhatsApp alerts on the events that matter, scheduled summaries, and reminders on anything overdue, so the system chases rather than a person remembering to.
Who changed what, when, and what the value was before. Non-negotiable once more than two people share a system, and far easier to build in than to add afterwards.
One file everybody edits, nobody can audit, and two people have open at once. Becomes records with owners, permissions and a history of every change.
Customers emailing for a status that is already in your system. A portal shows them their own records, and stops the phone ringing for information you already hold.
Figures copied from several screens into a deck every month. Generated from the same data the screens use, so the numbers cannot disagree with each other.
An off-the-shelf product that fits eighty per cent and blocks the other twenty. Rebuilt around your process, with the source code handed over so you are never blocked again.
These are the figures a build of that shape starts at. Beyond them an engagement is quoted as one fixed figure against an approved scope, so the price does not move unless the scope does.
Entry scope. Core build, one role set, standard reports and exports.
View this packageExtended scope. Several modules and roles, an integration, and full reporting.
View this packageQuoted against your approved scope. Multi-site, multi-role or integration-heavy programmes.
Request a quotationFigures are entry prices in USD, exclusive of taxes. Hosting, gateway charges and third-party services are recharged at cost. Basic and Premium figures are clickable: they open the product page, where the full module list and the buy buttons are. See all products.
Because you have to live with it after we hand it over. PHP, MySQL and React run on ordinary hosting, cost little to keep online, and can be picked up by any competent developer in this market without a specialist search. A fashionable stack that nobody local can maintain is a liability disguised as a feature.
Yes, in full, including the database schema. There is no licence, no per-user fee and nothing that renews. At handover you receive the source, the database and the deployment notes, and you are free to take it to any other developer. We would rather be kept because the work is good than because leaving is difficult.
Every screen is built to work on a phone, because in practice that is where approvals and lookups happen. Heavy data entry is still better on a desktop, and where a screen is genuinely desk work we say so rather than pretending a twenty-column grid is comfortable on a handset.
State who uses it, what each of them may see, and the decisions it has to support. You receive a written module specification and a fixed price in return.
Submitting your enquiry