From the first report
to an agreed next step.

Payment, access and implementation have separate boundaries. Here is how the work is defined before it starts.

01

Describe the failing path

Share the app URL, what you expected, what happened and the business impact. Include screenshots or logs without secrets.

You provide

Reproduction steps, context and the technical environment.

Keep out of the form

Passwords, private keys, API secrets and customer data.

02

Separate diagnosis from repair

If the cause is unclear, choose the written diagnostic. If the repair is clear, request a defined scope directly.

Before a repair payment

Agree on deliverables, price in USD, access, timing and acceptance checks.

Before paid work

Confirmed payment and the agreed information and access.

03

Receive a written outcome

Triage provides evidence, priorities and a recommended repair order. Implementation follows only under a separate agreed repair scope.

Diagnostic timing

Within one business day after the required access is available.

Repair timing

Confirmed in the written scope. No general start or resolution deadline.

Practical questions.

Have these ready

  • Latest deployment URL
  • Steps that reproduce the failure
  • Expected and observed behaviour
  • Relevant screenshots or logs, without secrets

Grant project access only when requested.

Does $149 include fixing the problem?

No. Emergency Triage covers a written diagnosis: blocker map, evidence, likely cause, repair order, acceptance checks and a fixed-scope recommendation. Code changes need a separate approved repair scope and price.

Do I have to buy a diagnostic before a repair?

No. If the failing integration and repair scope are already clear, you can request an Integration Rescue scope directly. The diagnostic is useful when the cause or boundaries are unclear.

What access will you need?

Code access is usually needed, but only after the project is accepted. ShipRescue asks for the least privilege practical and recommends read-only access for diagnosis. Never paste passwords or secret keys in the public form.

When does the one-business-day timing begin?

After the information and access needed for the diagnostic are available. This timing applies to the written Emergency Triage report. Repairs have their own timing agreed in the written scope.

What are the refund and credit conditions?

If ShipRescue cannot accept the project before diagnostic work starts, the $149 is refunded to the original payment method. Once diagnostic work begins, completed analysis is non-refundable except where law requires otherwise. The fee is applied once as non-cash credit toward a follow-on rescue approved within 7 calendar days after report delivery. Full refund policy ↗

Is a successful launch or business result guaranteed?

No. ShipRescue verifies the agreed technical path. Third-party services, demand and business results are outside its control. A submitted request does not guarantee acceptance, a start date or a resolution deadline.

Describe what is failing.

The app URL, failing steps and business impact are a useful starting point.

Discuss your project Compare the three offers →