Services · Scan & Go · Rollout

Nothing moves because the calendar said so. It moves when the gate passes.

A diagnosis that shows where AI is stalling your team, and a rollout that delivers the first governed flow running in production. Our team effort: fourteen days of work. Calendar window: six to ten weeks from the moment access is granted, because the pilot needs real development cycles to produce a comparison.

Start with the diagnosisSee the real schedule

A forty-minute conversation settles whether the Scan makes sense for your team, and you leave it knowing what would be mapped.

About the h|ve Platform

This is the service that installs the platform in your engineering.

Every h|ve service runs on the same platform. Scan & Go is what stands it up: the Scan maps where AI comes in and where it should not, and the Go connects that design to what your team already uses, with the project rules written where the AI tool reads them. The method is not the platform, but the platform is what makes the method hold after we leave.

What this service touches

Map · context
Flow · orchestration
Guard · barrier
Judge · drift
Ledger · record

The minimum viable harness: context layer, flow with gate, barrier in the editor, drift reading and record. Installed once, measured in the pilot.

What stays on the platform after this service

The governed flow configured, the Person by AI responsibility matrix, the usage policies, the baseline and the pilot report. It is the base that Governed Method Packs keeps alive and that FDE Velocity and the Labs find ready: nobody starts from zero.

What stalls today

The team adopted AI. Leadership cannot see it.

It is not a productivity problem, it is a traceability one. Productivity is solved with training. Confidence comes back the way an audit brings it back: by seeing what happened, who decided and on what basis. That is what Scan & Go gives back.

The team adopted AI, and each person uses it their own way, with a prompt of their own, in a different editor.
Nobody can say how much of the codebase came from AI, who reviewed what, or which decision was recorded.
Speed went up and confidence went down, so leadership brakes what it cannot see.

One service, two speeds

Scan, the diagnosis. Go, the rollout.

The method does not change: understand, decide, build the minimum, prove. What changes is what each speed promises and what you hold at the end of it. The Scan comes first because the diagnosis is useful even if the rollout never happens, and because rolling out a flow nobody validated is paying twice. Effort and calendar appear separately, because they are different measures, and the calendar variables live on your side.

Speed 1 · phases 1 to 3Scan

Understand the current development flow and design the target operating model. It is the AI Value Discovery equivalent for whoever already has an engineering team: a diagnosis with a clear deliverable, useful even if the rollout never happens.

Effort7 days of work

Calendar3 to 4 weeks

The picture of how the team works today, and the map of where AI comes in and where it should not.
The prioritization matrix and the target operating model, with the Person by AI responsibility matrix.
The design of the first governed flow, with the decision points named, and the enablement plan.

At the end of the Scan you know where you stand, you have decided how you want to operate and you hold a design any vendor can execute. If the diagnosis shows the company is not ready yet, that is a legitimate result, not a failed project.

Speed 2 · phases 4 and 5Go

Build the minimum viable harness and prove it with real teams. The flow designed in the Scan in production, the integrations with what the team already uses, the project rules written where the AI tool reads them, and the comparison between before and after measured in real cycles.

Effort7 days, plus the pilot follow-up

Calendar4 to 6 weeks, 3 to 4 of them pilot

The harness in a controlled environment, the usage policies and the developer manual.
The pilot report, with the before and after.
The business case to scale, or the recorded decision not to scale, with the reason.

Prerequisite: Scan completed. Rolling out a flow nobody validated is paying twice.

The real schedule

Governance starts by not hiding its own timeline.

Fourteen days of our work are not three calendar weeks. The Prove phase, on its own, is a pilot with real teams and before-and-after metrics, and that does not happen in five running days. The table says what depends on you in each row, starting with the pre-start, which is where the rollout usually slips.

Phase	Effort (days)	Calendar	What depends on you
Pre-start	1	1 to 3 weeks	Environment access, security approval, leadership calendar
01 Align	1	1 week	Leadership, technology and business in the same room
02 Map	3	1 to 2 weeks	Team availability for interviews
03 Design	3	1 week	Target model approval by architecture
End of Scan	8	4 to 7 weeks, with the pre-start
04 Enable	2	1 to 2 weeks	Access granted to IDE, Git, CI/CD and task management
05 Prove	5	3 to 4 weeks	A real team using the harness on real work
End of Go	7	4 to 6 weeks
Total	15	8 to 13 weeks from signature, 6 to 10 from access granted

How fast access is granted.Four integrations in a corporate environment do not happen in two days, and the bottleneck is not even technical. That is why the start date counts from the moment access is granted.

Leadership availability.Phases 1 and 3 demand decision, not attendance. One person with the authority to approve the design, at the two gate meetings.

Pilot length.Three to four weeks is the minimum to produce a comparison someone will sign. Five business days of use by one team do not produce one.

The five phases

Every phase delivers something, and only ends at the gate.

The design is always the same: understand where you are, decide how you will operate, build the minimum that works and prove it with real teams. What changes from company to company is the content, not the order. Not everything a phase produces is a document: Align produces four decisions and one document.

