03EngagementPrincipal Advisory
A second brain. Same person, every time.
Some decisions need one person who has made them before and will answer for the advice. Advisory gives you direct, ongoing access to me: architecture review, AI system evaluation, and escalation for the problems your team shouldn’t sit on.
- Shape
- Ongoing, scoped around your decision calendar
- Format
- Direct access to Theo — no rotating pool
- You leave with
- Decisions made, documented, and owned
01 — The problem
The decision that keeps getting postponed
Talent is rarely the constraint. Unallocated senior attention is: the architect is deep in delivery, the CTO is in meetings, and the system keeps growing around assumptions nobody has examined.
- The same architecture question has survived three quarterly plannings.
- The team can execute, but nobody senior has time to frame the decision.
- The last consultant’s deck is still unopened.
02 — What you get
Judgment on tap, accountability in writing
The person on your calls is the person who would build the system, not an account manager with a bench behind them. Reviews end in written recommendations with the trade-offs stated plainly, including the ones that argue against hiring me for anything further.
- Architecture review of the systems carrying the most risk
- AI system evaluation: quality, security posture, and operating costs
- Decision support with written rationale you can forward upward
- Design review for critical changes before they become expensive
- Escalation for the difficult problems your team shouldn’t sit on
03 — How it runs
First session
The systems, the constraints, and the decisions actually on the table — including the ones nobody has said out loud.
Cadence
Recurring sessions plus asynchronous review of designs, documents, and the decisions between meetings.
Escalation
The hard problems come to me first — incidents of judgment, not incidents of uptime.
Handoff
When advice becomes a build, the Production Build model takes over. When it becomes a ranking of options, the Decision Sprint does.
04 — Proof
2015
Co-founded Cult of Coders
1,900+
GitHub stars on open source
2012
Shipping software in public since
Advisory only works if the advisor still ships. The public record is on GitHub, where the tools I created or maintain carry more than 1,900 stars; client outcomes are in the work section.
05 — Straight answers
Is this a retainer with a pool of consultants?
No. You deal with me directly, every session, every review. When a build needs more hands, the names of the Cult of Coders engineers involved are agreed with you first.
Do you replace our CTO or tech lead?
No — I work for them as much as for the CEO. The role is second opinion, reviewer, and escalation path. Ownership of the decision stays inside your company.
How much access do we actually get?
A cadence we scope at the start around your decision calendar — recurring sessions plus asynchronous review. Deliberately not ‘unlimited Slack access’; vagueness helps nobody when a real decision lands.
Good judgment is cheaper than a postponed decision.