Demircode Case Study: Optimizing Projects and Productivity with Worktivity

Demircode is a software development and IT consulting company delivering client projects with a small senior team. They have used Worktivity since 2023 to see how development time distributes across concurrent work.

The problem they started with

Small senior teams are efficient and opaque at the same time. Everyone works on several things, context switches are constant, and the allocation that existed at the start of the week rarely survives it.

For a consulting company that is a commercial problem, not just an operational one. If a fixed-price project is consuming twice its planned share of the team, that shows up in cash before it shows up in a report.

What they use

• Time by project and task, so client work is separated from internal work

• Application and website categories, to distinguish development from meetings and support

• Reports, used as the input to planning rather than as a review artefact

What changed

Allocation became observable. When a project starts pulling more of the team than planned, that is visible in the same week rather than at the end of the engagement, which is the only point at which it can still be acted on.

Why this pattern fits consulting teams

In a consultancy the team is the product and its hours are the inventory. Not measuring where those hours go is the equivalent of not counting stock.

What Worktivity records

Worktivity records time, activity level, the application in the foreground and the site host, and only while a shift is running. It does not record typed text, window titles or full web addresses, and it never requests the camera or microphone. The full list is here.