Your most profitable product might not actually be your most profitable product. Sounds contradic...Your most profitable product might not actually be your most profitable product. Sounds contradic...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Your most profitable product might not actually be your most profitable product.
Sounds contradictory?
It can happen when a business allocates shared costs incorrectly.
Imagine a company sells two products:
Product A
Revenue: $200K
Direct costs: $120K
Gross profit: $80K
Product B
Revenue: $150K
Direct costs: $90K
Gross profit: $60K
At first glance, Product A looks more profitable.
But then the business allocates:
warehouse costs
customer support
marketing
software
management salaries
If those costs are simply divided evenly across products, the profitability picture can change significantly.
And that's where cost allocation becomes important.
The question isn't just:
“How much did this product make?”
It's:
“Which costs were actually caused by this product?”
Some costs are directly traceable.
Others are shared.
And some allocation methods can make a product look better or worse simply because of how the costs were assigned.
This matters when deciding:
→ Which products to keep or discontinue
→ Where to allocate marketing budget
→ Which customers deserve more resources
→ Whether a new product is actually attractive
→ Where the business should invest its limited capacity
A misleading profitability report doesn't necessarily contain incorrect numbers.
The numbers can be accurate.
The problem can be the logic behind how they're connected.
That's why good financial analysis isn't just about calculating the numbers.
It's also about asking:
“Does this calculation reflect how the business actually works?”
Because sometimes, the biggest financial insight isn't hidden in the numbers.
It's hidden in the assumptions behind them.
How does your business decide which shared costs belong to each product or customer?
New case study just dropped 💙 EvenUp — an expense-splitting app design
Ever been the one who remembers who paid for what? 💸 That's the problem EvenUp was designed to solve — because splitting costs with friends was never really about math. It was about the awkward conversation after.
Full UI/UX case study includes:
✅ User research & personas
✅ User flow mapping
✅ Complete design system
✅ Full UI — light & dark mode
✅ Edge cases & error states
✅ Interactive prototype
Full case study on Behance — link in bio ⬆️
I’ve been razzmatazzing and flibbertigibbeting with Claude Code and somehow ended up with a new yels.dev.
It finally feels like me: simple on the surface, slightly complicated underneath, and very much alive.
You can see who I am, what I do, the work behind Herodot, RaptorLabs, CyberLink Security and Solmint, plus a selection of projects I’ve built across AI, cybersecurity, Web3, product systems, education, archives, and experimental digital spaces.
The simple-on-the-surface, layered-underneath idea comes through so clearly in the presentation. I especially like how the project archive turns the site into something to explore rather than just a résumé of links.