← Courses
Building an AI Agency
← Module 1
Module 2 of 8
Module 3 →
Intro
Scenario
Lesson
Context
Lab Build ~25 min
Intro

What You're Actually Selling

2 min read

A services list is not an offer. A rate card is not an offer. A portfolio of past work is not an offer. These are answers to questions the prospect hasn't asked yet. An offer answers the question they're already asking before they contact you: Can this person solve my specific problem, and do I understand what I'll get?

Most AI freelancers lose deals on the scope call — not because they lack skill, but because the client can't map what the freelancer does to what the client needs. The offer is what creates that map. A well-designed offer tells the client exactly what they'll receive, what it costs, how long it takes, and what happens if something goes wrong. It eliminates the mental work of deciding whether to buy.

AI agencies have an additional challenge: the client often doesn't understand what AI work produces or how to evaluate it. A strong offer resolves this upfront — it specifies outputs in terms the client understands, sets expectations about AI-generated content, and names the human oversight layer so the client knows they're not just receiving unreviewed machine output.

Portfolio artifact — Build
A three-tier service offer document: starter, core, and premium tiers — each with named deliverables, AI tool stack, estimated delivery timeline, and a NIST MAP risk summary for the AI components involved.
  • Distinguish between a services list and a structured offer
  • Design three tiers that address different client budgets and risk tolerances
  • Specify AI outputs in client-facing language that sets accurate expectations
  • Name the human oversight layer in each tier
  • Apply NIST MAP thinking to identify what could go wrong in each tier's AI components
Scenario

The Scope Call Graveyard

3 min read

An AI agency that specializes in content systems for B2B SaaS companies has a 40% close rate on inbound inquiries. For every ten discovery calls, six don't convert. Post-call surveys reveal a consistent pattern: prospects liked the agency, believed in their competence, but couldn't figure out what they were actually buying.

The agency's proposals were bespoke — each one written from scratch after a 60-minute discovery call. The process was time-intensive for both sides. The proposals described the work in technical terms: "AI content pipeline with prompt engineering and output review." Prospects didn't know what that meant in terms of what they'd receive. They didn't know if it was monthly or project-based. They didn't know what they'd do if the output quality wasn't what they expected.

Three of the six lost deals went to agencies with higher prices. Post-loss interviews revealed the reason: those agencies had a clear package structure. The prospect understood exactly what the starter package included, what it cost, and what would happen week one. The AI agency with the better technical approach lost because their work was harder to buy.

The agency redesigned their sales process around three pre-built offer tiers. Each tier had a name, a specific deliverable list, a price range, and a one-page summary they sent before the discovery call. Close rates increased to 68% within three months. The average deal size also increased — prospects who previously hired at low prices were upgrading to the core tier because they could see exactly what they were getting for the additional cost.

The offer did the sales work that the discovery call couldn't do alone.

Lesson

Anatomy of a Tiered Offer

3 min read

A tiered offer converts browser-of-options into buyer-of-specific-thing. The three tiers correspond to three client types: the client who needs to validate you with a small project, the client who's ready to commit to your core service, and the client who wants full coverage. Building all three forces you to be explicit about what each tier includes — and what it doesn't.

A starter tier is a validation purchase. The client is not sure you're the right fit. The starter tier removes the risk of a large commitment while still being worth your time to deliver. It should produce a single, tangible output the client can evaluate. It should complete in two weeks or less. It should not require extensive discovery — if it does, it's too complex for a starter.

The core tier is your primary business. It's what you would do if every client bought the same thing. Design it as a complete solution to the core problem your niche has — the one you identified in Module 1. It should have a repeatable process, a defined scope, and a clear handoff. The AI components should be standardized enough that you can deliver it consistently without reinventing the workflow each time.

The premium tier adds either depth (more of the same work) or coverage (additional services the core tier doesn't include). It's for clients who want end-to-end ownership transferred. The premium tier typically includes more human review, more governance documentation, and more explicit accountability for AI-generated outputs.

NIST AI RMF — MAP Function

Before finalizing any tier, run a MAP analysis on the AI components: What is the AI being used to produce? Who receives that output? What are the failure modes — ways the AI could produce inaccurate, biased, or incomplete outputs? What is the severity if that happens? For AI agencies, the MAP function is part of your offer design, not a separate governance exercise. It shapes your quality controls, your review process, and your liability terms.

NIST AI RMF — GOVERN Function

Every tier should name the human oversight structure explicitly. Who reviews AI outputs before they reach the client? At what stage? What are the escalation paths if output quality fails? Clients buying AI services need to understand they are not buying unreviewed machine output — they are buying a professional service that uses AI tools. The GOVERN function requires that this accountability structure exists and is documented, not assumed.

Context

Three Decisions Before You Publish

2 min read

Before your offer is ready to share with a prospect, three design decisions need to be explicit. Leaving any of them vague is where scope disputes and client disappointment originate.

Decision 1: What the client receives

Name the output in terms the client understands, not the process you use. "Ten blog posts per month" is a deliverable. "AI-powered content pipeline execution" is not. The client needs to be able to evaluate whether they received what they paid for. If you can't describe it in a sentence a non-technical buyer understands, the scope is not clear enough to sell.

Decision 2: What the AI handles vs. what you handle

Be explicit in your internal documentation (and selectively in your client-facing copy) about which parts of the delivery are AI-assisted and which require direct human judgment. This is not just transparency — it's risk management. When clients understand the AI's role, they have accurate expectations. When they don't, any AI-generated error feels like a deception. The MAP analysis from your offer design should drive this distinction.

Decision 3: What happens when something's wrong

Every tier needs a revision and escalation policy. How many revisions are included? What counts as a revision versus a scope change? What is the process if the client believes the output quality is below the agreed standard? Having this language in the offer does two things: it protects you legally, and it signals to the client that you've thought through what could go wrong — which is itself a governance signal that builds trust.

You'll apply all three decisions in the lab — building a complete three-tier offer with deliverables, AI/human split, and revision terms for each tier.

◆ Build Lab
Service Offer Design
~25 minutes · 3 tiers
What you're doing
You'll design a three-tier service offer for your niche. We'll work through each tier's deliverables, AI/human split, timeline, and pricing. I'll push for specificity and flag anything too vague to sell.
Roles
👤
You — Offer DesignerYou're building the offer for your agency. Use the niche from Module 1, or a hypothetical if needed.
🔍
AI — Critical ReviewerI'll challenge vague deliverables, flag missing governance terms, and help you produce something a real prospect could buy.
Framework — for each tier
Deliverable — what the client receives, in client terms
AI/Human split — what AI produces, what you review
Timeline — delivery window, not just a number
Price range — or pricing model if value-based
NIST MAP — failure modes in this tier's AI components
Revision policy — what's included, what's extra
Success criteria
A three-tier offer document specific enough that a prospect could read it and decide which tier to buy — without a discovery call.
Shift + Enter for a new line
✓ Module Complete
You've completed Module 2 of 8. Your service offer is your second portfolio artifact.
Next Module →