Skip to content
Kon Fartusov

Taking one or two problems at a time

Your business runs harder than it should.I find out why, and build what fixes it.

Sixteen years in software delivery, from trainee to delivery director. I analyse how the work actually flows, design the system that fits, and build it — from a single automation to a full platform.

An answer within three days — yes or no, with the reason.

Prague · CZ

Kon Fartusov

Kon Fartusov

Systems consultant, Prague

How this works

From a problem to a working system, in four steps.

No agency, no account manager. You talk to the person who analyses the problem and builds the solution.

  1. 01

    You describe the problem

    One form, five minutes. What you do, what hurts, and what it costs you now in hours or money.

  2. 02

    I analyse it

    How the work actually flows, where it breaks, what it costs. Within three days you get a plain answer — sometimes that software isn't what you need.

  3. 03

    I design and build

    A system sized to your business: an automation, an integration, or a full platform. Working software, not a slide deck, and you can stop me at any point.

  4. 04

    You own the result

    Code, accounts, data — all yours. I pick problems I want to solve and don't charge for this; all I ask is permission to write up what we did.

The filter

I say no more often than yes, and I say it fast.

Being honest about this up front saves us both a week. Two conditions have to meet: the problem has to be interesting to build, and its effect has to be measurable.

I take it when

  • The problem is genuinely interesting to build
  • The effect is measurable — hours saved, errors gone, a step deleted
  • There is a real business behind it with a real pain
  • It fits into a few evenings, not a few quarters

I pass on

  • “Make us a site like our competitor's”
  • Open-ended projects with no edges
  • Subcontracting through an agency
  • Anything that needs round-the-clock support

Where I help

Three things I do well.

Analysis

Finding the real problem

Hundreds of projects taught me where work leaks. I map how it actually flows, where it breaks and what it costs — and give an honest answer on whether software is even the fix.

  • The step everyone works around instead of fixing
  • What to change first, and what to leave alone
  • A plan you can act on, with or without me

Systems

Designing and building what fits

From one integration to a full platform: CRM, accounting, inventory, customer portals, data pipelines. Built to run without me, documented so anyone can take it over.

  • Orders flowing into accounting without copy-paste
  • One number every system agrees on
  • A portal your customers use instead of calling

AI & automation

Taking routine off people

Agents, document processing, support bots — where they genuinely help, not where they demo well. The manual routine becomes a system that runs whether or not anyone remembers it.

  • Invoices and PDFs read into your system automatically
  • A bot that answers the same twenty customer questions
  • Reports assembled while you sleep

Work

Things I've built.

The write-ups are in progress. These are products I designed and built — my own, not client work. I would rather say that plainly than dress them up.

Personalised stories, printed as real books

Read

A child becomes the character. Text splits into blocks, each block becomes one narrated segment and one illustrated page, and the whole thing is printed on demand.

10+ AI steps in the chain
3 print providers
PDF · video · paperback

A short animated film from one paragraph

Write-up soon

A brief goes in, a crew of agents writes the script and storyboards it, and you approve every scene before it is animated. Only what you signed off gets built.

Human in the loop
Script → board → film
Downloadable video

Habits, rewards and challenges

Write-up soon

Parents track habits, children earn points, points turn into rewards. Time-boxed challenges sit on top, with enrolment and submissions.

Points ledger
Time-boxed challenges
Family accounts

A rental shop that runs its own warehouse

Write-up soon

Books and games rented with deposits, availability calendars, extensions and overdue tracking. Stock is placed by barcode scanning, one shelf at a time.

5 booking states
Barcode shelf placement
ISBN enrichment cascade

About

Why I do this

Kon Fartusov

Kon Fartusov

Systems consultant, Prague

I'm Kon. I joined a software company as a trainee in 2010 and have held every role since — developer, tech lead, project manager, delivery director. Sixteen years, one company, each of those chairs.

So I tend to know where projects slip. My work now is delivery, the bench and the process, plus a standing search for where the work can be simpler: fewer steps, less waiting, less routine carried by people.

On my own time I build products: an AI platform that turns a child's photo into an illustrated, narrated, printed book; a film studio driven by agents; a shop that rents physical things and tracks its own warehouse. That is where the four write-ups above come from.

The interesting problems are rarely the ones with a budget attached. A small business losing six hours a week to copy-paste has a better problem than most enterprise roadmaps, and nobody is going to solve it for them. So I take them on myself, on my own terms.

Based in
Prague, Czechia
Day job
Delivery director, software company
Scope
One automation to a full platform
Capacity
5–10 hours a week

Questions

The ones everybody asks first.

What kind of problems do you take?

Anything where a business loses time or money to how the work is organised: manual routine, tools that don't talk to each other, a process nobody can explain. From a single fix to a platform.

Is this consulting or building?

Both. I analyse first — sometimes the answer is to change a process, not to buy software. When building is the answer, I build it.

What does it cost?

Nothing, for now. I have a job I like; this is where I take on problems that interest me. Hosting and paid services are yours. If it grows into ongoing work, we talk then.

What if you say no?

You get a plain answer within three days, with the reason. Often the reason is useful on its own — sometimes the answer is that you don't need software.

Who owns what gets built?

You do. Code, accounts, data — all yours, handed over at the end.

Can you sign an NDA?

Yes. In that case the write-up is either anonymised beyond recognition or doesn't happen at all. Your call, agreed before I start.

How long does it take?

I spend five to ten hours a week on this and take one or two problems at a time. Small things land in days; anything bigger, I'll tell you honestly before starting.

Start here

Tell me what's broken

The more concrete you are, the faster I can tell you yes or no. There is no wrong way to fill this in — write it the way you'd say it out loud.

Prefer to just write?

Telegram·hi@fartusov.com

Hours a week, money a month, mistakes — whatever you can measure. This one matters most.

Optional — it tells me whether I'm building next to something or from scratch.

This isn't my fee. A solution usually needs hosting, an AI provider or a paid API, and that bill is yours. Knowing the ceiling shapes what I build.

I read every one myself.