Senior eyes on your team's code, every month.
Code reviews, architecture calls and agent workflows, on your codebase, while your team keeps shipping. You choose the hours each month, from 4.
30 minutes, free · first month paid upfront, then net 30
Teams we have worked with InervaHiiveErlang Solutions
The engineering and the context.
A monthly block can mix both: Bruce on the code and the review, Paulo on how the team feeds its agents.
Bruce Tate
Founder of Groxio and author of ten technical books on Elixir and programming languages.
- Elixir and OTP design: processes, supervision, boundaries
- Phoenix and LiveView code that grew faster than the design
- Reviewing what the agent wrote, and why it went that way
- Harnesses, skills and MCP for your own workflow
Paulo Valim
Groxio partner. He builds the context agents work from and turns it into work an agent can finish and a person can check.
- The business, customer and decisions an agent needs to know
- Stories small enough for an agent to finish
- Pull requests a reviewer can follow
- Checking the work before you trust it
You don't need a perfect question.
Part of the hour is finding the real problem behind the symptom. These are the usual starting points.
From a call to a monthly rhythm.
30 minutes, free: your team, your stack, how you use agents and where it hurts.
A short written plan: who joins, what we work on, how many hours a month.
The first month is paid upfront, before we schedule. After that, one invoice a month, net 30.
Reviews, pairing and design sessions. Change the hours from month to month as the work changes.
One rate, a monthly block.
Same hourly rate as individuals. Teams commit to a small monthly block so the work has continuity.
Discovery call
- Where your team is
- What it needs to ship
- Whether coaching or a workshop fits
A monthly block
- Code review, pairing and design sessions
- Bruce, Paulo or both
- Change the hours month to month
Private workshop
- One topic, on your stack
- A good way to start before coaching
- Your team, nobody else
First month upfrontThen net 30NDA on requestOne invoice a month
What to bring, what you take.
Bring
- The code: the repository, or the parts you can share
- One or two problems you want to solve
- The agent conversation that went wrong, if there is one
- What you can't change: deadlines, team size, old decisions
Messy is fine. Can't share code? Excerpts, diagrams or a good description work too.
Take
- A clearer picture of what the system really does
- The trade-offs, said out loud, instead of a hunch
- Next steps you can start the same day
- Questions to ask the agent next time
Not ready for a monthly block?
Before you book.
What is the minimum?
4 hours a month (US$1,000). Add hours whenever you need them, at the same US$250 rate.
Who from the team joins?
Whoever will make the change. Sessions work best with the people who will build it in the room, from one lead to a small group.
Can we change the hours?
Yes, from one month to the next, as long as you stay at or above 4.
How do we pay?
The first month is paid upfront, before we schedule. After that, one invoice a month, due in 30 days at most.
Can we sign an NDA?
Yes. Many teams work on private systems; we sign before we look at code.
Should we start with a workshop instead?
Often, yes. A one-day private workshop gives the whole team the same base; coaching keeps it going. The discovery call is where we decide.
Start with a free call.
Thirty minutes to see where your team is and whether coaching, a workshop or both fit.
Free · no commitment