Recruit: Recruit people running a current campaign, channel or content workflow—not people reacting to an idea pitch.
Guardrail: Measure completed workflow, time saved or a real distribution commitment; do not treat clicks or compliments as proof.
01 · Channel publishing & distribution
Write the problem hypothesis
For [publisher], distributing [content] to [channel] requires [manual handoff or reformatting], causing [delay, inconsistency or missed reach].
You can name one user, one situation and one measurable consequence without proposing a feature.02 · EVIDENCE INTERVIEW
Interview five marketers or growth operators
Which channels are part of the real campaign?
What must change for each channel?
Where do credentials or approvals enter?
How is failure detected and retried?
Which publishing result matters beyond clicks?
At least three people independently describe the same painful workflow with recent examples.03 · MINIMUM TEST
Run the smallest experiment
Operate one cross-channel post manually or through a narrow connector, including approval and failure recovery, for three real publishing cycles.
The publisher repeats the workflow across three cycles and keeps the connection active because it reduces measurable handoff work.Measure completed workflow, time saved or a real distribution commitment; do not treat clicks or compliments as proof.04 · DECISION GATE
Make a build decision
Build: repeated pain and active commitment
Narrow: pain is real but the audience or job differs
Stop: weak frequency or no behavioral proof
Do not let GitHub engagement replace direct validation.
Why this brief exists
Information has value only when it changes action. This page turns one public signal into a bounded validation exercise. It is a research aid, not proof of demand, investment advice or a product recommendation.