01 · Vlad Derkach

AI Product Leader

5 years in product · 12 years building businesses

I build AI product organizations. At RedTrack: 25+ agents in production, an MCP-based B2A strategy, and a Discovery function that turned C-level risk into decisions.

Open to Head of AI Product and AI Product Lead roles — remote or Gdańsk / Tricity. Also taking on one or two AI product engagements at a time.

See how I work
Vlad Derkach
25+
agents in production
17
competitors monitored weekly, automatically
$2.3M
smart-contract volume · Roketo
33 → 75%
onboarding completion · FemFast

02 · About

Vlad Derkach

Five years as a product manager. Twelve years building and running businesses before and around it — law, sales, and companies of my own.

My work is AI product operations: agent fleets that run in production, not demos. I've shipped 25+ agents live, an MCP server that lets external AI agents reach a product's API, a support assistant reading live account context behind two PII layers, and a weekly competitor scout across 17 platforms. I also ship the software myself — the apps in the Builds section below are mine end to end, from architecture to store listing.

I've been Chief Product Officer once — at Roketo, where I took over as CPO during the 2022 Web3 downturn and led the pivot to QUV.io on $70K in grants after half of the parent holding shut down. Before and after that, Product Manager and Product Lead at Zorka.Agency (FemFast), ERA Wallet, a crypto neobank across LATAM and EU, NOWPayments, ChangeNOW, Belkasoft, and others.

My operating principle is simple: adoption follows evidence. I run product on Advanced Jobs-to-be-Done and Next Move Theory — the Zamesin canon, not the generic Christensen version. 300+ customer interviews so far. Before I trained as a product manager I trained as a lawyer (Master of Law, Belarusian State University) — a useful foundation for precision and evidence discipline.

I sail. Not as a hobby garnish — sailing teaches the same things a product organization needs at scale: teamwork, resilience, focus, and calm under pressure.

Based in Europe, remote-first. Open to Head of AI Product, AI Product Lead, and Principal PM (AI / agentic products) roles in B2B SaaS — scale-ups and Series A/B. Also one or two engagements at a time.

03 · Selected case studies

03a

Building AI-Native Product Operations at RedTrack.io

Product Discovery Lead & AI Champion · November 2025 – October 2026

RedTrack is a MarTech attribution and analytics platform. When I joined, Discovery was ad-hoc, no AI ran in operations, and the shift toward e-commerce and DTC from an affiliate-heavy customer base was underway, with a competitive migration window closing on top.

What I built. I turned Discovery from a phase into a company function. A Discovery Request standard now sits at the front of every hypothesis, backed by a Notion-native backlog and a Discovery → decision → delivery flow that produces C-level risk memos before big bets. Around it I ran 25+ Claude agents in production: a weekly Competitor Scout tracking 17 platforms, a Discovery agent network doing Job-Graph segmentation and market-map ROI, a Mobile App Reviews digest, an Onboarding Copilot, and — with my first direct report — a Support AI Assistant that reads each customer's live account settings behind two PII layers, not just the knowledge base. On top of the RT MCP server, an MCP Skills Pack delivered value to users through their own AI agents before they subscribed — B2A infrastructure acting as an acquisition channel.

What changed. Four months in, I entered the Leadership Hub — the C-level strategy body. The mobile app shipped on iOS and Android. E-com and affiliate dashboards were defined, built, and released. MCP went live in production in June 2026. Twelve strategic outputs were personally green-lit by the CEO over the first seven months.

Numbers

25+ agents live · 17 competitors monitored weekly · mobile iOS + Android launched · MCP in production · 1 direct report · Leadership Hub seat

03b

CPO Through the 2022 Web3 Downturn

Product Manager → Chief Product Officer · Roketo · May 2022 – August 2023

Roketo streamed tokens as smart contracts on NEAR — a Web3 primitive with product-market fit signals, then a downturn. Between Q3 2022 and Q1 2023, half of Kikimora Labs — the parent holding — shut down. External funding wasn't available, and the runway on token-streaming as a category narrowed to a wallet + payment use case.

