Work you still do by hand
Copying rows between files, sending the same message, rebuilding the same report. It becomes something that runs by itself while you do the work that pays.
That Jonas
I build software that solves real problems.
Apps, automations, websites and the small tools that quietly delete an hour of your week. Built by one person, start to finish.
Problems, not packages
You do not need "a web app". You need a specific thing to stop being a pain. These are the four shapes it usually takes.
A tool shaped like your job
When the file has fourteen tabs and three people editing at once, it wants to be a small app. One screen, a login, no training day required.
A site that earns its place
Fast, plain and honest. Something a customer reads on a phone in ten seconds and knows exactly what to do next. No stock photos of handshakes.
The idea, small enough to test
A working version in weeks instead of a year. Put it in front of real people and find out whether it deserves the full build.
Talk, build, ship
Three steps. No discovery phase, no slide deck, no project manager standing between us.
Talk
You tell me what is broken and what it costs you. I ask a lot of questions. You leave with a straight answer: what I would build, roughly how long, roughly what it costs. Free, and yes, sometimes the answer is "do not build this".
Build
Fixed scope, fixed price, agreed before anything starts. You see it working every few days, so there is no silent month followed by a surprise.
Ship
It goes live and you actually use it. I stay reachable for the small things that only appear once real people touch it.
I build, I learn, I share
I am Jonas. I write software, mostly alone, mostly for small businesses and people building something on their own.
I like problems that are annoying and specific: the report nobody wants to make, the process held together by one person's memory, the form that gets filled in wrong every time. Boring problems, real money.
When I finish something, or break it badly, I write down what actually happened and send it out. That is the whole plan.
Notes from building things
One short email when I ship something, break something, or learn something worth passing on. No schedule, no filler, one click to leave.
Tell me what is broken
The quickest start is a call. If you would rather write first, that works just as well.
I read every email myself and answer within a day or two.