A8gent
AI Automation Agency BootcampGet full course
From Niche To A Clear Offer cover
Positioning Your Agency · Lesson 2 of 16

From Niche To A Clear Offer

A niche points at who you serve. An offer tells them exactly what they get, by when, and what it changes. Learn to write one that sells itself.

An offer is a promise, not a service list

Most new agencies describe what they do: "we build AI automations and chatbots." Buyers do not care what you do. They care what changes for them. A strong offer names a specific outcome, a rough timeline, and the workflow it replaces, so the buyer can picture the result before the first call. The difference shows up directly in your pipeline: a vague offer forces every prospect through a long education process, while a clear one lets them self-qualify before they ever reply.

The four parts of a clear offer

  • The outcome. The concrete result, stated in the buyer's language: "every missed call gets an instant text-back and a booked callback" beats "conversational AI system."
  • The workflow it replaces. Name the current painful process so they recognize it: the manual follow-up, the copy-paste reporting, the after-hours enquiries that go cold.
  • The scope. What is included and, just as important, what is not. This prevents the endless "can it also do" creep that kills margins.
  • The proof or guarantee. Early on this might be a simple promise: if it does not work in their tools, they do not pay the final invoice.

Write it with a fill-in skeleton

Draft your offer against this skeleton, then cut every word a busy owner would need to Google:

OFFER ONE-PAGER SKELETON

Name:        The [Outcome] Setup
             e.g. "The Lead Response Setup"

For:         [Type of business] that currently
             [painful manual workflow].

What you get:
  1. [Component in plain words, e.g. instant text-back
     on every missed call]
  2. [Component, e.g. enquiry logged to your existing CRM]
  3. [Component, e.g. booked callback on your calendar]

Not included: [The two or three tempting extras that are
              separate projects, named explicitly]

Timeline:    Live in [X] weeks from getting tool access.

Investment:  Fixed setup fee of $[X], then $[Y]/month to
             monitor, fix, and report on it.

Assurance:   If it does not work in your tools as described,
             you do not pay the final invoice.

Package it so it is easy to say yes to

Buyers stall when they have to imagine the whole project. Package the offer into a named thing with a fixed starting point. A named package feels finished and comparable, which makes the buying decision small. It also anchors the price to the package rather than to your hours, which matters more each time you get faster at delivery. Naming also gives referrals something to repeat: "you should get their Lead Response Setup" spreads; "they do AI stuff" does not.

Productized package or custom project?

Situation Lead with Reason
First 6-12 months, building repeatability One named package Repetition builds speed, proof, and margin fastest
Prospect asks for something adjacent but similar Package plus a scoped add-on Keeps the core repeatable while capturing the extra revenue
Large client wants a genuinely custom build Custom project at a premium Custom work is fine when priced for its true cost in time
Request is outside your niche entirely Referral or polite no One-off detours reset your learning curve to zero

Pressure-test it before you pitch it

  1. Write your offer as three sentences: who it is for, what changes, and roughly how long it takes.
  2. Remove every word of jargon. "Workflow," "integration," and "AI agent" are your words, not the buyer's.
  3. Read it to someone in the niche and ask them to repeat it back. If they cannot, it is not clear enough yet.
  4. Confirm you can actually deliver it with tools you know, such as n8n, Make, or Zapier, in the timeframe you promised.
  5. Sanity-check the price against the market: in 2026, typical AI automation setup fees run roughly $2,000 to $12,000 depending on scope, so a first named package in the $2,500 to $6,000 range is credible, not cheap.

A quick clarity test

THE REPEAT-BACK TEST (run with 3 people in your niche)

You read your offer aloud once. Then ask:
  1. "Who is this for?"           -> they name their own kind
                                     of business, unprompted
  2. "What would change for you?" -> they describe the outcome
                                     in their own words
  3. "What would you expect it
      to cost?"                   -> their guess is within 2x
                                     of your actual price

3/3 = pitch it this week.  2/3 = revise the weak answer.
1/3 or less = rewrite from the skeleton.

Designing the guarantee without betting the business

