Custom Web Applications
The tool that does not exist yet. Internal applications that replace spreadsheets and email chains, and customer-facing applications that are part of your product. Built on proven frameworks, delivered in working slices you can test from week two, and documented so anyone can take it over.
What you get
- A scoping phase with a fixed price: user stories, data model, screens, risks, estimate
- A working first version of the most important flow within the first weeks
- Weekly demos of real software, and a shared board where you see what is next
- Roles and permissions, audit logs, backups, monitoring, and security testing sized to the risk
- Repository, documentation and deployment scripts handed over; you own everything
- A support retainer after launch, so the application keeps up with your business
Typical applications we build
- Operations tools: planning, dispatching, inspections, checklists, approvals
- Customer-facing tools: configurators, calculators, booking, self-service
- Data tools: imports, validation, reporting, connections between systems
- Management platforms for devices, vehicles, sites or assets, with dashboards and alerts
Boring technology on purpose
We choose frameworks and databases that are widely used, well documented and still maintained in ten years: PHP and JavaScript frameworks, PostgreSQL or MySQL, standard Linux hosting in the EU. Your next developer will know them. Clever and rare is a risk we do not take with your money.
Questions we hear often
How much does a custom application cost?
Scoping is fixed price and tells you the build price with a small range. Small internal tools start in the low five figures; platforms with many roles and integrations are quoted individually. The pricing page explains the model.
Can it run on our servers?
Yes, on your infrastructure, in your cloud account or on hosting we manage in the EU. We document the setup either way.
What if requirements change halfway?
They will, and the process expects it. Work is planned in short cycles; changes go into the next cycle with a visible effect on time and budget, decided by you.
Guides on this topic
What an automation is really worth once things go wrong
A worked example for calculating the true value of an automation: exceptions, checking, maintenance, net time saved, break-even and when to keep a person.
Paying for a website monthly or once: which model suits which company
The two ways to pay for a website compared: what each includes, who each suits, an illustrative 36-month comparison and what to ask before signing.
How long does it take to build a website, and what slows it down
How long a website takes by kind of site, in illustrative weeks, where the time really goes, what delays a project and how to bring the launch forward.
The spreadsheet has done its time?
A person answers within one working day. No obligation.