FlywheelBrander
Guide6 min readGuides
DocsGuides

How FlywheelBrander decides

Understand how FlywheelBrander combines phase, offer linkage, workspace posture, post shape, and measurement reality into an owned-lane recommendation.

This guide explains the actual reasoning layers behind the recommendation. It is useful when the operator wants to understand why CMS, newsletter, both, or wait is the right posture now.

A practical page type for learning how FlywheelBrander thinks or how to make a specific choice.

The decision layers

The recommendation is grounded in a bounded sequence of product truths.

1. Phase context

The active phase changes what good owned distribution looks like before the product even looks at the specific post.

2. Offer linkage

Live offer linkage strengthens direct delivery cases and protects against Convert-mode publishing without a real commercial object.

3. Post shape

Category and format influence whether the post behaves more like durable education, proof, or directed promotion.

4. Workspace posture

Publishing priority and commercial mode shift the system toward thought leadership, balanced growth, or offer-linked distribution.

5. Metric contract

The system checks what the lane can honestly measure so the recommendation stays useful instead of theatrically precise.

Why wait can be the correct recommendation

A premium recommendation system should be able to say not yet with confidence.

Waiting is not inactivity

When FlywheelBrander recommends keeping a post social-first, it is protecting against a weak owned move. That is a quality decision, not a missing feature.

Typical reasons the system waits

The most common reasons are weak offer linkage, a phase mismatch, or a post that does not yet justify a clear owned lane. Waiting is often better than creating an owned artifact that the operator does not truly need.

Where the recommendation shows up in the product

The docs and the UI should tell the same story.

In /posts

The operator sees owned-lane fit, owned-lane state, and the next best action as part of the main post workflow.

In /posts/[id]

The operator can move an owned draft through review, approval, publish, delivery verification, and metric refresh actions.

In /strategy

The operator sees the control-surface explanation for why CMS, newsletter, or wait is the better posture in the current phase.

Visual support for the decision model

These placeholders keep the page ready for later explanation assets.

Placeholder for later enrichment

[Illustration placeholder: How phase + offer + metric contract affect recommendation]

Placeholder for later enrichment

[Annotated screenshot placeholder: /posts/[id] owned distribution panel]