Keep the margin.
Keep the work.

Start with the question you cannot answer

These are authored role-based decision prompts, not fabricated customer testimonials.

Choose the tool that answers your agency’s actual question

A project can ship on time and still lose money. Its tasks may all be green while an unquoted revision round consumes the fee. Agency software becomes useful when the same project connects its agreed scope, logged hours, internal delivery cost, customer revenue and future commitments. A task board supplies part of that picture; a financial operating system supplies more of it, provided someone enters trustworthy rates and time.

Start the shortlist with Productive for connected commercial operations, FunctionFox for focused time and budget tracking, or Teamwork for client delivery and participation. Monday, Asana and ClickUp deserve a fair evaluation when the team already uses them: current higher plans, add-ons and configuration can cover more agency requirements than an older comparison suggests. Wrike brings detailed creative review and higher-plan financial controls. Storyflow serves the brief and concept stage before delivery rather than agency bookkeeping.

This guide compares all eight products, including the creative canvas that falls outside the financial category. Product capabilities and public list rates were checked against primary pages on 7 October 2026. A listed feature is not an independently measured ranking, and a fictional worked example is not a customer case study. We have not measured Google rankings, purchased these subscriptions, or accessed a private agency workspace for this comparison.

Use the workbench to identify the questions your trial must answer. It works from your entered source in this tab using decimal arithmetic and date-aware periods. It does not connect to these vendors, capture timesheets automatically, send budget alerts, recognize revenue for your accountant, approve scope, or issue invoices. Download the source before leaving the page.

Eight products, with the plan boundaries kept visible

Compare the commercial loop, not only the task interface. Native financial modeling, an optional paid module, configured formulas and a separate accounting integration are different commitments. The summaries below deliberately avoid unsupported claims that every generic tool is financially blind, that Wrike is the only product with proofing, or that a particular headcount automatically outgrows FunctionFox.

Productive: connect the sold work to the work delivered

Productive is a strong starting point when the finance lead cannot reliably follow a deal through its budget, resources, logged time and invoice. Its agency-oriented model connects those stages rather than asking you to construct every relationship in a generic dashboard. The public plan comparison includes budgeting, employee cost rates, resource scheduling and financial reporting; Professional adds rate cards, billable-time approvals, recurring budgets and more advanced reports. Ultimate adds forecasting, scenario planning and overhead calculation. Those gates matter: do not evaluate an Essential trial and assume every financial control is included.

Applied trial: create a prospective brand project from the commercial pipeline, enter its fee and service budgets, assign the designer’s internal cost and customer rate, and book the person across the actual delivery weeks. Log one ordinary design task and a non-billable extra round. Inspect the project/client financial view, group services by the internal service type, and review person/team utilization and cost before following the time through invoice preparation. The finance lead checks whether the billing type and recognized revenue match the contract rather than treating every billable hour as revenue. The delivery lead checks that the resource commitment reduces availability. Reporting controls and service types and billing types define the useful grouping choices.

Rate setup is the main responsibility. A low or missing internal cost creates an attractive but misleading contribution. Decide whether cost rates already include overhead before selecting a plan’s additional overhead calculation. Keep effective-rate changes and expense dates consistent with the reporting period. Invoicing data still requires review of scope authorization, tax treatment and accounting export. For review-heavy projects, test the actual markup/version workflow separately rather than assuming a financial system is also your full creative proofing suite.

Client invitations are free under the pricing page, but contractors who track time are charged like employees. The client budget view is permission-dependent; reveal only the scope/progress figures that the client should see. A five-person studio may still find this connected model useful, while a much larger firm may prefer a simpler setup. The decision is the required commercial loop and setup capacity, not an invented headcount cutoff. Productive pricing and plan comparison; client budget visibility.

Its recurring-budget feature also changes the retainer decision. Professional and Ultimate can create repeating budgets with optional unused or overused hour rollover. Configure the period, invoice draft and rollover rule to match the signed retainer. A booking spanning periods needs reconciliation against the real service dates. Automatic duplication is a convenience, not permission to roll hours against an unwritten contract. Productive recurring budgets.

FunctionFox: make the daily time habit practical

