A tracking plan before the feature
Event, trigger, properties and the question the dashboard will answer, written down before the code. Then the event ships with the feature, never as a follow-up ticket.
PostHog in every project since 2024
A PostHog developer who makes the dashboard the source of truth
Tracking plans per feature, a first-party proxy so ad blockers stop eating your data, EU cloud for GDPR, dashboards leadership reads without asking, and agents that query PostHog through MCP. This page tracks itself below, in the open.
Available from November 2026 · Wrocław, Poland (CET), remote
- “someone you can always count on”public LinkedIn recommendation
- “a true bias for action”client CTO, on LinkedIn
- 15+ yearsshipping software
- Free call, no pitch deck30 minutes, then you decide
~40×more commits year over year with agents under enforced rules
~30%of merged PRs in 2026 opened by an AI agent, ~85% reviewed by me
8platforms shipped for Sandtime.io as founding engineer
15+years shipping software
Why me
Data that reaches the server
First-party proxy on your domain, no cookies, local storage persistence, EU hosting. The same setup runs under ciunkos.com and is what this page uses.
Dashboards leadership reads
Activation, retention, revenue and adoption per client, built so the weekly call starts from the numbers. Growth for a SaaS went from near zero organic acquisition on exactly that loop.
Agents on top of analytics
MCP adoption measured per client from day one, dashboards and insights built through PostHog’s MCP with coding agents. AI without analytics is running blind.
Proof
Work I can show
Problem, what I did, result. Client names only where I am allowed to use them.
Taking over growth: SEO, GEO and dashboards leadership reads
- The problem
- Organic acquisition was close to zero and nobody could say which feature moved which number.
- What I did
- A tracking plan per feature, PostHog KPI dashboards, SEO and GEO work on landing pages and help, with help, changelog and landing pages treated as one body of context for people and bots.
- Result
- Organic acquisition grew from near zero and leadership gets its numbers from dashboards, not from asking. Numbers stay relative on purpose.
Back-office task management: team lead of four, no product manager
- The problem
- A back-office tool needed new features, a UI refresh and a faster pipeline, with no product manager in sight.
- What I did
- I led four engineers and kept coding. Trunk-based development with CI/CD, live updates over server-sent events, a stopped parallel initiative that analysis showed would not pay off, priorities set directly with department managers.
- Result
- “Measurable changes in some key metrics” and “a true bias for action”, in the client CTO’s public LinkedIn recommendation.
See also: Full-stack & custom software
An MCP server from first merge to first external users
- The problem
- Users wanted to log time from their AI assistants. The API existed, the agent surface did not.
- What I did
- I set the tool surface, removed destructive tools, routed every operation through the existing REST controllers so an agent gets no wider access than a person, and instrumented adoption per client in PostHog from day one.
- Result
- First external users within weeks. A bot-protection rule that rejected MCP clients by user agent was found and removed the same day because the dashboard showed it.
See also: AI & agents · AI in your company
One foot in the door
Not ready for a project? Start smaller.
Two ways to see how I work before you commit to a sprint. Fixed scope, a number in writing after a short call.
PostHog & product analytics codebase audit, one week
I read the repo, CI, tests, security and the parts the team avoids. You get a written report with findings ranked by risk, a plan with milestones and a go or no-go you can defend. I have run this for a large software house before its clients saw the code.
Code review of one pull request or one module
Send me the diff that worries you. Within a few days you get line-level comments, the three things I would change first and whether I would merge it.
Ask about an audit Free 30-minute call first. If an audit is the wrong tool, I say so on the call.
Live demo
This page, tracking itself
Every event this page sends to PostHog appears in the feed on the left, with its properties, as it happens: the page view, this demo mounting, your clicks on the buttons. On the right, the tracking plan that produced them. Fire a test event and watch it land.
Demo loading…
Block the request in your dev tools and the feed shows it too. That is the point of a first-party proxy.
How it works
Three steps from this page to a running project.
- 1
A 30-minute call
You describe the product and the problem. I ask the questions I would ask on day one. If I am not the right person, I say so and point you to someone who is.
- 2
Scope in writing
A short written plan follows: what we build first, what we measure, how we work together and what it costs. No slide deck.
- 3
Something to touch in week one
The first slice ships in the first week: deployed, measured, reviewable. From there the work is paced by what the numbers say.
Fit check
Is this a fit?
A good fit when
- You need a senior who owns delivery, not a pair of hands
- The product has to ship and be measured, with or without a product manager
- A solo engagement or a team of up to four
- TypeScript, React, Node.js, Cloudflare, Postgres, PostHog
Probably not when
- A program that needs a ten-person vendor team
- A stack built around Java, Python or a cloud I do not sell
- Body leasing by the hour with no say in how the work is done
- A start before November 2026
Working style
How I work
Measured, not assumed
PostHog in every project from day one. A tracking plan per feature and dashboards leadership actually reads.
Zero bug policy
A bug is fixed or consciously closed, never parked. Alerts and error tracking in every project, so I learn about problems before the client does.
No product manager? Fine.
Where there is no PM I set priorities directly with the people using the software and answer support myself.
FAQ
Questions people ask before they book
EU hosting and GDPR?
PostHog Cloud EU, no cookies by default, no personal data in properties unless the product needs it and the policy says so. Consent banners only where consent is the lawful basis.
What about ad blockers?
A first-party proxy on your domain, with a path that filter lists do not match. Expect a visible jump in captured sessions the day it ships.
What is a tracking plan?
A table: event name, when it fires, which properties, which dashboard question it answers, who owns it. It lives in the repo next to the code and the PR that adds a feature adds its row.
Can you migrate from Google Analytics or Mixpanel?
Yes. Map the old events, run both for a few weeks, retire the old one when the numbers agree. Session replay and feature flags come for free with the move. If agents will read the data too, see the AI and agents page.
Feature flags and experiments too?
Flags for rollouts and kill switches, experiments when there is enough traffic to decide. I will tell you when there is not. Agents that query PostHog through MCP are covered on the AI and agents page.
How soon can you start?
November 2026. Book the call and bring your three hardest product questions.
Let’s find out in 30 minutes
A free 30-minute call. You bring the problem, I bring questions. No prices on this page because scope comes first.
If I am the wrong person I will say so on the call and point you to someone better.
After you book: a calendar invite, then the call. Nothing else to fill in.
Available from November 2026 · B2B contract or employment · Wrocław, Poland (CET), remote