30+ across team and network. Remote-first. The patience of a print job, applied to digital.
Kodapixel is one studio with six teams: development, design, brand, social media, marketing, and content. 30+ across the team and network, remote-first, distributed across Europe, the US, the UK, and Australia. Small enough to keep the work consistent, broad enough to take a launch end to end.
We take work end to end (strategy, design, build, launch, iterate) or we slot into one stage of it. Both work. The studio model is what keeps services on the same project rather than handing off across agencies; one timeline, one lead, one voice carried through the build.
Started solo by Leart in 2020, structured-team since 2022. Six teams now, same operating principles since the first project: be specific about tools, build systems that work, document what you build. The patience of a print job, applied to digital.
The shape of the work, on every project, no matter the service.
We never start a build without the type scale, spacing, and component primitives in place. Pages get composed; they’re not invented one at a time. The system is the spec. Once it’s right, every section that follows inherits the rhythm. It’s the difference between a site that holds together at scale and one that drifts into pretty exceptions.
Every web build begins as a self-contained HTML/CSS/JS prototype. We confirm the look and the structure in the browser before we touch Liquid, ACF, or any framework. The prototype is honest about what wraps, what breaks, and what reads as one idea. Figma comes in afterwards, as the polish layer.
Proposals say "Shopify Liquid" or "ACF Pro custom fields", not "modern web technology". The specificity is the brand. When we say multilingual we mean Shopify Markets or Polylang. When we say lifecycle we mean Klaviyo flows by name. Vague proposals produce vague work; specific ones make the project clear from day one.
Every project comes with a brief, change-request templates, menu and structure docs, field maps, and a handoff that lets the in-house team take it forward. A site without documentation is a site that decays. We treat the docs as part of the build, not an afterthought, and they are delivered on the same timeline as the code.
Iteration, reporting, and asset extension are part of how we scope the project from the start. Launch is a milestone in a longer arc: paid creative needs cutdowns, the storefront needs sections, the brand needs new applications. We stay close enough to keep the work consistent six months in, twelve months in.
Slot us in for a single stage, a few in parallel, or take the whole studio end to end.
A Liquid build, an identity refresh, a paid campaign, a shoot. Fixed scope, fixed timeline, delivered with the documentation to extend it in-house. Useful when you already have the rest of the system covered and need one specific thing made well.
Design plus development, brand plus social, marketing plus content. One studio lead, one timeline, no agency-to-agency handoff tax. The services stay in conversation through the build, which is where the consistency comes from.
All six teams. Strategy through launch through iteration. Site, brand, campaign, content, paid, lifecycle, landed together as one launch. The shape of work the studio was built for.
The same shape whether it’s a site, a launch, a brand, or all three at once.
What we’re building, what "done" looks like, and how we’ll measure it.
Type, color, spacing, components, and the voice they all carry.
HTML/CSS/JS prototype before CMS port for web. Concepts and shooting boards for content and campaigns.
Shopify, WordPress, ACF, multilingual, ad accounts, email platform, and analytics, all connected and tested.
Web launch, paid creative, organic plan, email flows, content drops. The campaign and the site go live together.
Reporting, asset extensions, theme updates, change-request flow. We don’t disappear at launch.
Restraint, & the patience to delete twice.Studio principle, n.1
Most projects start with a 30-minute call. We’ll come prepared.
Start a project