A8gent
Pick A Narrow Agent Offer cover
Offer Design · Lesson 1 of 15

Pick A Narrow Agent Offer

The AI agent services a marketing agency can actually sell: how to pick one narrow workflow, scope it, and make the second build far cheaper than the first.

Sell an outcome, not access to a model

The fastest way to lose a marketing agency deal is to pitch "we will add AI to your business." Clients cannot picture what they are buying, cannot judge whether it worked, and cannot tell you from every other agency saying the same thing. The agencies that get paid sell one narrow workflow with a clear before and after, such as qualified leads added to HubSpot each week or a first-draft campaign report ready every Monday. The buyer should be able to repeat the offer to their business partner in one sentence without your help.

What a narrow offer looks like

A narrow offer names a single repetitive task the client already does by hand and the concrete result the agent produces. Strong candidates for marketing agencies include:

  • Client reporting: pull Google Ads, GA4, and Meta numbers into a drafted weekly performance report.
  • Lead follow-up: research an inbound lead and draft a personalized first reply for an account manager to approve.
  • Content production: turn a brief into first-draft ad copy, captions, or outlines against a brand voice guide.
  • Campaign QA: check live campaigns for broken links, wrong UTMs, or budget pacing issues and flag them.

Each of these has a visible input, a visible output, and a result the client can price against hours saved or revenue created.

The offer definition template

Before you pitch anything, fill in this one-page offer definition. If you cannot complete every line, the offer is not narrow enough yet:

OFFER DEFINITION - one workflow, one outcome

Offer name:        Weekly Client Reporting Agent
Client we serve:   Paid media agencies with 10-40 client accounts
Task replaced:     Analyst manually pulling Google Ads, GA4, and Meta
                   numbers into a weekly report deck
Input:             Connected ad accounts + GA4 property + report template
Output:            One drafted weekly report per client account,
                   ready for account manager review by Monday 9am
Frequency:         Weekly, per client account
Human checkpoint:  Account manager reviews and approves before sending
Success metric:    Analyst hours per report drop from 2h to under 15min
One-line pitch:    "We turn your ad platform data into a reviewed weekly
                   client report so your analysts stop copy-pasting numbers."
Out of scope:      Strategy recommendations, ad management, sending
                   reports directly to end clients

This document does triple duty: it is your pitch script, the top of your proposal, and the acceptance criteria for the build. When a prospect asks "can it also do X," you check the Out of scope line and quote separately.

Why narrow beats broad, in money terms

A narrow offer is easier to scope, because you know exactly what the agent reads and produces. It is easier to price, because the work is bounded. And it is easier to repeat, because the second client in the same niche reuses your discovery questions, review rules, and build. Here is what that repeatability does to your margin across the first three clients of the same offer:

Client Setup fee Build hours Cost at 75/h Setup margin
Client 1 (first build)4,500503,75017%
Client 2 (template reuse)4,500221,65063%
Client 3 (SOP + template)4,500141,05077%

A broad "AI transformation" promise never gets that curve, because every project starts from zero. The margin lives in repetition, and repetition requires a narrow, named offer.

Niche the offer by vertical, not just by task

The margin curve steepens again when you constrain the buyer as well as the task. "Weekly reporting agents for paid media agencies" beats "weekly reporting agents" because every client in the vertical uses the same platforms, the same report structure, and hears about you from each other. Your discovery questions, brand-voice rules, and n8n template all transfer with almost no changes, and your case study reads like the prospect's own business. Pick the vertical where you already have one happy client or the deepest domain knowledge, and stay there until the offer feels boring to deliver. Boring to deliver is exactly when it is most profitable.

Choosing between candidate offers

When two or three tasks all look automatable, use this decision table to pick the one you sell first:

Signal Pick it Park it
FrequencyWeekly or daily, per client accountQuarterly or one-off projects
Input predictabilitySame sources and shape every runWildly different case to case
Output checkabilityA human verifies it in under a minuteNeeds an expert hour to judge
Risk profileInternal draft a human approvesTouches money or goes to customers unreviewed
Before/after clarityObvious to a non-technical buyerNeeds explanation to see the value

How to choose your first offer

  1. List the tasks your clients already pay people to do every week.
  2. Keep only the ones with predictable inputs and an output a human can check in under a minute.
  3. Run the survivors through the decision table above and pick the one with the most left-column answers.
  4. Fill in the offer definition template completely, including the Out of scope line.
  5. Write the offer as a sentence: "We turn X into Y every week so your team stops doing Z by hand."

