I build the layer
agents generate against.
Content infrastructure for B2B SaaS — schemas, content models, and the CMS architecture underneath. Built so the stack survives a third page type, and so the next wave of agents has something clean to generate against. Hackathon mentor on the side.
See where I can help
YEARS BUILDING REACT7+
BASED — REMOTE-FIRSTEUContent Infrastructure
Schemas, content models, and the CMS architecture beneath them. Structured so multiple page types — and the agents reading from them — scale without a rebuild.
0→1 Product Engineering
Greenfield Next.js. Stack picked from the product's actual constraints — TypeScript, React, Sanity, Vercel, Supabase. Owned end-to-end when solo, contract-bound when in a team.
Design Systems & Architecture
Reusable TypeScript/React component libraries documented in Storybook. Stack selection, state-management patterns, contract design, data-layer migrations. The boring foundations multiple product surfaces sit on.
Where I Can Help
Where I Can Help
Your CMS can't grow past one page type.
Schema and content-model design for B2B SaaS. Structured so marketing can add page types without an engineer in the loop — and so agents have something clean to generate against.
Your CMS is slowing marketing down.
Headless content migration to Sanity. Schema restructured so marketing can add page types without an engineer in the loop. Done in-flight, without a content freeze.
You need a 0→1 product shipped end-to-end.
Greenfield Next.js. Stack picked from your product's actual constraints — TypeScript, React, Sanity, Vercel, Supabase, or whatever fits. Frontend, backend, and deploy. Owned solo or alongside your team.
Your component library isn't surviving the scale.
Reusable TypeScript/React component libraries documented in Storybook. Consumed across multiple product surfaces without forking. Theming, accessibility, and a contract that holds.
You're mid-flight and need a senior pair of hands.
End-to-end feature delivery on Next.js applications. Contracts with backend engineers when in a team, full ownership when solo. REST and WebSocket integrations. Vercel ship and post-launch iteration.
The Product
Lens.
How I think about building content infrastructure. Same lens whether the stack is greenfield or already in flight.
01. Stack from constraints.
A stack should fit the product's actual shape — content types, who edits, who consumes. Picked from constraints, not from a house template.
02. Model the content first.
Schemas decide whether a site scales. A model that bends on the third page type is the one you rebuild in year two — design it before the first screen lands.
03. Beyond the demo.
Content stacks live with real authors and — increasingly — real agents. Not the live demo. The boring foundations are what ship the product.
Production code is a longer game than a demo.
What ships in week one is what runs in year three. Build for the year-three version.Community
Active mentor in the European hackathon ecosystem since 2024. Co-organiser of Hackathon for Builders (Poznań) and ADPList meetups (Poznań / Warsaw). Mentoring focus: scoping MVPs for 24–72h delivery and helping teams cut scope to ship.
- Mar 2026IDEA2IMPACT HackathonMentorGdańsk, PL
- Jan 2026European Critical Infrastructure HackathonMentorGdańsk, PL
- Dec 2025HackNation PL — 1500+ participantsMentorBydgoszcz, PL
- 2025Hackathon for BuildersCo-organiserPoznań, PL
- 2024ADPList MeetupsCo-organiserPoznań / Warsaw, PL
Currently
- →7th year at Tonik — building content infrastructure for B2B SaaS clients.
- →Stack: TypeScript, React, Next.js, Sanity, Vercel, Supabase.
- →Active mentor in the European hackathon ecosystem — HackNation PL, EU Critical Infrastructure.
Scaling content?
Need a content infrastructure engineer for your B2B SaaS? A senior pair of hands on a Next.js build? A mentor for your hackathon? Any of the above.