FunctionFox is worth testing when the immediate failure is missing timesheets and unclear budget consumption. Its Classic offer centers on a stopwatch, timesheets, estimates, project budgets, retainers and reports. Premier adds actionable to-dos, Gantt schedules and availability/traffic reports. In-House adds request intake forms, advanced report building, more job fields and request notifications. The current comparison also lists job costing, markups, quoting/invoicing, utilization and administration; confirm the actual tier for each control during a demo.

Applied trial: build a job with separate strategy and design estimates, record time against the correct job each day, then inspect actual time against the estimate before the second revision round. Use the stopwatch on a short favor instead of relying on Friday recall. The studio owner checks the report’s cost/rate basis; the producer checks whether Premier’s schedule and availability views can represent both overlapping projects. For a retainer, assign each request to the current period and reconcile the reported hours to the agreed allowance.

Focused setup can be an advantage, but “adopted this week” should be a trial goal rather than a guaranteed outcome. Ask the team to complete a real daily entry and retrieve the report without the administrator guiding every click. Inspect interface readability, client-facing access, expense handling, sales-pipeline handoff and report grouping with your own workload. The vendor publishes support and onboarding claims; those do not establish an independently tested response time or universal reliability ranking here.

The current page explicitly shows unlimited active user limits, so the source’s fixed claim that the product becomes unusable beyond about twenty people is not a defensible technical limit. Test a larger workload if relevant. The useful trade-off is how much commercial/project structure you need beyond straightforward time, budgets and schedules. Current prices also differ from older purchasing-help pages; use the dated pricing table below and confirm renewal terms for an existing account. FunctionFox’s current plans and detailed feature comparison, daily time controls, budget, expense and billing mechanics, resource management and retainer workflow.

Teamwork: bring the client into the actual delivery record

Teamwork makes client participation a concrete evaluation criterion. External client users can participate without an internal paid license, but they are not substitutes for employees. Its current help defines a client company and allows a client user in up to five of that company’s projects, with reduced permissions. A proof reviewer is a separate access path. Test both the client’s project workflow and a one-off approver invitation rather than assuming that “free clients” means unrestricted access to the whole account.

Applied setup: choose People, invite the client under the external company, select the client user type and assign the appropriate projects. Let the client open progress, upload the agreed reference and respond to the brief. For a proof, create the file proof, assign reviewers versus approvers, request a specific annotation, then upload a revised version. Teamwork keeps comments with their relevant version and marks the proof approved only after all designated approvers approve. Use one actual decision maker as an approver; extra observers should not accidentally block final acceptance.

The current pricing names are Basics, Accelerate, Optimize and Enterprise. Accelerate advertises workload/capacity, time budgets and retainers, plus invoices from logged time. Optimize is quoted and adds financial/multi-currency budgets, revenue/cost/profitability insights and more advanced staffing. Help pages still use Deliver, Grow and Scale for some entitlements. Preserve that conflict in the trial request: ask the vendor which new plan grants the documented client and profitability permissions in the proposed account.

Teamwork’s reporting documentation calculates billable value from billable hours and rates and cost from logged hours, cost rates and eligible expenses. That is useful operational reporting, but it must be reconciled with fixed-fee revenue recognition and retainer accounting. Detailed profitability can expose cost rates through inference, even without a salary column. Avoid granting those views to a client simply because the client license is free. We have not independently established that its reporting is universally shallower or its adoption universally faster than Productive’s. current Teamwork plans; client-user constraints; proof versions; profitability definitions.

Monday: visual coordination with a declared finance owner

Monday’s boards, status columns and configurable automations can suit a team that currently abandons a complicated system. Adoption remains a real buying constraint: a partially suitable system with truthful daily updates can be more useful than an ideal configuration nobody maintains. We have not measured Monday’s relative adoption speed, however, so treat that as a workflow hypothesis to test with designers, account leads and finance.

Pro includes time tracking; budget management can be constructed with numbers, formulas, views and automations. Enterprise has a resource directory, resource planner, portfolio-level resource utilization report and capacity manager. That makes an unqualified claim that Monday has no capacity or utilization functionality incorrect. Higher-level resource allocation is still a different model from a ready-made agency rate-card, cost and invoice ledger.

