7DEA

Chapter 12

Open the AppBack to Docs Home

Chapter 15: Commercial State Guides

Commercial state often explains more of the user experience than people realize. This chapter turns the major commercial patterns into concrete scenarios so users can tell whether they are looking at a normal gating rule, a healthy limitation, or a true contradiction.

State Guide 1 — Signed In but Not Yet Commercially Active

A user has completed sign-in and assumes that alone should unlock operational use.

Starting point

Dashboard and billing are available, but the commercial state still reads exploratory or otherwise non-entitled.

Decision pressure in this scenario

The user feels close to action and may misread commercial gating as a technical problem.

Best route sequence

  1. Check dashboard and billing side by side.
  2. Read the visible plan or trial language carefully.
  3. Decide whether trial or paid activation is the appropriate next step.
  4. Return to dashboard or Aegis only after the state change is confirmed.

What to pay attention to

  • Identity and entitlement are distinct layers.
  • Graceful invitation language is normal in this state.

If you use the route sequence above, read each page for the category of truth it owns rather than for generic reassurance. This prevents the most common scenario mistake: reaching the correct page but still asking it to answer the previous page’s question.

Common wrong turn

The wrong turn is repeatedly retrying live-guidance or export actions without first changing the commercial state.

Healthy outcome

A healthy outcome is that the user understands what sign-in accomplished and what still requires activation.

State Guide 2 — Active Trial with Locked Exports

The account is in trial and the user is surprised that some exports remain unavailable.

Starting point

Billing shows trial day language, while deliverable routes still show locked distribution actions.

Decision pressure in this scenario

The user expected the trial to behave like full paid access.

Best route sequence

  1. Read the trial limitations on billing.
  2. Confirm Aegis live behavior if guidance is the current need.
  3. Use Draft review and route interpretation productively instead of fixating on locked exports.
  4. Decide whether the workflow value already justifies a paid step.

What to pay attention to

  • Trial is real usage, but not the same as paid distribution posture.
  • Live guidance and export entitlement are related but not identical.

If you use the route sequence above, read each page for the category of truth it owns rather than for generic reassurance. This prevents the most common scenario mistake: reaching the correct page but still asking it to answer the previous page’s question.

Common wrong turn

The wrong turn is deciding the trial has no value simply because it does not unlock every distribution action.

Healthy outcome

A healthy outcome is that the user evaluates the live workflow honestly and understands what a paid plan would add.

State Guide 3 — Active Paid Plan with No Deliverables Yet

A paid user expects immediate distribution value but has not yet created an artifact.

Starting point

Dashboard shows an active plan, but recent deliverables are empty.

Decision pressure in this scenario

The user wants to justify the subscription quickly and may over-focus on outputs that do not yet exist.

Best route sequence

  1. Use dashboard to confirm paid state.
  2. Move directly to deliverable creation.
  3. Create a first baseline draft with a strong scope statement.
  4. Use deliverable review before thinking about distribution.

What to pay attention to

  • Paid state unlocks capability, but does not create artifacts by itself.
  • The first milestone is a meaningful draft, not a theoretical capability list.

If you use the route sequence above, read each page for the category of truth it owns rather than for generic reassurance. This prevents the most common scenario mistake: reaching the correct page but still asking it to answer the previous page’s question.

Common wrong turn

The wrong turn is staying on billing and reading plan cards repeatedly instead of moving into the workflow the plan unlocked.

Healthy outcome

A healthy outcome is a created draft that proves the paid state is being used for actual work.

State Guide 4 — Cancellation Scheduled but Access Still Active

A user sees cancellation language and worries access has already disappeared.

Starting point

Billing shows a scheduled change while the current period still appears active.

Decision pressure in this scenario

The user is anxious about continuity and may misread end-of-period language as an immediate shutdown.

Best route sequence

  1. Read the exact cancellation wording.
  2. Confirm current access on dashboard or billing.
  3. Decide whether you are planning a wind-down, a reversal, or simply documenting the horizon.
  4. Use the remaining access period intentionally.

What to pay attention to

  • Scheduled change language often differs from immediate loss of access.
  • Visible wording is more trustworthy than assumption in this scenario.

If you use the route sequence above, read each page for the category of truth it owns rather than for generic reassurance. This prevents the most common scenario mistake: reaching the correct page but still asking it to answer the previous page’s question.

Common wrong turn

The wrong turn is abandoning current work because of a misread of scheduled language.

Healthy outcome

