Michalina Kowalczyk
I build the tools and systems that marketing sites need. Whether that's a CMS that scales, a lead flow that works end-to-end, or custom tooling that solves a problem your current stack can't handle on its own.
Based in Warsaw, Poland. Sharing a life with a boxer pup🐾Lady Ruby, spending an unreasonable amount of time on weightlifting and sudokuing, and making questionable sock choices.
Sometimes that's a CMS architecture for thousands of pages. Sometimes it's custom tooling your site needs but your platform can't do natively. Sometimes it's connecting three internal tools that don't talk to each other. The common thread: there's a real problem, the existing setup doesn't solve it, and I work within the stack you have to build what's missing.
8+ years working with marketing and growth teams — which taught me something most engineers don't learn firsthand: why these systems matter and what breaks when they don't. I understand how acquisition and conversion work end-to-end. Now I design and ship the infrastructure and tooling that gets it right.
Projects
Content Infrastructure System
- The Problem
- V7's marketing site kept growing. First an agents library, then document types, then an integrations directory that needed to interlink with existing content. Each new section meant more CMS records, more cross-references between collections, and more demand on the search and filtering components I'd built earlier. The system needed to support 12,000+ records across 6 interconnected collections and keep scaling without rebuilding every time.
- What I Built
- A three-component data pipeline: a custom Framer plugin that exports and normalizes CMS data across 6 collections, a Vercel serverless API that stores it as public JSON, and React search/filter components that make thousands of records instantly searchable with URL-synced state. The whole system lets the content team publish independently while the data stays consistent.
- What It Did
- 2,000+ dynamically generated pages. Sub-second client-side search across thousands of records. Non-technical team publishing independently. Real-time content updates without deployments.
Framer CMS (12,000+ records, 6 collections)
↓
CMS Exporter Plugin (normalize + resolve cross-references)
↓
Vercel Serverless API → Blob Storage (public JSON)
↓
React Search/Filter Components (client-side, URL-synced)
↓
Production Directory Pages (agents, integrations, docs)Demo & Lead Acquisition System
JL Engine — Job Search Infrastructure
LeftyWorkout — Training App Frontend
Content Operations Data Pipeline
Little Xmas — Interactive Gift Experience
About Me
4 years owning V7's full marketing tech stack gave me a systems-level view of how marketing, growth, and engineering actually connect. Now I work with SaaS teams as a freelance engineer — designing and shipping the infrastructure and tooling their stack can't handle on its own.
I value autonomy, coherence, and systems thinking. Environments where systems don't exist yet or need scaling are where I do my best work.
Remote, EU based.
Work With Me
Project build
You have a specific problem your current setup doesn't solve. A CMS that needs to scale, a lead flow that's broken, internal tools that don't talk to each other, or custom tooling your platform can't do natively. I scope it, build it, document it, and hand it over.
Fixed scope and timeline. You get a working system, self-sustaining after handoff. Typical engagements 2–6 weeks.
Embedded growth engineer
You need someone who owns the marketing stack end-to-end — CMS, landing pages, lead flow, integrations, experiments — but you can't justify a full-time hire yet. I work alongside your team, part-time, with the context and ownership of an in-house engineer.
Part-time ongoing, 1–3 days/week. Retainer basis. Best fit for growth-stage SaaS teams with an existing marketing site and no dedicated engineer.