How I work - A clear next step, from idea to release
Understand the problem, build something you can try, then refine it for release. At each stage, you can see the work, question the decisions, and help choose what comes next.
Step 01
Agree on what to build
We review your goals, current product, and the tasks that matter most to your users. Together we agree on priorities, how to judge success, and what can wait.
What you receive
A prioritized scope with estimates, success criteria, and risks called out before building starts.
Step 02
Try working software
I start with one useful flow and build in small increments. Design and engineering happen together, so your feedback shapes the product while it is still easy to change.
What you receive
Working software you can try, regular demos, and a clear view of progress and the decisions that need your input.
Step 03
Plan the release and handover
I test the main journeys, error recovery, accessibility, and performance, and prepare deployment and backups. We review any remaining risks and agree on what needs to be resolved before release.
What you receive
A release plan, documentation your team can use, and an agreed approach to monitoring, support, and improvements.
Before we start
- What should I bring?
- A short description of the problem, who the software is for, and any timeline or budget constraints. If a product already exists, share what works and where people get stuck. You do not need a finished specification to start a conversation.
- How do we agree on scope and ownership?
- We discuss deliverables, access to source code and accounts, ownership terms, and third-party licenses before work starts, so those expectations are part of the agreement.
- What happens after launch?
- We agree on the handover, who operates the product, and what ongoing support covers. Monitoring, maintenance, and future improvements are scoped around what your team needs.
Have a product to build or improve?
Tell me where your project stands and what you want to change. You don’t need a finished specification to start a conversation.
Based in
- Rijeka
Croatia (Central European time). Remote-first across Europe and North America. I usually reply within one business day.