Consultancy & technical advisory

The cheapest part of any project and the one that decides whether the rest of the money is well spent. Often it is all a client needs.

Typical work

Audit what you already have. A written review of your site, database or system — performance, security, mobile behaviour, accessibility, content gaps — and whether repairing costs less than replacing.
Write the specification. Screens, data model, integrations and phases, in a document you own and can send to any developer, including ones who are not us.
Compare the quotes you have received. Three proposals that do not describe the same thing, translated into a like-for-like comparison.
Build or buy. An honest assessment of whether off-the-shelf software solves it for a monthly fee, and what you would have to change about how you work.
Technology choices. Which database, which hosting, which stack — decided against your budget, your team's skills and who maintains it in three years.
Handover review. Making an inherited system understandable to the people who now own it.

What makes the advice yours

The recommendation is shaped by your budget, your team’s skills and who maintains this in three years — not by what we would like to build. Sometimes the answer is that you need no project at all, and you get that answer in writing too.

What you get

You get

A written report or specification, a phased plan with indicative costs, and a call to walk through it.

Sold as

A fixed-fee engagement of one to two weeks, or by the day for shorter questions.

Good fit when

You are about to spend real money and are not certain what you are buying — or you have inherited a system nobody can explain.

Worth knowing

The fee is credited against the build if you go on to build with us. You keep the document either way.

Not sure this is the right one?

Describe the problem instead of the solution. A short call is usually enough to tell whether it is this, something else, or nothing you should spend money on.

Book a free call