Aurics.AI
← Back to Portfolio & Studio
Shipped · Open source

GTM Decision Engine

A portable decision system that makes criteria, evidence, tradeoffs, and human accountability inspectable.

High-stakes decisions need more than a winning score. Decision Engine keeps the criteria, priorities, evidence, and tradeoffs together - and preserves who made the final call and why. Built from a GTM positioning workflow, it also supports decisions such as vendor selection without requiring marketing-specific setup.

Try GTM Decision Engine View source on GitHub

How it works

  1. 1

    Frame the decision and alternatives.

  2. 2

    Define criteria, weights, and optional Must meet thresholds.

  3. 3

    Score each option and attach rationale, references, and uncertainty.

  4. 4

    Review the calculated comparison and record the human decision.

  5. 5

    Save locally or download a backup and readable Markdown report.

What runs today

  • One editable comparison matrix.
  • Editable criteria, descriptions, weights, options, and scores.
  • Criterion-level Must meet thresholds determine eligibility.
  • Recommendation drafted for one complete eligible leader.
  • Final output: named human decision with rationale and provenance.

Human-Engine boundary

Human responsibilities

Own criteria, evidence judgment, eligibility requirements, accepted tradeoffs, and the final call.

Engine responsibilities

Calculates, blocks false leaders, applies eligibility rules, prepares a deterministic recommendation, persists records, and invalidates stale confirmations.

Positioning example for reference

The tool includes the ten-criterion positioning example used to determine company strategy and product roadmap as an editable starting point. Ten criteria, three options, and a 150-point maximum are properties of that example - not requirements or limits of the Decision Engine.

That example is the instrument behind real calls: the positioning that scored 90%, and the AEO-first pivot that scored 87% and moved roughly three months ahead of the market.

Browser-based operation

  • Local drafts, saved checkpoints, and prior-draft recovery.
  • Lossless backup/import and readable Markdown reports.
  • Optional MOS (Messaging Operating System) handoff after a current confirmed decision.

Safeguards

  • It does not approve messaging, claims, proof, or generation. Development of those remains with the Messaging Operating System (MOS).
  • Incomplete comparisons produce no unique recommendation.
  • Blank scores remain unknown rather than becoming zero.
  • Comparison or decision edits invalidate earlier confirmation.

Portability

Decision Record

JSON supports restoration and continued editing; Markdown is for reading and sharing.

MOS Alignment Handoff

Use is optional. It is provided as an example of how the Aurics.AI GTM System works across nodes.

Possible future directions

Not implemented today
  • AI research support - probabilistic inputs alongside the deterministic calculations used today.
  • Operational Messaging Operating System integration beyond the optional alignment handoff.

Further Reading

FAQ

Is this limited to GTM?
No. This can be used for any business decision with multiple stakeholders and paths of action, and varying criteria. GTM decisions also work without MOS setup. MOS is an optional downstream handoff after a current confirmed decision.
How many criteria should I use?
As they apply to your situation. Criteria, weights, options, and scores are editable.
Can I move a decision between devices?
Yes, using JSON backup/import.
Does it perform AI research?
No. Current recommendations use deterministic calculations to assess human-entered information. AI research support is a possible future direction.