Victor Lipov
Independent operator · Funchal, Madeira · remote

I make your operations actually work.

With AI where it pays off, and not where it doesn't. For mid-market companies where the tools already exist, but the work still stalls.

Map your operation → See how it works
01 / The problem

You already bought the software. It works. And the leads still sit untouched, the pipeline stalls at the first stage, and people quietly run the real work on spreadsheets.

The software was never the problem. The operation didn't follow it. That gap, between a tool that works and an operation that moves, is where I work.

02 / What I do

I own the outcome, not the tool.

I read the operation first, find where the work actually gets stuck, then make the right next step easier than ignoring it. The software is the lever, not the deliverable.

01

Find

Process-mine the live system to see exactly where work stalls, with numbers, not opinions.

02

Fix

Rebuild the flow and automate the mechanical parts. Surface the one next action instead of a backlog.

03

Ship

Built into your production system, not a slide deck or a parallel tool nobody opens.

04

Sticks

When the new way is easier than the old, the behavior holds without anyone being nagged.

03 / Receipts

Numbers, not adjectives.

Real work, with the honest part included: the diagnosis is cheap and fast. Making the operation act on it is where the value is.

Mid-market CRM cleanup
~$15of AI surfaced that 995 of 1,007 leads in a €15K/yr CRM had never been contacted.
The diagnosis was the cheap part. Acting on it is the real work, and it is exactly what most software leaves undone.
Production company · live
200dmedian cycle time, with the slowest stage sitting right at the first step.
Built an in-app process-mining dashboard on a live workflow. It shows where work piles up and reports 93% process conformance. You cannot fix a stall you cannot see.
Industrial client · 1+ year
3 systemsproduct configurator, tender automation, and a new company website.
Shipped into production and still running over a year later. Not a pilot, not a prototype.
CASA · pro bono
In usea custom CRM built for a Madeira social-support nonprofit.
Useful software for a team that could not buy it. Built and maintained for free.
04 / Why me

Fifteen years deciding.
Now building.

I spent my first career in finance and credit risk, running decision systems for a multinational group: scoring, approval chains, controls, across a portfolio near €500M and five continents.

That taught me to read a business process, where decisions happen, where friction hides, and what actually matters versus what just looks busy. Now I build the software myself.

I read the process first. Then I write the code.

15 yrsFinance & credit risk, decision systems
~€500MTrade-receivables portfolio managed
5Continents covered by the systems I ran
SoloOne operator plus an AI agent team I built, not an agency
05 / How to start

One small step, no commitment.

Map your operation on a single page, send it over, and I will give you my read for free. If it is worth going further, the path is short.

STEP 01
Free

Map & read

Fill in the one-page operation map, send it, and get my honest read on where AI pays off for you, and where it doesn't.

STEP 02
€500

Diagnostic

A focused look at one workflow: where it stalls, what is worth automating, and what to leave alone.

STEP 03
Scoped

Build

I build the fix into your production, own the outcome, and stay on the hook until the operation actually moves.

06 / Start

Tell me what's stalling.

A few lines on where the work gets stuck. I read every one myself and reply personally, usually within a day.