How an engagement works

Six steps for the paid Claude Code live check. Free Preflight is static-only and is not these steps.

  1. Request. Tell us the MCP server or integration, which host it fails in, and what working looks like.
  2. Quotation. The quotation lists what is still open. It is not itself the agreement.
  3. Confirmation. Terms take effect only on a service confirmation issued after human approval.
  4. Delivery. Delivery means we send the final report (and, for US$300, the PR link) to your confirmed contact; interim logs are not delivery. The report names the artifact, the host, and the versions. Every finding is tied to that run.
  5. Recheck. You have 5 working days from the first working day after delivery (Monday–Friday, excluding Taiwan public holidays) to repeat the supplied steps and confirm acceptance, or use one dispute round: report a mismatch against the agreed scope in writing, with recheck evidence, or request the free rerun (once only) if the named versions are unobtainable. This pauses acceptance and issuance of the payment request once, for at most 10 working days, while we send a rerun or fix log or explain in writing why your mismatch report is not a mismatch against the agreed scope. Our response opens a new 5-working-day window for confirming acceptance only. If you state in writing within that window that the dispute remains unresolved, or we do not respond within the pause, section 6 of the Services Terms applies.
  6. Payment request. Issued after acceptance and due within 7 calendar days; no payment before delivery. Details are in sections 4 and 6 of the Services Terms.

Terms in brief

Start with an email

Send the MCP server or integration, which host it fails in, and what working looks like. We only need a public or runnable artifact.