Non-negotiable

Standards we build to

These are not tools you choose between. They are the rules the work has to satisfy whatever it is built on.

See our accessibility work
Where sites live

Platforms

If yours is on this list, we can take it over as it stands. If it is not, tell us anyway. We have picked up stranger things.

How things get built

Frameworks

Ruby on Rails is our default for custom applications, because it is fast to build in and cheap for someone else to maintain if you ever move on.

What we read and write

Languages

Useful mostly for one question: can these people read the codebase we already have?

Where design happens

Design tools

We work in whichever of these your team already uses, and we hand over the source files at the end either way.

See our design services
Common questions

Honest answers to the questions we get most

What platforms do you support?
All of them, in the sense that we've worked across most major and a lot of niche ones. We're most experienced with WordPress, Shopify, and custom Ruby on Rails applications. If your stack is something we haven't worked in before, we'll tell you that on the consultation, and we'll be honest about whether we're the right fit.
Can you build on my existing WordPress/Wix/Squarespace/Webflow/etc website?
Almost certainly. We work across nearly all major CMS platforms. The consultation is the fastest way to confirm, bring us your platform and we'll tell you right away.
Why Ruby on Rails as the default?
We've shipped Rails applications that are still running a decade later. That history matters when you're making a long-term technology investment. Rails ships fast, scales reasonably for most of what our clients need, and stays maintainable as teams change over time. It's not the right tool for everything. When it isn't, we'll say so.
What if my platform doesn't have an integration for the tool I need?
That's exactly when we build one. If the platform has an API (even an undocumented one), we can usually work with it. If it doesn't, we look at export options, webhooks, or other data pathways. We'll tell you in the scoping conversation what's realistic.
Do you use AI coding tools on client work?

Yes, with guardrails. They speed up the parts of the work that are repetitive and well understood. A person reviews everything before it ships, and we do not point them at work with security, privacy, or compliance stakes without a close human read.

Let's talk

Running something that isn't on this list?

Tell us what you are on and what you need done. If it is outside what we do well, we will say so and usually point you at someone who specializes in it.

The consultation is free either way.

Book a free consultation