Every website project starts with the same question: what platform should we build on?
Most agencies answer that question with whatever they know — and often, what they know is a drag-and-drop builder. Webflow, Squarespace, WordPress with Elementor. These tools are genuinely good at getting something on the screen quickly. But they come with a hidden cost that most clients don't discover until it's too late: you don't actually own your website.
The subscription trap
Page builders are subscription businesses. The moment you stop paying, your site goes dark (Webflow) or falls behind on security updates and breaks (WordPress plugins). You're renting infrastructure indefinitely, and the price only ever goes up.
More importantly, these platforms make a lot of decisions for you — about performance, about architecture, about what you can and can't customize. You're building inside their box.
What we do instead
We build every site on Next.js deployed to AWS. This means:
- You own the code. It lives in your GitHub repo. We hand over full access on day one.
- You own the infrastructure. AWS resources are in your account. If we got hit by a bus tomorrow, you could hire any Next.js developer to pick up where we left off.
- No ongoing platform fees. AWS costs at our scale are typically under $10/month. There's no per-seat fee, no "advanced features" tier, no annual renewal.
Performance isn't optional
Next.js with the App Router generates static HTML at build time for pages that don't need dynamic data. That means your homepage loads in milliseconds from a CDN edge node — not from a server that has to render the page on every visit.
For a small business website, LCP (Largest Contentful Paint) under 1.5 seconds is very achievable. Page builders routinely struggle to hit 2.5 seconds even on fast connections.
Google has been explicit: Core Web Vitals are a ranking factor. A fast site that loads well on mobile is no longer optional — it's table stakes.
The tradeoff
We won't pretend there's no tradeoff. Page builders let a non-developer update content in a visual editor. Our sites require either: (a) a developer to update code, or (b) a CMS integration.
For clients who need frequent content updates, we wire in Sanity or a lightweight MDX-based blog (like this one). For clients who mostly want a static presence that looks great and loads fast, code-in-Git is often the right answer — especially when the alternative is paying $50/month forever to a platform that controls your site.
What you should ask any web agency
Before signing, ask: "Who owns the hosting account? What happens to my site if I stop paying you?"
If the answer is anything other than "you own everything and can take it anywhere," you're renting, not buying.
We build websites you own. That's the whole pitch.