Services

Advice that comes with a working implementation behind it.

Three practices, four ways to engage. Every engagement is scoped tightly, run personally, and measured by whether the thing works in production — not by pages delivered.

IPractices

What the work covers.

Consulting

Advisory that survives contact with implementation.

Most consulting stops at the recommendation. This does not. Engagements start with the same diligence any firm would run — market, competitive position, unit economics, technical debt — and end with a decision you can act on, written by someone who has had to live with the consequences of decisions like it.

Typical engagements

Technical and product due diligence
Architecture and build-versus-buy review
Fractional CTO and technical leadership
Vendor, platform, and data-provider selection

Business Strategy

Positioning, product architecture, and the path to revenue.

Strategy work grounded in what can actually be built and sold. Brand architecture, tiering and pricing, go-to-market sequencing, and the unglamorous question of which three things to do this quarter instead of the thirty on the list.

Typical engagements

Brand and product-family architecture
Pricing, packaging, and entitlement design
Go-to-market sequencing and launch planning
New-venture and market-entry strategy

AI Creation

Agents and AI systems that do real work, in production.

Not pilots and not demos. Agents wired to live data with real tool use, evaluated for correctness and engineered for cost — because an agent that is right but uneconomic is not shipped. Includes the retrieval, caching, and voice layers that turn a model into a product.

Typical engagements

AI agent design and tool-use architecture
Retrieval, knowledge base, and grounding
Inference cost engineering and caching
Voice interfaces and conversational UX

IIHow to engage

Four shapes of engagement.

Pricing is set per engagement after the first conversation, once the actual scope is understood. There is no rate card because there is no standard problem.

Advisory retainer

Ongoing · monthly

A standing line to a technical operator. Architecture reviews, hiring calls, vendor decisions, and the strategy questions that come up between board meetings. Best for founders and executives who need a second opinion that has actually built the thing.

Best forFounders, CEOs, and boards

Diligence sprint

Fixed scope · 2–4 weeks

A hard look at a codebase, a product, or an acquisition target. What is real, what is scaffolding, what it would cost to operate, and where the risk is actually buried. Delivered as a written assessment with the evidence attached.

Best forInvestors and acquirers

Architecture engagement

Fixed scope · 4–8 weeks

Design of the system before it gets expensive. Data model, service boundaries, AI and inference layer, cost envelope, and the sequencing plan — with a working reference implementation of the risky parts, not just a diagram.

Best forTeams about to build something large

Build

Project · by scope

The system itself, delivered to production. Reserved for a small number of engagements per year where the problem is interesting and the scope is honest.

Best forCompanies who need it shipped, not specified

Not sure which one you need?

That is usually the right place to start. Describe the problem and the shape of the engagement will suggest itself.

Start a conversation