Technologies we build with - and when we'd steer you elsewhere.

In discovery, before anything is designed, and we put the recommendation in writing. We start from what you're building, who has to live with it after launch, and the one or two requirements that are genuinely hard - search visibility, offline, real-time, compliance, deep native hardware. That usually eliminates most of the shortlist on its own. Then we recommend a stack, explain what it costs you as well as what it buys you, and you approve it before a line of code is written.

Read the guides. Every in-depth technology guide on this site has a section that names when that technology is the wrong choice and sends you to a different one. Our React guide routes search-critical work away to Next.js. Our Shopify guide sends content-led stores to WooCommerce, and our WooCommerce guide sends product-first stores back to Shopify. Our Flutter guide tells you not to build a search-critical website in Flutter at all. An agency with one house stack cannot afford to write any of that, which is the point.

No. We don't rent out developer seats, and we don't sell dedicated-team retainers. We take on scoped projects at a fixed price agreed before the build, delivered by the senior people who actually do the work, with the code and the IP transferring to you. If what you need is bodies to add to your own team, we're honestly not the right firm, and we'll tell you that on the first call rather than take the engagement.

Often, and the first step is always an audit rather than a quote. We look at what the application actually does, the state of the dependencies, whether it can still be upgraded, and how much of the original intent survives in the code. Sometimes the honest answer is that a rescue is cheaper than a rewrite, and sometimes it is the opposite, and we would rather tell you which before you commit. We work in mainstream, open technologies precisely so that inheriting someone else's work is possible.

Tell us anyway. This page lists the technologies we work with regularly, not the limit of what we'll look at. If your stack is close to something here - another PHP framework, another headless CMS, another JavaScript runtime - the principles usually carry across and we'll say honestly how much of it is familiar ground. And if it genuinely isn't something we should be touching, we'll tell you that instead of learning it on your budget.

Almost never. The scope sets the price - how many pages or screens, how much custom logic, how many integrations, how much design. A brochure site costs about the same whether it lands on WordPress or a custom build, because the work is the same size. Our starting prices are published on the pricing page and on each service page, and you get a fixed quote before any build begins, whatever stack we land on.