Work with me

Bring me a problem to solve, or bring me onto your team. Either way the work starts in the same place: the workflow, and the part of it that actually hurts.

For companiesBring me a problemFor companies with a workflow AI should fix. See how an engagement runs and how to start.How an engagement runsFor hiring teamsBring me onto your teamI'm open to forward deployed and AI solutions roles from December 2026. See what I bring and get the CV.What I bring to a team

Bring me a problem

How an engagement runs.

This is my method, not a price list. The same six steps run on every project, from a short discovery phase to a two-year platform.

  1. Start with the workflow

    The first call is about what hurts, who will use the result and what the business needs first. If custom software is not the answer, I say so.

  2. Turn the idea into a plan

    A discovery workshop produces phased scope, acceptance criteria and a build plan people can approve. We agree what the first version must do and how we will test it.

  3. Prove it early

    Where it helps the decision, I build a prototype or a demo on your real material before anything is committed.

  4. Build in weekly steps

    Working software every week and a short weekly review, so scope changes and bad news reach you early and directly.

  5. Design for when the happy path breaks

    Permissions, source evidence, retries, visible failures and a clear handover to a person are part of the first version, not a later fix.

  6. Launch and stay

    I stay through launch to tune the system with real users, and I report results with the method behind every number.

Problems I've solved

Bring me onto your team

What I bring to a team.

I'm open to forward deployed and AI solutions roles from December 2026, fully remote, with US overlap until 14:00 Eastern.

  • Forward deployed engineer
  • AI solutions engineer
  • Sales engineer (AI)
  • AI deployment engineer

Customer-facing

Discovery, qualification, workflow mapping, technical scoping, demos and proposals. I have run the whole sales cycle for AI and software projects myself, then built what I sold.

Building

Production AI inside customer systems and codebases: retrieval with source citations, realtime voice, text-to-SQL, copilots, agents and MCP servers, with permissions and human handover designed in.

Operating

Hired and led a distributed delivery team after 100+ candidate interviews, ran sprint planning and weekly client reviews, and built the sales and delivery systems a company runs on.

Download CVEmailLinkedIn ↗

Questions

Before you email.

Where are you based, and which time zones do you work in?

I'm in Rijeka, Croatia, and I work fully remote. I'm available between 09:00 and 20:00 CET, which overlaps the US working day until 14:00 Eastern (11:00 Pacific).

Do you work through Adamant Code?

Email me at [email protected] and I'll reply personally. I read every enquiry and decide each one case by case.

Why are you looking for a full-time role?

After three years running a small AI studio, I want to spend all my time on the part I'm best at: working with customers and building what fixes their problems, on one product with a strong team. I'm open to forward deployed and AI solutions roles from December 2026.

What happens after I email you?

I reply personally and we set up a first call. It is about what hurts, who will use the result and what the business needs first. If custom software is not the answer, I say so. If you're hiring, I'll send my CV and we can talk about the role and the team.

At dusk, a vast slab of forested land hangs over a sea of cloud that combs beneath it like a wave. A lone hiker stands on a dark ridge, watching.

Work with me

Bring me the hard problem.

Based in Rijeka, Croatia, working with teams in the US, UK and EU. Email me what's stuck and I'll tell you what it would take to fix it, including when the answer isn't AI.

Email meLinkedIn ↗
I'm open to forward deployed and AI solutions roles from December 2026. Read my CV ↓