Service 05
Portals and internal tools for work a website cannot do
Booking, records, admissions, inventory, quoting, and the dashboards that sit behind them. We map the process you run today, cut the steps nobody needs, and build the rest.
Why people call us about this
The spreadsheet worked until it did not
Three people edit the same file, one keeps a local copy, and the monthly report is rebuilt by hand. Nobody knows who changed what, and onboarding a new staff member takes a week of shadowing.
- Data lives in several files that disagree with each other
- Reports are rebuilt by hand every month
- No record of who changed a number, or when
- Everyone has access to everything
What you get
What a software project includes
We build for the staff who use it daily, and their job titles decide the permissions.
01
Process mapping
We sit with the people doing the work and write down the real steps, including the workarounds.
02
Roles and permissions
Access modelled on actual job titles, so a bursar and a lecturer do not see the same screens.
03
Audit trail
Every change logged with who, what, and when, which matters the first time a number is disputed.
04
Data migration
Your existing spreadsheets imported and reconciled, with a report of what did not match.
05
Reporting
The reports you currently build by hand, generated on demand and exportable.
06
Training and docs
Sessions per role, short written guides, and a recording for people who join later.
Typical timeline
Ten to sixteen weeks for a first working version
We aim to get one department live early rather than everything at once.
Step 01
1 to 2 weeks
Map
Interviews, the current process on paper, and a scope that says clearly what version one does not do.
Step 02
2 to 3 weeks
Design
Screens per role, reviewed by the people who will use them every day.
Step 03
6 to 10 weeks
Build
Two-week cycles on a staging environment, with a working demo at the end of each.
Step 04
2 to 3 weeks
Roll out
Data import, training per role, one department live first, then the rest.
This service, in the wild
Systems we designed, built, and support
Open a project to read the full story.
Software Development
Academic platform, nursing and midwifery colleges
Scholarium
Admissions, fees, results, and transcripts in one multi-college portal with role permissions and a full audit trail.
Catalogue and admin
Retail, Uromi
Computer accessories store
Stock catalogue, cart, printing service intake, and a staff admin built around how the shop already ran.
Tools and platforms
Our usual stack
Standard, boring, well documented tools. Your next developer will recognise all of it.
Laravel
Node.js
PostgreSQL
React
Docker
Automated backups
Placeholder quote, replace with a real client
The audit trail settled a fee dispute in about two minutes. Before this we would have spent a day going through receipts.
Placeholder name
Bursar, placeholder institution
Questions we get asked
Software questions
Can you build on top of what we already use?
Usually. If your accounting or CRM works, we connect to it rather than replace it. Replacing a working system is expensive and rarely necessary.
Who hosts it?
Your own cloud account by default, so the data and the bill are yours. We can host it for you if you prefer, and you can move it later either way.
What if our process changes?
It will. We build the parts that shift most as configuration rather than hard-coded rules, and retained clients get a set number of development days a month for changes.
How do you handle data protection?
Least-privilege roles, encrypted connections, backups tested by restoring them, and a log of who accessed what. For schools and clinics we go through your policy requirements at the planning stage.
Previous service
Next service
Outgrown the spreadsheet?
Send us the file and tell us who edits it. We will come back with what a first version should cover and what it costs.