Async proposal path
Use this when the launch matters, the core workflow is mostly known, and the buyer would rather send context first than book immediately. The next response should confirm whether Launch Build (one surface, fixed $30,000) or Product Build (multi-surface, fixed $60,000) fits, and whether a call is the right next move.
Started from: mcp-scan proof surface. That context will stay attached to this request.
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. The response will name the smallest responsible move when there is a fit. Response SLA: within two business days.
This is a short decision note, not a vague sales intake.
Share what is blocked, what already works, and what must be safe when it ships.
We reply within two business days with a fit decision and the smallest responsible next step.
When there is a fit, the next step can be a focused review, a call, or a different lane.
Use this when