Ramp up an AI hire with a 30-day work plan

Give a Monthly Retainer one accountable owner, one representative workflow, staged access, scheduled review times, and a written 30-day acceptance record. Expand the role only after the work product, correction burden, approval path, and continuing owner time are visible.

Anthropic's guidance on effective agents recommends adding agentic complexity only when it improves the result. The same restraint applies to access and job breadth during the first month.

A Day Pass has one 24-hour availability window and its agreed priorities. A Sprint follows the milestones of its connected project. The 30-day sequence fits a continuing role, not every purchase.

The continuing role can replace human source gathering, brief assembly, routine checking, record updates, and follow-through inside its published function. A person still owns consequential judgment, approval, licensed decisions, and work outside that function.

Publisher disclosure: FidelicAI sells Day Pass, Sprint, and Monthly Retainer engagements for role-specific AI agents. Exact work, inputs, connections, checks, and limits depend on the current role.

Start with one job, not every possible use

Choose work that already occurs, has an authoritative source, produces an inspectable result, and can pause before a consequential action. Record the current human time and correction burden before the role begins.

Before the first run, record the maximum owner minutes allowed for the repeated workflow and the work product that must pass. Use that same ceiling at day 30. The buyer sets the ceiling from the job's cost and consequence; it cannot be invented after seeing the result.

For FARO, the AI SEO strategist, the first job might be a query-to-page map built from approved site and Search Console evidence. For SCOUT, the content operations lead, it might be an evidence packet and content brief from approved product and customer records. For ALEK, the executive operations chief of staff, it might be one weekly owner brief tied to the current priorities and decision register.

Do not ask the role to prove itself across unrelated jobs. A current production role has a published function. Work outside it needs another route.

The 30-day sequence increases access only after evidence

Keep output quality separate from job ownership

A strong draft does not prove that the role owns the job. The owner may still be gathering every source, restating every step, correcting repeated errors, and filing the result.

The management-overhead question supplies a fuller ledger. The finishability question supplies the acceptance test.

Corrections should change the right record

A wrong business fact changes the source record. A missing local rule changes the role context. A repeated product miss changes the provider method or narrows the assignment. A changed owner decision changes the approval record. A third-party outage changes the delivery state and recovery plan.

Do not teach the role around a broken source of truth. Do not hide a product miss as “more context needed.” The correction record should state the cause, affected work, fix, owner, and next verification.

NIST’s AI Risk Management Framework is voluntary governance guidance, not a staffing manual. Its useful transfer is to identify context, measure the important result and risk, and assign a response owner.

Set the work environment and retention boundary

The work-environment guide compares Slack, WhatsApp, and Microsoft Teams. Choose the accountable reader and governance requirement before the first delivery. The Slack guide covers channels and permissions.

Slack's app-permissions documentation provides the platform-level record for requested scopes. Inspect the exact installed app and test one allowed and one denied location.

The security page states current architecture and buyer responsibilities. The cancellation answer states which work and history remain. Set account ownership and retention before the role begins, not after a cancellation request.

End day 30 with a decision record

Keep the Monthly Retainer when the repeated job passes its checks, owner time is at or below the ceiling recorded before the first run, corrections reach the right record, permissions remain appropriate, and the approval boundary holds.

Narrow or end it when the buyer still directs every ordinary step, the result cannot be checked, the required work falls outside the current role, access risk exceeds the value, or a person should own the job.

Use the public rate board to compare the role’s Day Pass, Sprint, and Monthly Retainer. Use the current agent directory to inspect the role before granting access.