The Quota Desk
Sections
Quota design

Sizing account research hours before you hand them to AI

The honest estimate is records times decisions times minutes, plus the review time an approval gate adds. Here is the arithmetic, and when it stops holding.

In brief

  • The honest estimate is records times decisions times minutes, plus the review time an approval gate adds. Here is the arithmetic, and when it stops holding.

Sizing account research hours comes down to one formula: records, times the share that needs a human decision, times minutes per decision, plus the review time an approval gate adds. Run that sum before onboarding, not after. The onboarding tier you pick changes the review term, not the research term.

Most estimates skip the review term. That is where an approval-gated co-worker spends your hours, so it is where the estimate goes wrong.

What goes into sizing account research hours?

Four inputs. Count them separately, because each one fails differently.

  • Target accounts, and minutes of manual research per account today.
  • Records in the CRM, and the share that need a decision (merge, correct, delete) rather than a mechanical fix.
  • Minutes a human spends approving one proposed result.
  • One-time setup: the rules, guardrails and context written before the first run.

Here is a worked example. Every number is an assumption, none is benchmark data. A team has 160 target accounts at 20 minutes of manual research each: 3,200 minutes, or 53 hours. It has 4,000 CRM records, 10% needing a decision, at 4 minutes each to find and fix: 400 decisions, 1,600 minutes, 27 hours. Manual total: 80 hours a quarter.

Notice that the CRM data hygiene hours are half the research hours even though records outnumber accounts 25 to 1. Hygiene is mostly mechanical. Only the decision share costs human time, which is why sampling matters more than counting.

How do you convert records into hours with approval time?

Replace the manual minutes with review minutes. Assume the co-worker drafts each account brief and you spend 4 minutes approving it: 160 × 4 = 640 minutes, 11 hours. Assume each hygiene proposal takes 1.5 minutes to approve: 400 × 1.5 = 600 minutes, 10 hours. Add 6 hours of setup. Gated total: 27 hours against 80.

The saving is 53 hours. Be careful what that number is. A quarter of one person's time is about 520 hours (40 × 13), so 53 hours is roughly 10% of one RevOps headcount. It is not 10% of a seller. Those hours become selling capacity only if someone moves them there, and RevOps hours are not quota-carrying hours. Headcount and selling capacity are different columns, and this estimate fills only the first.

The review term also scales with volume in a way manual work does not. Double the target list and review time doubles. Approval-gated work is cheaper per item, not free per item. That is the part of sizing account research hours that vendor estimates rarely show.

What do the quick, standard and thorough tiers change?

The onboarding for Coco is built to elicit GTM context on purpose, in one of three depths: quick, standard or thorough. The public facts do not publish hours per tier, and this column will not invent them. What can be argued is the mechanism.

Context moves the rejection rate. A rejected proposal costs more than an approved one, because you correct it or re-run it. Assume a rejected item costs 5 extra minutes. At a 10% rejection rate that adds 0.5 minutes per item on average. At 40% it adds 2 minutes. Across the 560 items in the example (160 briefs plus 400 hygiene decisions), the gap is 1.5 minutes × 560 = 840 minutes, or 14 hours a quarter.

That gives a decision rule for sizing account research hours by tier. A thorough onboarding earns its place if it costs fewer than 14 extra hours and moves your rejection rate from 40% to 10%. If your first batch already clears 90% unedited, a quick onboarding is the cheaper answer. Whether a given tier delivers that shift is an empirical question for your data. The product is in private beta, so no tier has a track record to quote.

Every tier sits in front of the same gate. According to the product description, customer-facing actions such as sending an outbound sequence sit behind a hard approval floor with no bypass. Onboarding depth cannot buy you out of review on those steps, so budget the review hours at every tier.

Does credit pricing change the hours math?

It changes the cost math, which you should run beside the hours. The pricing page of one AI-native CRM vendor, Clarify, describes no per-seat cost and charges for AI work in credits, so spend tracks activity rather than headcount. A team plan from Viktor, per its changelog, is $100 a month for 40k shared credits, now rolling over for one month. Pricing for Coco is also credit-based, with an estimator on its site.

The planning point is the same across all three: your 560 items a quarter are also a credit forecast. Size the hours and the credits from one item count, and the two estimates cannot drift apart.

When does this sizing stop being true?

Three conditions break it, and each is testable.

First, the rejection rate. If more than 20% of the first batch needs edits, the review term is understated. Re-run the arithmetic with the observed rate.

Second, the decision share. If hygiene decisions are 20% of records rather than 10%, the hygiene hours double. Sample 200 records before committing to a number.

Third, volume. Review time scales linearly with items, so a list that doubles in size erases the headline saving.

Check all three against the first full batch, and no later than 2027-01-31. If the saving comes in under half of 53 hours, the formula held but the inputs were wrong, and the tier choice should be revisited. Same arithmetic, new inputs, stated plainly in the next column. Treat sizing account research hours as a number with an expiry date, not a plan.

Sources

  1. Clarify pricing — Clarify, 2026-11-15
  2. Viktor changelog — Viktor, 2026-11-15
  3. Coco — Coco, 2026-11-17