Skip to content
Hodl Advisory

FAQ

Frequently asked questions.

Which package should I start with?

Choose Architecture Review for one defined initiative that needs an outside diagnosis. Choose Agent System Blueprint when you need a complete target architecture and staged path. Ongoing Advisory normally continues after either engagement; direct onboarding is scoped separately.

Who performs the advisory?

I do. Hodl Advisory is founder-led: I read the material, run discovery where required, perform the architecture work and write the final recommendations myself. Specialists on your side remain the experts in their domains; my role is to examine how those domains and system layers fit together. About my background →

Why use an independent architecture advisor if we already have a CTO and capable AI agents?

Your CTO understands the system from inside the project and remains responsible for delivery. Frontier agents work from the context and framing they are given. An independent review adds a perspective that is not invested in the current design or responsible for defending earlier decisions.

I do not replace your CTO, specialists, or agents. I pressure-test where their decisions meet, surface assumptions that may have become invisible, and provide a bounded investment against potentially expensive implementation risk. Why Hodl Advisory →

Why are package prices shown as “From”?

The starting price applies when the initiative fits the stated package boundary and the material is ready to review. Broader systems, additional workflows, unusually large evidence sets, accelerated timing, or additional stakeholder work may require a larger scope. You receive the exact scope and fee in writing before work begins.

Can we speak before I commit?

Yes. The usual starting point is a written description so I can understand the system before taking your time. If important questions remain—especially for a larger or unusual engagement—I can arrange a short fit call before you commit.

How does PROOF relate to the advisory?

PROOF is an open working standard I authored for reasoning about Premise, Role, Operation, Outcome, and Failsafe boundaries. It is one control lens I may use when relevant. An advisory engagement is not a PROOF certification, audit, or assurance opinion.

Does the system need to be finished?

No. It needs to be defined enough to inspect: a use case, current state, available material, and a real decision the team must make.

Is the advisory limited to trading?

No. The advisory applies to consequential agent systems across domains, including AI products, research and decision support, internal operations, monitoring and escalation, personal AI crews, and market infrastructure.

Can you review AI products, personal AI crews, research, or internal operations?

Yes, when the work involves consequential decisions, roles, evidence, permissions, handoffs, or escalation.

Do I need to use OpenClaw?

No. The advisory starts with your system and its decisions, not a required framework.

Can you work under an NDA?

Yes. I am willing to review a reasonable mutual or client NDA before confidential material is shared. The NDA does not expand the agreed access, input, or advisory scope.

Can you work alongside our implementation partner?

Yes. Hodl Advisory provides architecture review and design while your team or chosen partner implements the system. Reuse, publication, and white-label rights require explicit written agreement.

What can you advise on in compliance-sensitive workflows?

I can help design the workflow, evidence, permissions, approval, and control architecture. Your legal and compliance professionals retain interpretation and approval.

What happens after I apply?

I read every inquiry personally and send a fit response, including if I decline or recommend another path. If there is a fit, I send the written scope, Terms, and a proforma invoice or quote. Once the required payment clears, I prepare the customized intake for your engagement.

Next step

Ready to show me the system?

Bring a short description of the work, its current state, what feels unclear, and the next decision your team must make.

Bring me the problem