Software and IT services
Six client builds.Blockers on day one.
QA cannot start until the front end lands, and nobody sees that until it is late. Work makes the dependency visible the day it is set, keeps billable hours on the tasks, and gives the client a place to sign off each release.
Website redesign · board
64% doneTo do
- Copy for About page
- Cross-browser QAblocked by build
In progress
- Build homepage
- Menu page design
Done
- Wireframes
- Brand refresh
[ 01 ] How it runs here
From kickoff to sign-off
- 01
Plan with dependencies
Milestones per release; blocked-by links between tasks.
- 02
See blockers loudly
Blocked work shows on the board; an overdue rule notifies the lead.
- 03
Bill the hours
Hourly or fixed-price per project, hours logged against the task they were spent on.
- 04
Sign-off in the portal
A release or UAT checklist sent for approval; the decision is on record.
[ 02 ] What IT services firms lean on
The parts that matter most
Dependencies and the board
Blocked-by links, and an automation that moves dependants to To do when the blocker completes.
Billable and non-billable hours
Per task, with utilisation per person and profitability per project.
Forward capacity
Estimates against committed hours: can we start the next build in three weeks?
Client hours view
Clients see hours on their project, never your rates.
AI assistants
Ask Claude or another MCP assistant what is overdue, or log hours from the conversation.
Not a sprint tool
No story points or code integrations: Work runs the client engagement around your engineering tools.
[ 03 ] Plans
Which plan has it
| Capability | Starter | Business | Agency |
|---|---|---|---|
| Projects, dependencies, board | Included | Included | Included |
| Billable hours and capacity | Not included | Included | Included |
| Automation rules | Not included | Included | Included |
| Client sign-off | Not included | Not included | Included |
Anything not on your plan can be added to one workspace on its own, priced from the same price book. Compare every plan