The assurance line in the skeleton deserves real thought, because it is doing heavy lifting in the buying decision. A good guarantee removes the buyer's biggest fear, which early on is not "will this be great" but "will I pay for something that never works." Guarantee the thing you fully control: that the workflow will run in their tools as described, or the final invoice is waived. Do not guarantee business outcomes you cannot control, like "30 percent more bookings," because their results depend on their call volume, their staff, and their market, none of which you own. Structure the guarantee around your payment schedule so your downside is bounded: with a 50 percent deposit and 50 percent on delivery, a waived final invoice caps your loss at time, not cash out of pocket. As your case studies accumulate, you can loosen the guarantee or drop it entirely, because proof replaces risk reversal. One more practical note: put the guarantee's exact trigger in writing ("works as described in the scope of work section 1"), so a vague feeling of disappointment cannot be invoked against a workflow that does exactly what was agreed. A guarantee with a precise trigger protects both sides; a vague one protects neither.

The skeleton, filled in

Here is the one-pager completed for the property-management niche from the previous lesson. The figures are illustrative - a first package priced inside the range noted above - but the structure and the wording are what to copy.

Name:  The Maintenance Intake Setup

For:   Residential property managers with 150-800 units, whose
       maintenance requests arrive by phone, email, and text into
       a shared inbox, and get triaged by hand every morning.

What you get:
  1. Every request - call, email, or text - lands as one ticket in
     your existing system, with the unit and tenant already attached.
  2. Urgent issues (no heat, water, lock-out, anything with a safety
     word in it) are flagged and texted to the on-call number within
     two minutes, day or night.
  3. Everything else is categorised, assigned to the right contractor
     list, and the tenant gets an automatic acknowledgement with a
     reference number.
  4. A Monday morning summary: what came in, what is still open, and
     what has been open longer than 3 days.

Not included:
  - Contractor scheduling and dispatch (separate project)
  - Rent, arrears, or accounting workflows
  - Migrating your existing ticket history
  - Anything that writes to your accounting system

Timeline:  Live in 3 weeks from the day I have tool access.
           Week 1 build, week 2 you test it on real requests,
           week 3 fixes and handover.

Investment: $4,500 setup, then $400/month to monitor it, fix
            breakages, and send you the monthly report.

Assurance:  If it does not do points 1-4 in your own systems, you
            do not pay the final invoice. Trigger is section 1 of
            the scope of work, in writing, before we start.

Read what makes it work. Nothing in "What you get" is a technology - the buyer never learns which tools are involved, because that is your problem, not theirs. The urgency rule is stated as the buyer would state it ("no heat, water, lock-out"), which only happens if you did the language research. The timeline names what happens each week, so "3 weeks" is a plan rather than a hope. And the assurance points at a written trigger, not a feeling.

The "not included" list is where the margin lives

New founders write this section apologetically or skip it. It is the most commercially valuable four lines on the page, and it does three jobs at once.

  • It ends the project. Without it, "can it also..." arrives in week two, and again in week four, and the three-week build becomes a three-month one at the same price. Every hour of that overrun comes out of your margin.
  • It sells the next project. "Contractor scheduling and dispatch (separate project)" tells a buyer that more exists without you pitching it. A meaningful share of second projects start as a line in someone's exclusions list.
  • It signals competence. A supplier who knows exactly where their work stops reads as someone who has done this before. Vagueness reads as inexperience even when it is generosity.

Write the list by taking your last three scoping conversations and noting every request that felt reasonable and would have cost you a week. Those are your exclusions. If you have not had three scoping conversations yet, list the adjacent systems in the niche - accounting, scheduling, payroll - and exclude the ones you have never integrated with.

Pricing the package: three anchors, none of them your hours

Hourly thinking punishes you for getting faster, which is precisely the thing a productized offer is designed to do. Price against these instead, in this order.

  1. The cost of the status quo. Use the arithmetic from the previous lesson, with their numbers. If the manual triage is costing them a meaningful multiple of your fee every year, the price argues for itself and you never have to defend it.
  2. What the alternative costs. The honest alternatives are hiring someone part-time, buying software that half-solves it, or doing nothing. Know the going rate for the role you are displacing in their market - it is public information in job adverts - and be able to state it plainly. A package priced well below a year of that role is an easy comparison for a buyer to make.
  3. Your own floor. Estimate the hours honestly, including the two you always forget: their delays waiting for access, and the fixes in week three. Multiply by what your time needs to be worth. If the floor is above what the first two anchors support, the package is wrong for this niche - either narrow the scope or change the buyer.

