AI strategy · ML engineering · Independent

AI strategy and the system to back it, from one person.

I help e-commerce and SME product teams turn AI experiments into production features that are measured and hold up. 16 years in product, including recommender systems at Seznam scale.

  • 16
    years in product
  • 50M+
    requests/day at Seznam scale
  • 3
    peer-reviewed RecSys papers
Karel Koupil

Who I work with

Pick your track

E-commerce

For online stores that have tried AI and want it to move store metrics, not slideware.

  • Support assistants that cut ‘where’s my order’ tickets
  • Product data and descriptions that scale to every SKU
  • Recommendations and search that lift discovery
Explore the e-commerce track

SME / product teams

For 10–250-person teams that want one AI thing in production, done properly.

  • An internal assistant over your docs, wikis and tickets
  • Back-office automation with guardrails
  • Evals so you can trust what shipped
Explore the SME track

What I do

Five things I build

Which one you need is part of the conversation. Often it is not the one you came in for.

RAG & assistants

Answer questions over your own content and data, with citations.

  • Grounded in your docs, catalog, tickets
  • Citations and guardrails, not guesses
  • Evaluated before it ships

Chatbots

Conversational front-ends done properly: scoped, evaluated, safe.

  • Clear scope and hand-off to humans
  • Multilingual where it matters
  • Measured on resolution, not deflection alone

Agents & workflow automation

Multi-step systems that call tools and take actions, with guardrails.

  • Catalog enrichment, triage, drafting, back-office
  • Human approval where the stakes are real
  • Observable, reversible steps

Classic ML

Recommenders, scoring, forecasting, segmentation: when an LLM is the wrong tool.

  • Recommendations, propensity, demand forecasting
  • Offline metrics and online A/B
  • Built to retrain, not rot

AI observability & evals

Know whether your AI is any good, and catch it when it regresses.

  • Eval sets and eval-in-CI
  • Trace logging, cost and latency
  • Regression alerts and PII / prompt-injection guards

The difference

I scope the work and I build it

Most options are either strategists who hand you a deck, or developers who build what they are told. I do the scoping (which use case, LLM-API vs a model, RAG vs a recommender, what ‘good’ means) and the build: prototype, integration, evaluation, handover. One person, one accountable line from idea to a measured result.

The engagement, end to end, run by one personA single horizontal path with six steps, all run by one person: idea, then use-case selection, then approach, then prototype, then evaluation, then handover. ONE PERSON IDEAUSE-CASESELECTIONAPPROACHPROTOTYPEEVALUATIONHANDOVER

Selected work

Systems I’ve built

Prior in-house work, reframed around what the system did and what changed. Client engagements are added as clients approve them.
Media · Recommenders In-house

Recommenders at Seznam scale

Discovery and ranking across 50M+ requests/day: clickbait mitigation, long-tail, an experimentation framework.

SME · Product In-house

Email Machine, concept to production

Co-founded and scaled an email platform from one retailer's internal tool to a SaaS running 100M+ emails/month for 196 brands.

Named client references available on request.

See all work

Writing

Papers & notes

Read more writing

About

Who you’d work with

I started out watching companies sit on data they never used. That led to co-founding an email platform, then a decade at Seznam as senior PM for its recommender systems. I now work solo, scoping and build, with e-commerce and SME product teams, from the EU.

More about how I work

Tell me where your AI is stuck.

Thirty minutes, no pitch. Your situation, your data, whether this is even the right problem.