Internal tools
The spreadsheet that grew past what a spreadsheet can do. Planning, quoting, stock, scheduling — whatever your team runs the business on.
Web app development
Internal tools, dashboards and customer portals. Custom software that does one job, scoped and handed over with the code.
What we build
Dashboards
Your numbers pulled from the systems that hold them, in one screen, updated without anyone exporting a CSV.
Customer portals
Somewhere for your customers to see their orders, documents and status without emailing your team to ask.
Integrations
The connection between the tools you already pay for, so a record entered once does not get typed in three more places.
How we keep it small
Most custom software fails by growing. It gets built for every case anyone can imagine, ships late, and is then too complicated for the people it was meant to help.
We scope the job the app actually has to do, build that, and put it in front of your team while it is still small enough to change. What earns its place stays. What nobody uses does not get built twice.
- One clear job per tool, agreed in writing before we build.
- Weekly builds your team can use, not a demo at the end.
- Your data in a database you can read, export and take with you.
- Access, roles and logins set up properly from the start.
- Documentation of the parts you will have to maintain.
Common questions
What does a web app cost?
The number of screens, the number of integrations and whether roles and permissions are involved drive most of it. We prefer to cut it up: the smallest version that does the job first, at a fixed price, and expand from there.
Can it connect to the systems we already use?
Usually yes. If a system has an API we can integrate it, and if it does not we will tell you that before you commit rather than after.
What happens to our data?
It lives in your database, on your hosting account, in a format you can export. Nothing is locked inside a platform of ours.
Can our own developer take it over?
That is the intention. Standard tools, readable code, and documentation of the parts that are not obvious. We hand over the repository and answer questions during the transition.
Do you build mobile apps?
We build for the browser, which covers phones and tablets. If a job genuinely needs a native app we will say so rather than sell you something that does not fit.
Describe the job.
Tell us what your team does by hand today. We will come back with a scope, a price and a date.