Applied workflow: put the agreed fee, sold hours, logged hours and loaded-cost inputs on a project board. Define the formulas and one owner who reconciles them against the accounting record. In Enterprise, set the designer’s role and availability in the resource directory, add the project’s planner, and book effort across six weeks before accepting the next campaign. Check whether the planner’s allocations and task effort are separate so they are not counted twice. The account lead resolves conflicts with the delivery owner rather than interpreting a colored status as financial approval.

Standard guest billing uses groups of four guests as a billed seat, with the first three alone free; Pro and Enterprise guest policies differ. Plans begin with three paid seats and then seat bands can raise the purchased total above actual staff count. Quote the work-management product rather than silently substituting CRM or service pricing. The current price screen displays promotional Standard/Pro annual rates beside higher crossed-out totals; confirm the applicable offer and renewal before budgeting. Monday pricing; Enterprise resource controls; configured budget workflow; guest billing.

Asana: dependencies, workload and the current budget add-on

Asana is useful when a slipped task affects several deliverables and the producer needs to see the dependency chain. Timeline, dependencies, portfolios and workload belong in that trial. It now also offers a paid Timesheets & Budgets add-on on Starter and above. Current help documents currency budgets, project user rates, billable/non-billable status, timesheet submission/review and time/cost reporting. The older categorical claim that Asana has no budget currency or rates is outdated.

Applied finance setup: the project administrator opens Set project budget, chooses hours or costs, and sets the relevant people and rates. Add the planned delivery effort and log actual time against one attributable project, avoiding duplicate financial counting when a task belongs to several projects. Configure the billable default and approval process deliberately. Set a chosen progress threshold notification, then inspect actual costs by all time as well as billable time so unpaid revisions do not disappear.

In Dashboard, add a time-entry widget, choose Time or Financials, and group by working date or staff. Select whether estimates come from tasks, capacity plans or both; do not count both sources for the same effort without reconciling them. Cost visibility belongs to project administrators. Enterprise/Enterprise+ capacity plans and placeholders remain base-license features; buying the add-on does not grant every enterprise resource view.

Advanced also supplies image and PDF proofing. Open an attachment, choose Add Feedback, click the affected area and turn the feedback into an assigned subtask with a due date. That is a documented native proofing mechanism, though it is not identical to Wrike’s timecoded-video/version comparison. Keep billing and invoice production scoped to what the proposed Asana/accounting workflow actually demonstrates. Organization guests and generic workspace participants have different billing treatment, and paid subscriptions start at two seats with larger seat increments. Asana plans and add-on price; add-on controls; budget and rate setup; time-entry reporting; image/PDF feedback.

ClickUp: broad tools with a configuration responsibility

ClickUp combines tasks, docs, forms, whiteboards, time tracking and dashboards. Unlimited includes native time tracking and resource management; Business adds advanced dashboard cards, portfolio workload and unlimited proofing in the current comparison. Its time workflow can distinguish billable entries and report filtered hours. This breadth is useful for a team that can maintain its own project model, but a large feature list does not itself define revenue recognition, loaded costs or a reconciled margin report.

Applied trial: create a repeatable client/project hierarchy, attach the approved brief in a doc, collect new requests through a form and assign each request to a scope owner. Log the first extra revision separately and classify its time. Build a dashboard that displays the relevant project’s sold hours and actual hours, with the rate/cost source documented. Reconcile a sample export against the timesheet and your finance record before calling the dashboard a profitability view.

Use a whiteboard for territory exploration and proofing for localized feedback; keep those artifacts linked to the delivery task instead of treating every comment as a new billable authorization. Test guest permissions and paid-versus-free guest entitlement with the real client actions required. Upgrading a paid workspace affects its member scope rather than granting an isolated feature to one chosen person. Leave optional Brain/agent consumption outside the base-tool total unless the team actually needs it.

