Loading
Because the proposal says three rounds and nobody counts. Round four arrives as a friendly email, round five as an assumption, and the studio absorbs both because raising it would be awkward.
The project looks profitable until somebody adds up the hours, which usually happens after the invoice has gone out.
Each deliverable carries its approval state and its revision history, so round four is a record with a date rather than a feeling. Time logged against it is visible as cost against the sold lines.
The client portal shows the same rounds, which makes the conversation about a fifth one factual rather than confrontational.
It is not a design tool and it does not host files for review — it references wherever your work actually lives.
And it will not have the awkward conversation for you. It gives you a dated record and a number, which is what makes the conversation short.
Books bills from what was actually delivered and approved, including the additional rounds if you decide to charge for them. Billable hours reach the invoice without being retyped from a timesheet.
Margin per project is available while the project is running, so a job going wrong is a decision rather than a post-mortem.
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.
You can record what was sold and count what happens. Loop makes the overage visible; enforcing it is yours.
The client portal shows what you publish to it, without a full licence.
Yes, billable hours flow to Books against the project.
Half an hour on your own numbers is usually enough to say whether Loop is the right place to start.