Why we built a checkpoint for coding agents.
Coding agents are good at logic and indifferent to side effects. The analytics call sitting inside a checkout function is a side effect. So it gets dropped, and your funnel goes quiet for three sprints. Skene exists because someone has to be aware that the call matters.
The pattern we kept seeing.
We watched teams ship faster with Cursor and Claude Code, and we watched their dashboards drift weeks later. The two things were connected. A function got rewritten, the insert that recorded the event did not survive, the funnel kept drawing from worse data.
The agents were not careless. They are pattern-matchers operating on logic, and the tracking is structurally invisible to logic. Skene reads the same code the agent does, but specifically for the calls the agent does not see.
Three co-founders in Helsinki.
€800K pre-seed in 2025. Building Skene full-time.
Teemu Kinos
Co-founder
Built and operated growth at SaaS companies for a decade. Skene is what he wishes existed when the dashboards stopped agreeing with each other.
[LinkedIn]Michele Boggia
Co-founder
PhD in physics. NLP since the start of the field. Handles how Skene reads code at scale.
[LinkedIn]Teppo Hudsson
Co-founder
Built multiple products end to end. Super technical, obsessively product-focused.
[LinkedIn]
Separation of duties
The agent writes the tracking. It should not grade its own work.
An agent checking the tracking it just wrote is the conflict of interest the check exists to remove. Skene runs alongside Cursor, Claude Code, and Codex, not inside them. The gate sits outside the tool that made the change: it reads the diff against your Supabase schema, sees a write stop landing in its table, and leaves the verdict as a PR comment. The reviewer answers to your schema, not to the agent it is reviewing.
It is not a dashboard you babysit or a copy of your data. Your data stays in your database. Skene owns the gate, and the trusted record you query over MCP for what drives revenue.
Broken tracking is more than a bug.
When dashboards drift, decisions drift. Product reads the funnel wrong. Growth optimizes against bad numbers. An exec makes a roadmap call against a chart that has been broken since a refactor three sprints ago.
The bug is not the missed event. The bug is that the team stopped being able to trust their own data.
Trust is the first half. The second is the intelligence built on it: query Skene over MCP from your coding agent for the user paths and cohorts that drive revenue, so the team knows what to reinforce and what to cut.
