Selling complex technology
Pre-sales and solution design for vendors and integrators: positioning, the technical narrative, and a business case that survives the CFO's second question.
Independent technology consultant · Serbia & Spain
Independent consulting on cloud, machine learning and applied AI. The solution gets designed, then explained to the people who have to sign for it — in plain language, with the economics worked out.
The work
Engineering describes a system. The business decides on an outcome. Most projects stall in the gap between those two sentences — and that gap is where I work. Every proposal exists in both columns at once.
Managed Kubernetes, autoscaled across availability zones
A traffic spike stops costing you a night of downtime — and you stop paying for idle capacity the rest of the year
Speech-to-text and synthesis pipeline, tuned on your own domain vocabulary
Every customer call becomes searchable text, and your agents stop writing summaries by hand
Retrieval layer over your internal document base
New hires find the answer themselves instead of interrupting the one person who knows it
Phased migration from on-premise to hybrid, over two quarters
Capital expense becomes a monthly line you can forecast, defend, and cut
Services
Pre-sales and solution design for vendors and integrators: positioning, the technical narrative, and a business case that survives the CFO's second question.
Finding the places in your business where AI returns more than it costs, and saying so plainly when it doesn't. Pilots designed to answer a question, not to demo well. Agent factories included: how many agents, which systems they may touch, where a human signs off, and what one run costs.
Transcription and speech synthesis put to work: call analytics, voice interfaces, accessibility, media production. Model selection, tuning, and the pipeline around it.
Architecture and migration for infrastructure that simply has to keep running. An honest assessment of what you have, a plan for what you need, real numbers for both.
Architecture, sizing and technical supervision for software other people build — mobile applications included. How hard the thing really is, what it will cost, which parts are risky, and whether the plan survives contact with a team. I don't take the keyboard.
The arithmetic
Idle capacity is the cheapest money on the table and the least often counted. Put in what you actually run — this is your arithmetic, not my estimate, and it stays in your browser.
Paid for nothing, per year
per month
The number is only the ceiling — some of that capacity is headroom you chose on purpose. Telling the difference is most of the work.
Stack
Seventeen years inside global technology companies — enterprise infrastructure, cloud platforms and machine learning, on the side that has to deliver what was sold. Long enough to know which promises hold after the contract is signed.
How it is built
The same stack, split by one question asked layer by layer: does owning this buy you anything? Hardware and the workloads on top usually stay. The middle usually does not.
Four layers kept because they have to be yours, three rented because owning them buys nothing.
About
Anton Gostev
Consultant, entrepreneur, engineer
My name is Anton Gostev, and I spent seventeen years inside large technology vendors: eleven at Microsoft, three at Yandex International, two at IBM and one at Dassault Systèmes.
The work always had the same shape — standing between an engineering team and a customer who has to sign, and making sure both were describing the same thing.
Today I do it on my own, through two registered practices: one in Serbia, one in Spain. You talk to the person who does the work, because there is no one else to hand it to.
Where those years went
How an engagement runs
Step 01 — Assess
A week or two: what you run, what it costs, where it hurts, and what the team already knows but hasn't been asked.
Step 02 — Plan
Architecture and a costed roadmap that separates what to do now, what to defer, and what to drop entirely.
Step 03 — Execute
Hands-on, alongside your team, or reviewing a vendor's work from your side of the table. Whichever the situation calls for.
Radar
Updated automatically · 26 Aug 2026
Infrastructure, applied AI and the security news that actually changes what you should do on Monday. Headlines link straight to the source.
Memory and RAG evaluations often treat the answering model's input as an implementation detail, even though systems may render the same history as a memory entry, summary, typed record, or…
Read at source →
US groups release cheaper models after new challenges to their trillion-dollar ambitions.
Read at source →
Large language models (LLMs) have shown strong capabilities in reasoning, planning, and tool use, but many scientific and engineering tasks require more than plausible text and code…
Read at source →
Amid talk of an Nvidia deal, the AI search biz is looking beyond the cloud
Read at source →
"We don't have access to the data on the hardware/servers," Iron Mountain told Ars.
Read at source →
Attackers now ready to exploit how things work, rather than just break them, says Oracle support expert
Read at source →
A curated digest, not a mirror: headline, source and a one-line summary, with the link going to the publisher.
Contact
A first conversation costs nothing and usually takes half an hour. If I'm not the right person for it, I will say so and point you at someone who is.
What the first call looks like