Operating Frameworks
The PROFIT Score: How to Rank Your DTC Roadmap in 2026
The PROFIT Score ranks a DTC roadmap by scoring every candidate project on six vectors, People, Return, Odds, Fit, Investment, and Time, then multiplying them so the highest score ships first. Time counts as risk rather than cost, so long projects penalize themselves, and a zero on any single vector kills the project outright. The practical cadence is to score 8 to 12 projects per quarter, sort, have the conversation, and re-score every 90 days.
It is the Monday after your quarterly planning offsite. The team came back with twelve priorities. You have five real swings of capacity. Your CFO wants margin recovery. Your CMO wants ad scale. Your Head of Ops wants the warehouse rebuild. As the CEO, you know you can ship maybe four of the twelve well. So which four?
If you are like most operators at this stage, the answer is: badly. The loudest leader wins the argument. The prettiest deck gets greenlit. You fund whatever you happen to be excited about that month. Or — the more sophisticated version — your team draws a 2×2 of "value vs effort," picks the upper-right quadrant, and calls it a day.
None of this scales past $20M ARR. A wasted quarter at $60M ARR is millions of dollars of opportunity cost. You spend six engineering weeks on the wrong project, and meanwhile your top competitor launches the comparison landing page you should have built. By the time you catch up, they have taken 200 basis points of share. The cost of mis-prioritizing is not the failed project. It is everything else you did not do.
The off-the-shelf scoring frameworks do not fit ecom either. RICE — the dominant prioritization model in product teams, short for Reach × Impact × Confidence ÷ Effort — was designed for software. It treats effort as your main constraint and divides by it. In ecom, effort is not the main constraint. Time is. The longer something takes, the more risk piles up: a competitor launches, the season ends, your supplier raises prices, the channel algorithm changes. RICE penalizes long projects because they are expensive. We penalize them because they are dangerous. That single difference reshuffles your stack.
So we built our own. We use it inside Eightx with our $20M-$250M DTC and CPG clients. It is called the PROFIT Score. Six things, multiplied together. The highest score ships first. That is the whole game.
Here is what each letter means, how to score it, and how to actually run this in a Monday leadership meeting at the end of the article. We will walk through one project end-to-end, then look at how a real five-project portfolio sorts.
Key Takeaways
- Score every candidate project on six things — People, Return, Odds, Fit, Investment, and Time — and multiply them. The highest score ships first.
- Time is risk, not cost. Long projects penalize themselves automatically because they expose you to more change.
- Score zero on any one vector and the project dies. A great idea that is anti-strategy is a great idea for someone else.
- The framework rewards throughput. It can underweight your one big strategic bet — handle that with judgment, not by changing scores.
- Score 8 to 12 projects per quarter, sort, have the conversation, re-score every 90 days.
The Six Things You Score
Polarity rule: higher is always better. For all six letters, 0 means "kills the project" and 5 (or 10 for Fit) means "maximally favorable." Even for cost vectors like Investment and People — a high score means cheap and small, not expensive and big. Once you see the polarity, the rest of the framework reads in one pass.
P — People. How much of your team's time will this eat? Smaller is better. 0 = consumes the year, 1 = a quarter, 2 = a month or so, 3 = a couple weeks, 4 = under a week of effort, 5 = trivial. Pick the band that matches your honest estimate of how much focused team-time the project will swallow. A merchandising plan refresh at three people for about a month is "a month or so" of focused effort — that earns a 2.
R — Return. How much contribution margin does this generate over the next twelve months? Not revenue. Margin. 0 = breaks even or worse, 1 = small win (~5% of monthly revenue in 12-mo CM), 2 = ~10%, 3 = ~20%, 4 = ~50%, 5 = 100%+ of monthly revenue. Anchor to your monthly revenue so the bands scale with the brand.
O — Odds. What are the realistic chances the return actually lands? Not whether the project ships — whether the dollars show up. 0 = "won't work," 1 = under 20% odds, 2 = ~20-40%, 3 = ~40-60%, 4 = ~60-80%, 5 = above 80%. A new product launch can ship on time and still miss its CM target by 70%; that is an O of 1 or 2, not a 4.
F — Fit. How well does this advance your stated strategy? Fit runs on a 0-10 scale: 0 = anti-strategy (kills the project), 2 = off-strategy, 3 = tangent, 5 = adjacent, 7 = aligned, 10 = core to this quarter's #1 priority. Fit is double-weighted on purpose because misaligned wins still cost you focus. A great execution of an off-strategy project doesn't make the strategy better — it makes the wrong thing easier to scale.
I — Investment. How much cash does this burn in agency fees, software, contractors, and committed inventory? 0 = over half your monthly revenue, 1 = ~20-50%, 2 = ~5-20%, 3 = ~1-5%, 4 = under 1% of monthly revenue, 5 = $0 (free). The polarity is intentional — small dollar = high score, just like every other vector.
T — Time. How many calendar weeks until it ships? Faster is better. 0 = over a year, 1 = 6 months, 2 = 3 months, 3 = 8 weeks, 4 = 2 weeks, 5 = under a week. We treat time as risk, not cost — explained next.
Why Multiply, Not Add
Score zero on any single vector and the project dies. A great idea that is anti-strategy is not a great idea. It is a great idea for someone else's company. Multiplication kills it for you automatically — no override, no exception, no conditional logic. That is one reason we multiply.
The other reason is amplification. A project that is strong on five things and weak on one should look very different from a project that is mediocre on all six. Multiplication amplifies extremes. Addition smooths them out. We want the amplification.
Why Time Is Risk, Not Cost
This is where RICE breaks for ecom. RICE puts effort in the denominator. Effort and time get treated as costs, and you penalize long projects because they are expensive.
That is not how an operating ecom business actually works. The longer a project runs, the more reality shifts under it. Your biggest competitor launches first. Your CMO accepts another offer. Your supplier raises prices. The platform algorithm changes. A six-month project lives through three earnings cycles, two BFCMs, and at least one major channel disruption.
Time is not a cost. It is a risk. So we put time in as a multiplier alongside everything else. Long projects score lower automatically — not because they are expensive, but because they are dangerous. The fix is to ship faster, not to budget more.
A Project Walked Through
Take a real example: a merchandising plan refresh, where your buying team maps the next two quarters of inventory across categories. Let us score it together.
People (P). Three people, about a month each. Roughly 60 person-days — "a month or so" of focused team time. Score: 2.
Return (R). A good plan adds about $1.25M of contribution margin over the next twelve months. At a $5M-a-month brand, that is roughly 25% of one month's revenue in CM. Score: 3.
Odds (O). You have done seasonal merchandising plans before, and the team knows the playbook. About 80% chance it lands close to plan. Score: 4.
Fit (F). Aligned with strategy. Not the headline initiative, but a meaningful contributor to the year. Score: 7.
Investment (I). About $250k between vendor analysis tools, freelance support, and freight modeling at this scale. Roughly 5% of one month's revenue. Score: 3.
Time (T). Eight weeks to ship the plan. Mid-range. Score: 3.
Multiply: 2 × 3 × 4 × 7 × 3 × 3 = 1,512.
The score is a default, not a verdict. If your gut says fund the slow project, fund it — just make the override conscious. By itself the number means nothing; it only matters compared to your other projects.
For context: most viable projects land between 200 and 2,500. Anything above 1,500 is a strong candidate; below 500 is usually a "no" or a "not yet." The number itself isn't sacred — it's there to make comparison honest.
The Stack Ranking
Here is what happens when you score five projects from the same $5M-a-month brand. First, the inputs and bucket scores side-by-side, so you can see the math.
| Project | P-days | R-CM | O | F | I-$ | T-wks | P, R, O, F, I, T | Score |
|---|---|---|---|---|---|---|---|---|
| Merchandising plan refresh | 60 | $1.25M | 80% | Aligned | $250k | 8 | 2, 3, 4, 7, 3, 3 | 1,512 |
| New comparison landing pages | 30 | $500k | 60% | Adjacent | $40k | 4 | 3, 2, 3, 5, 4, 4 | 1,440 |
| Change to lower-COGS supplier | 40 | $2.5M | 80% | Core | $100k | 24 | 3, 4, 4, 10, 4, 1 | 1,920 |
| Release new product line | 80 | $3M | 40% | Core | $500k | 36 | 2, 4, 2, 10, 3, 1 | 480 |
| Website redesign | 120 | $2M | 40% | Aligned | $300k | 8 | 1, 3, 2, 7, 3, 3 | 378 |
Now sort descending. This is the list you actually take into the room.
| Rank | Project | Score |
|---|---|---|
| 1 | Change to lower-COGS supplier | 1,920 |
| 2 | Merchandising plan refresh | 1,512 |
| 3 | New comparison landing pages | 1,440 |
| 4 | Release new product line | 480 |
| 5 | Website redesign | 378 |
The supplier change wins, even though it takes 24 weeks. At scale, a strong COGS reduction pulls $2.5M of CM from a $100k bet — that is the highest-leverage move on the list, and the math says so. The new product line, despite being the most "exciting" project in the room, lands fourth: it is slow, expensive, and roughly a 40% chance of hitting its CM target. The website redesign is last because it eats 120 person-days for a return the team is not actually confident in.
This is the framework working as designed. Quick high-confidence wins compound. Long strategic bets earn their slot only when the contribution margin is big enough to overpower the time penalty — like the supplier change. If the new product line is genuinely the unlock for the next two years, you fund it anyway, regardless of score. That is judgment, not scoring.
Run It Monday Morning
The framework only earns its keep if you actually run it. Here is the operating ritual we use with our clients.
Block 60 minutes at your weekly leadership meeting.
- First 15 minutes: each leader scores their top 2-3 candidate projects in the Sheet. Don't debate the scoring yet — just get numbers in.
- Next 30 minutes: sort the list. Look at the top 5. For each, ask: "Are we surprised? If yes, why?" Surprises usually mean either the score is wrong or your gut is wrong. Either is useful.
- Last 15 minutes: commit. Pick the 3-5 projects you'll actually staff this quarter. Anything below #5 goes in the parking lot until the next quarter's re-score.
Re-run the exercise quarterly. The scores drift fast — what was an Investment-3 last quarter might be Investment-2 this quarter as your team gets better, prices drop, or AI capability improves.
What This Framework Will Not Do
- It will not pick your strategy. You decide what is "Core." If you cannot state your strategy in one sentence, every project defaults to Adjacent and the framework cannot help you.
- It will not replace judgment on big bets. Sometimes the slow project is still the right one. Override on purpose, not by accident.
- It will not optimize anything for you. You score, you sort, you choose where to draw the line. The math is a discussion-starter, not a verdict.
Run Yours
The live Sheet has the rubric, all 5 example projects pre-filled, and a sort-by-score view. Make a copy, swap your projects in, and you're scoring inside 10 minutes. If your top three projects on the spreadsheet are not your top three on the actual quarterly plan, that gap is the conversation worth having with your leadership team.
Coming Next
Coming next: what changes when your team is using AI seriously. AI doesn't change Return, Odds, or Fit. It compresses three of the six (P, I, T). The stack reshuffles modestly — and predictably. Read Part 2.
Frequently Asked Questions
What is the PROFIT Score?
The PROFIT Score is how Eightx ranks projects for $20M-$250M DTC and CPG operators. Score every candidate on six things — People, Return, Odds, Fit, Investment, and Time — multiply them, and sort highest to lowest. Whatever lands at the top is what you should staff next. A project that fails on any single one of the six dies automatically, because a great idea that is anti-strategy or has no chance of working is a great idea for someone else.
How is this different from RICE?
RICE (Reach × Impact × Confidence ÷ Effort) was built for software product teams. It treats effort as a cost and divides by it, so long projects look expensive. For an operating ecom business at scale, the bigger problem with long projects is not cost — it is risk. The longer a project runs, the more reality changes underneath it: competitors launch, seasons end, suppliers raise prices, channels change their rules. The PROFIT Score puts time in as a multiplier, not a denominator, so long projects penalize themselves automatically. We also double-weight strategic Fit, because the cost of executing the wrong project well is the focus you spent doing it.
What does "Fit" being 0-10 actually mean?
Fit is the only vector on a 0-10 scale because misaligned wins still cost you focus. A great execution of an off-strategy project doesn't make the strategy better — it makes the wrong thing easier to scale. Anti-strategy = 0 (kills the project), off-strategy = 2, tangent = 3, adjacent = 5, aligned = 7, core to this quarter's #1 priority = 10. We weight Fit double on purpose.
How do I actually use this in my company?
Block 60 minutes at your weekly leadership meeting. First 15 minutes: each leader scores their top 2-3 candidate projects in the Sheet without debate. Next 30 minutes: sort the list, look at the top 5, and ask "are we surprised?" — surprises mean either the score is wrong or your gut is wrong, and either is useful. Last 15 minutes: commit to the 3-5 projects you'll staff this quarter. Re-run quarterly because the scores drift fast.