On the monthly fee: charge it from the first client, and be specific about what it buys. "Monitoring" is a word; "I check it every morning, fix breakages within one business day, and send you a monthly report of what ran and what needed attention" is a service. The recurring line is what turns a project business into a business, and it is far easier to include from day one than to introduce in month six.

The three objections, and honest answers

The same three come up in nearly every first conversation. Prepared answers are the difference between a call that ends in a proposal and one that ends in "let me think about it".

"Can you do it cheaper?" Do not cut the price for the same scope - it tells the buyer the first number was invented, and it prices every future client. Cut the scope instead: "I can do points 1 and 3 for $2,800 and we add the rest later." You keep the rate, they keep control, and the smaller project is a better first project anyway.

"How do I know it will work?" Early on, the true answer is that they do not, and neither do you with certainty - which is exactly what the assurance line is for. Say the guarantee, say its written trigger, and say the payment schedule that bounds their risk. A specific structure beats a confident adjective. If you have delivered something similar, describe what it does now, in operational terms, and only with the client's permission to name them.

"We'll do it ourselves / our IT person can." Sometimes true, and saying so costs you nothing. The real question is whether it will actually get built and maintained by someone whose job is already full. Ask when they last completed an internal project like this, and what happens when it breaks on a Saturday. If they have the capacity and the appetite, they are not your client, and finding that out on call one is a win.

The offer that is not ready, diagnosed line by line

The finished one-pager above is what you are aiming at. This is what the first attempt looks like, and it is worth reading closely because almost every founder writes some version of it.

BEFORE - the first draft

Name:       AI Automation Package
For:        Small businesses
What you get:
            - AI agents set up in your business
            - Automation of manual tasks
            - Integration with your existing tools
            - Ongoing support
Timeline:   Depends on the project
Investment: From $2,000
Assurance:  We work with you until you're happy
Not included: -

Six defects, and each has a specific commercial cost.

  • The name describes the technology. "AI Automation Package" is what you sell; it is not what they buy. Nobody repeats it to a peer, so it never travels by referral - which is the channel this whole business runs on.
  • "Small businesses" is not a buyer. After a lesson on niching, this line undoes it. The buyer must be able to read the For line and see themselves.
  • Every deliverable is a category, not a result. "Automation of manual tasks" cannot be checked off. Compare with a line the buyer could confirm on a Tuesday: "every maintenance request that arrives out of hours gets an acknowledgement within two minutes".
  • "Depends on the project" means the project has no end. An open timeline is an open scope wearing different clothes, and it is where a three-week build becomes three months.
  • "From $2,000" invites a negotiation you will lose. The word "from" tells the buyer that the real number appears later, once you know how much they can bear - which is exactly what they suspect and exactly what you want to avoid signalling.
  • "Until you're happy" is an unbounded liability. It sounds generous and it is the single most expensive sentence a new founder writes. Happiness has no trigger, no date, and no definition. A guarantee that points at a written scope clause is stronger for the buyer and safer for you.

The rewrite is not a copywriting exercise. Every fix above is answered by information you gather rather than words you choose: the niche research supplies the buyer and their vocabulary, the workflow sizing supplies the price anchor, and the scoping conversations supply the exclusions list. If the one-pager is hard to write, that is a signal the research is missing, not that the wording needs another pass.

The repeat-back test, run and scored

The test is simple: read your offer to three people in or near the niche, wait a full day, then ask them to explain it back to you. What follows is what the results actually look like, and how to read each one - because the useful information is in the shape of the failure, not the pass rate.

OFFER READ TO THREE PEOPLE. ASKED BACK 24 HOURS LATER.

Person 1 - letting agent, 6 staff
"You do something with AI for property people. Automating
 admin, I think? Sorry, I can't remember the specifics."
VERDICT: FAIL. Nothing survived a day.
DIAGNOSIS: The offer has no anchor - no single concrete
 moment they can picture. Add the out-of-hours scenario.

Person 2 - letting agent, 2 staff
"When a tenant reports something at the weekend, it gets
 answered and logged instead of sitting until Monday.
 Three weeks to set up. Few grand."
VERDICT: PASS, and better than PASS - they used their own
 words for the pain and they retained the timeline and the
 rough price. This is what a clear offer sounds like coming
 back at you.

