Founded the studio, and still works on both sides of it: draws the thing, then builds it. Holds the line that a fast site nobody wants to use is still a failure. Happiest camping with a dog and a cat who both think they are in charge.
We build the half of a website nobody photographs.
A eight-person studio in California. We take a small number of builds at a time on Shopify, WordPress, Craft and Drupal, and stay with them after launch. The people who scope your project write its code.
Frustration and expertise, in roughly equal measure.
We kept meeting the same business: a site that photographed well and quietly failed at its job. Slow, invisible in search, analytics never configured.
The gap was never taste. It was the engineering underneath. So we built a studio for that half, and paired it with people who can design.
What working with us is like.
You watch it get built rather than waiting for a reveal. Surprises at the end are a process failure.
What shipped, what’s next, anything we need from you. Short enough that you read it.
The engineer who scoped your build is the one who writes it. No handoff to a team who weren’t in the room.
During the build and after it, on sites we built and sites we didn’t.
What we are, and what we’re not.
Eight people. Every name, by the second call.
14 years in machine learning and language models. Designs the AI agents we build: which model to use, what data it can see, and how it’s tested against real conversations before it goes live.
Over a decade of code behind him, and the one who opens the hood on every audit. Hands the hardest platform problem and calls it a good week. Cricket obsessive out of hours.
Takes the projects nobody has a playbook for: the odd integration, the platform we haven’t touched yet. She scopes it with the client, runs the team through it, and checks every detail before it ships.
Platform work and migrations, including the unglamorous parts: redirects, data integrity, and making sure nothing quietly disappears at launch.
Turns design files into templates that hold up on a three-year-old Android — and is usually the first to find the flaw in a layout that looked fine in Figma.
Builds the pages and fixes what breaks, across browsers and devices. Also runs the accessibility pass before anything goes live.
Designs the pages and the flows through them, close enough to the build that what he draws is what ships.
A site you can’t measure is a site you can’t improve.
Server-side GTM and GA4 with real conversion events, matched to Ads and Search Console.
Core Web Vitals watched after launch, not just measured at it.
ADA Level AA and WCAG 2.2, built in from the first template.
One short monthly note in plain words. No dashboard nobody opens.
Now you know us.
Tell us what’s broken and we’ll tell you honestly whether it needs a rebuild or just a fix.
We rarely hire, and never in a hurry.
We don’t run an open pipeline or post generic listings. When a build needs a skill we don’t have, we go looking, usually through people we’ve already worked with.
If you’re the sort of engineer or designer who reads someone else’s code before rewriting it, we’d like to know you exist before we need you.
- Shopify or WordPress, deepLiquid, private apps, plugin internals: past the theme editor.
- Front end that survives handoffAccessible markup, real performance budgets, no framework worship.
- Writing, not just committingYou can explain a trade-off to a client without a diagram.
hello@pixelolabs.com · a person reads it, within one working day. Send your CV along with code, sites, or the thing you’re proudest of.