Arceon Decision Tool · ARC-GNG-001

Go / No-Go Decision

Decision answered: Based on all evidence collected, should I build this opportunity now, gather more evidence, pivot, or stop?

This is the final decision point before committing significant resources. Use it after the Five-Signal Demand Check, Opportunity Scorecard, and Validation Playbook.

Outcome: 🟢 Go, 🟡 Gather More Evidence, 🟠 Pivot, or 🔴 No-Go.

Decision Intent

Decision: Should this opportunity move from validation into build planning?
Target user: Independent builders who have completed the demand check, scorecard, and validation playbook.
Success: The user makes a clear evidence-based decision instead of drifting into premature build mode.
Relationship: This consolidates prior Arceon outputs into one final resource-commitment decision.

Inputs You Need Before Using This

Five-Signal Demand Check result: Continue Validation, Narrow, Pivot, or Reject.
Opportunity Scorecard result: Pursue, Proceed Carefully, Rework, or Pass.
Validation Playbook evidence: customer research, demand test, pricing validation, competitor review, success criteria, and stop/pivot criteria.
Your constraints: available time, budget, skill fit, maintenance capacity, and risk tolerance.

Step 1 — Summarize the Evidence

Create a short evidence brief before deciding.

What demand signal was strongest?
What opportunity score was strongest?
What validation evidence was strongest?
What evidence was weakest or missing?
What would make this fail?

Output: a one-page evidence summary.

Step 2 — Check the Evidence Quality

Good decisions depend on evidence quality, not confidence alone.

Strong evidence: real user actions, paid signals, repeated complaints, specific interviews, observable behavior.
Medium evidence: credible research, repeated online discussions, competitor patterns, early waitlist or reply signals.
Weak evidence: compliments, vague interest, personal excitement, trend articles, AI-generated assumptions.

Rule: do not choose Go if the strongest evidence is mostly weak.

Step 3 — Apply the Decision Rules

Use the prior tool outputs together. Do not let one positive score override major evidence gaps.

Prior results	Typical recommendation	Reason
Demand Check: Continue Validation + Scorecard: Pursue + Playbook: Proceed	🟢 Go	Evidence supports moving into build planning.
Scorecard: Proceed Carefully or Playbook: Proceed Carefully	🟡 Gather More Evidence	The opportunity may work, but the weakest assumption needs one more test.
Demand Check: Narrow/Pivot, Scorecard: Rework, or Playbook: Pivot	🟠 Pivot	The problem may be real, but the current version is not strong enough.
Demand Check: Reject, Scorecard: Pass, or Playbook: Stop	🔴 No-Go	Continuing would likely waste time, money, or momentum.

No-Go Overrides

Choose No-Go even if some signals look positive when any of these are true:

Users compliment the idea but do not take action.
Monetization depends on hidden bias or trust damage.
Maintenance burden is clearly unsustainable.
The opportunity depends only on search traffic with no repeat value.
You cannot identify a specific user and decision.
The strongest evidence is your own enthusiasm.

Final Decision Table

Decision	Use this when…	Commitment level	Next action
🟢 Go	Demand, opportunity quality, and validation evidence are strong enough to justify a focused build.	Commit to a limited build roadmap.	Define MVP scope, success metrics, maintenance plan, and first release.
🟡 Gather More Evidence	There is promise, but one critical assumption remains untested.	Do not build yet.	Run one targeted validation test.
🟠 Pivot	The problem is real, but the user, format, scope, or monetization model needs change.	Commit to redesign, not build.	Revise the opportunity and repeat the scorecard/playbook.
🔴 No-Go	Evidence is weak, risk is high, trust is compromised, or the opportunity does not fit.	Stop.	Record the lesson and evaluate another opportunity.

Step 4 — Write the Decision Record

Before acting, write a short decision record:

Final decision.
Evidence used.
Strongest reason for the decision.
Strongest counterargument.
Main risk.
Next action and review date.

This protects you from changing the story later because you became attached to the idea.

Your Recommended Next Step

🟢 Go: Next, create a focused Build Roadmap with MVP scope, success metrics, and maintenance plan.
🟡 Gather More Evidence: Return to the Validation Playbook and run one targeted test against the weakest assumption.
🟠 Pivot: Return to the Opportunity Scorecard after changing the user, format, scope, or monetization model.
🔴 No-Go: Stop. Return to the Business Model ADA library and compare another opportunity or model.

Decision Network

Read before this: Validation Playbook
Earlier step: Opportunity Scorecard
Earlier validation: Five-Signal Demand Check
Original business-model decision: Your selected Business Model ADA.
Compare models: Return to the Decision Assets library if the final decision points away from the current model.
Next decision: Build Roadmap after the validation journey produces enough evidence to justify building.

Your selected Business Model ADA: Continue with the ADA that brought you here, or compare the full Business Model library before using this tool:

Complete the Decision Intelligence Workflow

The goal is not only to read a Decision Asset. The goal is to leave with a structured Arceon Decision Record.

Open the Decision Record Use the Validation Worksheet Pack Open the Business Model Comparison Matrix View the Worked Example

Help improve Arceon: If this page helped, confused you, or left a decision unanswered, share practical feedback.