How We Work

Most of what gets built for the web now comes from templates, and most of the time that's fine. But there's a point where the template stops fitting, and the question becomes whether to keep working around its limitations or to build something that doesn't have them.

The code is written for each project. There's no theme underneath, no page builder generating markup, no framework we're customizing. Whether that's the right choice for a given project depends on what the project needs to do and how long it needs to last, but when it is the right choice, the difference shows up in ways that are hard to get otherwise.

Even for simpler sites, starting from scratch means no bloat, faster loads, and complete ownership. The result is a site that feels premium and lasts longer than template-based alternatives—without the limitations if your needs grow.

Design is part of the build, not a coat of paint applied at the end. What a site looks like and how it works are the same problem approached from different angles, and the best results come from treating them that way from the start. The visual design serves what the site is trying to do, and what the site is trying to do informs how it should look.

Page load time is one of those things that affects everything else, from search rankings to conversion rates to how people feel about using a site, and it's largely determined by decisions made during development. A site built on a page builder will carry that weight forever. A site built from scratch only loads what it actually uses.

The technical side of search engine optimization is mostly about not getting in the way: clean markup, fast loads, structure that makes sense to a crawler. These are natural byproducts of building a site well. Wordpress gurus will try to sell you their "SEO plugin" which just adds keywords to the page without actually making the site any better.

Websites are one thing. Applications are another, and the line between them keeps moving. A booking system, a customer portal, an internal tool for managing operations: these are all technically websites, but developing them requires thinking about data and workflow and user permissions in ways that a brochure site doesn't.

Off-the-shelf platforms exist for some of this, and sometimes they're the right answer; but more often than not, they are a well-marketed template which leads you to paying thousands of dollars a year for a service that doesn't work for your business.

Ownership matters in ways that aren't obvious until something goes wrong with a platform you depend on. The code we write is yours, hosted where you choose, not tied to a properietary system's procted code, subscription, or an external company's continued existence. If you want to take it to another developer someday, you can.