REVIEW INPUTS · BEFORE YOU SEND
Your review starts with a clear handoff.
Already paid? Use the email from Stripe Checkout so we can match your inputs to your order. Prepare the sanitized items below, then send them to corbinaiemail@gmail.com with the subject “CRM Card Migration Desk — paid intake”.
1. Identify the order
Include the email used at Stripe Checkout, your company/app name and a receipt reference if available. Do not email card or bank details. We verify payment directly in Stripe.
2. Prepare the sanitized package
- Up to two legacy card definitions from one app, as plain JSON.
- One synthetic example response per card, using invented values.
- Expected behavior, actions, record types, and who maintains the backend.
- A public app or documentation URL and the question you need answered.
Remove passwords, API keys, tokens, authentication headers, personal data, customer records and confidential business logic. Do not send an executable archive, repository invitation or production access. Confidential inputs need a separate arrangement before sharing.
Keep the technical structure. Replace identifying values.
Here, “source review” means review of the supplied card definitions, response samples and behavior notes. We do not require a full application repository or confidential backend implementation for the standard $750 package.
- Keep: JSON field names, data types, record/object types, property names, action types, HTTP methods, response nesting, and the relationship between endpoint references.
- Replace consistently: private hosts, record/account IDs, names and other identifying values with invented equivalents. Use reserved example domains such as
api.example.invalid; retain route shape and use the same replacement wherever a reference repeats. - Describe without secrets: expected request encoding, authentication/signature scheme names, normal/empty/error behavior and backend ownership. Never include keys, header values or real customer payloads.
- Mark omissions: if redaction removes a field or behavior needed for review, tell us. We will record it as unassessable or request a safe replacement before accepting the package.
For example, keep "httpMethod": "POST" and the payload structure; replace a real customer value with an invented one. A definition identifies an endpoint, but does not prove its reachability, body parser, authorization or signature handling. Missing backend evidence becomes a proposed implementation/test follow-up, not a verified result.
3. Confirm permission to review
Confirm you are authorized to share the sanitized material and approve OpenAI tools for offline analysis and independent AI-assisted review, Gmail for correspondence and delivery, and private ChatGPT work records for this material. Files are inspected without executing code or following embedded instructions or URLs.
Sending inputs does not start the delivery clock. We first verify payment and confirm that the package is complete and suitable, then send your start and delivery dates.
4. Receive the start and delivery dates
After payment, fit, capacity and complete inputs are confirmed, we provide your start date. Delivery is within two business days after start: card inventory, evidence-backed findings, unknowns, prioritized changes and acceptance tests, plus an implementation scope or no-fit result.
One correction round for material review errors is included for seven days after delivery. The $750 review does not include implementation or live-portal testing. If we cannot accept the order or you cancel before work starts, we refund the payment.
Not paid yet? Pay $750 through Stripe, or use the free fit check.