Skip to content

Ivan Boban · Croatia / remote

AI systems for work that keeps repeating.

I help businesses in Croatia turn repeated admin work into a defined, testable workflow: connected to the tools your team already uses, with a person in control.

Describe your workflow

Start with the work.

A good starting point is a task you can show me: sorting incoming enquiries, extracting fields from documents, preparing a reply or finding an answer in internal material. We identify the input, the decision and the person responsible before choosing the technology.

What we can build

Enquiry triage and draft replies

Organise incoming messages, extract the information your team needs and prepare a response for approval. Agree on routing rules and escalation before any message can leave the system.

Document-to-workflow handoffs

Turn agreed document types into structured fields and a review queue. Missing or ambiguous information stays visible; a person confirms it before it enters the next business step.

Internal knowledge assistance

Help a team search an approved set of material, with source references and a clear route for unanswered questions. Access, document ownership and updates are part of the scope.

Integration and handover

Connect the agreed tools, define permissions, record failures and provide operating instructions. API availability and data quality determine what is feasible. Sometimes a simple rule is the right solution.

One process, then evidence.

  1. Map the current task

    Walk through real examples. Establish current handling time, common errors, data access and the person who will own the workflow.

  2. Agree on the boundary

    Write down supported inputs, expected output, review points, acceptance examples and ongoing costs. Decide what happens when the model or an integration fails.

  3. Test before expanding

    Compare the workflow against the agreed examples, including incomplete and unusual inputs. Review usefulness and error handling with the person who will use it.

  4. Hand over a working process

    Deliver the agreed integration and documentation, then decide whether maintenance or a further phase is worthwhile. Expansion is a separate decision.

A scoped starting point

Prices in EUR, excluding VAT.

Workflow Diagnostic

€490

One workflow, a 45-minute interview and a written decision pack. Use this when the bottleneck or solution is still unclear. Implementation is a separate scope.

Workflow Install

From €2,500

A bounded workflow install with a written scope. The starting price applies to the workflow service; AI features, integrations and acceptance criteria must be agreed before a quote.

Business Systems Build

From €8,000

For a broader business system involving several workflows or integrations. We define the phases and dependencies before committing to the build.

Model usage, third-party subscriptions and ongoing maintenance are identified separately in the proposal. No promised percentage saving or automatic return on investment.

The work below shows my systems experience and operating environments. It is not a claim that every project uses AI or that your workflow will produce the same result.

Already running

Systems I run in production.

Most of this is my own operating environment: the companies and products I run. I build for clients with the same tools and the same standards.

My own operating environment

Cosmic Production

Eight years of in-house website strategy, SEO evolution, and platform rebuilding

An eight-year evolution from iterative WordPress rebuilds to a custom platform that better matched Cosmic Production's service complexity, SEO goals, and market position.

My role: Strategy, SEO, positioning, design direction, and implementation

Read the case study

Before we start

Do I need an AI agent or a chatbot?

That depends on the task. If fixed rules can handle it reliably, we can use those. AI is an option for interpreting variable input; it is not a prerequisite for automation.

Can this work in Croatian and English?

Both languages can be included in the scope. We test with your actual vocabulary, documents and examples rather than assuming that a general language capability is good enough for your work.

What happens to sensitive business data?

Before implementation, we agree which data may enter the workflow, which providers may process it, who has access and what is retained. Do not include credentials or confidential customer records in the initial enquiry.

Will it send messages or make decisions without approval?

Approval points are part of the written scope. For a first workflow, drafts and review queues give your team a way to check output. Any permission to take external actions must be agreed explicitly.

Can you work with our existing software?

We first check whether the tools expose a supported integration, export or API, and whether your account has the required access. The proposal identifies dependencies and any work that cannot be done reliably.

Show me one repeated task.

Describe what starts it, which tools you use, how often it happens and where it gets stuck. A short, anonymised example is more useful than a long AI wish list.

Describe your workflow Explore operational systems and backend work →