The process lives in spreadsheets
A calculation, a status list, a planning overview: three files, three versions of the truth. Nobody can say reliably which one counts.
Software for your work.
Not the other way round.
Standard software covers the standard. What sets your company apart usually sits beside it: in spreadsheets, verbal handoffs and workarounds. That is exactly what we build applications for — fitted to your processes, data and roles.
Request a conversationYour code
Source code, data and deployment with you
Open interfaces
Documented and extensible
Handover-ready
Designed for your team to develop further
Starting point
Standard software dictates the process. Your operation has its own.
Where a standard application does not model the process, workarounds follow: data parked in spreadsheets, information entered twice, agreements living in email and never documented. It works while people fill the gaps – and gets expensive once volume grows or responsibilities change.
The system has no field for it
An exception cannot be recorded in the existing screens. The information ends up in a free-text field and is lost to every report.
Knowledge sits with individuals
The process works because one person knows what to watch for. Holiday, illness or a change of role breaks it.
Licence costs grow with you
Per-user pricing scales against you once the workflow is used across the whole company.
How we work
How we go about it.
Scope, not a specification
We start with the workflow the application has to carry and cut the scope down to what has an effect.
Productive early
A narrow, usable version first. Decisions are made on the running system, not on a document.
Familiar technology
A proven stack rather than specialist knowledge: so your team or a third party can take the application over.
Built to be extended
Clear structures, tests and documentation — so your company can develop it further with today’s AI tooling.
Sequence
In what order.
Phase 1
Scoping
Workflow, roles, data model and the scope of the first version.
Phase 2
Building
Short cycles with a working state at the end of each one.
Phase 3
Going live
Migration, training, operation — accompanied through the first real transactions.
After that
Further development
Maintenance and expansion, or handover to your team.
Outcome
An application that knows your process.
You get a data model that uses your terms, roles that match your responsibilities and interfaces for the tasks that actually occur. Documented interfaces and comprehensible data models keep it extensible – including when you take it over later.
- A business application ready for production
- Source code in your repository
- Documented interface and data model
- Roles and permissions concept
- Automated tests and deployment
- Onboarding for team and administration
Frequently asked
What clients ask first.
- How long until we see a usable result?
- That depends on the cut. We deliberately scope the first step small enough to go live in weeks rather than months – typically one workflow, one role, one clearly bounded part of your process. You then decide what comes next with a working result in hand, not on the basis of a concept paper.
- How is the work billed?
- Bounded work is quoted at a fixed price. Where scope has to stay open because only engaging with the existing system reveals what is needed, we bill for time and say so beforehand. The two combine: fixed price for the first step, time and materials for what follows.
- Who owns the source code and the data?
- You do. The source code is handed over and your data sits in an environment of your choosing. We build in no licence barrier that would prevent further development without us.
- What do we need to provide internally?
- Someone who genuinely knows the workflow, and access to the systems involved. A finished requirements document is not needed – the understanding emerges in conversation. What matters more is that decisions can be made promptly while the project runs.
- Who operates and maintains the solution afterwards?
- You decide. We hand over so that you can take it on: documented interfaces, comprehensible data models, separated business logic. If you would rather leave operation and further development with us, that works too – the decision stays reversible in both directions.