Common mistakes

  • Leading with the tool ("we build n8n workflows") instead of the client result.
  • Offering everything at once, so nothing is provable and every project is bespoke.
  • Choosing an exciting one-off task over a boring weekly one. Boring and frequent is what pays.
  • Skipping the Out of scope line, then discovering every prospect assumed something different was included.

Get the offer narrow first. Every later decision about discovery, pricing, and delivery depends on knowing the exact result you are selling.

Where the reuse actually comes from

The margin table above is an illustration of a shape, not measured data, and the shape only appears if you deliberately build the reusable parts. Plenty of agencies deliver the same offer five times and see no curve at all, because each build was made from scratch with the previous one open in another tab. What transfers, and what does not:

Transfers almost entirely Transfers partly Never transfers
Discovery question setThe workflow skeletonTheir account structure and naming
Scope document and out-of-scope listPrompt and review rulesCredentials and access wrangling
Proposal and pricing structureReport templateTheir internal approval politics
Handover doc and training videoError handling and alertsData quality in their accounts

Read the right-hand column carefully, because it is where the second build overruns. Access wrangling in particular is stubbornly constant - waiting for someone to grant an ad account permission takes the same three days on the tenth client as the first. Build the left column deliberately after client one, while it is fresh: write the discovery questions down, save the workflow as a template, record a five-minute handover video you can re-record in fifteen minutes rather than rebuild in three hours.

One more honest note about the curve: the hours drop, but the price does not have to. You are selling the outcome and the reliability, not the hours. If you find yourself wanting to discount because "it was easier this time", you have slipped back into hourly thinking, which is the exact habit a narrow offer exists to break.

The four candidate offers, run through the table

Applying the decision table to the four offers listed earlier makes the choice concrete, and the result is not the one most agencies pick first.

Client reporting. Weekly per account, identical sources every run, checkable in under a minute by someone who knows the account, internal draft with a human approving. Five out of five left-column answers. It is also the least glamorous, which is exactly why it is the right first offer.

Campaign QA. Also strong - frequent, predictable inputs, and the output is a flagged list that is trivially checkable. Its one weakness is before/after clarity: the value is problems avoided, which is harder for a buyer to feel than hours saved. Sells better as an add-on to reporting than as a first offer.

Lead follow-up. Frequent, and the output is checkable, but the inputs vary enormously - every inbound lead is a different shape - and the risk profile is worse, because a draft reply is one careless click away from reaching a real prospect. Buildable, but a harder first project.

Content production. The one everybody wants to sell and the worst first offer of the four. Output checkability fails: judging whether a piece of copy is on-brand takes an expert, takes longer than writing it badly yourself, and is a matter of opinion - which means the acceptance criteria in your scope document cannot be written objectively. Sell it later, to clients who already trust you, with a named person as the arbiter of brand voice.

The pattern generalises: the offer with the most objective acceptance criteria wins, regardless of which is most interesting. If two reasonable people can disagree about whether the output is correct, you have bought yourself an argument at invoice time.

Discovery questions that stop you quoting blind

A narrow offer still meets a messy client. These eight questions, asked before you price anything, are what separate a build that lands in three weeks from one that drags for three months. Keep them as a fixed list - it is one of the assets that transfers to every future client.

DISCOVERY - ask before quoting, not after

Access
 1. Who can grant access to each data source, and how long
    did that take the last time someone asked?
 2. Is there anything I will need that only one person can
    approve, and are they available in the next two weeks?

The work as it is done today
 3. Walk me through the last time you did this by hand.
    (Watch them do it if you possibly can.)
 4. How long did that take, and who did it?
 5. What do you do when the data looks wrong?

The finish line
 6. Who signs off that the output is correct, and what
    would make them reject it?
 7. Show me two examples: one you were happy with and one
    you were not.

The exceptions
 8. How often does an unusual case come up, and what
    happens then?

Question three is the one that earns its place. What people describe and what people do are different, and the gap is always where the project overruns - the undocumented spreadsheet, the manual correction they no longer notice making, the one client account that is set up differently for historical reasons. Watching the work done once tells you more than an hour of description.

Question seven gives you the acceptance criteria in the client's own examples, which is far more useful than any adjective they might offer about quality. Put both examples in the scope document.

Selling it inside the retainer, or as a new line

