Services

Working software in production in 3–8 weeks. You own everything.

A fixed price, set before you commit; we carry the delivery risk. Each discipline is led by a senior expert, with orchestrated agents carrying the throughput: Applied AI, Bespoke Apps, ServiceNow, and Microsoft today; Salesforce, SAP, and Testing expanding. Every engagement runs on a published governance spine.

How long
3–8 weeks from scope to production
The price
Fixed before you commit. It does not move.
The risk
Ours. If a deliverable fails its acceptance criteria, we fix it at our cost.
Ownership
IP transfers on payment: code, tests, runbooks, full history

Find where AI fits

The advisory line: where AI pays first, and the governance to run it. Consulting

Build it

This page: custom agents, bespoke applications, integrations, and the platform work that carries them.

Run it for you

The end-state we build toward: your function operated as an AI service. Run grows out of Build; there is no cold door.

The craft — disciplines

Our disciplines. The craft behind the work.

Disciplines are the skills our pods bring to the work. The discipline and the engagement shape are named in the proposal, alongside pod composition and price. The shape fits the scope.

2–8 weeks

Production builds on the Anthropic and OpenAI stacks: custom agents, Claude Code skills, Custom GPTs and ChatGPT Apps, Realtime voice, retrieval pipelines. Substrate matched to the engagement.

Capabilities · Anthropic stack · OpenAI stack · Agents · Retrieval · Testing

AgentsClaude CodeCustom GPTsRealtime
BeginStart assessment
3–8 weeks

TypeScript-first delivery for web apps, integrations, automations, and migrations, built on a modern stack your team can operate.

Capabilities · Web · Mobile · Integration · Automation · Migration · Testing

WebMobileIntegrationAutomation
BeginStart assessment
4–10 weeks

ITSM, HRSD, Service Portal, Virtual Agent, and Flow Designer / Integration Hub work. Scoped apps, Solution Architecture, and Platform Uplift on production instances.

Capabilities · ITSM · HRSD · Service Portal · Virtual Agent · Flow Designer + Integration Hub · Scoped Apps · Solution Architecture · System Admin + Platform Uplift · Performance Analytics · Testing

ITSMHRSDService PortalVirtual Agent
BeginStart assessment
4–10 weeks

Power Platform, Azure, M365 and Teams customisation, Dataverse, and Copilot Studio. Significant government and enterprise estate.

Capabilities · Azure · M365 · Power Platform · Dataverse · Copilot Studio · Testing

Power PlatformAzureDataverseCopilot Studio
BeginStart assessment
4–10 weeks

Sales Cloud, Service Cloud, and Experience Cloud extension work: flows, Apex, LWC, integration. Ramping in line with confirmed client demand.

Sales CloudService CloudApex / LWCMuleSoft
BeginStart assessment
06

SAP

4–10 weeks

Integration, extension, and data work around an SAP core: clean-core extensions on BTP, CPI integration flows, and Fiori surfaces. Scoped as confirmed senior-expert depth lands.

BTPCPIFioriIntegration
BeginStart assessment
2–6 weeks

Standalone test engagements: automated regression suites, test infrastructure standup, coverage audits, post-incident hardening. Runs as its own pod when the work is test-shaped, and as a Capability inside every other discipline by default.

Capabilities · Regression suites · Test infrastructure · Coverage audits · Post-incident hardening

Regression suitesTest infrastructureCoverage auditsPost-incident hardening
BeginStart assessment

Shared across disciplines

What stays the same. Regardless of which discipline you buy.

The commercial and delivery structure does not vary by discipline. The pod composition, the four phases, the daily artefact, and the pricing model are constant.

Pod composition

Every engagement runs through a pod: 1–3 senior discipline experts plus orchestrated agent capacity, sized to the scope. The composition is declared in the proposal. You see exactly who is working and how agent capacity is structured.

Same four phases

Scope the outcome → Assemble the pod → Ship evidence daily → Hand off cleanly. The daily artefact — committed code, passing tests, staging environment, written decisions — runs from the first business day of the build.

Testing is embedded

A Test Expert — a senior QA practitioner embedded in the pod — participates in every outcome pod, regardless of discipline. Automated test suites are part of every handoff package.

Same price structure

Outcome pods are fixed-price. Capacity pods are priced per pod-day, all-in. The pod-day rate reflects the declared composition; discipline does not add a premium tier.

The practices

Technology first. More practices as we staff them.

We work in Technology today. We move into a new area (Legal, Finance, HR) only when senior experts can staff the disciplines it needs, so the work is real before we sell it.

  • TechnologyliveOur wheelhouse. Consult and Build delivered today, drawing on our staffed disciplines: Applied AI, Bespoke Apps, ServiceNow, and Microsoft; Salesforce, SAP, and Testing are expanding. Run is the end-state we build toward.
  • LegalnextConsult now: where AI fits in a legal function, and the governance to adopt it safely. Build with a domain partner; Run follows as the practice staffs up.
  • Finance · HR · Sales · OpshorizonOn the horizon. The same operating model extends to these functions as senior experts are staffed against the disciplines each needs.

Begin

Take the assessment. The discipline — and any named capability — show up in the proposal.

Self-driven, free, no sales call. A proposal, outcome pod or capacity pod, within 24 hours.