Head of AI Craft @ tonik.com / Remote / 25k+ PLN net
That's how much human creative work leaves this studio every month. Eighty people designing brands, products, and websites for the most funded startups on the planet.
Now imagine someone walks in and makes every one of those hours produce twice as much - without anyone working harder and without a single pixel dropping below the bar that got Segment, Okta, and Supabase through our doors.
That person changes the economics of the entire company.
That person is you.
Design partner to 200+ YC companies. 20+ unicorns. Official partner of a16z Speedrun. 80 people in Poznań. Profitable, growing, uninterested in being a commodity.
We're not starting from zero on AI. Our product designers already build in Cursor. We've built Alfred, an internal AI assistant that handles operational workflows. We run an AI-powered dashboard that tracks studio performance in real time. Pockets of the team are deep into AI-assisted workflows and pushing the edges of what's possible.
But that's the problem - it's pockets. Scattered adoption. Individual experiments. What we don't have is someone who takes all of this energy and turns it into a system. Someone who looks at 80 people, each figuring out AI on their own, and says: here's how we all work now.
You're not here to "explore AI" or convince anyone it matters - that argument is already won. Half the team is ahead of you on specific tools. What they need is architecture. A unified approach. Standards. Infrastructure that makes the best workflows available to everyone, not just the early adopters.
Founder-level mandate. Real budget. No committee. No "innovation lab." You ship changes into live client projects from week one.
Weeks 1–2. You've sat in on active projects. You've talked to the designers already using Cursor, the PMs experimenting with AI-generated briefs, the developers who've built their own shortcuts. You've mapped what's working, what's duplicated, what's missing. You've identified the five biggest time sinks that no one has touched yet - and the three existing workflows that need to scale to the whole team, not just the people who built them.
Month 1. Two workflow changes are live and being used daily. Maybe it's a brief-to-layout pipeline that gives designers three structural options before they've opened Figma. Maybe it's an automated QA pass that catches spacing, alignment, and consistency issues in seconds. Maybe you took something one designer hacked together and made it production-grade for the whole studio. The results are measurable. The skeptics are quieter.
Month 3. You've trained your first batch of custom LoRAs on Tonik's body of work. One captures our editorial illustration style. One nails the abstract 3D visual language we keep returning to. One handles textural, atmospheric hero imagery. When a designer generates starting points, the output already looks like us - not like the AI slop flooding every portfolio site on earth. Clients don't know AI was involved. That's the point.
Month 6. Project timelines have compressed visibly. Work that took four weeks takes two - not because craft was sacrificed but because the tedious middle was automated and humans spend their hours on the decisions that require actual taste. You've extended Alfred's capabilities beyond operations into creative workflows. You've built internal tools the team would revolt if you removed. Leadership is asking which ones could become products.
Month 12. AI fluency is no longer your department - it's ambient. Designers train project-specific LoRAs themselves. The developers who were already fast with Cursor are now mentoring others. PMs use content pipelines you built to draft case studies and client updates. The dashboard tracks AI-assisted productivity alongside everything else. You didn't just introduce tools. You took a studio that was already experimenting and gave it a spine. Now you're building whatever comes next - a product line, a new service offering, something nobody's imagined yet.