The move. I was promoted from Product Manager to CPO to lead the response. I redefined the product vision around a wallet + integrated payment solution and repositioned Roketo as QUV.io. I secured $70K in grants to buy runway without dilution. I kept the entire team — while half the holding was closing — through the pivot.

The base that made the pivot survivable. In my first six months as PM I had rebuilt the on-chain flow: conversion 4×, $2.3M moved across 7,600 transactions, partner reach 3× through API integrations. That base is what made the pivot survivable.

Numbers

$2.3M smart-contract volume in 6 months · 7,600 on-chain transactions · ×4 conversion · ×3 partner reach · $70K grants secured · 0 team losses during a period when the parent holding lost half its projects

03c

MVP for an AI Wellness App in 2 Months

Product Lead · Zorka.Agency (FemFast) · March – November 2025

FemFast is a personalized AI-driven wellness app for women that aligns fasting, workouts, and supplements with hormonal cycles. The task was to ship an MVP that would justify further investment in 60 days, without team expansion, in a category Meta restricts for advertising by default.

Discovery-first. I ran 40+ JTBD interviews with the target segment before writing a single requirement. That produced sharp segmentation and let me trim MVP scope to what the smallest coherent audience would actually pay for — instead of shipping the founder's original wish-list at half quality.

Attribution and paywalls. I set up a paywall analytics stack with RevenueCat, Mixpanel, and AppsFlyer, and implemented SKAdNetwork and Meta's AEM so we could measure conversions on iOS 14+ without breaking privacy defaults.

Ads unlocked. After sustained work with Meta, we secured approval to advertise in restricted categories — a category-level access, not a one-off ad. That let paid acquisition compound.

Numbers

MVP shipped in 2 months, on time, no team expansion · onboarding completion 33% → 75% · CAC −16% · organic installs 7.9% → 23.7% · SKAdNetwork + AEM unlocked 78% of previously unavailable events · ×3 UA volume with stable CPI after Meta approval

04 · Experience

Eleven companies, four industries — five years of it as a product manager. Details on LinkedIn.

05 · AI systems, inventoried

«25+ agents in production» is the kind of line most portfolios can't back. Mine has receipts. Everything I've shipped with AI lives in one running inventory — scheduled routines, production agents, internal tools, and growth sites — each documented with what it does, when it fires, and where its output lands.

11
scheduled routines
25+
production agents
17
competitors monitored weekly
Thousands
support tickets analysed

live

Competitor Scout

Weekly intelligence across 17 tracked platforms — changelogs, pricing, positioning — synthesised and delivered to Slack.

live

Support AI Assistant

Reads each customer's live account settings behind two PII layers, not just the knowledge base. Built with my first direct report.

live

MCP Skills Pack

Delivers value inside users' own AI agents before they pay — B2A infrastructure acting as an acquisition channel.

06 · Discovery, packaged for other product managers

I didn't just run discovery — I turned my own discovery pipeline into a toolkit any product manager can install in one command. Fifteen sub-agents across twelve steps take a raw brief all the way to a structured, bilingual Notion report. I authored the agent network and the orchestration; the framework underneath is Ivan Zamesin's Advanced JTBD.

15
sub-agents
12
steps
4
research phases
RU · EN
bilingual output
  1. 01 Structure the brief
  2. 02 Parallel research — market map · competitors · community signals
  3. 03 AJTBD validation gate
  4. 04 Segmentation, QA & bilingual report

Install in one command · built on Advanced JTBD (Ivan Zamesin) · MIT-licensed · bilingual · opens in a new tab

A second tool, the same canon

Discovery research doesn't stop at a report. I packaged the extraction step itself — turning desk research, chat corpora and interview transcripts into a Jobs-to-be-Done map — into a second installable toolkit: four Claude Code skills sharing one engine, rendering to a FigJam board, a Miro board, an Excalidraw file, or a single file that opens offline in any browser.

