HOW WE WORK

FROM FIRST WORKSHOP TO ORGANISATION-WIDE ROLLOUT

We install our agentic SDLC in your engineering organisation in three stages. Each one is designed to make a considerable step towards agentic development, and at any point in time, you can bring everything in-house.

How we run every engagement

FOUR RULES WE DON’T BEND

You pay for outcomes, not days

Every stage is priced on what you get, not on hours or day rates.

We measure before and after

A baseline at the start, re-measured after the pilot and rollout.

Your teams adopt it on any project

Change management is part of the work from day one.

We plan to leave

You end up self-sufficient as your engineers take over.

3

priced stages

2 to 3

weeks from commitment to workshop readout

1

fixed price to get started

THE PATH

Stage 1

The workshop: decide with numbers

A paid discovery workshop that shapes our agentic SDLC to your engineering organisation. You pay one fixed price for the outcome, not for days. [€15,000]

What happens:

Pre-work: an intake questionnaire, the metrics you already trust, an anonymous engineer survey and read-only access to repositories, CI and PR history
Workshop days: two to three days on site. Day 1 is diagnosis. Day 2 is target design, with live demos mapped to your constraints
Blueprint build: we turn it all into your blueprint, baseline and pilot plan, with up to two 2-hour follow-ups included
Readout: a 90-minute session where your team presents the case to your business, with our support

STAGE 1 IN PRACTICE

WHAT THE WORKSHOP LOOKS LIKE

Most engineering teams sit in one of three places:

What you leave with

Your blueprint, a measured baseline, a scoped and priced pilot plan, and the upside of acting and the cost of not, in euros.

Who should attend

Your CTO and executive sponsor, engineering leads, two or three senior engineers, and compliance and security for the risk session.

Who runs it

One of our agentic SDLC architects, paired with a senior agentic SDLC engineer who makes the demos real in your context.

How long it takes

Two to three weeks once you commit.

Stage 2

The pilot: prove it on a real project

We implement your blueprint on one project chosen in the workshop: bounded but real, with a champion leading it and an outcome you can ship and measure. It’s priced at a fixed figure agreed at the readout, so there are no open-ended hours. What happens:

We set up the agents, automation and human sign-off points your blueprint defines, including our own tooling, nissy.ai
Our engineers deliver one or more features through the new setup, in your environment
We coach a small team of your engineers as they work alongside us
We re-measure your baseline at the end

You leave with a working agentic setup, at least one feature shipped through it and before-and-after numbers.

Stage 3

Scale up: make it how your organisation builds software

One team working differently isn’t the goal. The rollout takes what the pilot proved across more teams and codebases, and it’s where the return shows up across your organisation. What happens:

We extend the agent setup and governance across your organisation, team by team
We run change management with your engineering leaders
Our engineers carry the method into each team, and step back as your teams take over
We re-measure your baseline at the end

This isn’t staff augmentation. You’re paying for the method and the change, not for extra hands, and we design our exit from the start.

FAQs

QUESTIONS CTOs ASK US

Do we have to commit to all three stages?

No. You commit to the workshop. If it does its job, the pilot is an easy decision. If it doesn’t, you still keep the blueprint.

Could we implement the blueprint ourselves?

Yes. It’s a transferable plan you could run with your own team or another partner. Most teams choose us because we’ve run the method before.

Which AI tools and models do you work with?

Our agentic SDLC isn’t tied to one model or vendor. We work with tools such as Claude Code, Codex and Copilot, and choose what fits your stack.

How do you measure the gains?

A baseline at the start, re-measured after the pilot and the rollout. Where a number can’t be measured honestly, we say so rather than invent one.

What access do you need, and when?

Read-only access to repositories, CI definitions and PR history, requested only after you’ve committed to the workshop.