The trade-off is ongoing configuration ownership: someone must maintain IDs, rate definitions, dashboard formulas and reporting periods. We do not repeat unverified claims that ClickUp is uniquely unreliable or universally slower at scale. Run your largest relevant workspace and export test, then judge the actual result. An affordable setup that demands constant reconciliation may cost more in staff time than its subscription saving. ClickUp current pricing and capabilities; time tracking and billable filters; Timesheets Hub.

Wrike: prove the review round and the financial plan separately

Wrike belongs on the shortlist when a large review volume creates expensive ambiguity. Its documented proofing supports annotations on images and documents, video comments tied to time, new versions, comparison and approval workflows. Guest review can give an external reviewer limited proof access without a full internal seat. Supported formats and upload sources matter; verify the actual campaign file rather than extrapolating from a screenshot demonstration.

Applied review: attach the campaign asset to its task, invite the decision maker with the intended review/approval permission and request one localized comment. On video, tie the comment to the relevant time instead of “near the end.” Upload the revised version under the same artifact, use the Compare control for the supported side-by-side view, and verify which version each comment refers to. Set an approval route and confirm that the human decision remains attached to the final asset, not an obsolete export named FINAL.

The finance layer is plan-dependent. Business includes resource/capacity planning; Pinnacle advertises budgeting with bill and cost rates and advanced reporting/BI. The source’s blanket description of inherently partial financials needs that current qualification. Test a specific fixed-fee project, one expense, one unpaid revision and a client aggregation on the quoted plan. Ask how invoicing and accounting integration work; an integration such as NetSuite is not proof that the base product issues every required invoice itself.

Evaluate navigation and setup effort with the actual reviewers, not a universal claim that Wrike has the worst adoption. Teamwork, Asana and ClickUp also have real proofing capabilities, so choose Wrike for the mechanisms and permissions your assets need rather than an inaccurate exclusivity claim. Current Team allows two to fifteen users, Business five to two hundred, and financial Pinnacle/Apex prices require contact. Wrike proofing and versions; external review and comparison; Wrike financial and resource plan boundaries.

Storyflow: settle the creative argument before scheduling it

Storyflow’s role here is the creative workspace preceding financial delivery. Use a shared canvas to connect the brief, reference material, territories and concept options. That can reduce the risk that the account lead schedules a campaign nobody has actually agreed to make. It is not evidence of native agency timesheets, financial budgets, rate cards, profitability, utilization, resource bookings or invoicing. A view/edit board link is collaboration, not the same thing as a cost-controlled financial client portal.

Applied board: add the approved Campaign Brief and a Target Audience reference, then write: “Build three campaign territories for Harbor’s refillable travel bottle. Keep each territory tied to the audience problem, substantiated benefit, required assets and decision owner. Treat the fee and hours as creative constraints; do not invent a financial ledger or claim client approval.” Inspect the proposed cards before accepting them. Type @ to select a relevant Tactic, attach the intended documents/boards and request a revision using that context. Ask for a mind map connecting audience need, promise, proof and channel ideas. The producer then exports or shares the selected creative decision with the delivery system’s owner.

The older article says one Tactic and three documents. Current creator copy advertises five documents and three additional boards; it does not establish a current Tactic attachment cap in the retained text. Verify that account control rather than merging historical limits into a new claim. Pro/Max add image generation and conversation memory, while Max adds shared-workspace roles/permissions. AI actions remain usage-metered. A generated concept and a remembered decision do not become signed scope or approved spend.

Current pricing says paid early access, with invited collaborators of a paid member joining free and a standalone Free plan planned before the end of 2026. Some surrounding calls to action still say “free”; the pricing FAQ’s explicit early-access qualification is more useful than reproducing a contradictory button promise. The published Plus/Pro/Max rates appear in the cost section. This page’s local workbench is separate and does not call Storyflow AI or charge a generation. Storyflow plans and early-access FAQ; current creative context description.

Price the required capability, including unused seats

These are dated public USD list-rate comparisons checked on 7 October 2026, not personalized checkout, renewal, tax or sales quotes. Annual equivalents are multiplied by twelve for the committed year. Amounts exclude tax, exchange conversion, optional AI, implementation and accounting/proofing add-ons. A low entry tier does not automatically include the financial/reporting capability you need.

