---
name: traction-channel-prioritization
description: Systematically identify and test your highest-potential traction channels using the bullseye framework. Use when the user asks which traction channel to test, mentions the bullseye framework, customer acquisition, channel prioritization, or the 19 traction channels.
triggers:
  - "traction channels"
  - "bullseye framework"
  - "channel prioritization"
  - "customer acquisition"
  - "traction testing"
  - "19 traction channels"
disable-model-invocation: false
title: traction-channel-prioritization
canonical_url: https://skilld.dev/gh/salikshah/startup-agent-skills/traction-channel-prioritization
last_updated: 2026-10-29T10:46:09.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [evals/evals.json](https://skilld.dev/api/skills-raw/salikshah/startup-agent-skills/traction-channel-prioritization/evals/evals.json).
>
> If the user asked to install this Skill, run `npx skilld install salikshah/startup-agent-skills/traction-channel-prioritization`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/traction-channel-prioritization`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/salikshah/startup-agent-skills/traction-channel-prioritization) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/traction-channel-prioritization`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/traction-channel-prioritization --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/traction-channel-prioritization --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Traction Channel Prioritization

## Intent
Use Gabriel Weinberg's Traction bullseye framework to systematically identify, prioritize, and test the most promising of 19 traction channels until you find one that drives significant growth.

## Inputs
- Product or service with a clear value proposition
- Target customer profile (demographics, behaviors, where they congregate)
- Budget and timeline for traction testing
- Existing analytics and customer acquisition data
- Team capabilities (content, PR, sales, engineering)

## Process (SOP)
1. Step 1: Brainstorm all 19 traction channels — viral marketing, PR, unconventional PR, SEM, SEO, content marketing, email marketing, engineering as marketing, targeting blogs, business development, direct sales, affiliate programs, existing platforms, trade shows, offline events, speaking engagements, community building, social and display ads, and offline ads.
2. Step 2: For each channel, estimate three variables based on research: potential reach (how many target customers it touches), cost to test, and expected conversion rate.
3. Step 3: Place each channel into one of three bullseye rings: inner ring (top 3-5 most promising), middle ring (worth testing later), outer ring (not viable for your situation).
4. Step 4: Select one inner-ring channel as your primary focus — do not test multiple channels simultaneously; you need focus to get signal.
5. Step 5: Design a low-cost, fast experiment for the primary channel — define the hypothesis, the minimum success metric, and the experiment budget.
6. Step 6: Run the experiment within 2-4 weeks — generate at least 100 data points (visitors, leads, or customers) to evaluate the channel.
7. Step 7: Analyze results against three criteria: customer acquisition cost (CAC), scalability (can it grow 10x?), and sustainability (does it compound or plateau?).
8. Step 8: If the channel fails the criteria, return to the outer ring, select the next most promising channel, and repeat the experiment.
9. Step 9: When a channel passes all three criteria, pull the bullseye — invest aggressively and scale it until it saturates before diversifying.
10. Step 10: Document every experiment result to build an institutional knowledge base of what works and does not work for your specific product-market combination.

## Outputs
- A completed 19-channel bullseye worksheet with ring assignments
- Experiment log with results for each channel tested
- A validated primary traction channel with CAC and scale data
- A prioritized testing queue for future channels

## Evidence
Source: "Traction" by Gabriel Weinberg & Justin Mares. Key concepts: 19 traction channels, bullseye framework (three rings), channel prioritization criteria (CAC, scalability, sustainability), rapid low-cost testing, engineering as marketing, pull the bullseye principle.

## Examples
A B2B analytics startup tests three channels: content marketing (CAC $45, scalable, compounding), LinkedIn ads (CAC $180, limited scale), trade shows (CAC $500+, not repeatable). They pull the bullseye on content marketing, publish 4 articles/month for 6 months, and grow to 2,000 signups/month with CAC trending downward.

## Metrics
- Number of channels tested within budget and timeline
- CAC per validated channel
- Channel scalability assessment (can it grow 10x current volume?)
- Time from first experiment to validated primary channel
- Customer volume generated by the primary channel month-over-month

## Anti-Patterns
- Testing 3+ channels simultaneously — you will not get clean signal on any of them
- Falling in love with a channel because it is trendy when your customers are elsewhere
- Ignoring channels that seem unsexy (email, blogs, targeting blogs) — often the highest-ROI channels are the least glamorous
- Pulling the bullseye before reaching statistical significance — 10 data points is not a pattern
- Abandoning a channel after one failed experiment — test variations before declaring a channel dead
- Choosing channels from competitor behavior instead of customer research
