Loading
Because the sold value is in one system and the hours are in another, and joining them is a monthly job that gets done when there is time. There is rarely time.
So the retainer that has been fifteen hours over every month for a year is discovered during an annual review, by which point it has been renewed twice.
Sold lines and logged time sit on one record, so margin per project, per client and per month is a view rather than an exercise. Utilisation is real because capacity comes from Nest with leave already in it.
The retainer running over shows in the month it starts running over, while the conversation is still easy to have.
It will not tell you what to charge. It shows what the work costs and what you sold it for; pricing remains a commercial judgement.
And it will not make an unprofitable client profitable. It makes the number impossible to avoid, which is usually the missing part.
Flow's pipeline and Loop's capacity are on the same platform, so selling work you cannot staff is visible before the start date is promised.
Books bills from what was delivered, and cohort analysis shows whether the work you sold in Q1 was the work that paid.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes, live, across projects and retainers.
It uses real availability from Nest, so leave and part-time patterns are already accounted for.
No, but margin needs sold value, which usually comes from one of them.
Half an hour on your own numbers is usually enough to say whether Loop is the right place to start.