Paid-scope example · one critical launch path

Know exactly what the A$149 review starts—and what it does not.

This is the default scope-confirmation shape for a Launch Path Review: one flow, accepted evidence, a founder-readable delivery and one bounded correction round.

A$149fixed review fee
1 flowagreed before payment
≤5prioritised observations
2 daystarget after scope + evidence acceptance
Scope example, not an automatic contract: work begins only after both sides confirm the exact flow and evidence in writing and payment clears. The delivery target is not an uptime, launch, security or commercial-result guarantee.

Default review scope

The paid review deepens one decision-critical path. It does not quietly expand into a whole-codebase audit or production implementation.

Included

  • One named user/operator flow, with start and expected end state.
  • Public, fictional or founder-redacted evidence accepted in advance.
  • Up to five prioritised observations: evidence, why it matters and smallest next action.
  • A founder-readable Markdown or PDF report plus asynchronous clarification.
  • One correction round for factual misunderstandings in the agreed evidence.

Not included

  • Certified security testing, penetration testing or compliance/legal advice.
  • Production account, customer-data, secret, API-key or payment-detail access.
  • Whole-repository code review, live deployment changes or open-ended debugging.
  • Fix implementation, retesting outside the named flow or third-party platform approval.
  • Guarantees of safety, uptime, launch approval, conversion, revenue or defect-free operation.

The start gate

No delivery clock starts from a vague “review my app” message. These three checkpoints must be accepted first.

1

Name the flow

Example: create an agent task → handle a tool failure → review retained state → accept, edit, reject or hand off.

2

Freeze the evidence

List each public/redacted URL, screenshot or fixture and the observed version/date. Remove secrets and customer data before sharing.

3

Confirm the question

Choose one decision the review should support. Unknown production behavior stays unknown unless separately evidenced.

Accepted scope line

Flow: [one start → recovery/review → end path]

Evidence: [named public/redacted materials only]

Question: [one founder decision]

Delivery: up to five observations + priority order + one factual correction round; no production changes.

Delivery and acceptance terms

Delivery clock

Target: two business days after written scope/evidence acceptance and cleared payment. If evidence is inaccessible, materially changed or unsafe to process, the clock pauses before analysis.

Evidence states

Each observation distinguishes what was observed, what was inferred and what remains unknown. Missing evidence is not converted into a defect claim.

Correction round

One asynchronous round corrects factual misunderstandings against the frozen evidence. New flows, new artifacts or implementation requests are separately scoped.

Stop / re-scope

If the useful answer requires secrets, customer data, production access or certified specialist work, the review stops or narrows before that material is requested.

Start with the free three-observation pass.

Use one public or redacted flow first. If the pass is useful, the A$149 scope is confirmed in writing before payment or deeper work.

Build the free requestAsk for the paid scope