Frequently asked questions

Both, scoped deliberately. Assessments and reviews are advisory with written deliverables. Pilot squads include hands-on build in your tenant (or a reference environment you own) plus handoff runbooks. We do not operate your production systems 24/7, that stays with your team or your MSP.

Ned Jamieson leads engagements as principal. Larger programs may bring specialist subcontractors (security, data engineering) named in the statement of work. You always know who is in workshops and code reviews.

Live demos call real model APIs so engineers can see latency and behaviour. Case studies, diagrams, guides, and architecture notes work without keys. In engagements we use your enterprise keys and tenancy.

Patterns and reference code are starting points, not warranted production software. Engagements produce configs and code tailored to your IAM, data boundaries, and review gates. Licence the repo for internal learning; do not treat it as a supported product.

You pay providers directly (OpenAI, Microsoft, AWS, Anthropic). We help you estimate pilot spend and set routing/caps, we do not markup tokens.

Use Start here to pick a path by org size or role, then contact via The Ops Toolbox for an intro call. Short assessments are quoted fixed-scope after we understand goals and constraints.

Yes, remote-first workshops and reviews across APAC, EMEA, and Americas time zones. On-site is optional for executive sessions.

AI Labs is a practice within The Ops Toolbox (scale-up diagnostics and playbooks). This site is the technical portfolio; the main site covers broader operating system work for founders and COOs.