Question 1

What does the Stack Builder give me?

Accepted Answer

Two possible routes — Stack A and Stack B — built from your answers. Stack A is the highest-scoring route for your goal, obstacle, and stage. Stack B is a meaningfully different way to reach the same outcome. Each route is a short, ordered plan of three to five steps, with no more than three steps active at once and the rest queued.

Question 2

How is each route chosen?

Accepted Answer

By a fixed, versioned scoring method that runs on our servers — never in your browser. Your goal, main obstacle, readiness, stage, capacity, market, and history each contribute a set number of points, and the same answers always produce the same result. The weights are set and reviewed by our team; they cannot be edited from your account.

Question 3

Why do I see two routes instead of one answer?

Accepted Answer

Because there is rarely only one sensible way forward. If the two routes score within eight points of each other, we mark it a close fit, pick no winner for you, and offer a single deciding question to help you choose. If Stack A leads by more than eight points, we label it the recommended route and Stack B the alternate.

Question 4

Does a route only include tools on my plan?

Accepted Answer

Yes. Every step in both routes is something your current plan entitles you to run. If a better step exists on a plan you do not have, we may note the publicly listed difference, but we never place a step you cannot access into your route, never unlock anything, and never mention private or internal tiers.

Question 5

Can I see why a route was recommended?

Accepted Answer

Yes. The comparison page includes a plain-language explanation of why each route appeared, when it works best, its advantage, its tradeoff, and how its fit score was reached. Nothing about the scoring is hidden from you.

Question 6

Are the recommendations a promise of results?

Accepted Answer

No. Everything the Stack Builder produces is a decision-support estimate. It never predicts revenue, leads, rankings, or any other outcome, and no route guarantees growth. Results depend on your execution and on factors outside anyone's control.

Question 7

What counts as progress on my stack?

Accepted Answer

Only work you actually completed. Opening a tool never counts. A step is marked finished when you confirm the action is done, and a step that depends on a report can only be credited when a real report exists in your account — ticking a box on screen can never stand in for a finished run.

Question 8

What do the step statuses mean?

Accepted Answer

Each step is one of: not started, started, tool run completed, action started, action completed, outcome evidence added, blocked, skipped (with your reason), or already covered by previous work. Steps already covered by something you finished earlier are marked as such instead of making you repeat them.

Question 9

Where does my progress live?

Accepted Answer

On your My Current Stack page. It shows your chosen route, your goal and 90-day target, up to three active steps, what is queued, what is done, anything blocked with what to do next, and progress against the measures you chose when you selected the route.

Question 10

What if I get stuck on a step?

Accepted Answer

Mark the step blocked and say why. The page records the blocker, shows resolution instructions, and your blocker is visible to the support team so a person can help. A blocked step pauses nothing else — your other active steps keep moving.

Question 11

What is a reassessment?

Accepted Answer

A short check-in of five to seven questions — never a full restart — offered when something material changes: a major step is completed, roughly 30 days have passed, your goal, offer, market, or plan changes, or you ask for one. The review first decides whether to keep, advance, replace, or pause your stack, and only then offers two updated routes. Your original routes and progress are kept permanently.

Question 12

What happens if I change my plan?

Accepted Answer

Your finished work is never deleted. Steps that require tools outside your new plan can no longer be launched, and where a substitute exists on your current plan we offer it. Nothing about your stack changes until you confirm it.

Question 13

What does it mean when a step's tool run can't be matched?

Accepted Answer

It means our records cannot confirm a completed run for that step's tool in your account — for example the run failed, was abandoned, expired, or belongs to a different niche than the step expects. When that happens the step is not credited as completed, and the page tells you exactly what is missing.

Question 14

Will an unmatched run block my whole stack?

Accepted Answer

No. Only that step is affected. It stays in its current state with a clear explanation and the first action to resolve it — usually re-running the tool with the required inputs or linking the correct existing report. Your other steps are untouched.

Question 15

Can I just mark the step done myself?

Accepted Answer

You can record that you started or completed the real-world action, but a step whose purpose is a finished report is only credited when the report exists in your account. This keeps your progress record trustworthy — and it is the same record a reviewer sees if you ever ask for help.

Question 16

What if a report exists but isn't linked to my step?

Accepted Answer

You can link it yourself from the step. Completed QuickScan, Strategic Report, and other eligible reports in your account can be attached as evidence, and a step is only credited when the linked report matches what the step requires.

Question 17

Who can see my stack and progress?

Accepted Answer

You, and a small number of specifically authorized staff who use an internal read-only oversight view. They can add notes, request missing information, or start an assisted review — but they can never silently rewrite your history. Every action is recorded in an audit trail.

Two routes. One honest record of progress.

The two-route recommendation

How progress is tracked

When a tool run can't be matched