A healthy outcome is that the user knows what remains active now and what changes later.

State Guide 5 — Past-Due or Payment Attention Required

A user suspects billing posture is affecting capability, but has not yet confirmed what the product is saying.

Starting point

Billing or related surfaces imply the account needs commercial attention.

Decision pressure in this scenario

The user may believe the platform is failing them when the real issue is the unresolved commercial state.

Best route sequence

  1. Open billing and confirm the visible state.
  2. Avoid diagnosing export or Aegis behavior before understanding commercial posture.
  3. Resolve the billing issue through the provided billing path.
  4. Return to dashboard and re-check capability after the state changes.

What to pay attention to

  • Billing state can explain surprising product behavior elsewhere.
  • Route order matters; billing truth comes before workflow assumptions here.

If you use the route sequence above, read each page for the category of truth it owns rather than for generic reassurance. This prevents the most common scenario mistake: reaching the correct page but still asking it to answer the previous page’s question.

Common wrong turn

The wrong turn is spending time debugging routes that are correctly reacting to a commercial problem.

Healthy outcome

A healthy outcome is a clean separation between product defects and billing-state consequences.

State Guide 6 — Explorer Reading the Product Like a Paid User

A public visitor has learned enough to imagine advanced usage and starts expecting the interface to behave like a paid workspace.

Starting point

They are moving between docs, catalog, and perhaps public Aegis interactions without an active commercial state.

Decision pressure in this scenario

The user’s mental model is ahead of their actual state.

Best route sequence

  1. Re-anchor in docs and billing rather than in imagined workflow steps.
  2. Identify which capabilities are public-learning layers and which require activation.
  3. Choose whether to stay exploratory or activate a trial.
  4. Only then attempt live guidance or deliverable operations.

What to pay attention to

  • The public learning path is intentionally generous but not identical to full operational use.
  • A clear next step is better than forcing a premature one.

If you use the route sequence above, read each page for the category of truth it owns rather than for generic reassurance. This prevents the most common scenario mistake: reaching the correct page but still asking it to answer the previous page’s question.

Common wrong turn

The wrong turn is treating commercial gating as though it invalidates the product’s educational value.

Healthy outcome

A healthy outcome is that the explorer understands the difference between learning mode and operational mode.

State Guide 7 — Trial-to-Paid Conversion Decision

A trial user has seen enough to decide whether the workflow merits paid continuation.

Starting point

They have a trial state, at least one meaningful session, and some sense of what remains locked.

Decision pressure in this scenario

The user wants to decide with evidence rather than momentum or fear of missing out.

Best route sequence

  1. Review the quality of the draft and the usefulness of live Aegis guidance.
  2. Read the plan differences on billing.
  3. Identify the one or two capabilities that truly matter after trial.
  4. Choose the paid path that matches actual workflow needs.

What to pay attention to

  • The right paid choice follows from real use, not just from plan naming.
  • The best conversion decisions are grounded in observed value, not generic preference.

If you use the route sequence above, read each page for the category of truth it owns rather than for generic reassurance. This prevents the most common scenario mistake: reaching the correct page but still asking it to answer the previous page’s question.

Common wrong turn

The wrong turn is choosing a plan before identifying which post-trial workflow really matters.

Healthy outcome

A healthy outcome is a commercially grounded decision that reflects real artifact quality and route behavior.

State Guide 8 — Paid Renewal with New Team Expectations

A renewing paid account now needs to serve more people or more formal review cycles than when it started.

Starting point

The current paid posture works for one user, but the team’s operating needs are changing.

Decision pressure in this scenario

The user must decide whether the current commercial path still matches the real workflow.

Best route sequence

  1. Review how the team currently uses dashboard, Aegis, and deliverables.
  2. Compare the live plan scope to the team’s future usage pattern.
  3. Use version changes and plan chapters to discuss the product honestly.
  4. Decide whether the current plan still fits or whether a broader path is needed.

What to pay attention to

  • Renewal should be tied to workflow fit, not just continuity.
  • A growing team changes the meaning of commercial sufficiency.

If you use the route sequence above, read each page for the category of truth it owns rather than for generic reassurance. This prevents the most common scenario mistake: reaching the correct page but still asking it to answer the previous page’s question.

Common wrong turn

The wrong turn is renewing on autopilot when the team workflow has outgrown the original plan assumptions.

Healthy outcome

A healthy outcome is a plan decision aligned to the current team reality instead of the initial evaluation snapshot.