Services
Eight practices. Below is what each actually involves — the work, not the category.
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.
What it looks like
- Architecture and code reviews with a written verdict, not a rating out of ten
- Build, buy or platform decisions, with the total cost of each spelled out
- Delivery assessments when a programme is late and nobody agrees why
- Roadmaps sequenced by dependency and risk rather than by wish list
ServiceNow
Implementation, remediation, CMDB and CSDM, integrations, upgrades and retained support across ITSM, ITOM, HRSD, CSM and SecOps.
What it looks like
- Implementations across ITSM, ITOM, ITAM, HRSD, CSM, SecOps and IRM
- Remediation of instances that drifted: heavy customisation, stalled upgrades
- CMDB, CSDM, Discovery and service mapping, with a health dashboard you can run
- IntegrationHub, REST and MID Server integrations built with real error handling
- Upgrades, ATF regression coverage and a runbook you keep
- Retained platform support on a monthly block of hours
Application development
Custom internal applications, APIs and integrations, and modernisation of systems that still work but nobody wants to touch.
What it looks like
- Internal tools and line-of-business applications, built to be maintained by a small team
- APIs and integration layers between systems that were never designed to talk
- Modernisation of systems that still work but cannot be changed safely
- Data models and reporting that reconcile with the operational numbers
Mobile app development
iOS and Android, native or cross-platform, including store submission, release pipelines and the analytics to know whether anyone uses it.
What it looks like
- Native iOS and Android, or cross-platform where it genuinely fits
- Field and workforce apps that work when the signal does not
- App Store and Play submission, signing, and release pipelines
- Crash reporting and analytics, so you know whether it is being used
Website development
Marketing sites, portals and content platforms built for speed, accessibility and editors who are not developers.
What it looks like
- Marketing sites and portals with a content model editors can actually use
- Static and headless builds where speed and low running cost matter
- Accessibility to WCAG AA, tested rather than assumed
- Performance budgets set before the design, not apologised for afterwards
Cloud migration
Assessment, landing zone design and migration in waves, with cost control designed in rather than discovered on the first invoice.
What it looks like
- Current-state assessment and a migration plan grouped into waves
- Landing zone design: accounts, networking, identity and guardrails
- Lift, re-platform or rebuild, decided per workload with the reasoning recorded
- Cost visibility and tagging from day one, and infrastructure kept as code
Quality engineering
Test strategy, automation that survives refactoring, CI gates, and performance and accessibility testing before launch rather than after.
What it looks like
- Test strategy proportionate to the risk, not a document nobody reads
- Automation at the layer where it pays: unit, contract, and a thin UI suite
- CI gates that fail loudly and fast, and flake treated as a defect
- Performance, security and accessibility testing before launch
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.
What it looks like
- Assistants and workflow agents grounded in your own documents and systems
- Retrieval, tool use and human handoff designed around a real process
- Evaluation sets and guardrails, so quality is measured rather than demonstrated
- An honest account of what the system will get wrong, and what that costs
Tell us what is stuck
One email, one reply from a person who will actually do the work. No sales sequence, no discovery deck.