Web applications
When pages are not
enough, you need
something that runs.
A website shows people information. An application does something with it. Accounts, records, a database that has to stay correct, rules that have to hold when somebody tries them, and a way for you to run the thing without calling me every week.
What people ask for
Usually one of these.
A customer area
People sign in and see their own records, orders, documents or history. Roles decide who sees what, and the check happens on the server where it cannot be edited from a browser.
An internal tool
The thing currently living in a spreadsheet that three people edit at once. Turned into something with a database behind it, so two people cannot overwrite each other.
A dashboard on live data
Numbers pulled from somewhere else on a schedule, cached, and reconciled so the figures on screen still agree with each other an hour later.
Scope
What a build includes.
The front
- Interface drawn for this product, not a template
- Sign in, sign up, password reset, the whole path
- Dashboards, tables, charts, live state
- Mobile from the first screen, not bolted on at the end
The back
- Database design, and migrations to change it safely later
- Accounts, sessions, roles and access rules
- Server side validation of anything worth faking
- Scheduled jobs, outside data feeds, notifications
- Admin tools so you can run it without calling me
- Backups, and a way to restore from one
How it is priced
One call, a written scope, one number.
No hourly billing. If the scope changes you approve a new number first.
- Thirty minute call, free, no obligation
- A written list of what is being built, and what is not
- One fixed price for that list
- A link you can open any time to see where it actually is
Anything touching real funds, trading or custody needs your own legal advice before it goes live. I will say so every time it comes up.
Tell me what it has to do.
A paragraph is enough to start. If it is not something I should build, you will hear that on the first call.