One managed service. Three ways to put AI to work.
We build it. We connect it. We manage it. Choose a starting pathway, then confirm scope, capacity and allowances with us before onboarding.
Managed AI Assistant
Your own AI assistant.
A dedicated assistant for the independent professional or business owner who wants everyday work organised, researched and prepared.
Daily briefings and task preparation.
Research, drafts and document workflows.
Connections to selected everyday tools, after feasibility checks.
One primary user and a small, agreed set of starter workflows. Integration counts and execution allowances are confirmed before onboarding. An isolated managed runtime is the proposed starting model. A dedicated VM is not automatically included as standard.
Specialised agents working across your operations, commercial processes and delivery tools, with agreed permissions and oversight.
Project coordination and status reporting.
CRM and commercial research workflows.
Document processing and controlled task execution.
Multiple agent roles within one customer environment. Integration, concurrency, user and AI allowances are defined in the agreed scope. A dedicated VM is the default proposed architecture, subject to technical validation. Agent roles are logical identities, not a VM per agent.
A tailored, managed execution environment integrated with your technology estate, security requirements and governance processes.
Private-cloud deployment and network controls assessed against requirements.
Custom integrations and agent orchestration.
Auditability, approvals and service governance designed into the scope.
Discovery and a bespoke statement of work are required. Implementation is scoped to your requirements. Bespoke infrastructure and access design follow discovery. No automatic claim of UK-only processing, certification or a particular SLA.
Tell us your requirements. We confirm scope, service allowances and a tailored proposal before onboarding. No purchase or immediate deployment is created by an enquiry.
From a conversation to a working AI team.
01
Tell us what you need.
Choose outcomes, tools and how much authority your agents should have.
02
We configure your environment.
Confirm scope, connect approved systems and test workflows.
03
Your agents get to work.
Start with supervised execution and clear approval points.
04
We keep it running.
Monitor, maintain and improve within the agreed service plan.
Powerful enough to act. Controlled enough to trust.
You choose the tools and data to connect; we confirm feasibility and permitted access.
Explicit permissions restrict actions. Sensitive or high-impact work needs approval unless specifically authorised under a bounded policy.
Activity and usage must be recorded and reviewable within the agreed plan.
Access must be revocable and workflows stoppable. These controls are validated before enabling execution.
Customer configuration, secrets and data must be separated between environments; architecture and isolation are checked during onboarding.
Questions before you choose
What am I actually buying?
A human-configured managed agent engagement: agreed workflows, approved connections and ongoing operation within a written plan. It is not a licence to a generally available self-service control plane.
Is this different from a chatbot or automation tool?
The engagement adds workflow specification, configuration, integration and management around agreed work. Tools and models are chosen for the task; their separate licences and limitations are reviewed during scoping.
Will I have my own server?
Personal starts with an isolated managed-runtime design, not an automatic dedicated VM. Business defaults to a dedicated VM subject to validation. Enterprise infrastructure is designed after discovery. The final architecture is confirmed before onboarding.
What does setup include?
The agreed discovery, configuration, connection checks and workflow testing needed for your initial scope. Setup effort, revisions and deliverables are specified in writing; additional engineering is separately measured.
Which systems can you connect?
Tell us your project, CRM, document, email, support or development tools. We assess available APIs, authentication and permitted actions. Listed use cases are examples, not a verified out-of-the-box integration catalogue.
What happens when the AI makes a mistake?
We agree review points, stop conditions and recovery actions for each workflow. Start under supervision and investigate recorded failures before increasing authority. Outputs and actions still require checks appropriate to their consequences.
Can agents act without approval?
Only specifically authorised actions inside agreed bounds should run without a new approval. Sensitive or high-impact actions require review unless explicitly authorised under a bounded policy. Unrestricted autonomy is not a package entitlement.
Are AI model costs included?
Each final proposal defines its AI allowance, usage measurement, spending limits and overage mechanism. Unlimited tokens or unlimited execution are not included. These numerical allowances are not yet published as firm entitlements.
Can I upgrade or cancel?
Changes, contract term, cancellation notice, export/deletion and offboarding are agreed before onboarding. No self-service cancellation terms or refund promises are assumed from these indicative prices.
Who owns my data and workflow configurations?
Data access, configuration ownership, portability, subprocessors and model-provider policies are recorded in the agreement. Secrets and customer configurations must be separated from reusable runtime code; no rights are inferred from submitting this form.
Our system already supports rapid development and governed execution. We’re building the enterprise control plane around these seven tenets: how agents run, what they can use, what they know and how people stay in control. Human-led specification and design set the direction; the operating model makes AI work reviewable.
01
Runtime
Execute agents in isolated environments.
02
Tools
Connect to external applications through APIs and MCP.
03
Context
Supply relevant information and persistent state.
04
Orchestration
Manage objectives, reasoning loops and multi-step execution.
05
Governance
Enforce permissions, approvals and operational limits.
06
Observability
Record actions, outcomes, costs and failures.
07
Lifecycle
Deploy, pause, update, restart and terminate agents.
Your tools. Your context. Clear ownership across the whole agent lifecycle.