✓ Small creative agencies
✓ Productized-service teams
✓ Readers with a specific client-delivery problem
— Guaranteed sales or traffic
— Enterprise security certification
— Replacing a sufficient tool without a concrete gain
Compare the tradeoff: compare what the number means
An hour is a unit of time; a credit is a unit your agency defines. A credit might cover a specific deliverable, a category of work or a bundle of effort. Without that definition, a credit balance can look precise while remaining commercially vague. ManyRequests documents time-based and credit-based service configurations. Select the unit that clients can understand and that producers can apply consistently, not the one that makes a pricing table look simpler.
Publish an understandable conversion example
For an invented service, a small resize might use one credit and an original layout three. These numbers are illustrative and not recommended market prices. Explain what changes the estimate, who approves that change and when credits are deducted. Avoid pretending every deliverable has identical effort. If a unit depends on scope, show the customer the estimate before work begins rather than revealing an unexpected balance reduction afterward.
Keep internal learning separate from client billing
Even a credit-priced agency can record time internally to learn which work is consuming capacity. Conversely, an hourly service still needs an output and approval standard. Do not equate every logged minute with a chargeable minute without the agreed rules. Compare planned and actual effort privately, then use that evidence when revising future service definitions. The measurement should improve the process, not retroactively rewrite a client’s accepted price.
Test the edge of the allowance
Take a fictional request that exceeds the remaining balance. Decide whether it waits, needs an approved top-up or becomes a separately scoped job. Rehearse what the client sees before committing. A portal warning is useful only when it matches the agency’s rule. Keep the original request and approved estimate linked if the entitlement changes, so a later review can explain why the work proceeded and what the customer authorized.
What this comparison can—and cannot—settle
This guide draws on ManyRequests service pricing configurations, ManyRequests time tracking. Merchant-controlled records describe the provider’s own capabilities, terms or standards; they do not independently validate those claims. These records do not establish independent confirmation of the product claims.
Verify any current price, plan limit, label direction, compatibility rule, or commercial term that would materially change the decision. The dated source ledger shows the underlying records so this conclusion can be checked and updated.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- ManyRequests service pricing configurations — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests time tracking — Merchant documentation · manyrequests.com · Merchant-controlled · checked 2026-09-19