Person 3 - accountant, not in the niche
"It's for lettings. Handles tenant messages out of hours.
 I'd guess a few thousand? Not really my world."
VERDICT: PASS. And the most useful of the three - an
 outsider retaining the buyer and the job means the offer
 is legible to someone who was not trying.

Score two of three or better and proceed. Score one or zero and the fix is almost never more words - it is fewer. Three specific rescues, in order of how often they work:

  1. Add one concrete moment. Abstract benefits do not survive a night's sleep; a scene does. "A tenant messages at 9pm on Saturday" is remembered; "improved responsiveness" is not.
  2. Cut the second and third deliverables from the pitch. Not from the offer - from the pitch. People retain one thing. Lead with the one, and let the rest arrive on the one-pager.
  3. Say the price. Offers with a number attached are recalled far more reliably than offers without one, because the number gives the whole thing a shape. Vagueness about price makes the entire offer feel provisional.

One caution about who you test on. Do not run this on other founders or on anyone who has heard you talk about the business before - they will reconstruct your offer from context rather than from your words, and you will get a false pass. The accountant in the example is a better test than a fellow founder precisely because they had nothing else to go on.

Offer problem or delivery problem?

Once the offer is live, everything that goes wrong feels like an offer problem. Most of it is not, and misdiagnosing this costs months. Use the table.

What is happening Where the fault is The fix
Calls booked, nobody buysOffer - usually the price anchor is missingDo the status-quo arithmetic out loud on the call, with their numbers, before you name a figure
They buy, then the project overruns every timeDelivery, caused by the exclusions listMove the top two overrun causes into "not included" and price them as add-ons
Clients happy, no referralsOffer - the name is not repeatableRename it after the outcome, and ask for the referral at handover while the result is visible
Every client wants a variationOffer - too broad for the nicheNarrow to the one workflow they all share. Variations become the add-on menu
Nobody renews the monthly feeDelivery - the fee buys something invisibleSend the monthly report whether or not anything happened. Invisible work is unpaid work
Guarantee invoked, and it is ambiguousOffer - the trigger was not written downPay it, without arguing, then fix the wording before the next proposal goes out

The last row deserves the closing word. The first time a guarantee is invoked ambiguously, the cheap move is to argue and the correct move is to pay. You are buying two things with that money: a client who tells people you were straight with them, and a hard-won piece of information about exactly which sentence in your offer was unclear. Both are worth more than the invoice.

Common mistakes

  • Selling your tools instead of their outcome. The buyer does not want an agent; they want the result the agent produces.
  • Leaving scope open, so every project becomes a custom research effort with no repeatable margin.
  • Promising outcomes you have not yet delivered once. Under-promise until you have real proof.
  • Skipping the name. An unnamed offer is invisible in referrals and impossible to anchor a price to.

What you should be able to do now

  • Fill in the offer skeleton end to end, including the "not included" line, for your chosen niche.
  • Name your package in five words or fewer and state its fixed timeline.
  • Run the repeat-back test with three people and score at least two out of three.
  • Decide, for any incoming request, whether it is package, add-on, premium custom, or a polite no.
  • Answer the price, the risk, and the do-it-ourselves objection without discounting or overpromising.

Where this goes next

That is the end of the free part. With the niche lesson and this one you have a buyer, a named package, a price you can defend, and answers to the three objections. Go and run the repeat-back test with three real people before anything else - it is the cheapest way to find out whether your offer is clear or only clear to you.

The paid lessons are everything after "I have an offer". Building the outreach list and the sequences that actually get replies. The sales call, start to finish, including what to do when the buyer goes quiet. Writing the proposal and the scope of work that makes the guarantee enforceable. Delivering the first build without scope creep, and the handover pack that stops you being on call forever. Then the second phase: retainers, raising prices, subcontracting delivery, and the numbers to watch in a business that is no longer only you. Every lesson ships the artefacts - scripts, proposal, scope document, handover checklist.

One honest note. a8gent does this work as a service as well as teaching it, so if you have arrived here as a business owner rather than a founder, the shortcut is AI automation services or the free automation audit. And if you are here to price your own work, AI automation cost lays out real market ranges, and the proposal template is a working document you can adapt rather than a lead magnet.

Enter your email below and both free lessons arrive with the niche scoring sheet and the offer one-pager as editable files. That part is free and it is the fastest way to have something on paper tonight.

