How I rebuilt my SaaS dashboard to speak the "language" of my users (The Spreadsheet Killer)
Hi Indie Hackers! 👋
I’m the founder of Wheelytics, a tracking tool for options traders using the "Wheel Strategy" (Covered Calls/CSPs). Today, I officially launched a massive update that changed the core philosophy of the product.
The Problem: Being a "Trade Log" wasn't enough.
For a long time, Wheelytics was essentially a beautiful version of a trade journal. It listed transactions, calculated basic P&L, and kept things organized.
But I realized something by lurking in subreddits like r/thetagang: Traders don't think in "trades"—they think in "cycles."
When a trader sells a Put, gets assigned, sells Calls, and then rolls those calls for weeks—that’s not 10 separate events. It’s one single, continuous story with an adjusted cost basis. Most tools (and brokers) break this story into pieces, leaving traders to fix it in "Spreadsheet Hell."
The Solution: Moving to a Cycle-Oriented Model
I decided to stop being a general trade tracker and rebuilt the dashboard to understand the The Wheel Strategy natively.
What we changed:
Native Cycle Stitching: The system now automatically links rolls, assignments, and expirations into one "Cycle" card.
True Adjusted Cost Basis: We moved away from simple P&L to a model that tracks how every premium collected lowers the cost basis of the underlying stock.
High-Density UI: I realized traders hate whitespace. They want data. I tightened the UI, removed redundant descriptions, and replaced noise with "Action Required" status tags.
The "Aha!" Moment
The best feedback I got during beta was: "Finally, a tool that speaks Wheel fluently." By leaning into the niche slang (like using "21 DTE" for trial periods) and focusing on the specific mechanics of one strategy, the product went from "nice to have" to "essential."
My Lesson for IH:
If you are building for a niche, don't be afraid to be too specific. General tools are easy to ignore. Tools that understand the "unwritten rules" of a community are the ones that stick.
I’d love to hear your thoughts on radical dashboard redesigns! Have you ever had to move from a "list view" to a more "complex logic" view for your users?
