Package
An operations app for the workflow your team runs on
Pick the workflow that costs your team the most time. We turn it into a web application with proper records, roles, permissions and an audit trail.
What the package is
An operations app replaces the spreadsheet, inbox or group chat that one core process has outgrown. A tracker that four people edit at once. Jobs assigned in WhatsApp and lost when the conversation moves on. An inbox doing the work of a database. Each one has a workaround, and each one costs time in double entry, chasing and checking.
We build that one workflow as a web application. Your records, screens and rules sit on a standard foundation of sign-in, roles, permissions, audit logging, exports and file handling, so the effort goes into your process. Your team uses it on a laptop in the office or a phone on site, and your current data is imported before launch.
Signs you need this
- A critical spreadsheet that someone keeps a private copy of, because the shared one keeps breaking
- Jobs, approvals or requests assigned in a group chat, with no record of who agreed to what
- The same details typed into two systems because they do not share data
- A weekly report that takes someone half a day to assemble by hand
- No quick answer to "where is this up to" without asking three people
- A process that only works because one long-serving person holds it in their head
What’s included
Included
- A workshop with the people who run the workflow, mapping each step, role and exception
- A written scope listing every screen, role, rule and integration before the build starts
- The web application, with sign-in, roles, permissions and an audit log of every change
- Import of the live data from your current spreadsheet or system
- CSV and Excel export, file and photo upload, and email notifications on key events
- Training for your team, and documentation written for the people who use it
- Deployment to hosting in your name, with backups, monitoring and TLS configured
Not included
- Native iOS and Android apps. The application works in any phone browser without an app store
- Migrating years of archived records, which is separate work from importing your live data
- A second workflow. Each one is scoped on its own once the first is running
- Accounting, payroll and statutory filing, which stay in the software you already use
- Requirements raised after the scope is agreed, until they are written up and added to it
How it runs
Scoping
We walk through the workflow with the people who run it, record the exceptions and agree a written scope covering every screen, role, rule and integration.
Data model and core screens
We shape your records and the rules around them first, so you can click through the main screens with your own sample data early in the build.
Workflow and permissions
Statuses, permissions, notifications and the awkward cases come next. Your team tests each part in a working environment and we adjust it from their feedback.
Launch
We import your live data, train your team, configure hosting, backups and monitoring, and move the workflow over from the old spreadsheet or chat.
What the foundation covers
Every operations app starts from the same tested foundation: sign-in and password reset, roles and permissions, an audit log, search and filtering, file and photo upload, email notifications, CSV and Excel export, and hosting with backups and monitoring. None of that is specific to your business, so it is configured, not rebuilt. The build effort goes into your data model, your screens and the rules that make your process yours.
Choosing the first workflow
Start with the workflow that costs the most time or causes the most errors. Good candidates share three traits: several people depend on it, it holds live data, and the business would be disrupted if that data were lost or wrong. A single workflow keeps the scope clear and gives your team one new system to learn. Once it is running, the next workflow builds on the same foundation and data.
Common questions
What kind of workflow suits an operations app?
A workflow that several people share, that holds live data and that currently runs on a spreadsheet, inbox or group chat. Job tracking, approvals, stock requests, bookings, compliance checks and client onboarding are typical examples. If the process is used by one person for analysis or modelling, a spreadsheet is usually still the better tool.
What does it cost?
The cost depends on the number of screens, roles and integrations, and on how much cleaning your current data needs. We send a written scope and a cost range after a first call, so you can see exactly what is included before you decide to go ahead.
What if we need more than one workflow?
Start with the one that costs the most, then add the next once the first is in use. Each later workflow reuses the same sign-in, roles, data and hosting, so it is quicker to build. Your team also learns one system at a time, which makes adoption easier.
Who owns the application after launch?
You do. You own the code, the data and the IP, and the hosting account is in your name. After launch we can keep it hosted, monitored and updated, or your own team or another developer can take it over with the documentation and access we hand across.
Is this an AI product?
No. It is a conventional web application with forms, records, permissions, notifications and reports. The problem it solves is the lack of a shared system, and ordinary software handles that well. If automation or AI becomes useful later, for example to read incoming documents or draft replies, it can be added to the application you already have.
Start a project
Planning something like this?
Share what you need and where things stand. We usually reply within one business day.
Or email [email protected]