Agencies have a choice consultancies do not: the client is already paying you monthly. There are two routes and they lead to different businesses.

  • Absorb it into the existing retainer. No sale required, no new budget approval, and you keep the efficiency gain as margin. This is the right move when the workflow is internal to your delivery - your analysts stop copy-pasting and your cost per account falls. The limit is obvious: you can only bank that once, and the client never learns to value the capability.
  • Sell it as a separate line. Slower, needs its own approval, and produces something the absorb route never does - a named product with a price, a case study, and a second revenue stream that does not depend on hours. This is the route if you eventually want to sell the offer to agencies that are not your clients.

A workable sequence is to absorb the first build, use the efficiency to fund a second one properly, and sell the third as a line item to a client who has watched the first two work. What does not work is pitching a brand new paid capability, with no track record, to a client who is already unhappy about this month's retainer.

A real offer definition, before and after

The template earlier is the finished form. Nobody's first draft looks like that. Here is what an agency actually writes on the first attempt, followed by the same offer after the discovery questions have been run - because the gap between them is where every overrun lives.

BEFORE - the first draft, written in a planning meeting

Offer name:        AI Content Assistant
Client we serve:   Our clients
Task replaced:     Writing content
Input:             Briefs
Output:            Content
Frequency:         Ongoing
Human checkpoint:  We check it
Success metric:    Faster content production
One-line pitch:    "AI-powered content at scale"
Out of scope:      -

Five defects, each of which costs real money later. "Our clients" is not a niche, so nothing transfers between builds and the margin curve never starts. "Writing content" covers blog posts, ad copy, and email sequences, which are three different builds with three different quality bars. "Briefs" has no defined shape, so every client's brief is a new integration. "We check it" names no person and no criterion. And the empty Out of scope line means the first client to ask "can it also do our newsletters?" gets a yes from whoever is on the call.

AFTER - the same offer, post-discovery

Offer name:        Paid Social Ad Copy Agent
Client we serve:   E-commerce brands running Meta ads, £20k-£100k
                   monthly spend, 3+ active campaigns
Task replaced:     Junior copywriter producing ad variant sets from
                   a campaign brief - currently ~90 min per set
Input:             Campaign brief in OUR standard form (5 fields),
                   the brand voice document, and the last 20
                   best-performing ads from the account
Output:            One variant set per brief: 6 primary texts,
                   4 headlines, 3 descriptions, each tagged to the
                   angle it tests. Delivered as a Google Sheet the
                   media buyer can paste straight into Ads Manager.
Frequency:         Per campaign launch, typically 4-8 sets/month
Human checkpoint:  Senior copywriter reviews and edits before it
                   reaches the media buyer. Named: Sam.
Success metric:    Time from brief to approved variant set drops
                   from 90 min to under 20 min, measured on the
                   first 10 sets.
One-line pitch:    "You send the brief, you get a reviewed set of
                   ad variants ready to paste into Ads Manager the
                   same day."
Out of scope:      Campaign strategy, audience selection, budget
                   decisions, uploading anything to Ads Manager,
                   any channel that is not Meta, and image or
                   video creative.

Three things make the second version sellable rather than merely longer. The input is standardised by you, not accepted in whatever form the client has - "our standard form, five fields" is the single highest-leverage line in the whole document, because it is what makes client two cheap. The output is described physically: a sheet with a stated number of items in stated columns, which means "done" is not a matter of opinion. And Out of scope names the adjacent things clients will ask for, especially the dangerous one - uploading to Ads Manager - which is the difference between a review-gated draft tool and a system that can spend a client's budget.

The scope conversation, in the words you actually say

Out of scope only works if you can say it out loud without sounding unhelpful. The request always arrives the same way, usually in week two, usually cheerfully. Here is the exchange, written out.

CLIENT: "This is great. Could it do our Google Ads copy too?
        That's basically the same thing, right?"

YOU:    "It could, and I'd want to build it properly rather than
        stretch this one. Two reasons.

        The Meta agent is tuned on your last twenty best Meta ads
        and it knows Meta's character limits and format. Google
        needs different source material and different constraints,
        so quality would drop the day I pointed it at both.

        And it changes what Sam is reviewing. Right now she checks
        one format she knows cold. Two formats in one queue is
        where review gets sloppy, and sloppy review is the only
        way this ends up embarrassing you.

        So: same shape, separate build. It's cheaper than the
        first one was, because the brief form, the review step
        and the sheet structure all carry over - I'd estimate
        about half. Want me to scope it for next month, or would
        you rather run this one for another few weeks first?"

