Mika Pozo.

Full-Stack GTM Engineer / Growth Architect

A GTM Engineer & Growth Architect portfolio. Systems in production.

A curated selection of systems I've designed and built. Each deep dive walks through the thinking, the strategy, the technical execution, the trade-offs I chose, what broke, and what the numbers say.

65–75%cold replyWhatsApp BDR
$3CPCMeta Ads · sustained 1mo
R$30KMRRrecurring · solo
the thesis

In marketing and GTM, we trade in insights: how to do it, how to frame it, how to offer it. But what looks like insight is, most of the time, intuitive assumption. A guess.

What I came to realize is that the best motions I've designed (in my own business or someone else's) came from systems thinking, and from knowing the buyer as intimately as you'd know a partner, not a persona. That's the real edge. I've spent most of my career solo or fractional, and the only reason I could outcompete bigger companies was that one “little” detail.

A business, the way I see it, is a living system, not a fixed machine. It grows, adapts, and responds to its environment, and that's how it survives. The customer isn't outside that system; they're an integrated part of its ecosystem.

It may sound silly, but GTM is too often a rigid blueprint, when the optimal thing to be is the organism's nervous system: its behavioral response, the way the business feels out the market. Its job is to find the business's ecological niche, the one space where it can thrive without being rejected by the environment.

AI has collapsed the cost and time of building software, so the market is overflowing, and everyone is fed up with outreach and ads that sound like everyone else's.

My move is the opposite of more volume: learn the exact way the ICP talks (the words, the mannerisms, the pain and the outcome they name themselves) and feed it through inbound, outbound, and content alike, all stitched together.

That's what I call customer-driven systems: data and neuropersuasion in one motion, so you're not competing in a market at all, because you're not offering what you think they need. The lead feels understood, not sold to, and the guard never goes up. You can get a sneak peek in the breakdowns below.

applied thinking
Strategy / take-home
Final round · CEO

A YC startup's SDR lead flow, rebuilt as a take-home — capacity math over effort.

Deep dive in progress
skills & stack

Craft — what the tools don't ship

  • Copywriting
  • Sales psychology (NEPQ)
  • Offer design (value equation / risk reversal)
  • Positioning & demand creation
  • Buyer-language extraction
  • Conversation intelligence
  • Outbound & allbound strategy

Stack — what I operate

n8nLangGraphSupabaseEvolution APITwenty CRMReacherCal.comMeta AdsCloudflare Zaraz / Meta CAPIClaude Code (MCP)Figma (MCP)Custom scrapers & enrichmentCustom lead scoring

Technical — languages & primitives

SQLPython (scripting, data extraction)JSONREST APIs & webhooksPrompt designStructured outputError handlingEmail deliverability (DMARC/SPF/DKIM)AI-assisted scripting
about

By the time I'm writing this, I've tinkered with ~30 LLM models, a few harnesses, and a dozen custom solutions I built myself. I still think AI is an amazing thinking and building partner — extremely useful for someone who knows what they're doing and the output they want, and awful at doing anything on its own.

I'm a multi-hyphenate — the Virgil Abloh route, if I'm honest about the lineage: a civil engineer who ended up in taste and persuasion instead of structures. The engineering is where the systems thinking comes from — you don't get to improvise a structure — even though I never practiced it. I ran my own mid-luxury resale store, where storytelling, taste, scarcity, and positioning beat follower count every time. Then I consulted and co-produced product launches — offers and direct-response marketing at scale. Apex is where all of it converged: my operating lab, solo, end to end, selling to the most skeptical ICP there is, where fine-tuning isn't polish — it's survival. Now I want to bring that mix somewhere it compounds — a team, real resources, harder problems.

The BDR is almost a state-of-the-art of who I am — an intersection of a dozen disciplines.

Open to roles

Full-Stack GTM Engineer / Growth Architect — full-time or fractional. B2B SaaS, remote.