Install in one command · built on Advanced JTBD (Ivan Zamesin) · MIT-licensed · open source · opens in a new tab

07 · Personal builds

I ship products under my own name, not just under a job title. Four live, several in the pipeline.

HandoverBoat

handoverboat.com · charter deposit protection · flagship

A charter deposit protection platform for yacht and boat rentals. Before you sail: photograph the boat's condition with GPS-timestamped, RFC 3161–qualified evidence. When you return: a matching inspection produces a before/after PDF the operator and the charterer both sign against. A public verify endpoint lets anyone independently confirm the record wasn't edited.

Built solo, top to bottom: system architecture, Next.js 15 + Supabase + Stripe stack, UI/UX, illustrations, product design, legal review across HR/EL/IT/PL jurisdictions, copy, SEO, launch. Deployed on Vercel. Eight languages live at launch.

Positioning: an independent evidence record with a reversal of the burden of proof — not a «you-signed-so-you-accepted» acceptance engine.

Sixteen zones on one boat illustration, each a photo-capture point.

Three steps to the first skewer, in RU / EN / PL.

Shashlyk Assistant

mangal-time.shop · consumer app, multilingual, live in production

A shashlyk grilling timer and assistant. The interesting product decision: the UX is designed around the operator's real conditions — dirty hands, bright sun, awkward posture, split attention. Every touch target, every timer trigger, every glanceable state is tuned for that context, not for a comfortable office demo.

The domain runs deeper than a timer. Meat type and cut, coal stage, open-flame behavior, fuel type, height above coals, skewer count — a grillmaster's tacit knowledge translated into structured inputs. Multilingual from launch across RU / EN / PL, illustrated in-house, adapted for the moment of use, not the moment of a design review.

Built for friends; open to the world.

Tapset

tapset.fit · one-tap strength training log · phone + Wear OS

A strength-training log for people who already train and want to record a set faster than a spreadsheet allows. Weight and reps arrive pre-filled with the last result — match it, and logging is a single tap. The rest timer starts itself the moment a set is logged and vibrates through a locked screen in a gym bag. No account, no server: the entire history lives on the device, fully offline.

Tapset is also built for smartwatches running Wear OS. The watch takes over the between-sets loop — rep counter, one-tap confirm, rest countdown on the wrist — so the phone can stay in the bag from the first set to the last. The phone keeps the record; the watch is the remote.

Same design constraint as Shashlyk Assistant: an interface tuned for the actual moment of use — chalked hands, ninety seconds of rest, split attention.

Weight and reps arrive pre-filled from last time — a set logs in one tap.

The hook: your pet, painted like royalty, framed and shipped across the EU.

ArtPaw

artpaw.shop · live e-commerce · real orders across the EU

Renaissance-style pet portraits — your dog or cat composed in the light of the old masters, printed, framed, and delivered across Europe. A full Shopify storefront: catalogue, variants, checkout, EU shipping and tax, and every policy page.

I built the whole thing — brand, copy, imagery, and store — 100% by AI-assisted coding, originally as an attribution testbed for my day job. Then it started taking real orders.

The point it proves: vibe-coding reaches all the way to a transacting business, not just a prototype.

08 · How I think

Three ideas I actually operate on. They are one chain rather than three opinions: jobs come from authentic data, mechanics come from a more mature market with the same behaviour, and delivery is designed around attention instead of frequency of contact.

Each one has a limit, and I've named it underneath.

01

Where the jobs come from

You can't automate the interview. You can automate everything around it.

Nothing replaces a live customer interview — I tested that conclusion hard before accepting it. A synthetic persona generates what's plausible, and plausible is the opposite of what you go into discovery for. But most companies already sit on an archive of real conversations with real customers: sales calls, demos, onboarding, support. Those are authentic words from real people, collected for a different purpose. The model isn't a generator there. It's an extractor.