Key takeaways

What to remember from this lesson

  • An offer has four parts: the outcome in the buyer's language, the workflow it replaces, the scope including what is excluded, and a proof or guarantee.
  • Name the package. An unnamed offer is invisible in referrals and impossible to anchor a price to - 'get their Lead Response Setup' spreads, 'they do AI stuff' does not.
  • Guarantee only what you control: that the workflow runs in their tools as described. Never guarantee business outcomes that depend on their volume, staff, and market.
  • Structure the guarantee against your payment schedule - 50 percent deposit, 50 percent on delivery - so a waived final invoice caps your loss at time, not cash.
  • 'Workflow', 'integration', and 'AI agent' are your words, not the buyer's. If a busy owner would need to Google a word, cut it.

Try it yourself

Review two offers for the four parts and a safe guarantee

An offer has four parts plus a guarantee, and a missing part is invisible until a prospect goes quiet. Below are two offers as data. Write the reviewer that reports which parts are absent and flags any guarantee that promises a business outcome you do not control.

Write it

Write the offer, exclusions and all

Write your package the way a prospect would read it: named, with the outcome in their language, what is included, what is explicitly not, and a guarantee about your delivery rather than their results. Structure is what gets checked here; only a real prospect can tell you whether the words land.

2 of 6 checks passing

  • The package has a name a client could repeat
  • States what is included
  • States what is NOT included
  • Has a guarantee sentence
  • Guarantees delivery, not their business results
  • Enough detail to price against (60+ words)

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

Offer decisions that decide the sale

  1. A prospect asks you to guarantee a 30 percent increase in booked appointments. What is the right answer?

  2. Why does the exclusions list matter more than the inclusions list?

  3. What is the practical cost of an unnamed offer?

Answer every question to mark.

Exercise

Write the offer one-pager and pass the repeat-back test

60 min
  1. 1Fill in the offer one-pager skeleton end to end for your chosen niche: name, who it is for, three concrete components, what is NOT included, timeline, fixed setup fee plus monthly, and the assurance line.
  2. 2Name the package in five words or fewer, built around the outcome rather than the technology.
  3. 3Write the 'not included' line explicitly, naming the two or three tempting extras prospects will assume are in scope.
  4. 4Set the guarantee's exact trigger in writing, referencing the scope section, so a vague feeling of disappointment cannot be invoked against a workflow that does what was agreed.
  5. 5Sanity-check the price: a first named package in the $2,500 to $6,000 range is credible. If yours is far outside, write the reason.
  6. 6Confirm you can deliver it in the promised timeframe with tools you already know. If you cannot, change the timeline on the page, not in your head.
  7. 7Run the repeat-back test with three people in the niche: read it aloud once, then ask who it is for, what would change, and what they would expect it to cost.

You are done when Your one-pager has every line filled including the exclusions and a guarantee with a precise trigger, and at least two of three people scored the repeat-back test correctly - naming their own kind of business, describing the outcome in their own words, and guessing a price within 2x of yours.

Companion files

Offer one-pager skeleton and repeat-back test

The fill-in offer skeleton, the package-versus-custom decision table, and the three-question repeat-back script - the worksheet the exercise above walks through.

The free-preview pack includes the worksheet for this lesson for From Niche To A Clear Offer, plus the other free lessons of this course. No email needed.

Free preview pack - 6 KB zip

Check yourself

Answer before you reveal

Why is 'we guarantee 30 percent more bookings' a bad assurance line?Show answer

It promises an outcome you do not control. Their results depend on call volume, staff, and market. Guarantee what you own: the workflow runs in their tools as described, or the final invoice is waived.

A prospect in your niche asks for something adjacent but similar to your package. Package, add-on, custom, or no?Show answer

Package plus a scoped add-on. That keeps the core repeatable - which is where your margin comes from - while still capturing the extra revenue.

All three repeat-back testers guessed a price less than half of yours. What does that tell you?Show answer

The outcome is not landing as valuable enough - they are pricing the work, not the result. Rewrite the outcome line in their language and quantify what the replaced workflow currently costs them, before you consider lowering the price.

Free lesson notes

Get the notes pack for AI Automation Agency Bootcamp, plus every new module free by email.

No card, no spam, unsubscribe any time.