The decisions
people get stuck on.
Balanced comparisons of the choices that stall a project — written to help you decide, including the cases where the answer is not to hire us.
Honest side-by-side comparisons of the technology and commercial decisions buyers get stuck on — platforms, frameworks, hiring models and contract shapes. Each one states its verdict before the detail, and several conclude against us.
Updated August 2026
Shopify or WooCommerce?
Both build good stores. The decision usually comes down to who maintains it and which payment gateways you need.
React Native or Flutter?
Both build one app for both stores. The right answer usually depends on what your team already knows.
Hire in-house, or outsource?
The honest comparison, including the cases where hiring is clearly the better answer.
Fixed price, or pay by the day?
Which contract shape actually protects you depends entirely on how settled the scope is.
Build it, or buy it?
Most businesses should buy. This is how to work out whether you are one of them.
SEO or paid ads?
One buys visitors today and stops when you stop. The other takes months and keeps working.
Magento or Shopify?
Adobe Commerce is powerful and expensive to keep alive. Shopify is neither. The right answer depends less on features than on who maintains it on a Tuesday.
RAG or fine-tuning?
Almost every project that asks for fine-tuning needs retrieval. The distinction is knowledge versus behaviour, and confusing them is expensive.
Next.js or WordPress?
One is a publishing system anyone on your team can drive. The other is a framework that needs a developer. Most sites are better off with the first.
Shopify or Shopify Plus?
Plus is a large step up in cost for a specific set of capabilities. Most stores that ask about it do not need it yet.
Chatbot or AI agent?
One answers questions. The other does things — and doing things is where the risk, the integration work and most of the cost live.
— deciding
Including when the answer is not us.
Tell us the constraint.
Budget, timeline, or who maintains it afterwards — whichever is hardest to change. We will tell you which option fits, including when it is not us.
How to use these.
They would be worthless if they were. Each one names the cases where the option we do not sell is the better choice — and if the honest answer for your situation is a template, a freelancer or an in-house hire, that is what the page says.
Start from the constraint that is hardest to change: budget, timeline, or who maintains it afterwards. Most of these decisions look like technology questions and are actually staffing questions, so the page that matches your constraint is the one to read first.
Most of these are recoverable and the pages say how, including what a migration actually costs in time. The expensive mistake is usually not the original decision — it is spending another year defending it.