This section covers cloud from the commercial side: unit economics, licensing, procurement, and the conversation that happens before any architecture diagram gets drawn. It is written from practice in Central Asia and neighbouring markets, where most large enterprises still run their own data centres and the decision to move is a question of trust and risk ownership before it is a question of technology.
Why this angle
There is no shortage of technical material about AWS. There is very little about what happens on the commercial side of the same deals: how the licence model shapes the deployment, which costs appear only after the first invoice, why a demonstration loses to a two-week proof of concept, and what a finance director actually needs to see before approving a migration.
Everything here is checked against vendor documentation. Where a figure could not be verified, it is not used.
Selling and the economics of migration
- Closing AWS deals with companies that still run on-prem — a six-step framework for traditional enterprise, from the opening question to the first ninety days after signature.
- How AWS segments its customers, and why size has nothing to do with it — business model over revenue, and what changes in the pitch once you know the segment.
Amazon Quick: a series
- What it actually is and how it is priced — an agent platform rather than a chat assistant, and why that distinction decides the deployment.
- By department: thirteen scenarios that pay for themselves — where the value shows up first, and why narrowness wins.
- What it really costs: modelling a hundred-user deployment — three components drive the bill and seat count is only one of them.
What is coming
- Agent platforms compared: where Amazon Quick differs from adjacent tools
- Implementation: governance, security, and a catalogue of reusable agents
- Hybrid architectures under data residency requirements in the region
- Licensing during migration: where money is lost before the calculation starts
About the author
Written by Ruslan Omarov, Full-Stack Business Architect working on cloud and AI from the commercial side. Longer English-language pieces appear on Medium; shorter field notes on LinkedIn. Full profile: about the author.
Why only AWS?
Depth beats coverage. Writing about one provider from the commercial angle produces material that is specific enough to act on; writing about all of them produces comparison tables that age within a quarter.
Is the rest of the site available in English?
No. The wider knowledge base is in Russian, because that is the working language of the buyers and sellers it describes. This section is bilingual because cloud and AI conversations increasingly are.
Is this vendor-sponsored content?
No. The project is non-commercial and independent, and nothing here is written on behalf of a vendor or paid for by one.