Project time and support effort are not the same thing
Feature work can be planned; incidents cannot. MetronHR keeps the two apart, so that maintenance contracts do not eat the project margin.
- Project and support hours kept apart per client
- Onboarding a new developer runs by itself
- Recording from home works as it does in the office
In short
Support effort eats the project margin when both book to the same pot. Separate services per customer, automate onboarding.
Support eats the project margin, unnoticed
In software teams, planned development and unplanned incidents run side by side. When both book into the same pot, the project costing looks fine until the maintenance contract is invoiced.
Support does not get assigned
Half an hour of debugging between two tickets lands on the project instead of on the maintenance contract.
Onboarding hangs on individuals
Accounts, hardware and the introduction are handed out by word of mouth, from scratch for every new developer.
Distributed teams, scattered hours
Anyone working from home often enters hours days later, and by then they are estimates.
Project, support and onboarding in one system
Every client gets its own projects and services, with support as a service of its own. You create onboarding processes once, and after that they hand themselves out.
Project and support reportable separately
For every client it is clear how much effort went into development and how much into support.
From the task to the report
Three steps that keep development and support apart.
Step1
Model the processes once
Create onboarding, offboarding and approvals as a workflow, with the tasks, the order and the owners set out.
Step2
Tasks run through by themselves
On the start date the tasks are handed to IT, HR and the team lead and ticked off. Nothing hangs on one individual any more.
Step3
Report project against support
Hours per client, project and service, with a target-against-actual traffic light per project. As Excel or CSV for the invoice and the costing.
What IT and software teams need
Project against support, distributed teams and onboarding that keeps coming round.
Separate services per client
Development, support and maintenance as separate services under the same client.
Reportable separately, the basis for the maintenance invoice and the project margin.
Onboarding and offboarding as a process
Modelled once, and handed out and followed up automatically after that.
Accounts, hardware and the introduction as tasks with an owner and a deadline.
A project budget with a target-against-actual traffic light
Hours and an hourly rate per project, with the usage colour-coded.
Green up to 80 per cent, then at risk, over budget beyond 100 per cent.
Recording from home works as it does in the office
Browser or app, with no extra hardware and no compulsory VPN.
Hours for past days can be added later.
Effort per client and period
Filter by client, project, service and person.
Download as Excel or CSV.
Digital employee file
Contracts, agreements and deadlines in one place.
With reminders about the end of probation and contract deadlines, on the Professional plan.
Client data in Germany
Servers in Germany, encrypted, GDPR compliant.
It matters when your clients audit data processing.
No rollout, no onboarding workshop
Runs in the browser and as an app, with no package for software distribution.
Invite external developers by email and deactivate them afterwards.
For management, project leads and development
Four roles, four reasons, from the maintenance invoice to the first working day.
Knows what support really costs
The maintenance contract looks profitable because incidents get booked to the project.
Hours per client and service, with development and support kept apart.
Sees the budget before it tips
The overrun shows up while the invoice is being written.
A target-against-actual traffic light per project and utilisation per developer on one page.
Books without switching context
Time tracking interrupts the work and therefore gets put off.
Pick the client, the project and the service, at the computer or on the phone.
Onboarding runs without anybody having to ask
With every new starter, accounts and hardware are organised by word of mouth.
The process modelled once, and the tasks hand themselves out.
Data processing your clients are allowed to audit
Software providers process data for their clients, and are therefore audited themselves. MetronHR runs in Germany and provides the evidence that gets asked for.
- Servers in Nuremberg and Falkenstein, no data transfer to third countries, no CLOUD Act
- TLS encrypted transfer, encrypted storage, GDPR compliant
- A data processing agreement and a record of processing for client audits
- Two-factor authentication and passkeys available to every user
Trust Center
Processing agreement and record included
Frequent questions from IT and software
Project against support, onboarding and distributed teams, answered briefly.
Yes. Every client gets projects, and under them services such as development, support or maintenance. Every entry goes to a service, and in the report you filter by client, project and service, as Excel or CSV.
You model the process once: create the accounts, order the hardware, the introduction, the probation review. On the start date the tasks are handed automatically to IT, HR and the team lead and followed up. Workflows belong to the Professional plan.
Yes. MetronHR runs in the browser and as an app for iOS and Android, with no extra hardware and no compulsory VPN. Hours can be added for past days when nothing was booked in the middle of focused work.
Yes. Per project you set hours and an hourly rate, and every entry draws on them. The position is shown as a traffic light: green, at risk from 80 per cent, over budget beyond 100 per cent. There is no automatic notification.
Yes, from the Professional plan up. REST API v1 hands out people, departments, clients, services, projects, time entries, absences and published shifts; clients, services, projects, time entries and absences can be changed. A key carries exactly the rights you give it and can be rotated and revoked. On top of that there are outgoing webhooks for hours, absences, people and shifts, and an MCP server for AI assistants that is off out of the box; writing there is a separate release by the business. The overview is on the page "REST API, webhooks and MCP server" at /api.
Two-factor authentication and passkeys are available to every user, whatever the plan. Roles and departments control who sees which clients, projects and reports.
Question not answered here? Every step is explained in the help centre.
Finally keep project and support apart?
Try MetronHR free for 14 days, no credit card. Team plan from 5 € per user per month.
Questions about services and workflows? Write to us: an answer within 24 hours, within 8 hours on the Professional plan.