Public pricing logic page

Use the right price tier for the actual scope.

This page defines when the sprint fits the `$299`, `$799`, or `$1,500` bucket, when to upgrade the scope, and when not to accept a badly shaped project at the wrong price.

Open Price Map Open Payment Page

$299 teardown tier
$799 default core sprint
$1,500 broader setup tier

Price Map

Pick the tier that matches the real work.

$299

Use when the client mainly needs a short teardown, narrow audit, or one directional fix rather than a full sprint execution.

Open Micro Offer

$799

Use when the project fits one meaningful bottleneck with a real delivery shape: message flow, intake structure, handoff, and SOP.

Open Deal Desk

$1,500

Use when the scope is clearly broader: more packaging, more systems, more handoff, or a more complete setup.

Open ROI Board

When To Move Up

Do not keep broad scope in the core tier.

Upgrade To $799

If the client wants execution instead of diagnosis, move out of the teardown tier.

Upgrade To $1,500

If the client is stacking deliverables or asking for a fuller setup, treat it as the broader package.

Split Into Another Sprint

If the scope keeps expanding beyond the broader tier, stop discounting and break it into a second sprint.

Do Not Underprice

Bad scope shape is a pricing problem first.

Too Many Deliverables

If the ask includes several unrelated outputs, the scope is too broad for lower tiers.

Too Much Ambiguity

If the client cannot name the main bottleneck, diagnose first before pretending the scope is priced.

Too Much “Just One More”

If new asks keep appearing, that is a renewal or new-scope decision, not a reason to quietly absorb more work.