Artifact · v0 (format-only stub)

AI Augmentation Playbook

How SmartOne introduces AI tools into the annotation pipeline without reducing workforce, how the margin improvement is quantified, and how to present the augmentation strategy to enterprise buyers as a quality signal rather than a cost-cutting story.

2.2 · Workforce and Augmentation · artifact id: augmentation-playbook-v0.html · 2026-05-28 · v0 format stub

This artifact is a format placeholder. The Phase 2 engagement builds this playbook after the workflow map is complete. Augmentation decisions require knowing exactly which pipeline steps are candidates for AI assist before building a playbook for introducing tools. The structure below shows what the live playbook will look like.

The augmentation question from the call

"could you improve them if you increase the efficiency of your people? And if you do win that big contract, do you need to go out and hire three hundred more, or do you just need to hire a hundred more and you pocket a bunch." Amyn · ~32:55

This playbook answers that question with a specific implementation plan. The answer is not "yes, AI replaces workers." The answer is "yes, AI augments specific pipeline steps, which means each annotator can handle more volume at the same quality, which means you can grow revenue faster than you grow headcount." That is the margin expansion story. It is also the workforce protection story.

Playbook structure (when built)

Tool introduction sequence

Pipeline step	Augmentation tool	Implementation sequence	Quality validation	Workforce impact
[Step N: e.g., pre-labeling]	[Tool name or type]	[Pilot on work type X for 4 weeks; compare accuracy vs. human-only baseline; deploy if accuracy holds]	[Accuracy delta vs. human baseline; reprocessing rate change]	[Same headcount; higher throughput per person]
[Step N: e.g., routing]	[Tool name or type]	[Placeholder]	[Placeholder]	[Placeholder]

Margin expansion model

Scenario	Current throughput per annotator	With augmentation	Revenue at 300-person ramp	Headcount required
No augmentation	[N units/day]	[N units/day]	[$X]	300
Moderate augmentation (pre-labeling)	[N units/day]	[1.3N units/day]	[$X]	230 (+70 cost savings)
Full augmentation (pre-label + routing + QA assist)	[N units/day]	[1.6N units/day]	[$X]	190 (+110 cost savings)

Buyer-facing framing of augmentation

Enterprise buyers in 2026 are asking data vendors whether they use AI in their annotation workflow. The question is not suspicious; it is a quality signal inquiry. Buyers want to know whether SmartOne's annotators are assisted by pre-labeling tools that surface likely labels, or whether they are doing every annotation from a blank canvas. The answer affects consistency metrics.

The playbook includes a one-paragraph buyer-facing description of SmartOne's augmentation approach, tested against the messaging stress test framework.

What you need to send us to build this

Inputs needed. To build the live playbook: (1) the completed workflow map (prerequisite), (2) which AI tools you already use internally in the pipeline vs. which are entirely manual, (3) whether the founders have a position on AI augmentation vs. headcount growth (this is the alignment session question), and (4) what accuracy drop, if any, you have observed on pre-labeled vs. blank-canvas annotation tasks.