Notice what the answer never does: it never says no, and it never says yes for free. It gives a technical reason and a quality reason, prices the extension against the original, and ends with a choice between two versions of yes. That structure works because the client's underlying question is not really "will you do this" - it is "am I going to be nickel-and-dimed". Naming the reuse discount answers that directly, and it happens to be true, which is why it survives scrutiny.

The failure mode to avoid is the reflexive "sure, I'll add it". It costs you the second sale, it degrades the first build, and it teaches the client that scope is negotiable in the direction of free.

What goes wrong in the first three deliveries

The offer definition is a bet. These are the ways it comes back wrong, and what each one means, because the correct response to most of them is to change the offer rather than to work harder on the build.

What you observe What it means What to change
Client two took nearly as long as client oneNothing transferred - you built bespoke twiceFind what differed. It is almost always the input format. Standardise it before client three
The reviewer edits nearly every output heavilyThe quality bar was never written down, so the build aimed at the wrong targetGet the two example outputs from discovery question seven into the spec, and rebuild against them
The reviewer approves everything without readingThe checkpoint is decorative, and you now carry the risk you thought was theirsMake review require one specific act - tag each variant with its angle - so it cannot be done blind
Every client wants a different output formatThe offer is scoped around the task but not around the deliverableFix the deliverable and let clients adapt to it. An agency that ships one format is a product; one that ships nine is a service
The saving is real but nobody at the client noticedYou measured your own hours, not something the buyer feelsRe-state the success metric in the buyer's terms - turnaround time, launches per month - and measure it in front of them
Setup keeps slipping on access to dataDiscovery question one was skippedMake access a precondition to starting, with names and dates, not a task inside the project

The second and third rows are the pair to watch, because they look like opposites and are the same failure: nobody defined what good output is. Heavy editing means the reviewer knows the bar and the build missed it. Rubber-stamping means the reviewer does not know the bar either. Both are fixed upstream in the offer definition, not downstream in the prompt.

When a narrow offer is the wrong move

  • You have exactly one client and no plans for a second. The whole argument for narrowness is the margin curve across repeated builds. With one client, build whatever they need and skip the productisation.
  • The task you picked is about to be a platform feature. Ad platforms ship copy generation themselves. Choose workflows that join data across systems the platforms will not join for you - that is the ground they do not take.
  • Your delivery team cannot review the output. If nobody in the agency can tell a good output from a plausible one, you cannot sell a review-gated service, and a review-gated service is the only kind worth selling.
  • The client's process changes monthly. A narrow offer encodes a process. If the process is genuinely unsettled, you are building on sand, and the honest sell is a paid discovery to settle it first.

What you should be able to do now

  • Explain why an outcome-based offer beats "we add AI" in a client conversation.
  • Fill in the offer definition template for one workflow, including the out-of-scope line.
  • Use the decision table to choose between two candidate offers and defend the choice.
  • Show a prospect the margin math for why you sell the same offer repeatedly.
  • State your offer as a single before-and-after sentence a non-technical buyer can repeat.
  • Run the eight discovery questions before quoting, and get two example outputs into the scope document.

Where this goes next

This lesson and Build proof assets clients trust are the free part of the course: choose the offer, then earn the right to sell it. Fill in the offer definition template and run the discovery questions on one existing client this week. Both are free, both take an afternoon, and neither requires you to build anything yet.

The paid lessons cover the build and the business around it. The reporting agent end to end, including the data joins that actually break. Brand-voice systems that survive more than one writer. Review workflows so nothing reaches a client unchecked. Pricing and packaging for agencies specifically, including how to price when the client can see your cost base. Selling into an existing retainer without devaluing it. Then delivery at volume: templates, SOPs, subcontracting, and the QA that keeps quality flat as client count rises. Every lesson ships the workflow files and the documents.

If you would rather have the system built than build it, that is a project we take on - see AI automation services, or start with the free automation audit to identify which of your delivery workflows is worth automating first. For pricing context, AI automation cost shows what this work goes for, and the proposal template is a working document rather than a teaser.

Leave your email below and both free lessons arrive with the offer definition template and the discovery question set as editable files you can take into a client call tomorrow.

Key takeaways

