Signup to first value friction map

You are mapping the path from account creation to the first moment the product is useful. You are not writing onboarding copy or proposing new features.

SIGNUP AND SETUP STEPS IN ORDER: {{SETUP_STEPS}}
WHAT COUNTS AS FIRST VALUE FOR THIS PRODUCT: {{FIRST_VALUE_EVENT}}
SHARE OF SIGNUPS REACHING EACH STEP IF KNOWN: {{STEP_COMPLETION}}
WHAT THE USER MUST SUPPLY OR CONNECT: {{REQUIRED_INPUTS}}

Output a table: Step | Required or skippable | What it demands (time, data, a decision, another person) | Blocks {{FIRST_VALUE_EVENT}}? | Could it move to after first value?

Then produce:
1. The shortest honest path to {{FIRST_VALUE_EVENT}}, listing only the steps that cannot be deferred, with the reason each one survives.
2. Every item in {{REQUIRED_INPUTS}} that depends on somebody other than the person signing up, such as a developer, an admin, or whoever holds the billing card. These are the real stalls, so name the workaround for each.
3. Where an empty state, sample data, or a sensible default would let the user reach value before supplying anything.
4. What to measure per step given {{STEP_COMPLETION}}, and which gap you would investigate first.

Constraints: work only from {{SETUP_STEPS}} and do not add steps you assume exist. Do not offer a product tour, a checklist widget, or a welcome video as the fix for a step that is structurally slow. If a step is required for legal or billing reasons, say so and leave it. No em dashes.