Hi, I'm Sasha Kai.

Every company I've ever worked with has the same problem. They built something good, sometimes something genuinely great, and they can't explain it. Not in a way that makes someone stop and listen.

The engineers know what it does and the founders know why it matters. But somewhere between the product and the person who should be buying it, the story falls apart. Features get listed, jargon piles up, and a product that could change how people work gets ignored because nobody translated it into something a human being would care about.

That's where I've spent the last 17 years. In the gap between what's built and what people actually want.

Third-culture person

I started coding when I was 6, growing up in Belarus. Built my own computers, took apart anything with a circuit board, learned how things connect at the level where electrons move. At 15, I came to the States as an exchange student. That year changed everything. When you're a kid dropped into a completely different culture, speaking a language you're still figuring out, you learn something most people never have to: how to take an idea that makes perfect sense in one world and make it land in another.

I didn't know it then, but that's the skill that would define my career.

I went back to Europe, studied, then came back to the US for good.

The accident and meditation

In 2019, I was hit by an SUV. I'll spare you the details. The recovery took years, and it was exactly as hard as you'd imagine.

But something happened during that time that I didn't expect. I went deep into meditation. Not the kind you find on apps. Real practice, with real teachers. I got certified, accumulated over 500 hours of direct teaching, and worked with practitioners and healing professionals.

A decade of consistent practice gave me something I didn't plan for: a deep, working understanding of human psychology. How emotions form, how attention shifts, how people construct meaning from incomplete information. When you spend thousands of hours watching your own mind operate, you start seeing the same patterns in everyone else.

I use this constantly. When I'm positioning a product, I can feel how a message lands, where attention drops, what creates the "this is for me" moment. That understanding shapes everything I write, from the first line of a landing page to how I structure a whole go-to-market narrative.

How I think

My approach to every problem starts with design thinking and humane design as a daily practice. I map customer jobs, pains, and gains before I write a single line of positioning. I build frameworks for rapidly validating ICPs, then prototype and test before committing.

I pull from systems thinking and pattern recognition across seemingly unrelated fields. I've built my own tools for this, frameworks for structuring customer research and value proposition design that I use on every engagement.

If someone asked me to describe what I actually do in one sentence: I absorb signals from places that don't seem connected, find the insight that matters, and present it in language that stakeholders can understand and act on immediately.

The builder

I don't just market products. I build them.

Get Zesty is an AI-powered ADHD medication tracking app I designed, built, and put on the App Store. Mango Lollipop is a lifecycle messaging generator I built and published on npm as an open-source CLI tool. Just Meditate is a minimal meditation app that works on pretty much every device. I've built AI agent systems that process real data across scrapers, enrichment APIs, and react dashboards with real-time updates.

All of these are live, you can explore more in my Work.

This isn't a side hobby. It's why my positioning works for technical products. When I sit in a product review, I understand what the engineering team built because I've built things myself. When I write a narrative for a developer tool or an AI product, technical audiences trust it because it's accurate and clear.

The team builder

I've built cross-functional teams from scratch and led groups of 10-20 spanning marketing, design, engineering, and sales. At PandaDoc, at SENLA, and across consulting engagements.

The hardest part of cross-functional work is never the strategy. It's getting a designer, an engineer, and a marketer to understand each other's constraints well enough to make real tradeoffs together. I've been on all sides of that conversation, which makes it easier to bridge the gaps and keep everyone building toward the same outcome.