Productive’s static page text mixed hidden billing cards and stale totals. The rendered annual/monthly controls gave the rates above with matching ten-user totals of $100/$250 annual equivalents and $120/$290 monthly. Teamwork’s localized digit animation did not expose ordinary visible digits consistently; the official plan data and current official comparison corroborate $9.99/$24.99 annual. Its old structured offer still named Grow, so this guide uses the new named plans and keeps help-page conflicts explicit. Do not use an old cached offer as a private checkout guarantee.

Five practical costed starting setups

1. One independent operator with a financial spreadsheet: this browser workbench has no added subscription charge. ClickUp Unlimited’s public one-member rate is $7 annual equivalent ($84/year) or $10 monthly if that workspace scope is applicable. A solo FunctionFox Classic or Productive Essential purchase still buys three seats: $31.50/$378 annual or $30/$360 annual respectively; monthly totals are $38.25 and $36. Asana Starter’s two-seat floor is $21.98 equivalent/$263.76 annually. Compare the useful answer with the extra administration rather than buying a nominal one-user rate that cannot be purchased.
2. Five-person focused studio: FunctionFox Classic costs 5 × $10.50 = $52.50 equivalent/$630 yearly, or $63.75 month-to-month. Premier’s schedule/availability scope costs $80 equivalent/$960 yearly or $96.25 monthly. The difference is $27.50 equivalent per month annually; trial the schedule before assuming the extra plan pays for itself.
3. Five-person commercial operation: Productive Professional is 5 × $25 = $125 equivalent/$1,500 annually, or $145 monthly. That buys the stated recurring-budget/rate-card plan rather than merely quoting Essential at $50 equivalent/$600 yearly. If the agency requires annual wire transfer, the published ten-seat minimum makes Professional $250 equivalent/$3,000 yearly even for five actual staff.
4. Five-person delivery workspace with financial add-on: Asana Starter plus five Timesheets & Budgets licenses is 5 × ($10.99 + $5.99) = $84.90 equivalent/$1,018.80 yearly. Advanced plus that add-on is 5 × ($24.99 + $5.99) = $154.90 equivalent/$1,858.80 yearly. This compares those five assigned add-on licenses, not an unverified rule that every member must buy the add-on. Confirm the required reviewers/licenses and base-plan workload features. Five Monday Pro seats at the displayed $19 annual offer are $95 equivalent/$1,140 yearly; the crossed-out $22 equivalent would instead be $110/$1,320, so confirm offer duration. Neither base figure promises an entire reconciled agency finance workflow.
5. Twenty-two-person agency choosing the commercial layer: Productive Professional is 22 × $25 = $550 equivalent/$6,600 yearly, or $638 monthly. Teamwork Accelerate’s linear public rate subtotal is 22 × $24.99 = $549.78 equivalent/$6,597.36 yearly before any confirmed seat minimum or account terms; the current financial Optimize requirement needs a sales quote, so do not compare Accelerate as if it contains every profitability view. Asana’s documented increments round twenty-two base seats to twenty-five: Starter plus twenty-two $5.99 add-on licenses is $274.75 + $131.78 = $406.53 equivalent/$4,878.36 yearly, conditional on those assigned-license scopes. A twenty-five-add-on requirement would be $424.50/$5,094. Ask for the actual license proposal. Five Wrike Business seats are $125 equivalent/$1,500 yearly; a twenty-two-person financial Pinnacle setup remains quoted rather than inferred from Business.

Add a creative layer only when it has a job: one Storyflow Pro creator subscription is $168/year. Five FunctionFox Premier users plus that single creator plan total $960 + $168 = $1,128/year, not five times $168 when the collaborators are eligible free invitees. Paid roles, team permissions and AI allowances still need checking; a single creative subscription does not include an agency financial client portal.

Primary pricing: Productive, FunctionFox, Teamwork, Teamwork minimum-seat comparison, Monday, Asana, Asana seat increments, ClickUp, Wrike, Storyflow.

A six-week pilot for a twenty-two-person agency

The following is a fictional planning scenario retaining the useful scale of a twenty-two-person brand/campaign agency handling about forty projects a year. It is not a report of an observed Productive or Teamwork customer trial. The agency has a generic task system and disconnected finance sheets; its finance lead cannot explain last quarter’s project margins consistently.

