WebWork is a time tracking platform that was built by the people who needed it first.
In 2016, the WebWork team set out to solve a problem they had themselves. They couldn’t reliably see where their working hours went. So they built an MVP and released it to real users early, on purpose, so they could learn from the feedback and improve as they went.
After that, WebWork grew every day, adding new features as it went. But through the whole journey, one thing stayed the same. The team kept listening to the people using it, to their feedback, their reviews, and their feature requests. That early choice shaped everything after it. As more teams started using WebWork, the product kept growing in the same direction, guided by the people who used it every day. It is why 244 of WebWork’s features began as a request from someone using it.
WebWork’s Journey
The first version was a basic time tracker with screenshots, simple enough to be useful right away and open enough to improve with real use. In 2017, WebWork added app and website usage monitoring, activity monitoring, and employee monitoring software features, giving teams a clearer picture of how work time was spent. In 2018, project management arrived, taking WebWork beyond time tracking for the first time. Over the next few years, the product matured and its user base kept growing.
By 2023, WebWork had widened into a much fuller platform, adding payroll, timesheets and approvals, report scheduling, and integrations. In 2024, it completed a major phase of development and launched its Finance section, bringing payroll and payments into the same platform with connections to Deel, Stripe, and others, so a team could move from tracking hours to paying people without leaving the tool. That same year, the first version of WebWork AI was built internally.
WebWork AI officially launched on February 24, 2025, bringing intelligent time analysis, productivity insights, and the ability to ask questions about a team’s work in plain language. In July 2025, the Smart Monitoring add-on followed, reading activity patterns, workload signals, and behavior automatically, so managers could understand how work was going without watching over anyone’s shoulder. That year WebWork also released a major new version of its desktop software, added Silent Tracking for company-owned devices, expanded payments through PayPal, Payoneer, Wise, and Bitwage, and advanced its security and compliance work in line with HIPAA and CCPA. In December 2025, founder Vahagn Sargsyan published Builder’s Time, framing time as a system to be designed rather than a number to be tracked.
In 2026, WebWork grew more capable again. In February, it launched its long-requested Google Calendar integration, letting teams sync their schedules directly with the tool. Smart Monitoring gained the ability to generate summaries, create tasks, and send proactive alerts on its own, and WebWork AI moved from simply analyzing work to acting on it, offering nudges, recommendations, and real help across time tracking and team performance. Payroll and payments came together into unified flows for salary, hourly, and contract-based work, and the platform grew stronger for larger organizations through compliance workflows, audit controls, role-based permissions, and better privacy. Today WebWork serves over 26,000 businesses around the world, and that number keeps climbing.
Closer to the People Who Use WebWork
Through its whole journey, WebWork has stayed close to the people who use it. From the very first release, the teams opening the app every day have been the ones who know it best. They track their hours in it, manage their projects in it, run their payroll through it, and lean on it to keep a remote or hybrid team moving. They see what helps and what gets in the way in a way no planning meeting ever could. That is why, year after year, their voices have shaped where the product goes. The people using WebWork are the reason it exists, so it makes sense that they are also the ones who guide it.
That closeness has never faded as WebWork has grown. Reviews, suggestions, and feature requests are read as direct signals of what to build next, not as noise to filter out. When a customer takes the time to explain a problem or describe something they wish the product could do, it usually points at a real need, and often one that many other teams share without ever saying so out loud. One person asking for a small change can reveal a gap that thousands of users have quietly worked around.
Staying close to those voices does more than solve problems. It keeps WebWork honest about what it is building and who it is building for. Features shaped this way earn their place, because they answer something real that a user actually asked for. And the teams behind those requests feel the difference, because they can see their own ideas show up in the product they open every day. That connection, kept alive through every stage of WebWork’s growth, is what turns a piece of software into a tool people genuinely trust.
A Page Built for Feature Requests
WebWork gives its users a dedicated place to be heard. On its feature request page, anyone using the product, whether an employer running a team or an employee tracking their own hours, can submit an idea for something they want WebWork to build. The invitation is simple: have a feature request? Feel free to submit it.
The page does more than collect ideas. Users can submit their own requests, view what others have asked for, and vote for the ones they want most. Every request is public, so people can see which ideas are shared by others and which ones have the most support. Users can also follow the progress of a request as it moves from a new idea to development and eventually to a completed feature.
The very first requests came in back in September 2019, and user feedback has shaped WebWork ever since. In those early months, teams asked to change the project or task on time that had been tracked by mistake, to link projects with their tasks, and to set how often screenshots were taken. One customer running offices in the UK, US, India, and the Philippines asked for more time zones. Another wanted different currencies for different employees. An invoice generator with editable content, idle time tracking, a Kanban board for organizing tasks, team chat, and sick time and paid time off all began the same way, as requests in 2019 and 2020, and all of them shipped.
As the platform grew, so did the requests. What started as small fixes to time tracking turned into asks for deeper reporting, more flexible scheduling, tighter privacy, and connections to the other tools teams already used. Often a request that began with one user’s problem became useful to thousands of others facing the same thing. Year after year the requests kept coming, and WebWork kept working through them, until 244 of them had been built and released.
From 348 Requests, 244 Released and 10 in Progress
The feature request page tells the story in plain numbers. Of 348 requests submitted over the years, 244 have been completed and released into the product. Another 58 are new and waiting to be reviewed, while 10 are currently in progress. The remaining 36 have been reviewed and marked as not planned. Together, these numbers show how much of WebWork’s development has been shaped by direct feedback from its users.
Those 244 completed requests reach almost every part of the platform. Some help businesses understand how their teams spend time, through things like real-time monitoring and all-time task reports. Others make project management and scheduling easier, from project budgeting by task to individual and custom work schedules and mandatory task and activity descriptions. And others open WebWork up to the wider toolset a team already runs on, including the Apps and Websites API and integrations with tools like Notion and Zoho Projects. There are quieter wins too, like employee rate privacy, which lets a company keep pay rates from being seen across the team.
The range also shows how the needs of WebWork’s users have changed over time. As teams have become more distributed and their workflows more complex, requests have moved beyond basic time tracking toward automation, integrations, reporting, privacy, and deeper project management.
The process is still ongoing, and the requests marked in progress give a glimpse of what is coming next. The WebWork team is working on an option to enter shift start and end times by hand, monthly leave accrual, detection of fake mouse and keyboard activity, and an unread toggle for notifications. Like the features already shipped, these did not appear out of nowhere. Each one began with a user pointing to something they wanted WebWork to improve.
With 244 requests released and 10 more in progress, the list keeps growing. Some requests become features, some stay under review, and others are not planned. But the process behind them stays the same. Users say what they need, other users back the ideas they share, and WebWork uses that feedback to decide what to build next.
Always Listening, Always Building
WebWork works the same way now as it did at the first release: the people using it decide what comes next. You can see it in the product itself, in 244 features that exist because someone asked for them.
The list isn’t finished. Requests keep coming in and the team keeps working through them, which means the next feature is already sitting on the page, waiting for its turn.
“`
