Full-stack development · SaaS · Internal platforms · CMS
I build the software
your business runs on.
Seven years shipping production systems for rail logistics, public administration and higher education. SaaS platforms, internal tools, content-driven sites, and the unglamorous migrations that keep all of it alive. One senior engineer, the whole stack, from database to deployment.
- Availability
- Accepting new projects
- Response
- Reply within 1 business day
- Engagement
- Project or monthly retainer
- Based
- Remote — Bosnia and the region
Services
Six ways I get hired
Most projects start as one of these and grow into two. You get one person accountable for the whole thing — no handoffs between an agency’s backend team and its frontend team.
-
SaaS product development
From empty repository to paying customers.
Multi-tenant architecture, authentication and single sign-on, subscription and billing hooks, an admin back office, and the audit trail your first enterprise customer will ask for. Built so you can add the second and third feature yourself.
-
Internal tools & operations platforms
Replace the spreadsheet, the phone calls and the email thread.
The work I do most. Real-time, multi-user systems where several people edit the same data at once and the numbers have to stay right — dispatch boards, planning tools, approval flows, validation-heavy back offices.
-
Websites & CMS
Content your team can actually edit.
Marketing sites, product sites and content platforms on a headless or traditional CMS. Fast, accessible, measurable, and structured so publishing a page never needs a developer.
-
AI features that hold up
Answers with sources, and permissions that are honoured.
Retrieval-augmented assistants over your own documents, semantic search, and document processing. Built to respect existing access rights and to cite where every answer came from — the two things that decide whether anyone trusts it.
-
Legacy modernisation
Move off the system nobody wants to touch.
I have replaced a production database-generated application suite with a modern stack without a big-bang cutover. Incremental migration, the old and new running side by side, and the old one switched off only once nothing depends on it.
-
Support & maintenance
For software I built, and software I did not.
A monthly retainer covering fixes, dependency and security updates, small features and an agreed response time. Also available as a rescue engagement on a codebase whose original team is gone.
How it runs
Four stages, in this order
You always know what is being built, what it costs, and when you next see something working.
-
Scope
A 30-minute call, free. If it is a fit, I write down what we are building, what is explicitly out of scope, and what it costs — a fixed price for a defined deliverable, or a rate and an estimated range for open-ended work. You approve that document before anything starts.
-
Build
Two-week increments. At the end of each one there is software you can open and use, not a status report. You see progress continuously and can change direction between increments without renegotiating the whole project.
-
Ship
Deployment, automated pipeline, monitoring and backups. Written handover: how it is built, how to run it, how to change it. The code and the infrastructure are yours, in your accounts, from day one.
-
Support
Either a monthly retainer with an agreed response time, or a clean handover to your own developers — including the session where I walk them through it. Both are fine. Being impossible to replace is not a service.
Stack
What I work in
Chosen per project, not per fashion. If your team already runs something on this list, I can pick it up rather than argue for a rewrite.
- Backend
- Java · Spring Boot · Quarkus · Python · FastAPI · Go · Node.js
- Frontend
- Angular · React · Next.js · TypeScript · RxJS · Tailwind
- Data
- PostgreSQL · Oracle and PL/SQL · MongoDB · Redis · Elasticsearch · SQLite
- Infrastructure
- Docker · Kubernetes · OpenShift · AWS · Azure · CI/CD
- AI
- Retrieval-augmented generation · LangChain · Azure OpenAI · AWS Bedrock · vector and hybrid search
- Security
- Keycloak · OIDC and SAML single sign-on · role-based access control
Who you get
One senior engineer,
not a rotating team
I have spent seven years building enterprise software that other people’s jobs depend on — freight dispatch, border clearance, university administration. Systems where being down is not an inconvenience but a queue of lorries.
I work across the whole stack because most of the interesting problems live at the seams: between the database and the API, between the API and what a dispatcher sees on screen at five in the morning. In teams of two to ten I have done the architecture, the estimates, the code reviews, the deployment pipelines and the training sessions afterwards.
I am direct about what is hard and what a thing will cost. If a project is a bad idea, or off-the-shelf software would serve you better than anything custom, I will say so on the first call — that conversation is cheaper for both of us than the alternative.
- Experience
- 7 years, full stack, enterprise
- Education
- Computer science, technical university
- Sectors
- Logistics, public sector, higher education, sport
- Languages
- Bosnian/Croatian, German, English
- Method
- Scrum and Kanban, code review, pair programming
- Availability
- Accepting new projects
Questions
Asked before the first call
How do we start?
Send the form below with roughly what you have in mind. I reply within one business day, usually with two or three questions. Then a 30-minute call, free and with no obligation, after which you get a written scope and a price.
What does it cost?
Defined deliverables get a fixed price, so you carry no estimation risk. Open-ended or evolving work runs on a day rate with an agreed budget ceiling that I flag well before we reach it. Retainers are a monthly fee for an agreed number of days. I will give you a realistic range on the first call rather than a number that grows later.
How long does it take?
A focused internal tool or a content-driven site: three to six weeks. A first sellable version of a SaaS product: two to four months. A legacy migration depends entirely on what is being migrated, and I will not pretend otherwise before seeing the system.
Can you work with our existing team and codebase?
Yes, and often that is the better arrangement. I have spent most of my career in cross-functional teams — sprints, code review, pair programming, shared ownership. I can join your process rather than impose one, and I am comfortable being the person who takes on the part nobody else wants to touch.
Who owns the code?
You do, in full, in your own repository and your own cloud accounts from the first commit. Handover documentation is part of the delivery, not an extra. Happy to work under your NDA and contract.
What happens after launch?
Your choice. A monthly retainer covering fixes, security updates and small features with an agreed response time — or a handover session with your developers and a clean exit. Either way you are never locked in by not understanding your own system.
Contact
Tell me what you need built
A couple of sentences is enough to start.