/check
Process Check
One broken process. One week. What you get: a blueprint — a specification for the software with a map of where exactly the money and time leak out, and what to build about it.
Your 30 minutes
You tell me what’s driving you mad. That’s it. Nothing else required — no spec, no “gathering requirements”, no workshops.
My week
I watch how the process actually lives: people, systems, files, workarounds. I talk to the people inside it — briefly, without pulling them off work.
In your hands
A blueprint: a specification for the software with the process map and the leaks marked — what exactly to build or rework, in what order, and what it returns in numbers. Ready to work from: by me or by any other developer. A document plus a call to walk through it.
Frequent questions
What if the process is “too tangled”?
Tangled ones are my favourite. That’s where the losses are biggest and the first step pays off fastest.
Will I have to buy something afterwards?
No. The blueprint stands on its own: take that specification to any developer or build it in-house. Most people come back — but that’s a choice, not a hook.
Do I need to prepare anything?
Nothing. Access and documents come up after the call — and I only ask for what’s genuinely needed.
Wait, you work alone?
For you — yes, deliberately: you talk to the person who actually figures it out and does it, with no account manager in between. When a job is bigger than me, I bring in people I trust — but you always talk to me.
What if you disappear?
Everything I do lives on your side from day one: your accounts, your repository, documentation as I go rather than at the end. The next specialist opens it and continues.
fixed price — ask · about one week
Describe the pain
Three fields. I reply within 24 hours — in English or Russian.
Done.
I have it. You’ll hear back within 24 hours at the contact you left.
Or directly: mikhail@mytrigub.com · Telegram
// for the technical readers: 1C/ERP integrations, REST/SOAP, Python, JS/TS, SQL, Telegram Bot API, LLM pipelines (RAG over knowledge bases), BI dashboards. The stack follows your infrastructure, not the other way round.