Given the discipline to store those conversations properly and a lawful basis to use them, transcripts give up Jobs at scale — the context, the trigger, the success criteria, the alternatives that were weighed. That produces a map instead of a handful of points, which is what stops live interviews being spent on reconnaissance.

Where it stops. It will not surface hidden, unarticulated jobs — those still come out live. The archive is also biased towards people who made it to a conversation at all. And with no lawful basis to use the recordings, the method doesn't run.

02

Where the mechanics come from

Shop for mechanics on a donor market.

Benchmarking direct competitors converges a whole category on the same dashboard. Everyone studies everyone, so nobody finds a mechanic that isn't already in the room. That's a local optimum, reached expensively.

So I look for a more mature market whose users behave the same way, and go shopping there instead. A performance media buyer works several screens with their own money at risk in real time, decides within the day, and distrusts somebody else's automation. So does a day trader — and trading terminals are decades of product selection already paid for by a bigger, older, wealthier market. Thresholds instead of reports. Watchlists. Acting straight from the alert rather than being sent to an interface. Real-time P&L. Stop-loss limits. Deliberate information density where the design instinct says to simplify.

Where it stops. An analogy is not an identity — decision horizons, switching costs and regulation all differ, and part of the segment genuinely works slowly and in batches. Every transfer is a value hypothesis, and it goes through the same cheapest-test-first validation as anything else.

03

How the value gets delivered

Silence is a feature.

There have been two eras of value delivery. In the first, the user had to come in and do the work. In the second, products started doing the work and delivering a result — reports, digests, recommendations. Both still charge the user attention: somebody has to read the thing and decide whether it mattered.

The third shift isn't more automation, it's less attention. The product stays quiet while everything is fine, and speaks only when an action is required — carrying the action, not just the news. A recurring digest is actively harmful: if nine messages in ten need nothing, it trains people to ignore the tenth. Zero false alarms beats completeness. And the metric isn't open rate, it's the share of messages followed by an action.

Where it stops. Staying quiet means occasionally missing a weak signal. I take that trade knowingly: a missed alert costs one mistake, while trained-in indifference costs the entire channel — and that one is irreversible.

All three rest on the same base — Advanced Jobs-to-be-Done, in Ivan Zamesin's canon rather than the generic Christensen framing: a segment defined by shared jobs and success criteria, value as energy saved rather than features added, and the riskiest assumption tested before anything gets built.

09 · Engagements

I take on one or two engagements at a time, alongside my main role. The work is always the same shape: production AI inside a product organisation — not a strategy deck about it.

Two weeks

AI Product Audit

I map where AI actually pays inside your product and operations, which agents to build first, and what each will cost per user per month. You get a prioritised build list with unit economics attached — not a maturity model.

From €4,000

Four to eight weeks

Agent Fleet Build

I design and ship the first agents into your production operations — support, competitive intelligence, research, onboarding — with logging, evals, confidence thresholds and a cost model from day one. Your team takes over a running system and a handover document.

From €12,000

One to one and a half days a week

Fractional AI Product Lead

I own the AI product line: what gets built, what gets killed, how quality is measured, and how the team learns to work this way. Minimum three months.

From €5,000 / month

Discovery work — AJTBD research, segmentation, opportunity mapping — is part of every engagement, not a separate product. The toolkit above is how I run it.

Start a conversation

10 · Recognition

Speaking

What people say

«The way he frames problems now — that's strategic-level thinking.»
Vlad Zhovtenko , CEO, RedTrack.io
«He is the kind of person who turns complex and risky startup hypotheses into functioning businesses.»
Dzmitry Khudy , CEO, Zorka.Agency
«When budget cuts hit Roketo, Vlad secured grants, retained the team, and led our pivot as CPO. A highly reliable product leader.»
Taras Dovgal , Co-Founder at NoVPS · previously at Roketo

11 · Contact

Open to: Head of AI Product, AI Product Lead, and Principal PM (AI / agentic products) roles — B2B SaaS, scale-ups and Series A/B. Remote or Gdańsk / Tricity.

Based in Europe · remote-first.