Almanac / Integrations
Payroll → Team capacity

Give the team time back.
Know what it is worth.

A proposed Gusto connection to put an authorized, aggregated cost behind recovered hours. More capacity is valuable—even when payroll stays the same.

Planned integration · Sample data. No live accounts connected.

AlmanacIllustrative workflow
You ask

What would three recovered hours per person mean?

For an illustrative team of 10, that is 1,440 hours a year. Capacity value is not a reduction in payroll.

1,440 hIllustrative annual capacity
Team size10 peopleIllustrative team
Net time recovered3 h / weekPer person, after review
Working weeks48Editable assumption
Payroll reduction$0 assumedNo headcount changes
Model your own assumptions
A little less busywork. A lot more possibility.
01

Count the review, too.

Time saved only counts after the work of checking, correcting, and approving it.

02

Keep salaries private.

Use an authorized blended team cost for capacity planning, not a public list of individual compensation.

03

Separate value from cash.

An hour recovered creates an opportunity. An expense avoided changes the cash picture.

The workflow

Useful from the first question
to the next decision.

  1. Set the baseline

    Choose the team, productive hours, and recurring work you want to measure.

  2. Model the change

    Subtract review time from automated hours. Use a conservative starting assumption.

  3. Validate in practice

    Compare actual effort before and after a pilot. Expand only when the quality holds.

Planned integration · This prototype uses sample data. No Gusto account is connected.

Aggregate delivery cost

Use authorized compensation and employer-cost totals to estimate a blended hourly delivery cost. Show team-level capacity to account managers, while individual compensation stays restricted to authorized finance users.

A useful first workflow

  1. Choose a reporting period and a named owner for the connection.
  2. Review the proposed client or team mappings before importing data.
  3. Keep source totals, imported totals, and unresolved records visible.
  4. Compare the result with the source system before using it in a client decision.

What the connection should not do

Gusto integration access requires provider approval. A future connection must be vetted and authorized; the current demo does not fetch employee data or process payroll.

The accounting or payroll platform remains the source of truth. A missing field, expired permission, or incomplete period should be shown as missing—not silently converted to zero. Any future write action would need a separately reviewed permission and an explicit approval step.

From data to a better decision

Use this information to ask whether the team can serve another client sustainably, which services consume too much effort, and whether automation frees time for strategy. Do not call recovered staff hours cash savings unless a real expense falls.

Read the agency margin guide → · Try the savings model →

Implementation reference

Gusto platform documentation ↗. Product scope, provider approval, geography, and permissions must be verified during implementation.

Before you connect

A few clear answers.

Can I connect a live account today?

Not in this prototype. The demo uses fictional clients and numbers. Live access requires a production integration, provider permissions, and an authorized account owner.

Does Almanac replace my payroll provider?

No. The payroll provider remains responsible for payroll. This proposed workflow analyzes authorized cost inputs and does not run payroll.

How should I evaluate it?

Start with a single workflow, a small client set, and a documented baseline. Compare effort, accuracy, and review burden. Use observed results rather than the sample numbers shown here.

See the work in context.

Explore a sample agency in Almanac. No account, payment, or real client data required.

Open the demo ↗Model your capacity