We built Trackly to kill the manual "Daily Standup" chaos for SaaS teams. Thoughts on our approach? 🚀
Hey SaaS Makers! 👋
We all know the pain of keeping a product team aligned. While there are a million task managers out there, we noticed a major bottleneck: teams waste a huge chunk of time just doing manual check-ins, status updates, and chasing people down for standups.
To solve this friction within our own workflow, our team built Trackly.
Instead of making engineers fill out manual reports or sit through long sync meetings, Trackly automatically tracks team progress, streamlines standups, and gives project managers a real-time, bird’s-eye view of everything without micro-managing anyone.
We’ve just launched the core product and are officially Building in Public.
Since this group is packed with brilliant SaaS minds, we’d love to get your technical and product feedback on a few things:
The Pain Point: Do you feel manual status tracking and standups are a genuine productivity killer in your teams, or do existing tools (Slack bots, Jira, etc.) solve it well enough for you?
Feature Set: What is the number one feature you always wish your team monitoring or standup tools had?
Pricing/Value: For a SaaS tool that eliminates 1-2 hours of team meetings per week, what model makes more sense—per-seat pricing or flat team tiers?
We’d love to get your brutal, honest feedback on what we’ve built so far so we can iterate fast.
Let’s chat in the comments! 👇
Automatically tracking team progress to skip manual reports is a strong angle, especially for engineering teams that hate micromanagement. To make the value clear fast, focus at once on how you differ from standard Slack bots or Jira setups. That will be your biggest hurdle. The strongest messaging angle here is the exact amount of engineering hours saved by eliminating those manual sync meetings.
If you want to see how other B2B SaaS teams position similar workflow tools, run it through painbase.space. You can also see how they score early demand to map out the highest-intent angles.
Brutal but useful: your pricing question is premature, and that's the tell. You're asking per-seat vs flat-tier before the harder question is answered, which is whether "automated standups" is a vitamin or a painkiller. In this category (Geekbot, DailyBot, Standuply, Slack workflows all own it), it's mostly sold as a vitamin, and vitamins struggle at any pricing model because nobody urgently needs them.
The pricing answer follows from the buyer, and you have two opposite ones. If the buyer is the manager who wants visibility, per-seat works (they're buying oversight, more seats = more value). If the buyer is the team that wants fewer meetings, flat-tier works (they're buying relief, and per-seat punishes them for growing). You can't pick a pricing model until you pick which of those two you're selling to, because they want opposite things and one of them (the team) actively resents being tracked.
On the feature question, the answer that would actually differentiate you: don't report activity, detect blockers. Every tool shows who's busy. None reliably flags "this person's stuck on the same thing 4 days." That exception-detection is the only feature in this space people would call a painkiller.
The thing to nail before pricing: how does Trackly know status without asking? If a human still types the update, you're Geekbot with a new coat. If it reads from GitHub/Jira/Linear automatically, that's the whole product and the whole pitch.
What's the actual auto-tracking mechanism? That determines whether you have a wedge or a fourth entry in a crowded category.
Tool fatigue is the real enemy here. If Trackly pulls data automatically from git commits and Jira without engineers having to type updates, you've got a winner.