01 / Map
Find the actual bottleneck
Trace one workflow, the people responsible and the information that gets lost. Separate a process problem from a software problem.
Ivan Boban / Systems / Split, Croatia
A business that runs on more than your memory.
The same information copied twice. A handoff nobody owns. Another tool to check. Let’s turn one recurring problem into a clear, usable workflow.
Tell me what keeps breakingStart with a short brief. Scope and price are agreed before implementation.
Built in a business I run
Cosmic Production: a website that reflects the real operation.
My own event-production company is a working environment for website strategy, service structure and platform development. The case study documents the rebuild; it is evidence of systems work, not a claimed AI result.
Read the case study ↗From starting point to delivery
A useful system starts with a clear decision.
02 / Decide
Choose the smallest useful fix
Define what should change, what stays manual and where AI genuinely helps. Agree the scope and how the result will be checked.
03 / Build
Make it usable day to day
Implement the agreed website, automation or internal tool, then test the handoffs and document how your team will operate it.
Before we begin
Bring one process. We’ll define the next step.
Useful starting points include enquiry routing, repeated data entry, reporting and disconnected business tools. If the problem needs investigation, a paid workflow diagnostic is available; it is not a compulsory first purchase.
Scope, pricing and service details ↗Does this have to involve AI?
No. A reliable rule, clearer workflow or simpler interface may solve the problem better. AI is used where it has a defined job and a way to check its output.
What does it cost?
The main service page carries the current diagnostic, workflow and systems pricing. Implementation depends on scope, integrations and the work required; no subscription is started by submitting a brief.
What should I send?
Describe the task, how it works today, the tools involved and what failure looks like. Keep passwords, credentials and sensitive records out of the first message.
AI & business systems / Ivan Boban
Which task should stop coming back to you?
A few lines about the workflow are enough to start a useful conversation.
Tell me what keeps breakingStart with a short brief. Scope and price are agreed before implementation.