Technology consulting
Architecture reviews, platform selection and delivery assessments. A written recommendation you can take to a budget committee, with the trade-offs stated rather than buried.
A boutique technology consultancy
Eight practices, one small senior team
We advise, build and run software for organisations that would rather have four people who understand the whole problem than forty who each own a slice of it.
What we do
Eight practices that overlap on purpose. Most engagements draw on two or three of them, because most real problems do not respect a service catalogue.
ServiceNow
Implementation, remediation, CMDB and CSDM, integrations, upgrades and retained support across ITSM, ITOM, HRSD, CSM and SecOps.
Application development
Custom internal applications, APIs and integrations, and modernisation of systems that still work but nobody wants to touch.
Mobile app development
iOS and Android, native or cross-platform, including store submission, release pipelines and the analytics to know whether anyone uses it.
Website development
Marketing sites, portals and content platforms built for speed, accessibility and editors who are not developers.
Cloud migration
Assessment, landing zone design and migration in waves, with cost control designed in rather than discovered on the first invoice.
Quality engineering
Test strategy, automation that survives refactoring, CI gates, and performance and accessibility testing before launch rather than after.
AI agent building
Assistants and workflow agents grounded in your own data, with evaluation, guardrails and a clear account of what the system cannot do.
Why a boutique firm
The large-firm failure mode is familiar: the people who understood the design rolled off, and what is left cannot be changed safely.
We keep teams small and senior, put your people inside the build rather than beside it, and write down every decision that would otherwise live in someone's head. It costs a little velocity. It is the difference between owning a system and renting one.
- SmallThe people who scope the work are the people who do it
- SeniorNo pyramid of juniors learning on your budget
- OpenYour team in the build sessions, holding real work items
- WrittenA decision log you still understand in two years
- BoundedPhases you can stop between, not a rolling engagement
- HonestWe say no to work we would do badly
How an engagement runs
Four stages, each ending in something you own outright — a document, a working system, a trained team.
Assess
Two to three weeks with your systems and your people. You get a written findings report with priorities, effort and risk, whether or not you continue with us.
Design
Architecture and process decisions agreed before anyone builds, with the long-term cost of each shortcut stated next to it.
Build and test
Two-week iterations, a working demo at the end of each, and test evidence collected as we go rather than assembled the week before launch.
Run or hand over
Documentation, enablement sessions and a defined exit. Retained support is an option, never the assumption.
- Engagement models
- Fixed scope, retained, or embedded
- Team shape
- Small and senior, no handoff layers
- First step
- Usually a short paid assessment
- Every engagement ends with
- Documentation and enablement
Tell us what is stuck
One email, one reply from a person who will actually do the work. No sales sequence, no discovery deck.