Frequently asked questions
Can't find what you need? Ask us directly.
How does an engagement work?
It starts with an intro call to understand your challenges and opportunities, and whether we are the right fit. We then agree a statement of work with scope, deliverables, acceptance criteria, and dates. Delivery runs with a weekly review with your sponsor, and all work lives in your repositories and cloud accounts from the first day. Documentation, runbooks, and training are handed over as we go, so your team can run and extend what we built.
How long does a typical engagement take?
It depends on the scope. We agree the timeline with you during contracting, before any work starts, so you always know the finish line.
Who owns the intellectual property and source code?
You do. All code, prompts, model configurations, evaluation data, and documentation belong to you and live in your own repositories from the first commit. The accelerators we bring are licensed to you permanently, at no extra cost.
How much time will my team need to commit?
It depends on the scope and the level of support you are looking for. We agree what we need from your team, such as a sponsor and subject experts, during contracting, so everyone can plan for it before work starts.
Do you work with our existing technology and vendors?
Yes. We are model- and cloud-agnostic and design around the systems you already use, whether that is AWS, Azure, Google Cloud, Salesforce, Microsoft 365, or your own internal tools. We only recommend new tools when they clearly pay for themselves.
What happens after the engagement ends?
You get a full handover: runbooks, architecture documents, and training sessions, so your team can run what we built on its own. If you want us to stay involved, our Operate engagement measures the value delivered, maintains and enhances what we built, keeps the roadmap current, and supports governance, with no minimum term.