Fractional architecture

Hire a senior staff agentic AI engineer.

Book 30 minutes See what you get ↓

**Brian Love**Google Developer Expert since 2019. Maintainer of hashbrown, threadplane and b4.run.

Teams usually call me when

“We have more agent decisions than agent experience.”

“Our team needs someone to review the work already in flight.”

“We don’t need a full-time hire. We need the right calls, every week.”

A month, and what it leaves behind

About sixteen hours, spread so your team is never waiting on me. Every session ends in writing your team can keep.

Week 1Design review of the agent plan

Week 2Pairing on the eval harness

Week 3Protocol decision memo

Week 4Review and next month’s focus

Async between sessions: pull request reviews and short answers in your chat.

Decision memo · week 3sample

Expose the claims tools over MCP, keep the UI on AG-UI

Decision

One MCP server for the six claims tools. The adjuster UI keeps streaming over AG-UI.

Why

Two other teams want the same tools from their own agents next quarter, and AG-UI already carries the approvals the adjusters rely on.

Revisit if

Tool latency over MCP exceeds 300ms at p95.

Owner

Platform team lead. Review in six weeks.

Decisions, not opinions

Each memo names the decision, the reason, and what would change it.

In your code

Reviews and pairing happen in your repo, on the work already in flight.

Built to hand back

The goal is a team that makes these calls without me.

A typical month, in hours

Week 1Design review

Week 2Pairing on the eval harness

Week 3Protocol decision memo

Week 4Review and next month

Live with your teamAsync reviewsWriting it down

Start with one architecture review. It works as a fit test: if we don’t work well together, you keep the review and we stop there.

Done before

Santander

Lead architect from the first roadmap to the day the old system was switched off.

I analysed a legacy app delivered over Citrix, wrote the roadmap with leadership, architects and users, then led the migration to a cloud-ready Angular application. Read the story

For your security and procurement review

Data: I work inside your repo and tools with the access you grant. Nothing is copied to my systems.
Independence: I don’t resell models or platforms. When I recommend a library I maintain, I say so.
Code and IP: Anything I write or draft for you is yours.
Access: Least privilege, removed when the engagement ends.
Paperwork: US LLC. Your MSA and NDA or mine. Professional liability insurance. W-9 on request.
Billing: A monthly block of hours, invoiced net-30.

Questions

How many seats?: A handful at a time. I don’t take more than I can give real attention to, and if I’m full I’ll say so.
Can a team start small?: Eight hours a month is the floor; thirty-two is the ceiling.
Do you write code?: Yes, when pairing on the hard parts. Most of the value is in the calls your team makes faster.

Start with one architecture review.

Tell me the decision or design your team is stuck on. I’ll reply within a business day with what the review would cover.

Describe the decision →