Web application development
Internal tools, client portals and line-of-business applications built around how you actually work. You talk directly to the person who writes the application, not to a salesperson.
What I build
Applications for processes currently held together by spreadsheets, email threads and conversation.
- internal record and warehouse systems
- client portals with their own logins
- quoting and invoicing tools
- dashboards for jobs and capacity
- a CRM shaped around one operation
- connections between existing systems
How a project runs
We start with one process and a usable version, not an eighty-page specification.
- a conversation about the actual process
- proposal with scope and price
- first usable version in weeks
- tested on real data in the business
- adjusted after real use
- handover with documentation
When it pays off
Custom software makes sense once a standard product adds more work than it removes.
- the spreadsheet became a database
- several systems know the same number
- off-the-shelf fits about eighty percent
- every new hire needs to be trained on it
- one process rests on one specific person
Working languages: English and Czech
I work from Czechia for clients across Europe and further out. Everything runs in English — calls, documentation and handover — or in Czech if that suits you better. Time zone is CET, which overlaps a normal working day almost everywhere in Europe and the morning in the US.
FAQ
- How long until a usable first version?
- For a clearly scoped process, a version your team can genuinely work with typically lands in four to eight weeks. Larger systems then grow in steps rather than arriving all at once.
- Do you work alone or with a team?
- Alone. That means no handing off to juniors, no project-management markup, and you always speak to the person writing the code. It also means I take on a limited number of projects at a time.
- What if I need someone else later?
- You get the source code, the documentation and the access. I build on mainstream technology like React, Next.js and Postgres so another developer can pick it up without starting over.
- Can you take over an existing application?
- Yes, where the code is accessible and the stack is common. I look at the project first and tell you honestly whether taking it over or rebuilding is cheaper.
Tell me about one process
Send me a process, a spreadsheet that outgrew itself, or an idea for an internal tool. We start small, with something that is useful immediately.
Get in touch