Enterprise engagement

Structured to survive procurement, security review, and a steering group.

Larger organizations do not buy AI and software from a capabilities list. They buy when the commercial structure, the governance, and the risk position all hold up under scrutiny. This is how we contract and deliver.

Request an Executive Briefing Read Our Security Position

How engagements are structured

Three phases, each one a decision point.

You are never asked to commit to the whole programme to find out whether the first part works.

012–4 weeks · fixed fee

Discovery & Feasibility

A paid, fixed-scope first phase that establishes whether the work should happen at all.

Current-state map of the process, systems, and data involved
Target architecture with the integration points named
Risk register covering data, dependencies, and failure modes
Delivery plan, sequencing, and a cost model for the build
A written recommendation, including the recommendation not to proceed

Ends with a decision document you can take to a steering group. No obligation to continue.

026–16 weeks · milestone billing

Fixed-Scope Build

Implementation against agreed acceptance criteria, with change control rather than scope drift.

Production system built in your cloud accounts, under your credentials
Acceptance criteria agreed before the build starts, tested at each milestone
Technical documentation, runbooks, and architecture decision records
Named delivery lead, weekly delivery cadence, fortnightly steering
Handover and enablement for the team who will run it

Fees are fixed per milestone. Changes are quoted and approved before work begins.

03Rolling · quarterly review

Managed Operations

For systems that need to keep working after launch: monitoring, iteration, and accountability.

Monitoring, alerting, and response against an agreed support tier
Model, vendor, and dependency updates with regression testing
A prioritised improvement backlog reviewed with you each quarter
Usage, cost, and performance reporting from your own analytics
Documented exit plan maintained throughout the engagement

Terminable on notice. Everything needed to run the system without us stays current.

Commercial structure

Fixed scope, fixed fee, and nothing you cannot leave.

Fixed fees per phase

Each phase is quoted as a fixed fee against a defined scope. You approve the scope and the fee before the phase starts. We do not bill discovery findings as change requests.

Milestone billing

Invoicing is tied to delivered milestones, not elapsed time. If a milestone slips for reasons inside our control, the invoice moves with it.

You own the output

All deliverables, source code, prompts, evaluation sets, and documentation transfer to you. We retain no licence over work produced for your business.

You own the infrastructure

Systems are built in your cloud accounts, under your API keys and your vendor contracts. There is no Elevariq platform to be locked into and no hosting margin in the fee.

Change control

Scope changes are estimated in writing and approved before work starts. The alternative is a project that quietly doubles, which serves nobody.

A documented exit

Every engagement maintains a current handover pack: architecture, credentials inventory, runbooks, and known issues. Leaving should be an administrative task, not a project.

Delivery governance

How the work is run once it starts.

Most failed programmes are not failures of engineering. They are failures of decision-making, ownership, and reporting.

Named accountability

One senior lead is accountable for the engagement and attends your steering meetings. You are not handed to a rotating pool.

Delivery cadence

Weekly working sessions with the delivery team, fortnightly steering with decision-makers, and a written status covering progress, risks, and decisions required.

RAID discipline

Risks, assumptions, issues, and dependencies are tracked in a shared log with owners and dates. Nothing material lives only in a conversation.

Defined acceptance

Acceptance criteria are written before the build and tested at each milestone, so sign-off is a check against a list rather than a matter of opinion.

Escalation path

A named escalation contact and a target response time for anything raised as blocking, agreed at kickoff.

Post-engagement review

A written review at close covering what was delivered, what changed, what we would do differently, and what to watch.

Support tiers

What happens after go-live is contracted, not assumed.

Support tiers, coverage, response targets, and review cadence
Tier	Coverage	Response target	Review	Typically for
Standard	Business hours, Mon–Sat	Next business day	Quarterly	Included with Managed Operations
Business	Extended hours	Within 4 business hours	Monthly	For systems in daily commercial use
Critical	Extended hours, on-call escalation	Within 1 hour, business-critical	Monthly + incident reviews	For systems where downtime stops revenue

Response targets are the time to a human response and a plan, not to full resolution. Resolution targets are agreed per system, because a reporting delay and a stalled payment flow are not the same problem.

Procurement

The paperwork your process requires.

Vendor onboarding should not be the reason a project starts a quarter late.

Contracting

We can work under your MSA and SOW templates, or provide ours. Legal review is expected, not resisted.

Data protection

A DPA is available before any data is shared, alongside a current subprocessor list.

Security review

We complete security questionnaires and vendor assessments as part of onboarding, and can provide a written security overview in advance.

Insurance

Certificates of professional indemnity and public liability cover are available on request.

References

Client references are provided at shortlist stage, with the client's permission.

Onboarding

Supplier registration, purchase-order workflows, and consolidated invoicing are all accommodated.

Read our security and data governance position

Who owns the intellectual property?

You do. Source code, prompts, evaluation sets, configuration, and documentation transfer to you on payment. We keep no licence over work produced for your business, and we do not reuse your material with other clients.

Can you build inside our environment?

Yes, and it is our default. Systems are deployed in your cloud accounts under your credentials and your vendor agreements. Where your organization requires work to happen inside a certified or air-gapped environment, we work within it under your controls.

How do you price work?

Fixed fee per phase against a defined scope. Discovery is quoted before it starts, and the build is quoted at the end of discovery when the scope is actually knowable. We will decline to quote a build we have not scoped, because that number would be fiction.

Will you sign our MSA, NDA, and DPA?

Yes. We work under client paper regularly and expect legal review as part of a serious engagement. If a clause is genuinely unworkable for a firm of our size, we will say so and propose an alternative rather than sign and hope.

What happens if we want to bring this in-house?

That is a normal outcome and the engagement is structured for it. Documentation, runbooks, and the handover pack are maintained throughout, and we will train your team as part of closing the engagement.

Do you subcontract delivery?

The delivery team is named at kickoff. Where a specialist is brought in, you are told who, for what, and under what confidentiality terms before they touch anything.

Next step

Bring us your constraints, not just your requirements.

An executive briefing is a working session, not a pitch. Come with the process that is failing, the systems it touches, and the limits you are working inside. You will leave with a view on whether it is worth building and roughly what it takes.

Request an Executive Briefing Send a Written Brief

Typically 60 minutes, with the people who would run the system in the room.

AI Systems

Intelligent Automation

Web & Digital Products

Marketing & Growth

Not sure where to begin?