MR
consulting · rollins.io
●  Engineering leadership · onsite or remote

Bring agentic engineering to your team.

For engineering leadership. One or two days, onsite or remote.

Your team builds something real. Hidden structural pain surfaces. You leave with a private debrief on dynamics and who can lead.

Get in touch The approach
The shift

Coding stops being the bottleneck.

A leadership decision, not a tooling one. With coding off the critical path, planning, infra, trust models, and team composition hit their limits fast.

Trust models break

Senior review can't match agentic velocity. Trust moves to tests, AI review, and deterministic build gates.

Bottlenecks migrate

Planning, ticketing, and infra become the limiters — engineers idle on Jira while DSO chokes.

The deck reshuffles

With coding skill leveled, broad thinkers and self-starters rise. Some resist enough that reassignment's on the table.

Approach

A working session, not slides.

The first day stands on its own: your team builds, the pain surfaces, you get a private read. A second day adds a guided hackathon and a deep-dive scoped to what Day 1 surfaces.

01
The Shock
One-hour build challenge with a real prize. Engineers ship something real; the room sees what's now possible — viscerally.
02
Trust in Engineering
Reframes how you trust code: from "a senior catches it in review" to "what lets me ship a junior's code unsupervised?" Tests, AI review, build gates.
03
The Pain Snake
An exercise that surfaces the hidden structural pain. Group catharsis, plus a prioritized list leadership couldn't see yesterday.
04
Agentic Mechanics
Hands-on patterns: structuring ideas for the model, working with non-determinism, a daily workflow that compounds. Prompt engineering demystified.
05
Leadership Debrief
A private end-of-day session: team dynamics, standouts, friction, and concrete team-structure recommendations. Written report follows.
Day 2 · optional
06
Guided Hackathon
An aggressively-scoped goal with live coaching. Engineers pushed past where they'd stop — the point. ~half a day.
07
Custom Deep-Dive
Scoped from Day 1: fine-tuning on your hardware, infra/DSO acceleration, build-pipeline design, dev-env restructuring, or a Pain-Snake challenge.
Outcomes

What changes after.

Immediate · in-session
  • Engineers ship a working app in under an hour.
  • Leadership gets the new trust model.
  • A prioritized list of hidden structural pain.
Short-term · 30 days
  • 5–10× on infra, containerization, and pipelines.
  • Tests and automated review replace manual review as the trust mechanism.
  • First fine-tuned models where on-prem GPU allows.
Medium-term · 30–90 days
  • Right-sizing becomes obvious — 30 engineers' output from 5–6.
  • Planning moves from tickets to features; engineers get discretion.
  • Downstream bottlenecks (DSO, infra) fixed before they choke velocity.
Strategic
  • A culture selecting for broad thinkers and self-starters.
  • Soft skills, design sense, domain knowledge become multipliers.
  • Near-sovereign AI capability where compute allows.
Engagements

Two shapes.

One dayFocused

The full Day 1 arc — build, discussion, exercises, debrief, report. A high-signal read in one session.

  • The Shock build challenge
  • Trust in Engineering reframe
  • The Pain Snake exercise
  • Agentic Mechanics walkthrough
  • Private leadership debrief + written report
Inquire — one day
Two daysRecommended

Day 1 plus a guided hackathon and a custom deep-dive scoped to what surfaces. For teams ready to move.

  • Everything in One day
  • Guided hackathon with live coaching
  • Custom Day-2 deep-dive (fine-tuning, infra, pipelines, or a team-specific challenge)
  • Extended written follow-up
Inquire — two days
Logistics
FormatOnsite preferred; remote available
Group sizeEngineering org of 8–60
PricingQuoted per engagement
Lead time~4 weeks for onsite
FAQ

Quick answers.

Can you run this remotely?
Yes. Build, discussions, exercises, and the debrief all translate to remote. Onsite reads team dynamics better, but remote works for distributed teams.
What size team is this for?
Engineering orgs of ~8–60. Smaller loses exercise texture; larger dilutes the debrief. Outside that range? Get in touch.
Do engineers need to know AI tools already?
No — comfort with code is the only prerequisite. The Shock is built for engineers new to agentic tools, which is most rooms.
What does the leadership debrief actually cover?
Who moved fastest, who resisted, the real structural pain vs. what leadership assumed, who's positioned to lead, and concrete team-structure recommendations. Written report follows.
How is this priced?
Quoted per engagement, scaled to team size and travel. Quote within a couple of business days.