/check
Diagnostic
Point at the pain — in one week I’ll find what’s actually broken and hand you a blueprint to fix it.
Your 30 minutes
Tell me what hurts, in your own words. Symptoms, not specs. That’s all I need from you.
My week under the hood
I look at how the work really runs: software, people, documents, workarounds. And I check beyond the spot you pointed at — the pain and the break often live in different places.
Diagnosis and blueprint
You get: what exactly is broken, what it costs you right now — and a blueprint: what to fix in the software, what to fix in how it’s used, and what to leave alone. A technical specification ready for development — mine or any other developer’s.
A case I keep seeing
The software is fine — invoices get lost because of how they’re routed. Then I fix the document flow, not the code; that’s my job too. And the reverse: “our people are careless” turns out to be an integration silently eating every twentieth document.
The honesty clause
If it turns out no code is needed, I’ll say so. A diagnostic that always ends with “you need development” is a sales pitch, not a diagnostic.
Frequent questions
What if it’s all “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.