Use this when
- Architecture or execution order is still unclear
- The team needs a written risk map before committing build budget
- Founders want a scope recommendation before opening the calendar
Async proposal path
Request a Technical Audit recommendation.
Use this when build money is about to move but the architecture, risk order, or scope edge is still unclear. Send the context now, and the next response should clarify fit, likely audit focus, and whether the work should stay diagnostic or move into implementation.
Technical Audit$5K fixed scope1 week
Started from: MCP Risk Review buyer brief. That context will stay attached to this request.
Send the context now
Keep it short and specific. Rodolf should be able to tell whether this is a fit, what lane it belongs in, and whether the next step should be a call, a review, or a different path.