The offer
Your developers keep owning the product. We put in place the engineering around agents so output is reviewable and repeatable: instructions, gates, conventions, and a flow where a person still signs off.
What you get:
- A workshop day on your codebase and your tickets — not a demo repo. The team merges agent-written changes and sees where the agent fails.
- Tooling in your repositories: agent instructions, lint and test gates, review conventions, model access within your policies — the same pieces we run on our own systems.
- The first pull requests together. A Cirit engineer works alongside your team until the flow is yours.
- A short written readout: what worked in your codebase, what failed, and what to change so it fails less.
What this is not
Not a tool licence. Not a generic AI training day. Not us taking over delivery — that is senior engineers in your team, or custom software, when you want capacity or ownership on our side.
Constraints we already expect
- Stack and policy drive the tools. We are not tied to a vendor.
- If code cannot leave the EU or your premises, the model runs where policy allows; the surrounding setup does not change.
- Engagement length fits your cadence: workshop, a few weeks of paired pull requests, then a lighter follow-up — or a senior engineer embedded for a release if that is the better next step.
Commercial
Scoped engagement: workshop plus setup and paired weeks. Fixed price or capped hours, agreed up front.