AI Get AI Superpowers
The 10-Hour Guarantee · Full Methodology

Save 10 hours a week within 60 days.
Or we work free. Or we refund.

Most consulting guarantees are written to be uncashable. This one isn't. We publish the baseline methodology, the measurement window, and the refund mechanics here so there's no ambiguity when day 60 arrives. If we haven't hit the number, you pick, keep working free, or take the money back.

The guarantee, in writing.

For each team member trained during the Installation, we guarantee a measurable savings of 10 or more hours per week on the originally-scoped workflows, within 60 days of Installation completion.

If we have not hit that threshold on day 60, you choose one of two options: (A) we continue working, building, tuning, training, at no additional charge until the threshold is hit, or (B) we refund every dollar paid for the Installation, processed within 5 business days.

How the hours get counted.

No black box. The methodology below.

Step 1 · Week 1

Baseline observation

We sit with each trained team member during their normal week. We watch and document how many hours they spend on the workflows being automated. This is the floor.

Step 2 · Week 1 (parallel)

5-day self-reported time log

Each team member tracks their own time on the targeted workflows for the same 5-day window. Two data sources, cross-checked. We use the higher of the two numbers as the baseline (favors you).

Step 3 · End of week 1

Baseline signed off

You countersign the baseline document. There's no debate later about what the starting number was, it's a signed artifact.

Step 4 · Day 60

Re-measurement

Same methodology, same workflows, same team members. We measure how many hours per week each one now spends on the originally-scoped work. The delta vs. baseline is the saved-hours number.

Step 5 · Day 60 decision

Pass or pick

If the delta is 10+ hours per trained team member, the guarantee passes and the Installation closes. If it isn't, you pick: free continued work, or a refund. We'd rather keep building.

Why we'll bet on this.

Five team members, ten hours each per week, fifty weeks a year, that's 2,500 hours of recovered capacity in year one, more than a full extra person's worth of time, on the same payroll.

The reason we can guarantee it isn't optimism. It's that Hermes Agent plus Claude Code, Cowork, and Design in skilled hands, against the kinds of workflows a typical 5-50 person business runs every week, quoting, follow-up, intake, scheduling, reporting, basic drafting, produces 10 hours a week of savings per trained team member without breaking a sweat. We've yet to find a business where the math doesn't work; we've found plenty where the team doesn't adopt, which is why we built the in-person training and the 90-day support window into the Installation.

A guarantee that can't be cashed isn't a guarantee. This one can be. The reason we sleep fine is the same reason an auto mechanic guarantees a brake job, at this point, we know what's under the hood.

FAQ

Edge cases

How do you measure the baseline?

Week 1 of the Installation, we sit with each of the up-to-5 trained team members and document how many hours per week they currently spend on the specific workflows we're automating. We do it by direct observation plus a 5-day time log. The baseline number gets signed off by you in writing before week 1 closes. There's no ambiguity later about what the starting point was.

What counts as a "saved hour"?

Hours that are no longer being spent on the targeted workflows. If the baseline says your scheduler spent 11 hours a week building routes by hand, and the day-60 measurement says she's spending 1 hour a week reviewing routes the agent built, that's 10 hours saved. The hours she now uses on other work don't count against the guarantee, saved means "reallocated off the targeted workflow," not "team works fewer hours."

What if my team refuses to use what you installed?

We'll work with you on adoption, that's part of the 90-day support. But adoption is a two-sided agreement. If a trained team member won't use the agents we built after multiple coaching sessions, that's a personnel decision on your side, not a guarantee trigger on ours. The guarantee assumes the trained team members are willing to use the trained system.

What if we don't have 5 team members?

The guarantee scales. For a 3-person team it's 10 hours saved per week per trained member, so 30 hours across the team. For a solo owner it's 10 hours saved for you. The principle is per-trained-person, not aggregate.

What if I add a workflow mid-install that we didn't scope originally?

Scope changes are fine, but the guarantee tracks against the original baseline of the originally-scoped workflows. New workflows added mid-install get their own scope and their own measurement, but they don't affect the original 60-day guarantee.

What does "work free until" mean in practice?

If at day 60 we're at, say, 7 hours saved per trained member instead of 10, we keep building, tuning, training, no additional charge, until we hit 10. There's no cap on how long. It's our job to get you there, and we'd rather work the extra two weeks than refund.

What if I want the refund instead of the extra work?

Your call. The guarantee is bilateral: at day 60, if we haven't hit 10 hours, you pick whether we keep going or you get a full refund. We've structured it so both options leave you whole. Most clients pick the extra work because the agents are already running and the hours are coming, but the refund is real and we'd issue it the same week.

How long after Installation does the 60-day clock start?

Completion day, which is the end of week 3 of the Installation. Day 1 of the 60-day clock is the day we hand off the SOPs and you sign the completion checklist. The 90-day support window starts the same day.

What's NOT covered by the guarantee?

Three things. First, hours saved outside the originally-scoped workflows, we don't track those, even though they often happen. Second, indirect benefits like "better customer experience" or "fewer mistakes", real, valuable, but not measurable on a stopwatch. Third, hours saved that exceed 10 per week per trained member, also valuable, but the guarantee floor is 10, not 25.

Send us one workflow.

A quick call shows you exactly how the math works on a workflow that's actually yours. Free, and the plan is yours to keep.