Solutions

A solution is a piece of work with a known shape. Unlike a capability, which describes an area we work in, each of these can state what is included, how long it takes and how it is delivered, because we have done that specific job before.

How these differ from capabilities

If you are still deciding what to build, start with the capabilities pages: they cover the whole area and help you work out what the project actually is. If you already know, for example, that you need a Shopify storefront built or a Drupal site migrated off an unsupported version, these pages are more specific and will answer more of your questions.

Reading these pages

Every one carries a section called “the wrong choice when”. That is not modesty. The most expensive mistakes in software are made at the point of choosing an approach, not while building it, and a page that only lists reasons to say yes is not helping you decide. If a solution page tells you your situation is a poor fit for it, believe it and read the one it points you to instead.

None of these pages carries a price. No rate card is agreed, and a number published here is one that every later quote has to defend regardless of what your project turns out to involve. Scope drives cost, so scope is what we discuss first.

If nothing here matches

These are the engagements that come up often enough to be worth describing. Plenty of good work does not fit a named shape. Tell us what you are trying to do and we will tell you what it would take.