The operational gap we noticed while talking to growing teams
Over the past few months, while speaking with different businesses and teams, we noticed a pattern.
Most companies don't struggle because they lack tools.
They struggle because as the team grows, their existing processes stop working.
A company with 10 employees can manage things through conversations and spreadsheets.
But when the team grows to 50, 100, or more employees, simple operational tasks start becoming complicated.
Managers start dealing with questions like:
• Are all teams following their assigned schedules?
• How are attendance and overtime being tracked?
• Where are productivity gaps coming from?
• How much time is being spent on manual reporting?
• Do HR and operations teams have a reliable view of daily workforce activity?
The challenge is that the data usually exists.
But it is scattered across different places:
spreadsheets
chat groups
attendance sheets
multiple disconnected systems
This creates unnecessary manual work for HR teams, operations managers, and business owners.
That’s the problem we started working on.
We’ve been building Trackly, a workforce management platform designed for growing companies that need better visibility into their teams without adding more complexity.
Our focus is helping businesses manage:
✅ Employee attendance and shifts
✅ Work hours and overtime
✅ Break tracking
✅ Leave management
✅ Workforce reports
✅ GPS-based check-ins for distributed teams
While building, one thing became very clear:
Companies don't just need another tracking tool.
They need a better way to understand their operations and make decisions with confidence.
We’re currently speaking with founders, HR leaders, and operations teams to learn how different companies are solving this today.
I’d love to hear from people managing teams:
What systems or processes are you currently using for workforce management?
And what part of managing teams becomes the hardest as your company grows?
Would love to learn from your experiences.
"The data usually exists, it's just scattered across different places" rings true even at the tiny end of the scale, not just at 50-100 employees. We're a very small operation and this week alone we had lead data spread across a spreadsheet, a CRM export, and a dozen community platforms we'd joined for outreach, and just reconciling "who have we actually contacted" across those became its own manual job. I'd guess the hardest part scales the same way regardless of headcount: it's not the tracking itself, it's trusting that the number you're looking at is current and not three systems behind reality. Curious whether Trackly's GPS check-in feature came from a specific customer request or was something you built speculatively, that's usually the tell for whether a feature actually gets used after launch.
The scatter is the feature, not a bug - it reflects the actual decision-making authority. Spreadsheets for HR because the manager owns it, Slack for ops updates because people watch channels, attendance tracking over here. Tools don't fix that; they just make the scatter more efficient. What usually happens first at this scale isn't tool adoption, it's process standardization. Teams pick "we count Slack messages from the #standup channel" not because it's good data but because everyone sees it. Before Trackly can work, the team needs to agree that unified visibility matters more than preserving each group's data independence. That's organizational, not technical. Worth asking: who has to give up what to make this centralized view actually get used?
Curious what "operational gap" specifically means here — is this more about communication breakdowns, or about tooling/process gaps as teams scale? I'd love to hear a concrete example if you have one.
Great question. From what we’ve seen, it’s usually a mix of both, but the root issue is process gaps as teams scale.
For example, a 20-person team might manage attendance, shifts, and updates through chats and spreadsheets. But once they grow, managers spend more time collecting information than actually using it to make decisions. That’s the gap we’re trying to solve with Trackly, creating a clearer operational picture without adding more complexity.
That "collecting information vs. using it to make decisions" distinction really resonates — it's a subtle but important shift as teams scale. Is Tracky meant to sit on top of existing tools like Slack and spreadsheets, or does it aim to replace them entirely?
Worth pricing in early if any of those teams are in the EU: continuous location tracking of employees is one of the messiest cases in the book. Consent doesn't work as a basis in an employment relationship, the power imbalance means it isn't freely given, so you're left with legitimate interest or whatever national labour law allows under Art 88, and that varies per country. Systematic monitoring of workers also sits on most supervisory authorities' mandatory-DPIA lists, and in DE/NL/FR the works council has co-determination rights that function as a veto.
None of that says drop GPS check-ins. It says your blocker is often the DPO rather than the ops manager, so shipping a DPIA template, sane retention defaults and a check-in-only-during-shift mode is product work, not paperwork.
This is a great point, and something we’ve been thinking about deeply while building Trackly. GPS check-ins are not meant to become continuous employee surveillance, the goal is to help teams with distributed or field-based employees have reliable attendance and shift visibility when they actually need it.
We’re approaching this with privacy and trust in mind: shift-based check-ins, limited data collection, clear visibility into how information is used, and giving companies better operational insights without creating a monitoring-heavy environment.
I agree that compliance shouldn’t be treated as an afterthought. Building the right controls, retention rules, and transparency into the product from the start is part of building something teams can actually trust. Appreciate you highlighting the DPO perspective, it’s an important conversation.
Which markets are you selling into first? If Germany or the Netherlands are on that list, the works council gets a say before the ops manager does, and their questions are narrow: what triggers a location read, where it's stored, how long it's kept, who can query the history.
Four written answers turn a six-week procurement stall into one meeting. Cheaper to write them now than during your first enterprise deal.
I scaled a services company from one person to teams across six continents, and the thing that broke at every stage was never attendance data, it was who owns the decision when the data disagrees with the manager. Workforce management is a brutally crowded category, so I'd pick the one wedge incumbents do badly (GPS check-ins for distributed field crews is a real gap) and own that buyer completely. 'Better visibility' is what every competitor already says, a named workflow for a named buyer is what gets you the first 50 customers.
This is a really good point. We’ve also realized that the real problem isn’t just tracking attendance; it’s helping managers make confident decisions when information is spread across different places or teams have different ways of working.
With Trackly, we’re focusing on distributed teams, remote workers, and growing companies where visibility around attendance, shifts, workload, and daily operations becomes harder to manage as they scale.
Still refining the exact workflows that matter most, but feedback like this helps us focus on solving a specific operational problem rather than just building another dashboard. Appreciate the perspective.
Really insightful take. The jump from 10 to 50+ employees is where makeshift workforce management processes collapse. So much valuable operational data exists, yet it’s trapped in disconnected systems.
One question: When building Trackly, how are you balancing feature depth while avoiding overwhelming growing teams? That complexity trap is what many existing workforce tools suffer from.
This is actually one of the biggest things we’re trying to get right with Trackly.
The goal isn’t to keep adding features, but to simplify the workflows teams already struggle with. We’re focusing on making things like attendance, shifts, leave, overtime, payroll reporting, and workforce visibility easier to manage without requiring a complex setup.
Growing teams don’t need more dashboards, they need a clear picture of what’s happening and the ability to take action quickly. We’re still learning from different teams as we build, and feedback like this helps us keep that balance.
I think there is another operational gap between centralized visibility and trustworthy evidence.
Bringing attendance, shifts, overtime, leave, and GPS check-ins into one dashboard makes the information easier to see. But it does not automatically make every conclusion drawn from that information reliable.
For example, a GPS check-in may prove that a device recorded a location at a specific time. It does not necessarily prove that the employee worked the full shift, completed the assigned task, or remained at that location.
The same applies to other workforce signals:
a scheduled shift does not prove attendance;
a clock-in does not prove productive work;
submitted overtime does not prove approved overtime;
dashboard activity does not prove the underlying records are complete.
I would separate three layers:
Recorded data: what each system captured.
Operational claim: what the company concludes from it.
Verification rule: what independent evidence is required before treating that claim as true.
That could become a meaningful differentiator for Trackly.
Instead of only showing managers that “overtime increased,” the platform could explain:
which records support that conclusion;
which system is authoritative;
whether the data is complete;
what contradictions or missing records exist;
how confident the manager should be in the result.
Centralization gives teams one place to look.
Verification gives them a reason to trust what they see.
Are you currently defining which source is authoritative when attendance, schedules, GPS records, and manager reports disagree?
This is a really interesting point, and I agree that visibility alone isn’t enough.
While building Trackly, we’ve been thinking a lot about the difference between simply collecting signals and helping teams trust the information they see. Attendance, GPS, overtime, and schedules each tell only one part of the story.
The challenge is making sure managers understand the context behind the data, especially when different sources don’t match. This is definitely an area we want to keep improving as we learn from real teams.
This matches what I’ve seen too. The tools exist. The process breaks when headcount jumps and everything still lives in chats and sheets.
The hardest part usually isn’t tracking hours. It’s getting a trustworthy daily view without making managers chase people for updates.
For teams I’ve talked to, leave + overtime + “who’s actually working today” gets messy first. GPS check-ins help field teams, but only if the reporting side is simple enough that people actually open it.
I built Make it RAIN for a different stage (creators monetizing products), but the same pattern shows up: data everywhere, no clear operating picture.
Curious for Trackly users so far: are you winning more with HR buyers or ops/founders first?
Completely agree. The process side is actually one of the biggest challenges we’ve noticed too.
Many teams already have some kind of system, but every department develops its own way of tracking things over time. Then the problem becomes bringing those different processes together.
So far, we’ve seen interest from both HR and operations because the pain usually sits between them. Still learning which side feels the problem most urgently as we continue talking with teams.
The part I'd push back on slightly: the hard part often isn't building the visibility layer - it's that teams have usually built different processes in each department by the time they hit 30-40 people. HR is tracking one way, ops another way, field teams a third way. So Trackly solves the consolidation half, but teams often need help forcing process standardization first. Otherwise you're just making scattered bad data visible in one place. Have you run into pushback from teams resistant to standardizing how they report time/shifts?
Really good point. I think you’re right that visibility alone doesn’t fix a broken process. If every team follows a different workflow, a centralized system can only highlight the gaps.
One thing we’re learning while building Trackly is that adoption and standardization are just as important as the data itself. The goal isn’t only to collect information, but to help teams create a consistent operating process around attendance, shifts, and workforce updates.
We’re still exploring the best ways to make that transition easier for teams that are used to their existing methods.
the pattern I've seen is that the gap doesn't just show up in processes — it shows up in skills too. teams past ~30 people start having invisible competency gaps because nobody knows who can actually do what anymore. the spreadsheet breaks down for skills tracking the same way it breaks down for scheduling.
This is actually a very similar pattern. The number of tools keeps increasing, but the challenge becomes having one reliable view of what’s happening.
We’ve seen the same with workforce operations, the information exists, but managers spend too much time searching, comparing, and following up.
I think both consolidation and process clarity matter. A single dashboard helps, but it needs to reflect a process people actually follow.
The version of this I ran into wasn't headcount, it was tool count. Once I had client work running across three different automation platforms instead of one, the "system" for knowing if anything was broken stopped being a system at all — it was just me remembering to check each dashboard separately, which I didn't always do. Same root issue you're describing: the information existed, it just wasn't anywhere I could see it in one place. For us the fix was consolidating visibility rather than adding another tool to check. Curious whether that pattern holds for workforce ops too, or if the fix ends up being more about standardizing the process itself rather than just surfacing it.
The gap we kept running into talking to teams was similar, ops knowledge scattered across Slack, someone's head, and a doc nobody's opened since Q1.
It gets worse right around 15 to 30 people.
Past that, a founder can't personally be the API for every "wait how does this work" question anymore.
Full disclosure, I'm building something in this space (Rootr), so take that with the appropriate grain of salt.
But curious what gap you all found, more process knowledge, or more decision context that people were missing.
This resonates a lot. The pattern I keep seeing isn't that teams lack tools, it's that the "system" is actually just tribal memory: someone remembers to check the spreadsheet, someone remembers to follow up in the chat thread, and it holds together purely because a few people keep it in their heads. The moment headcount grows past what one person can mentally track, that invisible system breaks and nobody notices until something falls through. Curious whether you're finding the hardest part is the tracking itself or getting managers to trust a single source of truth over their own spreadsheets.
The 10 to 50 employee window is a really specific detail, that's usually right when the "just use a spreadsheet" setup quietly stops working and nobody notices till something's already broken, curious what "actionable" actually looks like day to day though, does Trackly tell a manager "these three people are heading toward burnout" or "this shift's always understaffed," or is it more that the same data just becomes easier to look at in one place? Those are pretty different things even if both get called "actionable insights."
Great question. I think the difference between “data” and “actionable insights” is whether it helps someone make a better decision.
Our current focus with Trackly is not just showing more numbers, but helping managers understand patterns behind those numbers, things like repeated overtime, attendance gaps, workload visibility, or where teams may need support.
We’re still exploring what signals are most valuable for growing teams, because every company has different workflows and challenges. That learning process is actually a big part of building it.
One thing I've noticed is that the real challenge isn't collecting workforce data, it's making it actionable. As teams grow, even simple questions can require digging through multiple tools. Having accurate, centralized information helps leaders spend less time chasing updates and more time making decisions. Curious to see how others have tackled this as they've scaled.
Absolutely agree. We noticed the same thing while building Trackly, collecting data is only the first step. The real value comes when teams can quickly understand what’s happening and make better decisions without spending hours searching through different tools.
That’s exactly what we’ve been trying to incorporate into Trackly, making workforce information more clear, centralized, and actionable rather than just another place to store data. Still learning from how different teams handle this as they scale. Thanks for sharing your thoughts!