SENIOR AE · AWS STOCKHOLM · NORDICS & EMEA EST. 2020

Most enterprise cloud deals are lost in the architecture review, not the commercial negotiation. I close the ones that aren’t.

Murat Eksi.

Technical seller. Operator. Writer.

Now building ReelForge. Q2 2026.

01 Index.
  1. 02PrinciplesSix positions, arguable on purpose.
  2. 03WorkFive tenures. Pattern before bullets.
  3. 04Selected EngagementsFive rows a partner can quote in an email.
  4. 05Case StudiesLong-form reads on the two hardest ones.
  5. 06How I WorkThree shapes the engagements tend to take.
  6. 07BuildingWhat’s on the bench this quarter.
  7. 08WritingEssays CTOs and founders actually forward.
  8. 09SpeakingTalks, panels, and internal sessions.
  9. 10Selected ResultsFour figures. No stat cards.
  10. 11ContactTwo audience-specific lines. No form.
02 Principles. Arguable on purpose
  1. 01

    The AE who brings the right architect wins before the pricing conversation begins.

  2. 02

    Architecture is downstream of organizational design. Fix the org and the diagram redraws itself.

  3. 03

    A cleaner data layer beats a cleverer model. Every time.

  4. 04

    Programs that ship on time ship because someone said no early.

  5. 05

    The essay is not the opinion. The essay is the work that produces the opinion.

  6. 06

    Altitude is a liability when you stop talking to the people doing the work.

03 Work.
01

Enterprise cloud deals, sold technically.

$30M+ in platform revenue closed across EMEA. Deals won in the architecture review, not the commercial negotiation.

02

Programs that ship when the stakes are real.

Led 50+ consultants across FinTech, GameTech, and Manufacturing. 200% of target, 10/10 satisfaction across the book.

03

Writing founders and CTOs actually forward.

Essays on selling to technical buyers, AI-ready architecture, and the operator’s craft. Read by the people doing the buying.

  1. 2025–Present

    Senior Professional Services Account Executive

    Amazon Web Services·Stockholm · Nordics / EMEA

    At this altitude, the deal is won in the quarter before the forecast. Pipeline is a trailing indicator; trust with the architect is the leading one.

    • P&L responsibility for the Professional Services Nordics practice.
    • 200% of 2025 quarterly target. 10/10 client satisfaction across the book.
    • Expanded existing partnerships by 60%, generating $120M in incremental platform revenue.
    • Direct reports and dotted-line leadership across a team of 50+ consultants.
  2. 2024–2025

    Senior Professional Services Consultant

    Amazon Web Services·Stockholm · Nordics

    The practice that did not exist on a slide last year has to exist in the pipeline this year. You build it by picking the first three customers well.

    • Owned $20M PS revenue and $80M+ downstream AWS platform revenue.
    • Built the Nordics practice across GameTech, FinTech, and Manufacturing.
    • Tech lead across teams of 30+ consultants on multi-quarter engagements.
  3. 2022–2024

    Professional Services Consultant

    Amazon Web Services·Stockholm · EMEA

    You learn the craft by delivering. Seventeen projects, zero below a 9/10. Patterns start to repeat and you start to see them before the customer does.

    • $40M in platform ARR across 16 projects. 10/10 satisfaction.
    • Led a 25-person team delivering a predictive-maintenance SaaS used by 6,000+ companies.
    • Architected a serverless IoT platform for 1.6M+ vehicles at 200K messages per second.
    • Scaled the EMEA-wide Serverless bootcamp to 137 consultants per quarter.
  4. 2020–2022

    Professional Services Associate Consultant

    Amazon Web Services·Stockholm · EMEA

    Security is where your judgment gets tested publicly. The Bar Raiser seat is how the organization decides whether it trusts you to make calls alone.

    • Built a real-time ML application for DFL (Bundesliga). +30% fan engagement.
    • Open-sourced a Security Hub solution adopted by 10+ Fortune 500 companies.
    • EMEA North Security Bar Raiser for $10M+ engagements.
  5. 2019–2020

    Software Developer

    Slagkryssaren·Stockholm

    The apprenticeship. Six end-to-end customer projects in eighteen months teaches you more about shipping than any architecture diagram ever will.

    • Delivered six customer projects end-to-end across the full lifecycle.
    • Built CI/CD tooling adopted across every platform in the practice.
