
Engagement packages
Short, defined starts, each led by a division and priced in a proposal.
A first engagement has to be small and specific
A first engagement has to be small enough to start quickly and specific enough to show whether the fit is right.
Each rapid engagement package is a short, defined piece of work with one division, with a result you can take into a larger decision.
Digital transformation and AI ROI blueprint
A rapid start with XSIS Advisory, typically 3–4 weeks, that ends with a roadmap you can take to the board.
System and data maturity audit
A full audit of the systems and data the transformation depends on.
Prioritised AI and digitisation cases
A prioritised set of AI and digitisation use cases for the business.
Token-economics model
A model of the token economics behind the proposed use cases.
Board-ready roadmap
An RFP and execution roadmap ready for the board.
Sovereign agentic POC (MCP, A2A, GraphRAG)
A rapid start with XSIS Intelligence, typically 4–6 weeks, that proves one agent workflow in your environment.
A working production prototype
A prototype that runs in a production-like environment.
Permission-aware GraphRAG or multi-agent workflow
Either a permission-aware GraphRAG system or a multi-agent workflow.
Connected to internal enterprise tools
The prototype connects to your internal enterprise tools.
A private VPC
It runs in a private VPC inside your environment.
Mandate e-invoicing and ERP readiness sprint
A rapid start with XSIS Enterprise, typically 3–5 weeks, that tests the mandate against your ERP.
Gap analysis
A gap analysis against the mandate and your current ERP.
A live sandbox connector
A connector tested in a live sandbox.
The mandate you need
UAE PINT-AE, Saudi ZATCA Phase 2, or EU ViDA and PEPPOL.
Your ERP
Integrated with SAP, Oracle, Dynamics or Odoo.
Cloud portability and AI token FinOps audit
A rapid start with XSIS Cloud, typically 2–4 weeks, that finds what can leave the hyperscaler and what it saves.
Hyperscaler lock-in assessment
An assessment of how far the current estate is tied to one hyperscaler.
SovereignCloud exit blueprint
An exit blueprint for the workloads that should leave.
Semantic caching and model routing
Semantic caching and model routing set up for the estate.
Lower AI and cloud bills
A target cut in AI inference and cloud bills of 35%+.
Post-quantum (CBOM) and agent security audit
A rapid start with XSIS Cyber & PQC, typically 3–4 weeks, that shows where the cryptography and agent risks are.
Cryptographic Bill of Materials
An automated inventory of the cryptography in use (CBOM).
NIST FIPS 203–205 migration plan
A migration plan for the NIST post-quantum standards.
Non-human identity findings
Red-team findings on non-human identity (NHI) risk.
Prompt-injection findings
Red-team findings on prompt injection in agent systems.
Questions and answers
How do we choose a package?
Start with the package that matches the decision in front of you: a transformation roadmap, an agent prototype, an e-invoicing mandate, a cloud cost review or a security audit. The free 30-minute online pre-consulting session is where we confirm the fit.
How long does a package take?
Each package lists its typical duration. The proposal fixes the scope and the dates for your case.
Is a package a build contract?
No. It is a defined piece of work with a result; any build is scoped and proposed separately.
Start with a conversation, not a contract.
Tell us what you need to build, connect or secure. An architect goes through it with you, then recommends where to start.
What happens next
Agreeing a time
Our team emails you to agree a time for the session.
Pre-consulting session
A free 30-minute online pre-consulting session: we go through your goals, systems and constraints.
Readiness review
In a free 48-hour readiness review, a Principal Architect checks your project against the 6-point Definition of Ready and recommends the track that fits.
Choosing the track
Scope-ready projects receive a binding proposal within 3–5 business days. Concept-stage projects start in the Blueprint Studio. A live system that is failing, undocumented or needs integration starts with a diagnostic of 1–2 weeks. The Blueprint Studio and the diagnostic each have a fixed fee, quoted in the proposal.
