From idea to post
Use this guide when you need the main daily operating loop from dashboard start, review boundary, active offer availability, canonical lane intent, and scheduling through publish and bounded evidence.
This guide explains the practical workflow that sits underneath the daily dashboard start, the posts queue, post detail, and the calendar surface. It is the bridge between strategic intent, next work, queue momentum, and visible execution.
A practical page type for learning how FlywheelBrander thinks or how to make a specific choice.
Returning users should get a daily start, not a fresh orientation problem every time they open the workspace.
- Dashboard is the daily start. It should tell you what matters now, what is stalled, and which surface owns the next bounded move.
- Posts is the queue execution surface. Use it for review, refinement, repair, retirement, and bounded movement on concrete items.
- Calendar is the cadence surface. Use it when ready work exists and the near-term lane still needs trustworthy slots.
- Strategy is for posture refinement and control, not for normal day-to-day queue movement.
- Settings remains setup and control. It should not become the generic destination for normal daily work.
Placeholder for later enrichment
[Illustration placeholder: FlywheelBrander daily operating loop]
Placeholder for later enrichment
[Annotated screenshot placeholder: daily start / top next work surface]
Placeholder for later enrichment
[Illustration placeholder: when to stay in dashboard vs move into posts vs open calendar]
Onboarding establishes first posture and first value. Daily work is different. The question is no longer what the product is. The question is what the right bounded move is now, what it unlocks, and what can safely wait until later.
A new operator should understand what each premium surface owns, what to look at first, and how bounded autonomy stays credible in-product.
- Dashboard is the daily start. It tells you what matters first and which surface owns the next deeper move.
- Calendar owns slotting and near-term cadence. Approval does not automatically mean slot-ready.
- Strategy owns phase, mix, and commercial direction. It is not the daily queue surface.
- Settings owns deliberate control changes. It is where you unblock or reconfigure, not where you run the day.
- Commercial Ops owns live route follow-up, review cadence, and bounded traceability after work is already in motion.
- Posts and Offers stay adjacent execution surfaces, but the five premium control surfaces are the orientation spine for first contact.
Dashboard
Start here when the next question is what matters now and which surface should own the next bounded move.
Calendar
Use this page when the real decision is slotting, cadence coverage, or whether ready work can safely take a publish slot.
Strategy
Use this page when you need to understand phase, mix, and commercial direction rather than daily queue movement.
Settings
Use this page when something must be deliberately changed in connections, posture, access, or reporting controls.
Commercial Ops
Use this page when a live route needs follow-up, review cadence, exception handling, or bounded commercial traceability.
FlywheelBrander should orient quickly without pretending the product is hands-off or simpler than it really is. The right move is to reduce confusion while keeping proof, policy, and commercial bounds visible when they matter.
The five premium surfaces should behave like one operator workspace with distinct decision roles, not like separate feature silos.
- Dashboard is the daily start. Use it to understand what matters first and which surface owns the next bounded move.
- Calendar is the cadence surface. Use it when slotting, near-term lane coverage, or schedule-ready truth is the real decision.
- Strategy is the doctrine surface. Use it when phase, mix, lane semantics, or commercial direction needs interpretation or adjustment.
- Settings is the control surface. Use it for connections, persisted workspace posture, billing/access posture, and deliberate operator configuration.
- Commercial Ops is the follow-up surface. Use it for route health, review cadence, exception handling, and bounded commercial traceability.
- Act now, keep moving, monitor, and deep context should not carry equal visual weight. The product should show the bounded next move before it opens the full governance stack.
Placeholder for later enrichment
[Illustration placeholder: operator workspace map across Dashboard, Calendar, Strategy, Settings, and Commercial Ops]
Placeholder for later enrichment
[Annotated screenshot placeholder: act now vs keep moving vs monitor vs deep context across the premium workspace]
FlywheelBrander should reduce cognitive load by improving hierarchy and disclosure, not by flattening real posture differences. The right move is to show the most important truth first and keep deeper bounded context one deliberate step away.
The product is meant to move through a bounded sequence of actions, not a random pile of disconnected screens.
1. Generate or top up
Move from ideas to a healthy queue by generating a full batch when the queue is thin or a smaller top-up when the machine already has momentum.
2. Review the drafts
Use review to refine, approve, or retire work before it creates scheduling pressure too early.
3. Align the commercial object
Check whether the draft is linked to the right active offer and whether the current phase supports the motion you are asking it to carry.
4. Schedule or publish
Move the post forward when readiness, workspace policy, and channel truth all support the next execution step.
5. Verify and refresh
Once the post is live, the next job is no longer draft creation. It becomes delivery verification and bounded evidence refresh where that truth exists.
Active offer availability should reduce avoidable blockers without forcing every post into a direct commercial lane.
- Active offer availability means the current phase has a real commercial object ready when a post genuinely needs one.
- Commercial alignment is required for direct promotion and conversion pressure, but it is optional for signal-first value, build-in-public, and social-proof work.
- When no active phase offer exists, the blocker is real. The smallest truthful recovery is to activate the right offer or keep the item non-commercial instead of forcing promo pressure.
- Approved posts can still stay out of calendar when offer truth, workspace posture, or lane truth says the next move is not scheduling yet.
- A healthy workspace should encounter fewer avoidable offer-gap blockers because live offer context and post intent stay closer together.
FlywheelBrander should not invent a commercial object to rescue a post. It should show the smallest truthful recovery: activate the right offer, realign the post, or keep the item signal-first.
Placeholder for later enrichment
[Illustration placeholder: commercial alignment and active offer availability]
Placeholder for later enrichment
[Annotated screenshot placeholder: approved post blocked by missing offer]
Placeholder for later enrichment
[Example placeholder: attract-phase item recovered by activating the right offer]
Placeholder for later enrichment
[Example placeholder: signal-first post that correctly stays non-commercial]
The review boundary should create usable approved inventory, not just clear blocked drafts.
- Review-ready inventory is not the same as all drafts. It is the smaller set where approval is now the real next decision.
- Approved inventory means the post has crossed review and can now be reused as real execution inventory across queue, post detail, and calendar.
- Approved is still not the same as schedule-ready. Some approved posts still need posture, commercial, freshness, or channel truth to be rechecked before calendar should trust them.
- Schedule-ready inventory is the subset of approved work that can truthfully take a slot right now under current cadence and workspace posture.
- When schedule-ready inventory exists, the next best move often becomes calendar. When it does not, posts or post detail still owns the next bounded move.
Approval should leave the operator with stronger, reusable inventory. If approval only changes a label without making the next stage clearer, the workflow is still too theoretical.
Placeholder for later enrichment
[Illustration placeholder: review boundary in FlywheelBrander]
Placeholder for later enrichment
[Annotated screenshot placeholder: approved inventory vs schedule-ready inventory]
Placeholder for later enrichment
[Example placeholder: one review away from movement]
Placeholder for later enrichment
[Annotated screenshot placeholder: queue-to-calendar conversion]
posts/[id] should turn one item into a bounded progression decision, not a dead-end editor.
- Why this exact post matters now, not just what it contains.
- Whether the item is blocked, weak, review-pending, schedule-ready, already carrying cadence, or effectively out of lane.
- What the smallest bounded move is from here and what that move will unlock next.
- Whether the item should stay in post detail, return to queue context, or move into calendar for a slot decision.
- How item-local truth stays local so it does not compete with higher-level workspace posture.
- Stay in post detail when the next move is still editorial, local blocker repair, or a deliberate approve / refine / retire decision.
- Return to queue when the item no longer outranks broader review pressure and needs comparison against the rest of the lane.
- Move to calendar when the item is already clean enough for scheduling and the next decision is now about cadence, not copy.
- Treat owned and asset notes as item-local support truth, not as replacement for post-level readiness.
- Use the surface to finish one bounded move, then step back out into queue or calendar deliberately.
A post can be schedule-ready without calendar being the most urgent next move. The premium interpretation is: can this item safely take a slot, and does the current cadence posture make calendar the right next surface now?
Placeholder for later enrichment
[Illustration placeholder: item progression in FlywheelBrander]
Placeholder for later enrichment
[Annotated screenshot placeholder: posts/[id] next move and readiness explanation]
Placeholder for later enrichment
[Annotated screenshot placeholder: post detail to calendar handoff]
Placeholder for later enrichment
[Illustration placeholder: when a post stays local vs returns to queue vs moves to calendar]
Future work should bias toward the canonical brand lane without rewriting items that are truthfully local to proof-lane execution.
- Canonical brand lane describes where similar future work should prefer to land by workspace policy when live channel fit allows it.
- Item-local proof lane describes where this specific post is currently tied for real execution, certification, or proof-oriented distribution.
- The system can rebalance future or movable work toward the canonical brand lane when that lane is both policy-correct and practically live.
- It should not silently relabel historical or item-local proof-lane work as canonical just to make the lane picture look cleaner.
- When only proof-lane execution is live, the product should keep that local truth while still preserving the broader canonical intent for future work.
Premium lane behavior means keeping the local item honest while gradually pulling future and movable work back toward the canonical brand lane whenever that route is truly available.
Placeholder for later enrichment
[Annotated screenshot placeholder: canonical brand lane vs item-local proof lane]
Placeholder for later enrichment
[Example placeholder: future work rebalanced toward canonical brand lane]
Placeholder for later enrichment
[Illustration placeholder: how FlywheelBrander decides lane intent vs local lane repair]
Queue health and draft aging are governed by explicit policy, not intuition alone.
- A full initial batch targets 30 drafts when the queue needs to be established from thin inventory.
- A top-up adds 12 drafts when the machine needs fresh inventory without resetting the whole queue.
- A healthy queue floor is 12 drafts, while the broader target queue size remains 30.
- Drafts start to feel stale after 7 days, near-retirement pressure appears after 14 days, and retirement pressure appears after 21 days.
- Publish-window urgency increases once a scheduled item moves inside a 36-hour window.
These are not vanity thresholds. They are there to keep the queue usable, to stop stale drafts from clogging attention, and to distinguish between healthy backlog and disguised drag.
Queue momentum is about where motion is building, stalling, or waiting on the wrong kind of work.
- Review-heavy means the machine has inventory, but too much of it still needs operator judgment before cadence can benefit.
- Blocked momentum means failures, channel truth, workspace policy, or commercial gaps are constraining movement more than lack of content.
- Ready-to-convert momentum means there is already clean work that should be slotted before more drafts are created.
- Thin momentum means the queue is running low on usable inventory and a bounded top-up is becoming the right move.
- Aging momentum means stale drafts are starting to absorb attention that should belong to fresher work.
- Move the strongest review items forward before you generate more work into the same queue pressure.
- Repair explicit blockers before trying to hide them under new scheduling or new batch volume.
- Use calendar to convert already-ready work into near-term cadence when slots are the real gap.
- Retire or refresh aging drafts instead of letting stale inventory quietly become the default attention sink.
- If posture itself is wrong, use re-entry or control surfaces deliberately instead of treating every daily problem like a strategy rewrite.
Placeholder for later enrichment
[Annotated screenshot placeholder: queue momentum readout]
Placeholder for later enrichment
[Example placeholder: review-heavy queue with clear next action]
Placeholder for later enrichment
[Example placeholder: blocked owned-distribution work with useful alternative path]
Placeholder for later enrichment
[Example placeholder: stale queue with momentum recovery]
Assets belong in the workflow, but they do not universally decide whether a post is allowed to move.
- Text-first posture means assets are optional for readiness and should not block execution by default.
- Supporting-assets, carousel-friendly, and video-forward postures increase the relevance of assets without implying that every post must become media-heavy.
- The system can recommend supporting images, quote cards, carousels, or video concepts while still allowing text-only execution where that is the cleaner move.
- Rendered video output is still outside this workflow, even when video concepts and scripts are present.
Placeholder for later enrichment
[Annotated screenshot placeholder: Asset review lifecycle in post detail]
The main workflow should make the next move obvious instead of leaving the operator to infer it.
- Generate a full batch when the queue is thin enough that the machine lacks working inventory.
- Top up when the queue still has momentum but not enough fresh drafts to stay healthy.
- Retire or restore aging drafts instead of letting stale inventory silently absorb attention.
- Fix commercial or channel blockers before trying to brute-force scheduling.
- Once a post is published, switch attention to delivery and bounded evidence instead of repeating earlier draft work.
- Review now means operator judgment is still the tightest useful unlock.
- Schedule now means ready work already exists and cadence is now the main constraint.
- Repair blocker means the queue is being slowed by concrete blocker evidence, not by lack of new ideas.
- Preserve momentum means a bounded top-up matters more than extra refinement because inventory itself is getting thin.
- Hold steady means the product should not force a bigger intervention when calm execution is still the truthful move.
The product does not fully automate daily prioritization into a self-driving workflow. It still expects operator judgment around approvals, retirements, commercial alignment, and slot choice. The goal is clearer next work, not pretending that all editorial trade-offs should happen invisibly.
Placeholder for later enrichment
[Illustration placeholder: Main workflow from idea queue to post execution]
Placeholder for later enrichment
[Example placeholder: Thought leadership workflow from idea to owned distribution]
Workspace setup and first 3 recommended moves
Use this guide when you want to understand how FlywheelBrander narrows intent, drafts the first workspace posture, handles connection readiness honestly, and chooses the first 3 moves without front-loading advanced setup.
Publishing readiness and review
Use this reference when a post looks blocked, commercially unclear, approved-but-unclear, stale, missed, or unclear in review and scheduling surfaces.
Publishing readiness and review
Use this reference when a post looks blocked, commercially unclear, approved-but-unclear, stale, missed, or unclear in review and scheduling surfaces.
CMS vs Newsletter
Use this guide when a post looks like an owned candidate and you need to choose the right lane with confidence.