User accounts
- Different access to features and data for staff, managers and administrators
- Several companies in one system, with their data kept apart
- A record of user actions and changes to data
- Bulk onboarding and invitations
Web applications
I build web applications for the way your company works.
Accounts and roles, operational panels, reporting, and integrations with the tools your team already works in. Deployment and what happens after it are part of the project from the start. Scope and date depend on how many roles and systems are involved, and I give them once you have described your process.
Features for your application
We choose the features your team needs. These are examples of areas I can bring together in one system.
Data and reports
- Organising and moving data from your old system
- Views showing the information each group of users needs
- Reports, exports and summaries
- Search across content and across meaning
Integrations
- APIs of the systems already in use
- CRM, email and spreadsheets
- Payments and documents
- Webhooks and event queues
Launch and ongoing support
- Launch on the target domain
- Monitoring and backups
- Admin panel handed to the team
- Development after release
How the work runs
Five stages, the same ones every project here goes through. Each ends with something you are handed.
Understand
I write down the process, the data and the roles before choosing any technology, and you get a scope and a date out of it.
Design
I design the main screens and how the data will be stored, then check that users can complete their tasks.
Build
You try the first working version at a test address. I add further features after your feedback.
Ship
Launch on the target domain, with the data migrated, monitoring switched on and the admin panel handed to your team.
Run it
After release I monitor the system, fix what breaks and add the next modules.
Scope and pricing
What sets the scope
A dashboard showing one team the numbers it already has is a different job from a platform with roles, payments, exams and certificates. The number of roles, the number of integrations and how much data has to come off the old system set the scope and the date. You can click through a first working version before the further modules are built.
When it is not worth building
If the process fits in a spreadsheet and an off-the-shelf SaaS, and the only reason to build is wanting something of your own, I say so. Sometimes the cheaper answer is an integration between two tools you already pay for, and then I propose that.
Selected work
Projects you can see running. Each write-up shows what was built and how it works.
Application quote
Say what the application should do and who will use it. I reply with a price range, or with the questions that have to be answered first.
