Track project hours and utilisation across IT delivery, from sprint to invoice
Mera Work logs engineers' tracked time against the project and task they are on, whether the work is billed by the hour, sold as a fixed bid or delivered by a dedicated team. Delivery managers see effort against estimates, who is stretched and who is on the bench, and roles are measured by their own tools: an IDE for developers, a ticketing tool for support.
Mera Work by industry
What Mera Work gives an IT or software company
The numbers delivery, finance and engineering leads ask for week after week, without anyone compiling them.
Protect margins on fixed bid projects
Estimated, logged and final hours for all projects and tasks. When a fixed bid project starts using hours faster than planned, you see it the same week.
Bill time and material work with confidence
Entries carry their project, task, start time and end time, ready to export when the invoice goes out or a client asks.
See utilisation and the bench
Compare a person's project hours with their expected hours to see who is fully allocated, who is stretched across projects and who has room.
Measure engineers fairly
Development tools count as productive for engineering, and a longer idle interval covers code review, long builds and reading documentation.
Common problems in IT companies and what changes with Mera Work
Most IT and software companies come to Mera Work with questions like these. A setting or a report you already have answers them.
- Timesheets are filled in on Friday from memory
- Tracked time is logged against the task an engineer has selected, and Daily Time Entries builds the timesheet as the week goes.
- A long build or a code review shows up as idle
- Give engineering a longer idle interval, up to 30 minutes, and mark development tools as productive for that department.
- Fixed bid projects lose margin quietly
- The Project Report puts estimated, logged and final hours side by side by project, so an overrun shows while there is still time to act.
- A client asks if their dedicated developer works only on their project
- The User Task report shows a person's hours by project, and Daily Time Entries lists all entries for that client's work.
- Engineers are split across too many projects
- User Task shows a person's logged hours across projects, so context switching is visible before it slows delivery.
- Nobody is sure who is on the bench
- Compare project hours in User Task with expected hours in the Attendance report to see who has capacity for the next project.
- The team works inside a client's VPN or VDI
- The agent works over VPN, proxy and VDI connections, so work in a client's environment is recorded like any other.
- Licences for IDEs, design tools and AI assistants pile up
- Search any tool in Application Usage to see who used it and for how long, and see time in AI tools through the built in AI & Machine Learning category.
A day across an IT team, and how Mera Work records it
Five moments from a team, in the hours that role works. All of the work lands in the right place, including the parts away from the keyboard.
-
09:30
Developers
Stand up on a video call
Meeting tools are labelled productive for engineering, and the team's idle interval can be set up to 30 minutes, so a stand up spent talking stays active time.
-
10:15
Developer
Coding on a sprint task
Time lands against the task the developer picked, and the IDE counts as productive for the team.
-
13:40
Tech lead
A code review
Time in the repository and the review tool is recorded against the same task, labelled productive for engineering.
-
15:00
Delivery manager
Workshop at the client's office
Time away from the computer is claimed from the day's timeline with a reason, and approved by the delivery lead.
-
22:00
Support engineer, night shift
Night support for an overseas client
The support engineer works a night shift. A cut off time after midnight keeps the whole shift in the same working day, in their own time zone.
The features IT and software teams rely on
These features cover delivery, engineering time and tool use. Select any card to see how that feature works.
Project and Task Tracking
Tasks allocated with dates, time logged against them, and estimated, logged and final hours side by side.
Learn more →Time Tracking
Active, idle, away and offline time on all computers, including Linux workstations.
Learn more →App and Website Monitoring
Development, communication and other tools grouped into categories and labelled by your rules by team.
Learn more →Activity Monitoring
Keyboard and mouse activity counted as volume only, so code and what people type stay private.
Learn more →Productivity Reports
Project Report, User Task and Daily Time Entries, exported for delivery leads or the client.
Learn more →Productivity Dashboard
Team and project leads see their people at a glance, scoped to the manager looking.
Learn more →All features are included in the free trial. Start free →
How Mera Work fits your delivery model
IT work is sold in different ways, and the numbers that matter change with the model.
Time and material
Time entries with project, task, start and end time, exported for the invoice and for any question the client raises.
Fixed bid
Estimated against logged hours by task while the project runs, and final hours to price the next quote from real numbers.
Dedicated teams and staff augmentation
A person's hours on the client's project, screenshots with blur where the contract allows, and a weekly report for the account manager.
Managed support and helpdesk
Shifts and rosters, including night shifts for overseas clients, attendance against the roster and live screen for escalations.
How Mera Work supports IT and software teams
Time lands against the work, teams are measured by their own tools, and delivery leads get the numbers without asking.
Hours logged against projects and tasks
Create projects with estimated hours, then allocate tasks with a start and end date, task by task or by spreadsheet. A person picks the task they are on, and their tracked time is logged against it until they switch. Redmine is a delivered integration, and other tools connect through the API.
- Estimated, logged and final hours per project and per task
- Tasks allocated with dates, or uploaded in bulk
- Daily Time Entries with start and end times for the client
- Redmine integration, and an API for other tools
Productive time measured the way IT work happens
Apps and websites fall into built in categories, including Development & IT and AI & Machine Learning. Mark categories productive by department or person, so an IDE counts for developers and a ticketing tool for support, and set the idle interval by team, from 2 to 30 minutes. Keyboard and mouse activity is counted as volume only, so source code and what people type stay private, and screenshots cover the primary display and one extended display.
- Categories and labels per department or person
- Idle interval per team or person, 2 to 30 minutes
- Screenshots on or off per person, with adjustable blur
- Activity counted as volume, content stays private
Activity is a signal. Mera Work reads it next to the tools in use and the hours by project.
Try it with two engineers on a real project. Start free →
Active categoryDevelopment & ITInherit from OrganizationProductiveBack to List
Software and platforms used for programming, software development, source code management, API testing, databases, DevOps, cloud infrastructure, system administration and IT operations.
Configuring for: Department: DEV, inherited from Organization
Utilisation, overruns and tool spend together
The User Task report shows a person's hours across projects, and Attendance shows logged and expected hours, so allocation, the bench and burnout risk are visible side by side. The dashboard puts a lead's team at a glance. Application Usage shows how much paid tools are used, so renewals for IDEs, design tools and AI assistants are based on real numbers.
- Hours per person across projects
- Expected hours and overtime per person
- Application Usage search for any tool or website
- Reports exported for delivery leads
Set up fairly for the roles in IT
Different roles use different tools and work at a different pace. Mera Work lets roles be measured by their own work.
- Developers
- Development & IT tools marked productive, an idle interval long enough for review and builds, and activity counted as volume only so source code stays private.
- QA and testers
- Test tools and browsers marked productive for QA, with screenshots showing which build or environment was under test where you enable them.
- DevOps and infrastructure
- Linux workstations with .deb and .rpm builds, work over VPN and VDI, and a cut off time for night shifts and releases that run past midnight.
- Scrum masters and project managers
- Communication tools marked productive for these roles, and meetings away from the computer claimed from the day's timeline.
- Support engineers
- The ticketing tool marked productive, shifts and rosters for cover, and live screen so a lead can help with an escalation.
- Tech leads and architects
- Hours across several projects in the same report, and live screen to help a new joiner through their first tasks.
Set up an IT team in four steps
Most of it is set once. The first project hours appear the day you install.
Install on your workstations
Windows, macOS and Linux (.deb and .rpm), or a silent install through Active Directory, Group Policy or Intune.
Set up your roles
Mark development tools productive for engineering, test tools for QA and the ticketing tool for support, and set idle intervals by team.
Add projects and tasks
Create projects with estimates and allocate tasks. Redmine is a delivered integration, and other tools connect through the API.
Send the reports
Export the Project Report for delivery leads and Daily Time Entries for finance.
Ready to see your team's project hours? Start your free trial →
Mera Work is an exceptional tool for performance monitoring, offering invaluable support for organisational decision making. Its real time monitoring and live streaming capabilities provide complete visibility into team activities, ensuring transparency and accountability.
Simple pricing, all features, real people on support
IT teams get what they need with a subscription. Here is the rest of what you get.
Priced per user, all features included
Billed monthly or yearly, with nothing extra to buy. Start with two users.
PrivacyPrivacy settings you control
You choose who is captured, who can view and who can download. Mera Work records time, apps and activity levels, and what people type stays private.
HostingCloud, private cloud or on premise
Cloud hosted by default, with private cloud and on premise options for enterprise customers.
SupportCritical issues answered within the hour
Monday to Friday, 08:00 to 22:00 IST, by portal, email and phone.
Results our clients report
What IT and software teams changed after rolling out Mera Work.
-
Azure Virtual Desktop
Fitted a cloud first team
A cloud first company that needed visibility to work with Azure Virtual Desktop.
Read the story
-
Schedule based
Visibility within working hours
A team that wanted visibility only within working hours.
Read the story
-
Partner
From internal use to partnership
A cybersecurity company that added a view of how its own team works.
Read the story
-
14 day trial
Compared before choosing
A Dubai headquartered advisory firm that tested and compared before choosing.
Read the story
Explore further
Project hours in detail, how Mera Work connects to your tools, and the other ways teams use it.
Common questions about Mera Work for IT and software teams
How do you track time for a software development team?
Engineers pick the project and task they are working on, and Mera Work logs their tracked time against it. The Project Report compares estimated, logged and final hours, and Daily Time Entries gives the timesheet.
Does code review or build time count as idle?
Not if you set it up for the team. Give engineering a longer idle interval, up to 30 minutes, and mark development tools as productive for that department.
Does Mera Work read source code or what developers type?
No. Keyboard and mouse activity is counted as volume only. Code, documents, messages and passwords stay private.
Can we show a client how much time their dedicated team spends on their project?
Yes. User Task shows a person's hours by project and Daily Time Entries lists all entries with their start and end time. Both export to a spreadsheet for the client.
Does it work when engineers use a client's VPN or VDI?
Yes. The agent works over VPN, proxy and VDI connections, and keeps recording when the connection drops.
Does it run on Linux?
Yes. There are .deb and .rpm builds for Ubuntu, Debian, RHEL, Fedora and CentOS, alongside Windows and macOS, in interactive and stealth builds.
Can it connect to our project management tool?
Redmine is a delivered integration, and other tools connect through the API. Reports also export to Excel.
See your team's project hours
Install the agent on two workstations, create a project, and hours start landing against its tasks the same day.
