advisory
Advisory.
Three ways to engage. Pick the one that matches the decision you're actually trying to make: an honest outside read on strategy, a monthly seat at the table, or an embedded build that ships something real and leaves a playbook behind.
Engagements are priced as monthly subscriptions, not hourly. Each tier defines what you get (sessions, reviews, async access, deliverables) so you're paying for the work, not clock time. AI tools make execution faster; that efficiency stays with you, not on your invoice.
[a-01] Strategy Review
single engagement 2–4 weeks A senior outside read on where your AI strategy actually is.
Six to eight stakeholder interviews. A working session with your leadership team. A written deliverable: where you are, what will actually move the needle, what to build first and what to kill. Honest, specific, no slideware.
good fit: You have a strategy on paper. You're not sure it survives contact with reality.
- ✓ 6–8 stakeholder interviews
- ✓ 1 working session with leadership
- ✓ Written assessment (20–40 pages)
- ✓ 30-day follow-up call
most teams start here
[a-02] Advisory Retainer
ongoing 3–12 months A seat at the table for the decisions that matter.
Two working sessions per month. Async availability on Slack. Quarterly written strategic reviews. Vendor and RFP reviews on request. I read your roadmap, your release notes, and your incident reports. I show up to the meetings where the architecture gets decided.
good fit: You're shipping agents and want someone in the loop on the decisions you can't unmake later.
- ✓ 2 working sessions / month
- ✓ Async availability M–F
- ✓ Quarterly strategic review (written)
- ✓ Vendor + RFP review on request
- ✓ Slack channel I actually read
[a-03] Embedded Architect
focused build 8–12 weeks I join your team part-time for a focused build, then leave you with the playbook.
About ten hours per week embedded with your team: pair with named engineers, set the architecture, write the spec, ship the prototype, document everything. AI-native productivity means a focused 10 hrs/wk lands more shipped work than most 40 hrs/wk old-model engagements. Includes 30/60/90-day follow-through after handoff.
good fit: You have funding and intent but the team isn't yet equipped to ship the system you've sold internally.
- ✓ ~10 hrs / week embedded
- ✓ Pairing with named engineers
- ✓ Production-grade prototype
- ✓ Architecture spec + playbook
- ✓ 30/60/90-day follow-through