Three stages, and you can stop after any of them.
Every stage produces something you keep and can act on without us. That is deliberate: a consultancy whose first deliverable is a dependency on the consultancy has misunderstood the job.
- Assessment: two weeks
- We read your repositories, your tracker and your CI, and interview the engineers who actually ship. You receive a written assessment: where work enters, where it stalls, which of the six components exist, and the measured baseline for cycle time, rework, review latency and escaped defects.Fixed scope, fixed fee. Yours to act on with or without us.
- Pilot line: six to eight weeks
- One team, one repository, end to end. We install the control plane, write the contracts with your engineers, scope the agents, put the gates in CI and wire the record. Your team runs real work through it while we are still there to fix what breaks.Ends with the baseline re-measured against the same four numbers.
- Rollout: scoped after the pilot
- The pattern extended to further teams and repositories, which is mostly a question of how much your repositories disagree with each other. We work alongside an internal owner from the first day, because the rollout is theirs to finish.Scoped only once the pilot has produced numbers worth extending.
What we need from you.
An engineer who can say yes
Someone with authority over CI, credentials and branch protection. Without them the engagement becomes a document.
Access, early
Read access to the repositories and the tracker in week one. We will work to your security review; we cannot work around it.
One real team
A pilot on a toy repository proves nothing. It needs a team shipping real work to real users, with real deadlines.
Permission to measure
The baseline is taken before anything changes. Without it, every claim afterwards, ours included, is a story.
When we will tell you not to.
Your delivery problem is not agentic
If work stalls in product decisions, unclear ownership or an approval chain with four names on it, agents will make the queue longer, not shorter. Fix the queue first.
Nobody owns CI
A pipeline is enforced in CI or it is advice. Where no one has authority to change the build, the engagement cannot deliver what it promises.
The mandate is headcount reduction
Organisations that install this to cut engineers get neither the cut nor the pipeline. The gates need engineers with judgment, and judgment does not survive being told it is being automated away.
You want a demo for the board
We do not build showcases. If the deadline is a board meeting rather than a delivery problem, a pilot will look impressive and change nothing.
Start with the assessment.
Two weeks, fixed fee, and a written answer about your own delivery pipeline that is useful whether or not you ever hire us again.
or write to hello@genica.org