Shortlist the actual financial Productive and Teamwork plans, including a quote where needed. Run the same two live projects through the six-week pilot: one fixed-fee campaign and one retainer or revision-heavy engagement. Avoid judging products on different datasets. The producer performs time entry, the account lead invites a real client, and finance reconciles the sample report to the cost and revenue record. Record which configuration was required, how long each real workflow took and what remains unproven.

In week four, suppose the agency discovers 61% measured billable utilization rather than the assumed 75%. The gap is fourteen percentage points, not “fourteen percent less.” If all twenty-two people actually had forty available hours for each of six weeks, total availability would be 5,280 hours; 75% represents 3,960 billable hours and 61% represents 3,220.8, a gap of 739.2 hours. A mixed agency with directors, leave and part-time staff must replace that denominator with actual available hours. Do not apply delivery-role targets to the entire payroll.

Investigate two accounts with unbilled scope rather than labeling the team idle. Check the individual entries for extra rounds, sales/admin work and forgotten billing status. A billable label is a classification, not proof of authorization or payment. Choose the platform only after the money question reconciles and people can maintain the daily record. Neither adoption difficulty nor inaccurate rates disappears on an automatic six-week deadline.

For migration planning, budget a fictional eleven-week window and ninety hours of owner effort as a starting estimate, then replace it with a measured backlog. Inventory two years of required finance records separately from low-value old tasks. Retain contractual, financial and compliance records; migrate only useful task history after testing links and permissions. The example’s decision to preserve finance without importing every historical task is a scope lesson, not a rule to delete the past.

Decisions to record before buying

• Can finance explain one project’s fee, recognized revenue, loaded labor, expenses and remaining estimate without reconciling incompatible definitions?
• Can the producer log time daily and find one unquoted revision without rebuilding a dashboard?
• Can the client review the intended version without seeing internal cost information?
• Can the delivery lead answer whether a new six-week commitment fits, including leave and existing bookings?
• Can the owner download complete source and recover it if the chosen setup changes?

Utilization measures a period, a role and a denominator

Billable utilization is billable actual hours divided by available hours for the same period. Decide what unavailable means before measuring: leave, part-time schedules and known exclusions must not drift between teams. If internal meetings remain in available hours, their logged non-billable time lowers utilization; if you exclude them by policy, document that policy rather than making the denominator smaller only when a result looks inconvenient.

The original’s ranges can be useful illustrative planning targets: delivery staff 70–80%, senior/lead roles with sales responsibility 50–65%, directors/principals 20–40%. They are not verified industry-wide benchmarks here. Calibrate against your own service model, non-billable obligations and quality. More than about 85% can be a chosen slack warning, but it is not an automatic medical or burnout diagnosis. Missing buffer for sickness, training, sales and creative thinking deserves a conversation.

Read utilization with contribution. High billable utilization and poor contribution can indicate underpricing, expensive delivery, repeated work or an inappropriate revenue definition; it does not prove the team is slow or that rates alone are wrong. Low utilization can reflect business development, admin, unpaid client favors or missing entries rather than idle capacity. Role-level charts and original notes make those explanations testable.

In the workbench, bookings show commitments while actual dated time produces utilization. The fictional demo contains aggregated illustrative hours, not believable single-day timesheets; replace them with actual daily entries before making a decision. Zero available hours yields an undefined percentage instead of an invented zero. A person’s one entered rate is a scenario snapshot for all their entries; preserve separate periods/scenarios when rates change, because this is not an effective-dated payroll system.

Scope leaks through small decisions

Four patterns deserve their own labels in your time records. A third revision round follows two quoted rounds because it feels easier than negotiating. Forty fifteen-minute favors accumulate into ten hours. A stakeholder arrives late and reopens an approved direction. A retainer absorbs additional formats and tasks until its deliverables no longer resemble the agreed monthly service. Logging only “design” makes these different causes invisible.