What to remember from this lesson

  • Sell one workflow outcome, not access to a model. The buyer must be able to repeat the offer to their business partner in one sentence without your help.
  • The margin lives in repetition. The same offer goes from 17 percent setup margin on the first build to 77 percent on the third - a bespoke 'AI transformation' promise never gets that curve.
  • Niche by vertical as well as by task. Same platforms, same report structure, and prospects who hear about you from each other.
  • Pick boring and frequent over exciting and rare. Weekly or daily per account beats a quarterly project on every line of the decision table.
  • The out-of-scope line is not paperwork. Without it, every prospect assumes something different was included and every project becomes bespoke.

Try it yourself

Run four candidate offers through the decision table

The decision table in this lesson is really a scorer, so score it. Four offers have already been answered against the five signals - each answer is either the pick-it column ('left') or the park-it column ('right'). Count the left-column answers and pick the offer you sell first. The answer is deliberately the least exciting one.

Write it

Write the one-line pitch a buyer can repeat

The test of a narrow offer is whether the buyer can repeat it to their business partner without you in the room. Write the one-line pitch as the lesson frames it: we turn X into Y every week so your team stops doing Z by hand. This checks structure only - whether the sentence names an input, an output, a rhythm and the work it removes. It cannot judge whether the offer is any good.

2 of 6 checks passing

  • Names what goes in (a source, a brief, a set of accounts)
  • Names the physical output (a report, a draft, a variant set, a flagged list)
  • Names the rhythm (weekly, daily, per launch, every Monday)
  • Names the manual work it removes
  • Avoids tool-led and hype words
  • One sentence, not a paragraph

These checks look at structure only, not quality. A prompt can pass every one and still be a poor prompt, so read it back and ask whether you would understand it cold.

Check yourself

The three choices agencies get wrong first

  1. You can sell a quarterly brand-strategy deck build or a weekly per-account reporting draft. Which is the better first offer?

  2. Content production is the offer most agencies want to sell first. What does the lesson say is wrong with it?

  3. Your third build in the same niche took 14 hours instead of 50. What should happen to the price?

Answer every question to mark.

Exercise

Fill the offer definition until nothing is left blank

45 min
  1. 1List the tasks your clients already pay people to do every week. Keep only the ones with predictable inputs and an output a human can verify in under a minute.
  2. 2Run the survivors through the decision table's five signals - frequency, input predictability, output checkability, risk profile, before/after clarity - and pick the one with the most left-column answers.
  3. 3Fill in the offer definition template completely: offer name, client we serve, task replaced, input, output, frequency, human checkpoint, success metric, one-line pitch, and out of scope.
  4. 4The success metric must be two numbers, a before and an after, in the same unit. If you cannot state the before, go and measure it.
  5. 5Write the out-of-scope line by naming the three things a prospect will most likely assume is included. Those are the ones that eat margin.
  6. 6Narrow the 'client we serve' line to a vertical, not just a company size, and say which platforms every client in that vertical uses.
  7. 7Say the one-line pitch to someone who does not work in your agency and ask them to repeat it back.

You are done when Every line of the offer definition is filled with no placeholders, the success metric is a before and an after number in the same unit, the out-of-scope line names three specific exclusions, and someone outside your agency repeated your one-line pitch back accurately after hearing it once.

Companion files

Offer definition template and decision table

The one-page offer definition, the candidate-offer decision table, and the three-client margin math - so you fill in the template rather than rebuild it from the lesson.

The free-preview pack includes the worksheet for this lesson for Pick A Narrow Agent Offer, plus the other free lessons of this course. No email needed.

Free preview pack - 4 KB zip

Check yourself

Answer before you reveal

Why is a quarterly high-value task a worse first offer than a weekly low-value one?Show answer

Frequency is what builds the margin curve and what makes the pain sell itself. Rare pain gets postponed forever, and a quarterly build never earns the template reuse that takes the second client from 50 hours to 22.

A prospect asks 'can it also handle X?'. What does the offer definition do for you in that moment?Show answer

You check the out-of-scope line and quote X separately. Without the line you either absorb it for free or renegotiate mid-project, and both destroy the margin the repeatability was supposed to earn.

What is wrong with leading with 'we build n8n workflows'?Show answer

It sells the tool, not the client result. The buyer cannot picture what changes, cannot judge whether it worked, and cannot tell you apart from every other agency saying it.

Free lesson notes

Get the notes pack for AI Agents for Marketing Agencies Course, plus every new module free by email.

No card, no spam, unsubscribe any time.