AI-Ops Starter Package: Turn One Automation Into a Billable Service

What This Builds

You've probably built a Zap or two for a client already and billed it as part of your regular hourly time, buried in a line item nobody notices. This guide turns that same skill into a named, scoped deliverable with its own one-page description and its own price, separate from admin hours. Once you can build the same automation a second time without starting from scratch, it stops being a favor you did once and becomes a service you offer to everyone on your roster.

Prerequisites

• At least one working automation you've already built for a client, or the confidence to build one from a guide like this role's lead intake automation
• A Claude or ChatGPT account for drafting the scope document and pitch
• An existing client relationship, or one prospective client willing to hear a short pitch

Total ongoing cost for this build: $20/month for the drafting account, plus whatever Zapier tier the underlying automation itself needs (see that automation's own prerequisites for the specific plan).

The Concept

Think about a contractor who used to bill by the hour for every task, then started quoting a flat price for a finished deck instead. The work is similar, but the pricing conversation changes completely once the client is buying an outcome instead of your time. The same shift applies here. The first time you build a lead intake automation, it's custom labor. The second time you build the same structure for a different client, it's a product with a name, a scope, and a price tag that has nothing to do with how many hours the client thinks you spent.

Because the deliverable you're packaging moves customer or lead data between systems, the scope document itself should state plainly what data flows where, so the client can check it against their own privacy policy before signing off. When you draft the one-pager with Claude, describe the automation generically and leave out a real client's actual customer names or account details. A template built from one client's live data is a template you can't safely reuse for the next one.

Build It Step by Step

Part 1: Pick one automation and write down its scope

1. Choose one automation you already know how to build well, such as a lead intake Zap, a follow-up sequence, or a CRM sync.
2. List exactly what's included: which triggers, which actions, which tools it connects, and what the client receives at handoff (a working Zap, documentation, a short training call).
3. List what's explicitly NOT included, such as ongoing edits after week one, connecting additional forms, or troubleshooting issues caused by the client changing their CRM setup later.

Part 2: Draft the one-page scope document with AI

1. Open Claude and paste this prompt, filling in your own details from Part 1:

I'm a virtual assistant packaging an automation I already know how to build
as a fixed-scope service offering, separate from my hourly admin rate.

The automation: [describe what it does, e.g. "captures new leads from a
website form, drafts a personalized welcome email with AI, and creates the
contact in the client's CRM"]

Included: [list from Part 1]
Not included: [list from Part 1]
Typical build time: [your estimate]

Write a one-page service description a small business owner could read in
two minutes. Include a plain-language name for the package, a short
paragraph on the problem it solves, a bulleted list of what's included,
a bulleted list of what's not included, and a closing line inviting them
to ask questions. No pricing numbers; I'll add my own rate separately.
Keep the tone confident and specific, not salesy.

1. Read the draft, correct anything that overstates what the automation actually does, and add your own rate to the finished document afterward.

Part 3: Draft the pitch and set your terms

1. Ask Claude to draft a short email or talking points for introducing the package to an existing client, referencing the actual time-consuming task they currently deal with by hand.
2. Decide your terms before the conversation: a flat project fee for the build, and whether ongoing monitoring is included or billed separately as a small monthly add-on.
3. Send the scope document alongside the pitch, or walk through it live on a call, and get written agreement on scope before you start building anything client-specific.

Real Example: Packaging the Lead Intake Automation

Setup: You already built the lead intake automation from this role's other Level 4 guide for one client. You decide to offer the same structure to a second client who runs a small online store and still manually replies to every contact form submission.

Input: You use the Part 2 prompt with Claude, describing the automation and its scope.

Output: Claude drafts a one-pager titled "Lead Response Starter," describing how it catches new leads instantly, drafts a personalized reply, and logs the contact automatically, with a clear "what's not included" section covering ongoing form changes.

Time saved: The build itself takes about the same time as before, since you're reusing a structure you already know. What changes is the conversation: instead of an extra unnoticed hour on an invoice, it's a named deliverable the client can see and value on its own.

What to Do When It Breaks

• The automation goes quiet after handoff and nobody notices → Once this becomes a client deliverable, a silently failed Zap is now a broken promise, not just your own missed task. Build a monitoring step into the scope itself: either you check Zap History on a set schedule and it's stated in the document, or the client agrees to flag it the moment leads stop arriving.
• The client pushes back on a flat fee after years of hourly billing → Reframe around the specific hours the manual version currently costs them, using their own numbers rather than yours.
• Scope creep starts immediately → Point back to the written "not included" list from Part 1 and treat any addition as a small separate quote, not a favor.
• The AI-drafted one-pager reads like generic marketing copy → Feed Claude a real sentence the client has said about their current pain point. Specific language from the actual client beats a generic problem statement every time.

Variations

• Simpler version: Skip the formal one-pager and pitch verbally from a short bullet list, saving the AI drafting step for the follow-up email that confirms scope in writing.
• Extended version: Package two or three automations into tiers (a starter build, a build plus one month of monitoring, a build plus monitoring plus quarterly review) and let Claude draft all three descriptions in one pass for consistency.

What to Do Next

• This week: Pick your strongest existing automation and write down its scope using Part 1.
• This month: Draft the one-pager, pitch it to one client, and track whether the flat-fee framing changes how the conversation goes.
• Advanced: Build a small library of two or three packaged automations so a new client conversation can start with "here's what I already offer" instead of a custom quote from scratch.

Advanced guide for virtual assistant professionals. These techniques use more sophisticated AI features that may require paid subscriptions.