At a loaded cost of $60/hour, forty quarter-hour favors cost $600. At a potential bill rate of $100/hour they represent $1,000 of possible billable value, but neither value automatically becomes client debt. The account owner checks whether the request was included, explicitly authorized as extra work, absorbed as goodwill, or declined. Keep that decision and its date next to the entry.

Set a conversation threshold such as 75% of sold hours, chosen by the project owner. When burn reaches it, compare remaining deliverables and the owner’s progress estimate. Name the person who will speak to the client, draft the change request, identify the affected date/fee and record the outcome before the next unquoted round. Specialist budget controls and Asana’s current add-on can provide real threshold workflows; configured general tools need their budget definitions and automation tested. This local tool only displays a flag.

For the late stakeholder, repair the briefing/approval path: name the decision maker, consolidate feedback, publish the accepted version and decide whether reopening changes scope. For the small favors, create a visible request bucket so nobody must reconstruct them at invoicing. A budget alert supplies evidence for the conversation; it cannot supply the client’s agreement.

Retainers need written rollover rules and a rolling view

A monthly fee should have a stated service scope, capacity or planning allowance, even when the purchased outcome is not simply a bank of hours. Define what requests are included, how overages are decided and whether unused capacity rolls forward. A client using sixty percent of July’s allowance does not automatically acquire forty extra August hours. That consequence belongs in the contract, not an inferred dashboard rule.

Use a filled three-month example: 100 planning hours each month, 60 actually used in July, 120 in August and 110 in September. Total use is 290 against 300 planned hours, or 96.67%; the average is 96.67 hours per month. At a $10,000 fee each month, total fees are $30,000 and fee divided by the 290 used hours is about $103.45 per hour. That last ratio is an effective fee-per-hour, not profit: costs, expenses and accounting recognition still matter. July alone would understate the later pressure.

Create period-level attribution for each request and inspect the rolling three calendar months. A missing August is not a complete three-month window made up from an older June entry. The workbench marks incomplete windows and does not silently carry unused hours. Month one can be under while month four becomes over; a regular rolling review is more informative than waiting until a client challenges a fee increase.

The original claim that every compared tool requires a manual retainer workaround is no longer accurate. Productive has recurring budgets and optional rollover; FunctionFox lists retainer tracking; Teamwork Accelerate advertises retainers. If the chosen setup lacks the precise contract logic, a separate monthly project with an explicit allowance remains a workable method. Test period boundaries, automatic drafts, carryover and reporting with an actual over/under month before treating native retainer support as a complete contract engine.

Attribute expanding work to its original request rather than hiding it in an undifferentiated retainer bucket. After a rolling review, the account lead can propose reduced scope, a revised fee or a separate project. The packet documents assumptions and figures; human approval remains outside it.

Software gives you evidence; management changes the outcome

Four problems remain yours. Underpricing requires a new commercial decision; a report only exposes it. A client ignoring scope requires a documented conversation. Friday timesheets reconstructed from memory require a better daily capture habit. An over-service culture requires someone senior to define finished work and hold the boundary. A negative dashboard cannot make those choices for the agency.

Choose by shape as well as size. A freelancer or two-person studio may be served by a timer and this sort of ledger, although complexity can justify a specialist earlier. A three-to-fifteen-person studio can trial focused FunctionFox setup. A growing fifteen-to-fifty-person agency can compare Productive’s commercial loop with Teamwork’s external delivery. Fifty-to-two-hundred-person operations need a named configuration owner, rate policy and rollout plan rather than merely buying more seats.

A heavy review bottleneck points toward the required Wrike or other proofing mechanisms. An abandoned existing system points toward a simpler coordination setup, potentially Monday, with a declared finance owner. An agency happy with Asana should test the actual budget add-on before migrating just because an older article says financials are absent. A production company may need production scheduling, crew, locations and shoot-specific cost controls instead; agency person-hours are not the whole unit economics of a shoot.

A staged migration that keeps the evidence usable

