Everything clients ask, answered here.
Sixteen questions across working with us, commercial terms, technical detail and practicalities. If yours is not here, email it and we will answer directly and probably add it.
Questions about working with us.
Answered as we would answer them on a call.
With a conversation, then almost always a discovery sprint. Two to three weeks, fixed fee, ending in a written recommendation and a cost model. You can take that document to another supplier if you want to.
Usually two to four weeks from agreement. Discovery sprints can often start sooner because they need less mobilisation.
Yes, though we are a UK company under UK law and most of our clients are here. Time zones within about four hours of London work well for our delivery cadence.
From single-site colleges to organisations with several hundred staff. We are a small team by choice, which means we take a small number of projects seriously rather than a large number badly.
Questions about commercial.
Answered as we would answer them on a call.
Discovery sprints are a fixed fee. Builds are milestone-based against an agreed scope. Embedded engineers are monthly. Support is a monthly retainer. Indicative starting figures are on the pricing page.
You do, unless we agree otherwise in writing. All deliverables produced for a client vest in the client on payment. Where a project builds on our existing platform components, those stay ours and you get a licence, set out plainly before work starts.
It usually does. Milestones are re-agreed in writing before the work happens, never invoiced as a surprise. If a change makes the original plan wrong, we say so.
No. Support agreements run monthly with thirty days' notice. Handover documentation is written so another supplier could pick the system up, which is the only honest test of whether you are locked in.
Questions about technical.
Answered as we would answer them on a call.
Wherever you need it to. Azure or AWS in a UK region by default, or your own infrastructure. We do not move client data outside the agreed region and we do not train shared models on your data.
No. Client data trains client models. If a project would benefit from a shared base model, that base is a public or licensed one, never another client's data.
Monitoring and scheduled re-evaluation against a held-out set, with alerting when performance moves beyond an agreed threshold. Retraining is part of a support agreement rather than an emergency.
Usually. We have integrated with Microsoft Graph, Moodle, Oracle, Firebase and a long list of internal systems with no documentation. Where an integration is genuinely impossible, we find that out in discovery, not in month four.
WCAG 2.2 AA is our default target, with keyboard paths, focus states, reduced-motion support and screen-reader labelling built in rather than retrofitted.
Questions about practical.
Answered as we would answer them on a call.
Named engineers, agreed before we start. We do not bid with senior people and deliver with juniors.
Fortnightly demos of working software as standard, plus a direct channel for anything urgent. No monthly status document that nobody reads.
Tell us early. Milestone-based delivery exists so a project can be stopped at a reviewable point without either side losing everything. That has happened, and it was better than the alternative.
Still have a question?
Send it over. You will get an answer from someone who would work on your project, not a link back to this page.