Know us/Est. California
We are a seven-person engineering studio in California, and we build the half of a website nobody photographs.
Seven people
California, remote
Shopify · WordPress · Craft · Drupal
One working day
Architects and designers who 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 are the people who 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
Four commitments, held on every build.
One person owns your build
The engineer who scoped the work builds it. There is no handoff to a delivery team who were not in the room.
A staging link from week one
You watch it get built rather than waiting for a reveal. Surprises at the end are a process failure.
One weekly note
What shipped, what is next, anything we need from you. Short enough that you read it.
Replies inside one working day
During a build and after it. Support clients get the same, on sites we built and sites we did not.
What we are, and what we are not
Worth saying plainly, before you brief us.
Engineers who can design, not an agency with account managers relaying messages.
A small team, staying small, not a page-builder shop skipping the hard part.
Specific before we are fast, not the cheapest quote you will get.
Seven people
Small enough that you will know everyone's name by the second call.
Gaurav
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.
Dolly
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.
Shivangi
Keeps the builds and the people on them moving: scope, sequencing, and who is blocked on what. Fixated on the details nobody notices until they are wrong.
Anjali
Platform work and migrations, including the unglamorous parts: redirects, data integrity, and making sure nothing quietly disappears at launch.
Arushi
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.
Nazish
Builds the pages and fixes what breaks, across browsers and devices. Also runs the accessibility pass before anything goes live.
Manu
Designs the pages and the flows through them, close enough to the build that what he draws is what ships.
Why we insist on numbers
A site you cannot measure is a site you cannot improve.
Almost every site we inherit has analytics installed and nothing useful coming out. So we configure it properly on the way in, and the arguments about what to change next have evidence in them.
Tracking
Server-side GTM, GA4 with real conversion events, Ads and Search Console on matching definitions.
Performance
Core Web Vitals watched after launch, not just measured at it.
Access & standards
ADA Level AA and WCAG 2.2 built in from the first template.
Reporting
One short monthly note in plain words. No dashboard nobody opens.
Now you know us.
Tell us what is broken and we will tell you honestly whether it needs a rebuild or just a fix.
Start the conversation
Bring the messy version: a half-finished brief, a site that misbehaves, a number you cannot explain.
See the work first →