1. Time first, two to four weeks as a planning window. Log actual daily work on existing projects. Audit coverage and classification rather than claiming a complete margin from incomplete data. Appoint a person who resolves ambiguous project attribution.
2. Budgets on new work first. Connect the approved scope, fee, sold hours and owner before delivery starts. If a live project must be brought in, record the opening balances and missing-history boundary instead of forbidding all retrofits or pretending history is complete.
3. Rates and cost policy. Define loaded cost, overhead allocation, customer rates, expense dates and approval responsibilities. Test one calculation manually. Record when a rate changes and whether the reporting system preserves the intended historical treatment.
4. Report after a complete cycle. Reconcile one complete project before extrapolating a service/client trend. Read partial-cycle results as provisional. Measure margin by project/client, revision rounds, billable/non-billable hours by role and quoted-versus-actual hours by service.
5. Recoverable history, deliberately scoped. Export required financial/contracts/approvals and preserve their links and permissions. Trial a small migration, verify record counts and a complete sample, and retain an accessible source backup. Skip low-value task history only after deciding what must remain available.

A quarter or the fictional eleven-week/ninety-hour example is a planning estimate, not a guaranteed duration. Record setup effort, concurrent obligations and rollback criteria. The first milestone is a truthful time record; the final milestone is a maintained commercial view and a recoverable handoff.

Six filled creative templates that can hand off to a budget

These are freshly authored examples for the six exact template applications named in the original. The fictional Harbor travel-bottle campaign uses them as linked decision artifacts, not six disconnected generic lists. The creative owner approves the content; the producer transfers the approved scope into the delivery system. A template does not issue a purchase order or make an AI-generated claim substantiated.

In Storyflow, start from the corresponding template, place the approved evidence alongside it and use the chosen Tactic as context. Ask for proposed structure and inspect it before accepting. In a delivery system, transfer the approved artifact’s stable reference and responsibilities. This local financial workbench exports entered financial source; it does not generate or execute a campaign in a vendor account.

Original template entry points: Marketing Campaign, Campaign Brief, Marketing Plan, Target Audience, Advertisement Brief and Brand Strategy. Access follows the vendor’s current early-access and invitation terms.

Build and recover a complete internal planning packet

1. Set the window and currency. Choose an actual Monday and a three-letter currency. The source uses one currency; separate a second currency into its own scenario because the tool performs no exchange conversion.
2. Enter people and available hours. Add loaded cost and potential bill rate, then six separate weekly availability values. Keep rate/capacity assumptions in the multiline notes. Zero availability remains zero; it is not silently replaced with forty.
3. Enter the project’s financial basis. Record agreed fee, sold hours, recognized revenue to date, expenses and remaining-cost estimate. Leave remaining cost blank if unknown. The forecast must then stay unknown instead of assuming free completion.
4. Log actual entries. Attribute each entry to an existing person and project, with a real working date, hours and complete description. Classify billable time separately from entered internal approval. Unpaid favors still incur labor cost.
5. Book the next six weeks. Record commitments by person/project/week. Compare each week’s bookings with availability, then resolve the actual collision with its owners. Future bookings are not logged time or invoice value.
6. Review period retainers separately. Enter each client/month once and compare rolling calendar windows. Missing months stay incomplete. Retainer figures do not double-add revenue to the project ledger.
7. Read the boundaries. Contribution uses entered recognized revenue; potential billable value uses billable hours and entered rates; final contribution needs a remaining-cost estimate. Compare the project, client and role views before drawing conclusions.
8. Download the right source. JSON is the complete editable scenario. CSV is a field-by-field ledger with an explicit spreadsheet formula prefix policy; original JSON text remains unchanged. Markdown and self-contained HTML preserve the complete source and derived view, including long Unicode notes. The HTML packet uses system fonts, requires no library/network load and is an internal document containing sensitive costs.
9. Restore and verify. Pick the downloaded JSON. Invalid data is rejected without partial replacement. A file still reading cannot overwrite edits or a later selected restore. Download JSON again and compare the complete values, then reopen the full HTML packet. Row order is retained; referenced people/projects cannot be removed until their entries are reassigned or removed.

No PDF is offered here. The formats are named for what they really provide; an HTML packet is not a searchable PDF. Every description, direction, name, source identifier and note uses a multiline text control so paragraphs remain intact. There is no automatic server persistence, accounting integration or external notification. Your browser receives the library files to calculate the scenario; the tool does not upload your entered financial source as part of its operation.