04 Selected Engagements.
05 Case Studies. Deep reads
  1. Nordic telematics · 18 months

    Serverless IoT at 200K messages per second, for 1.6M vehicles

    A legacy telematics platform was folding under load. We rebuilt the ingest layer on serverless primitives. Cost held flat through 3x traffic growth. Here's what that took.

    Read the case →
  2. European media, professional sport · 14 months, two phases

    Real-time ML for the Bundesliga

    The Deutsche Fußball Liga wanted broadcast-grade real-time insights during matches. We built the platform that scores match moments in under two seconds of latency, for every live broadcast.

    Read the case →
06 How I Work. Three shapes

Engagements tend to take one of three shapes. Not a menu. A pattern.

  1. I

    Anchor

    Long-horizon partnership

    12 to 36 months

    The deal that defines the quarter. Multi-year platform work where I'm the named commercial lead, the architect signs the paper, and the outcome shows up in the customer's annual report.

    Includes
    • Executive sponsor alignment, quarterly
    • Architecture review standing the commercial up
    • Delivery team selection and escalation path
    • Renewal authored a year before renewal
    Honest limit

    Two at a time. Anchor work is the thing that fails when you try to run a third one in parallel.

  2. II

    Review

    Focused engagement on one decision

    One to three weeks

    A single architecture review, deal review, or program reset. Typically before the commercial conversation, or when a program has drifted and needs an honest second read.

    Includes
    • Pre-read of current state, 1 hour
    • Whiteboard session with the team, 3 hours
    • Written memo with the recommendation
    • One follow-up if the call is close
    Honest limit

    I don't chair steering committees on Review work. If it needs ongoing governance, it's an Anchor.

  3. III

    Referral

    Connection or introduction

    A Slack message, a warm intro, done

    An intro to the right architect, the right founder, the right operator. These are the highest-leverage thirty minutes in my calendar and they happen for free.

    Includes
    • A real call with the person who should take this
    • An honest read on whether this is a fit
    • Follow-through when the intro lands
    Honest limit

    I only introduce people I have actually worked with. If I don't know them well, I say so.

Not currently taking advisory or consulting engagements outside AWS. This is how the work looks when it does happen.

07 Building.

Current craft Q2 2026

  1. ReelForge
    Swift · SwiftUI · AVFoundation · Ollama · Groq
    Local content-automation app running on a Mac Mini M4 as a headless inference box. Ollama handles the first pass; Groq is the fallback when the local model is wrong about a frame. Built in a single day, refining since.
  2. murateksi.com
    Hugo · Fraunces · Geist · vanilla JS
    Rebuilt from a generic template into a small custom theme. Three weights of information, one accent color, one editorial serif, no build step. This page is the reference implementation.
  3. Writing
    One essay every two weeks
    Publishing on selling to technical buyers, AI-ready architecture, and the operator’s craft. The writing is how the thinking stays honest.
08 Writing. 6 essays
Pinned

The Technical Seller Advantage: Why Engineers Who Can Sell Win

The most effective sellers in enterprise technology aren't traditional salespeople. They're engineers who learned to connect technical depth with business outcomes.

There’s a persistent divide in enterprise technology between “the people who build” and “the people who sell.” Engineers look at salespeople with suspicion. Salespeople look at engineers as resources to be deployed on calls. Both sides lose.

Read the essay →
  1. Your Architecture Isn't AI-Ready. Here's What to Fix First.

    Read
  2. How to Sell Cloud Transformation to Executives Who Have Been Burned Before

    Read

All writing →

09 Speaking.
  1. 2025

    Selling platforms, not products

    AWS re:Invent·Las Vegas·Internal session

  2. 2024

    What ships in production when the platform team is five people

    Nordic GameTech Summit·Stockholm·Panel

  3. 2024

    Serverless at 200K messages per second

    AWS Summit Stockholm·Stockholm·Technical talk

  4. 2023

    Cloud security patterns that close deals

    EMEA Financial Services·London·Breakout

10 Selected Results.
$30M+
in platform revenue influenced
200%
of 2025 quarterly target
50+
consultants led across EMEA
9
languages spoken, professionally

Languages EN · SV · TR · DE · ES · FR · IT · PT · NO

What you won’t find here: vanity AI demos, lift-and-shift migrations sold as transformation, or a slide that says “synergy.”

11 Contact.

For enterprise cloud, complex Nordics and EMEA engagements, or to argue with an essay, the fastest path is email.

Founders: if you’re pre-seed in infra, devtools, or applied AI, the cold email bar is low. Send the thing you’re building.

Current availability

  • Advisory closed Not taking engagements outside AWS.
  • Speaking selective Enterprise, GameTech, cloud architecture. Say which.
  • Writing open Essays and longer pieces, on the topics on this site.
  • Introductions open To people I have actually worked with.
  • Angel closed Not writing checks.
  • Interviews selective Podcasts and press, one sentence on the angle.

Print this page as a CV →