How we work

How an engagement runs, from scope to handover.

The services with a published price typically take two to four weeks from kickoff. The scope, the price and the schedule are agreed on in writing before any work starts.

Scope and access

We agree on the deliverables, boundaries, price and schedule before starting. That includes checking access to the systems involved, confirming the working environment and identifying who will approve the results. If a prerequisite is missing, we address it during scoping.

Build and review

The work is done inside your environment, under the access your team approves. We use AI-assisted development and reusable engineering tools to carry it out. The development runs on our own AI accounts unless you’d rather it ran on yours, and we agree on that during scoping. Our team makes the architecture decisions, reviews the implementation, tests the result and manages the handover.

We build and test the reusable tools in advance and call them kits. A kit holds the repeatable parts of a service, such as the steps for building an answer key, the evaluation runner and the readout format. Starting from a kit leaves more of the engagement for the parts that are specific to your data and systems.

Testing and handover

Before handover we run the checks agreed on at the start and write up the results in a readout. What gets measured depends on the service.

  • Governed-data agent pilot: how often the agent is right against the answer key, and the model cost of each answer
  • MCP tool layer: whether each task completes, and how many tool calls and how much data it takes
  • Agent eval and production readiness: pass and fail results for each model tested, and the gaps to close before a production decision
  • Demo and POC kits: whether the kit sets up, runs and tears down cleanly each time
  • Custom data and AI projects: the checks listed in the proposal for that project

You receive the work built for you, the readout, any wrong answers or failures we found, and the documentation your team needs to run it.

Ownership and what comes after

You own the work built specifically for your engagement. The Iron Condor components that existed before the engagement remain ours, and the engagement agreement sets out your rights to use them.

Work after handover is optional and scoped separately, for example maintaining a demo kit as the underlying products change or taking a pilot to production.

Tell us what you’re working on.

Discuss a project