I build applications that fit how your company works
From a simple panel to developing an existing system. I design tools that bring order to daily work instead of forcing your team into workarounds and spreadsheets.
Let's discuss your application
Sounds familiar?
Company work should not live in spreadsheets and workarounds
Off-the-shelf tools rarely cover the real process. One view, one step or a whole panel is missing. Then more spreadsheets appear, along with notes and knowledge that lives with one person.
A spreadsheet stands in for the system you do not have
The team tracks orders, dates or statuses in a spreadsheet, because no ready-made tool shows what they actually need.
The ready-made tool forces a process that is not yours
To finish the job, people work around fields, duplicate data or move information outside the system. The longer this goes on, the more mistakes appear.
The existing application is there, but nobody can move it forward
The system works, it just is not being developed. A new feature, a fix or someone who can take over the code and add what the team needs is missing.
Only one person knows how the whole thing fits together
Workarounds, passwords and exceptions live in one person's head. The rest of the team waits until that person clicks, checks or explains.
You do not need a finished specification. Describe how the work looks today and where it gets stuck.
Tell me about your processWhat I can do
I build a tool that fits the company's process, not the other way around
From a simple panel to developing an existing system. The team gets the view and the steps they actually need, instead of working around a ready-made tool in a spreadsheet.
Admin panels and internal systems
One panel for work that today lives in a spreadsheet, in email or in one person's head.
Orders, statuses and documents in one place
A view for the office, sales or the warehouse
Permissions and a change history where they are needed
Developing or taking over an existing application
I take over a working application, sort out what is blocking the work, and add the next features.
A new feature in the system the team already uses
Fixes in code that nobody wants to touch
Maintenance after the previous contractor
The first version of a SaaS product
A first version you can show and grow, instead of building the whole product at once.
Login, a panel and one core process
A version to test with the first users
A foundation for the next modules
Technologies I work with
How we work together
From a problem to a working solution
You do not need a finished specification or a chosen technology. First, we decide what is worth doing and which first step lets the project move forward safely.
01
You describe the problem or process
You show me what is not working today, requires manual work or takes too much of your team's time. I ask about the goal, the systems you use and the important exceptions.
02
We agree on the first stage
When the scope is clear, you receive a work proposal and an initial estimate. When there are more unknowns, we start with a short paid analysis, specification or prototype.
03
I deliver the solution in stages
Each stage has an agreed scope and result. I show progress regularly, test the important cases and discuss changes before they increase the time or cost of the work.
04
We launch and check the result
I launch the solution, hand over the information you need and we check whether it actually improves the process. Then we can close the project or plan the next stage or ongoing support.