Fixed-scope project
A total price against a written specification, invoiced at agreed milestones. Suits well-defined builds and one-off assignments.
Home/Services
Four registered activities, described in plain terms: what we actually do, what you receive at the end, and when each one is the right thing to buy.
Independent technical judgement, delivered in a form a non-technical board can act on.
We are often called in at a decision point: an ageing system that costs too much to keep, a cloud bill nobody can explain, a supplier proposal that needs a second opinion, or a product idea that needs a technical route to market. We assess the situation, set out the realistic options with their costs and risks, and give a recommendation we are willing to defend.
Consultancy engagements are deliberately short. Two to six weeks is normal, and the output is a document plus a session where we walk your team through it.
Software written for one organisation's actual problem, rather than configured around someone else's.
We build business systems — portals, back-office tools, booking and workflow platforms, APIs, data pipelines, reporting — and consumer-facing applications where the audience is the general public rather than a workforce. The stack is chosen for maintainability: we would rather hand you a system your next developer can read than one that shows off.
Every build includes automated tests, code review, deployment automation and written documentation. These are not optional extras and they are not line items you can cut; they are what makes the software cheap to own after we leave.
Launch day is the beginning of a system's life, not the end of it.
Under a support agreement we host, monitor and maintain the software we built — or, after a review, software someone else built. That means patching dependencies, watching error rates and performance, testing that the backups actually restore, and responding when something breaks within an agreed response time.
Support is always optional. If your own team is better placed to run the system, we will help them take it over and say so.
Research exists to change a decision. If a study cannot change what you do next, we will tell you not to commission it.
We design and run qualitative and quantitative research: interviews with customers and staff, survey design and fieldwork, market sizing, segmentation and competitor analysis. Fieldwork is documented so the method can be inspected, and findings are reported with the evidence attached — including the findings that are inconvenient.
Research participants are recruited and handled in line with UK data protection law, with informed consent and a stated retention period for every study.
Everything below is confirmed in a written agreement before work begins.
A total price against a written specification, invoiced at agreed milestones. Suits well-defined builds and one-off assignments.
An agreed number of days per month, re-prioritised every fortnight. Suits evolving products and ongoing improvement work.
A monthly fee covering hosting, monitoring, maintenance and an agreed response time. Runs alongside either model above.
| Service line | Typical duration | Primary deliverable |
|---|---|---|
| IT consultancy | 2–6 weeks | Written report, options and recommendation |
| Software development | 6 weeks – 12 months | Working system, source code, documentation |
| Managed technology | Rolling monthly | Running service and incident response |
| Market research | 2–8 weeks | Findings report and recommendations |
That is a normal position to be in, and it is usually a short conversation. Describe the problem and we will tell you which service fits — or that none of them does.