01AlignScan · 1 day
Exit gateThere is a measurable business outcome, a named sponsor, an agreed initial scope and the baseline of the indicators.
What comes outThe north star for AI development, the candidate teams and the success criteria. The baseline requires collecting company data, and that does not come out of one meeting.
02MapScan · 3 days
Exit gateEnd-to-end flow mapped and a list of opportunities prioritized by impact, effort and risk.
What comes outThe map of current development, the friction map and the prioritization matrix.
03DesignScan · 3 days
Exit gateTarget operating model approved, with clear responsibility between person, AI and system, and the pilot defined with a minimum volume of deliveries per week. If the team does not have that volume, the delivery stops at the Scan and the Go waits.
What comes outThe Person by AI responsibility matrix, the target architecture, the guardrails and the enablement plan.
04EnableGo · 2 days
Exit gateHarness working end to end in a controlled environment, with integrations, context, agents and the minimum controls to start the pilot.
What comes outThe minimum viable harness integrated with IDE, Git, CI/CD and task manager, the context layer, the usage policies and the developer manual.
05ProveGo · 5 days, over 3 to 4 weeks of pilot
Exit gateThe pilot shows proven benefit without degrading quality, security or compliance, with evidence to decide on scale. If it fails, the report and the metrics are delivered all the same, and the decision not to scale is recorded with the reason.
What comes outThe before-and-after metrics, the pilot report and the business case to scale.

After Go

Scaling and evolving are ongoing work, and each has its own path.

Scaling to other teams and keeping the method alive are not phases of Scan & Go: they are work that never ends, and each has its own service in the portfolio. What the rollout leaves behind is the base they start from, without starting over.

What keeps runningThe platform stays

The h|ve Platform configured in the Go keeps running in your operation after the rollout ends: the governed flow, the context layer, the guardrails and the record stay where your team already works.

Teams come in wavesAI Leadership Lab and the Labs

Each wave of teams goes through enablement applied to its own challenge, with the authority matrix decided by leadership beforehand.

The bar stays aliveGoverned Method Packs

Review the method, measure cost and drift in the recorded operation and adjust as the work changes.

Who it is for

Who it is for, and who it is not for.

Three conditions need to be present for Scan & Go to work. When one is missing, the diagnosis has nothing to map or the pilot has nowhere to run, and we tell you which path is right instead of this one.

It is for youIf all three are present

The team already uses AI with no standardEach person their own way, and leadership cannot see what comes out.
There is a person who decidesWith the authority to approve the target model design, at the two gate meetings.
There is real work to run the pilotA team with a volume of deliveries per week, in real development cycles.

It is not for youAnd where we point you

The team has not written its first line with AI yetThere is no flow to govern. AI Leadership Lab first, to decide where AI comes in.
Nobody has the authority to approve the designGates 1 and 3 do not pass. We come back when there is someone to decide.
You are looking for someone to write the code for youScan & Go prepares your engineering to build better, it does not build the product. FDE Velocity.

Has an engineering team of its own and wants it to produce better.Scan & Go
Has no team, or a small one, and needs a business capability working.FDE Velocity
Has already rolled out and needs to keep the bar alive.Governed Method Packs
Leadership still needs to decide where AI comes in and what stays a person’s decision.AI Leadership Lab
Does not know where to start.AI Value Discovery

Who delivers

Two partners, from the first gate to the pilot report.

There is no handoff. Whoever runs the Align is whoever follows the pilot, and whoever designs the architecture is whoever builds the harness in your environment: the same two people stay with you from the first gate meeting to the final report.

André JB RodriguesCo-founder and Business Lead · account manager

Runs the Align, the Map interviews and the gate meetings with leadership. Turns the real operation into the target operating model.

Gustavo HartzCo-founder and Technology Lead · client engineer

Designs the target architecture and the guardrails, builds the harness in your environment and follows the pilot. Answers for the platform, from the Map to the Guard.

Questions

The questions of the people who approve.

The ones procurement, security and legal will ask before sign-off, answered here so you walk into those conversations with the answer ready.

How long in calendar time?

Six to ten weeks from the moment access is granted: three to four of Scan and four to six of Go, of which three to four are the pilot running. What moves the calendar is how fast access is granted, leadership availability at the two gates and the pilot length.

How many of my people?

One person with the authority to approve the design, available at the two gate meetings. The Map teams, for short interviews. And one team that will run the pilot with real work for three to four weeks.

What happens if the pilot fails?

The report and the metrics are delivered all the same, and the decision not to scale is recorded with the reason. It is the same principle as AI Value Discovery, where not building is a legitimate result.

Does my code leave here?

What travels is flow metadata, the approved specification and the PR diff. The content of the code files stays in your environment, and code is not retained. The full answer is on the Trust page.

How soon does it start?

The pre-start takes one to three weeks: read access to the repository and the task manager, a named security contact, the leadership calendar reserved for the two gates and a candidate team for the pilot, with real work and outside any code freeze window. The start date counts from the moment access is granted.

The next step

Start with the diagnosis.

A forty-minute conversation settles whether the Scan makes sense for your team, and you leave it knowing what would be mapped.

We reply within one business day.

Prefer to write? hello@hybridvelocity.com