service
Web application development
A business building something its customers log into: a portal, a platform, a marketplace or a SaaS product with real users and real data.
What you get
- An application architecture sized to the actual user count rather than to an imagined future.
- Authentication, permissions and data handling designed for the data you will hold.
- Staged delivery you can use and react to before the whole thing is finished.
- Monitoring and error reporting from the first release.
How this differs from custom software
The audience is the difference: staff you can train versus customers you cannot. Public-facing software needs account recovery, abuse handling and support paths that internal tools do not.
How we approach it
- We separate the parts that must be fast and always available from the parts that can be slower, because treating everything the same is what makes applications expensive to run.
- Authentication, permissions and audit trails are designed before the first feature, since retrofitting them rewrites every screen.
- We test the failure paths — expired sessions, duplicate submissions, lost connections — not only the successful ones.
What is out of scope
- Pretending a small product needs enterprise architecture. It usually needs less, and the cost of over-building is paid every month.
- Guaranteed uptime figures we have no operational history to support.
How it is priced
Cost is driven by the permissions model and the number of distinct user roles, because those decisions reach into every screen.
See the pricing page for how that works in practice.
How to start
The first conversation is free and usually takes half an hour. Bring the problem as you experience it — what is not working and what you have already tried.
Tell us what you need
The more specific you are about the problem, the more useful the first reply will be. We read every enquiry ourselves.