App and web app developmentThe note on the wall is not a system.
We build the thing that replaces it.
Applications for processes that currently run on paper, spreadsheets and shouting across the room.
What this is about
Most companies have a process everyone knows and nobody has written down. That is exactly where duplicated work and follow-up questions come from. We turn it into an application that works on a phone just as well as on a desktop, and leave out everything you would never use.
- We map the actual process, not the intended one
- A web app that runs on any device without installation
- Roles and permissions for team, office and field staff
- Exports in formats your accounting already knows
- Training for the whole team, not just for management
Process
The note on the wall is not a system.
01
Shadowing
We look at how the process really works today, detours included.
02
Prototype
You get a clickable version before we touch a database.
03
Build
We build in short cycles and show every interim state in the real workplace.
04
Rollout
One area first, then the rest. The old way stays open until the new one holds.
Frequently asked questions
What clients ask us first.
What is the difference between a web app and a mobile app?
A web app runs in the browser on phone, tablet and desktop, without installing anything from an app store. A classic mobile app is installed through the App Store or Google Play. For processes inside your own company a web app is usually enough: everyone can use it straight away, and updates need no approval from a store.
Which processes are worth their own app?
For processes everyone knows and nobody has written down: jobs, timesheets, material lists or handovers between office and field staff. Wherever paper, spreadsheets and follow-up questions carry the work today, duplicated effort and mistakes follow. We map exactly that process and leave out everything you would never use.
How does app development work?
First we shadow the process and see how it really works today. Then you get a clickable prototype before we touch a database. We build in short cycles and show every interim state in the real workplace. Rollout starts in one area, and the old way stays open until the new one holds.
How much does an app cost?
That depends on the scope. Once we have mapped the process, we define what the first version has to do and what can wait. You get a fixed price and a fixed date for it in the quote, no day rates.
Tell us what you have in mind.
In a first call we settle in ten minutes what this is about and what it costs.
