Companies without an IT department
Those with a clear process in their head but no tool that reflects it, and no intention of bending the way they work to fit a generic system.
// web apps
Custom web apps, built around your needs.
Whether it means digitising a single process or building a product from scratch, the benefit is the same: less time lost on repetitive tasks, fewer manual errors, one single place to find the right information.
Who it is for
Those who outgrew off-the-shelf software
Commercial software covers 80% of cases and the remaining 20% is handled by hand. When that 20% becomes the real work, it is worth building.
Product teams
Startups and teams that need to put something in front of real users that does not exist yet, and need it to work before it is perfect.
What is included
- Mapping of the current process, including the steps that today happen verbally or over email and that nobody ever wrote down.
- Data model design: what the information looks like, how it connects, what must never happen.
- Authentication, roles and authorisation.
- Simple, intuitive interfaces, built around the task at hand.
- Backups, error and event logging, so everything stays traceable.
- Launch, training, and one month of fixes included.
How I work
Web apps almost always fail for the same reason: months spent building something nobody has used yet. The way around it is to put something in people's hands as early as possible.
- 01
The process, not the features
Before talking about screens we look at how you work today and where time is lost. The most requested feature is often not the one that saves the most.
- 02
Working core
The minimum version someone can genuinely use for a day of work. Not a fake prototype: something that saves real data.
- 03
Growth in blocks
One capability at a time, with weekly demos. You watch it grow and correct course before it gets expensive.
- 04
Going into service
Migration of existing data, training, and support through the first weeks of real use.
What I need from you
The work moves fast when whoever knows the process is available. They do not need to be technical.
- A contact person who actually uses the process every day, not just the person who designed it.
- The files and spreadsheets you work with today: they are the most honest picture of how things really work.
- One hour a week for the demo and the decisions. That commitment is the difference between a project that lands and one that stalls.
Frequently asked questions
- Do I own the code?
- Yes. The application I build for you is yours, and I hand it over whenever you want: source code, database and documentation to move it elsewhere.
- Can we start small?
- That is the approach I recommend. A working core in the hands of two people for a month teaches more than six months of meetings, and cuts the risk of building the wrong thing.
- How do you handle sensitive data?
- Authorisation checked on the server for every operation, data encrypted in transit, secrets kept out of the code, and retention limited to what is genuinely needed. If you process third-party personal data we address it explicitly during analysis.
- Who owns the domain and the hosting?
- The domain is registered in your name: you are the owner; I am just the technical contact who manages it. I take care of hosting: it is included in the service, fast and secure. The cost scales with the site's traffic and I state it in the proposal.
Let's talk
Thirty minutes, no commitment. You tell me about the project and I tell you what I would do, with timing and a ballpark figure.