● FAQ
The questions everyone asks before emailing.
Straight answers to the usual ones. If yours isn't here, it's a one-line email away.
How is work priced?
Fixed-scope projects get a fixed price, agreed in writing before anything starts. Ongoing support runs on a day rate or a monthly retainer. If scope changes, the price conversation happens first, not afterwards.
How long does a typical project take?
Reporting automation, integration and discovery sprints usually land in two to four weeks. Small operational software builds typically run six to ten weeks depending on scope. We scope the work so something working ships early, rather than everything arriving at the end.
What technology do you use?
Whatever fits the problem and your team's ability to maintain it: established dashboard tools, modern web stacks for internal systems, well-supported cloud services and boring integrations when boring is better. We avoid exotic dependencies that only we can run.
Who owns the code and the data?
You do. Source code, documentation, credentials and infrastructure are handed over at the end of every engagement, with no lock-in and no licence fees back to us.
What happens after handover?
Everything is documented and built so your team or any competent developer can run it. If you'd rather we stay involved, support retainers are available, although they are entirely optional.
How do you handle AI and data privacy?
Carefully and honestly. We'll tell you when AI is the wrong tool. Where it is the right tool, data handling is agreed up front: what's processed where, what's retained, and what never leaves your environment. UK GDPR requirements are built in from the start.
Do you work as a subcontractor?
Yes. A good portion of the work is white-label delivery for consultancies and agencies. Your client relationship stays yours; we provide the build capacity and stay invisible if that's what the engagement needs.
Where are you based?
The UK. Most work runs remotely with regular check-ins, with on-site days where it genuinely helps: workshops, discovery and handover sessions in particular.
Next step / Project fit
Reporting problem, data gap, internal tool, platform idea or AI workflow worth testing?
Send the rough shape of the problem. You will get a grounded view of what could be built, fixed, connected or tested first, without turning it into a bigger project than it needs to be.
Talk through the work