Choosing your first paid AI service: how a solo founder carves out one sellable unit of work

A&A perspective

Define your first AI service not as a list of what you can do, but as a unit of completion the buyer can receive and accept one instance at a time. There are only four things to settle: who buys, what they hand you, what you hand back, and where human judgement takes over. A proposal that cannot state those four in one sentence leaves the buyer unable to answer the question that actually blocks the deal — what exactly would we have ordered? When scope gets renegotiated in every conversation, the cause is usually not an indecisive buyer; it is that the seller has not yet done the narrowing.

A&A perspective

What is worth noticing is that within the same page the vision is broad while every described usage is narrow. Each of the three instances pairs one buyer — a sales team, a support function, the founder personally — with one task: lead identification and first outreach copy, first-line support, briefings and calendar conflicts. That is A&A’s observation about how the page is written, not advice that Lindy or Anthropic offers to service firms.

A&A perspective

So why can a platform afford to announce itself broadly? Because it has many customers, and each of them selects its own task. The mechanism that absorbs ambiguity sits on the buyer’s side. When one person sells the service, that mechanism does not exist. A broad claim hands the buyer homework — what should we ask for? — and that homework does not get done inside a single meeting. This is why the seller has to finish the narrowing in advance.

A&A perspective

Choose the task you sell first by whether completion can be judged, not by how much pain it carries; validation then moves faster. Four conditions do the judging. First, the completion standard can be written in the requester’s own words. Second, the buyer can check whether the output is correct using means they already have. Third, when an error is found, it can be fed into the next instance. Fourth, the place where a human holds final judgement is explicitly fixed.

A&A perspective

What that post argues about is technical fit — where automation works well. A&A reads the same conditions as a commercial test for a service firm choosing its first offer. The reason is plain: a deliverable that cannot be accepted cannot be invoiced. When the completion standard cannot be written in the buyer’s words, the post-delivery question of whether this is right drags on, and the extra work ends up unbilled. When the buyer already owns the means of checking, that check finishes inside their existing routine. This re-reading is A&A’s interpretation, not something the source states.

A&A perspective

The opposite selection rule also holds. One can argue the first offer should be the task with the largest pain and the highest price. It is true that a task chosen only for being easy to accept can be cheap and unwanted. Even then, rather than making the painful task itself your first engagement, carve out of it the portion whose completion can be judged; the first delivery earns trust more reliably that way. A&A recommends the ordering: select the target by pain, cut the unit by judgeability.

A&A perspective

The single page you bring to a meeting carries eight fields. The buyer: the role that can decide both the order and the acceptance. The situation in which the work arises, and its frequency. The input you receive: who provides it, in what format, and already in their possession. The deliverable you return: something that has a name as a single completed artifact. Exclusions: what you will not take on at this price. The acceptance view: what the buyer looks at to judge that it is done. Human-retained judgement: who holds final approval and exception decisions. And the pricing unit. One page is enough. If it feels thin, narrow the target before adding features.

A&A perspective

In most cases the field that does the work on this page is exclusions. When exclusions are absent, the buyer reads the offer as probably covering everything. When they are written down, the buyer sees which part remains their responsibility and can decide internally, in advance, who picks it up. Exclusions are not a refusal; they are information that helps the buyer plan. Whether the deliverable has a name plays the same role. “Support for operational efficiency” is not a name. “A completed specification form and a list of undetermined items” is a name. Once it has a name, the buyer can work out whom inside the company to show it to.

A&A perspective

There is one more cut that helps when filling in the sheet: take the distinction the source draws between what proceeds along a predefined path and what needs judgement on the spot, and apply it directly to the breakdown of what you take on. The part that runs in the same order every time, where the result follows once the inputs are present, is what you can promise per instance. The part whose premises change case by case, where how to proceed must be decided in the moment, goes either into exclusions or into human-retained judgement. In the specification-form illustration, transcribing items that exist in the master is the former; deciding a new value absent from the master, or judging regulatory conformity, is the latter. Drawing that line on the sheet in advance is what determines how far you can commit on price and turnaround. This is A&A applying the distinction; the source is not discussing how to divide service scope.

A&A perspective

Set acceptance conditions against a set of actual cases, not against an abstract quality standard. The procedure: ask the buyer for roughly twenty past instances of the same kind of work, and have both sides write down, at proposal time, how many of them should pass without rework. If too many fail, narrow the target or increase the judgement a human retains. Deciding the standard afterwards turns the post-delivery discussion into an exchange of impressions about whether quality was poor or sufficient.

A&A perspective

That twelve-of-twenty ratio cannot be carried over as an accuracy target. The twenty questions are a fixed set chosen by Newfront itself; the date, the breakdown of the failures and any independent evaluation are not published. It is a vendor account. What A&A transfers to a service business is not the number but the ordering. Before expanding, the hard instances were enumerated concretely. Because what counts as correct was fixed first, changing the procedure or the model can be compared on the same yardstick. The same holds in service work: line up twenty real instances beforehand and the acceptance conversation becomes a comparison rather than an exchange of impressions.

A&A perspective

Price in the same unit as completion. If a single deliverable has a name, you can invoice per instance. Being able to quote only in hours is another way of saying the unit of completion has not been decided yet. Do not, however, fold exception cases into the same rate. The first handling of a new format, cases with missing inputs, and cases held up waiting on the buyer’s own decision should be settled as separate treatment in advance.

A&A perspective

Outcome pricing works in a business with a volume buffer: with enough instances, losses on hard cases are absorbed by the average. A first offer sold by one person has no such buffer. Promising to invoice only on success while handling a handful of cases a month leaves the definition of failure partly in the buyer’s hands, and unpaid rework accumulates. What A&A considers realistic is the middle. Charge a fixed amount per ordinary instance, quote exceptions separately, and judge acceptance against the set of instances agreed in advance. The buyer can then predict the cost, and you can price exceptions instead of refusing them. How to account for checking and rework time inside per-instance economics is handled in “Low-ticket service economics depend on more than generation speed”.

A&A perspective

Write the condition for adding a second offer in observations, not in revenue. In the first task: did a second request arrive from the same buyer at their own initiative? Did the reasons for failing acceptance converge on the same few kinds? Did the time spent on human-retained judgement fall? Add only once those three are visible. Adding tasks before they are visible makes it impossible to tell which task is weak and where.

A&A perspective

That advice is written about implementation, but A&A reads it as applying directly to the shape of an offer. Expand the service menu only when you can show that the expansion actually speeds up the buyer’s decision. Once there are two menu items, the first question in a meeting becomes which one fits. If you do not hold the material to answer that question, the choice is a burden rather than a courtesy. When you add the second offer, prepare the criterion for choosing between them at the same time.

A&A perspective

Start with where it does not apply. First, a task that is easy to accept is not necessarily valuable to the buyer. Selecting on judgeability alone optimises for cheap work nobody was troubled by. Observe first that the buyer is already spending people and hours on it, and only then cut a judgeable unit out of it. Second, if the work arises only a few times a year, the second observation never comes and this approach does not hold. Third, if the input takes a different shape every time, a fill-in-the-form style unit cannot be fixed; in that case the work of standardising the input becomes a candidate offer of its own.

A&A perspective

These are vendor-published figures; the population, period, definitions and comparison conditions are not given, and they are not independently verified. They cannot be used as a forecast for what a Japanese solo firm would obtain on the same work, so this article takes only the selection reasoning and not the numbers. It is worth repeating that Lindy can announce a broad scope as a platform because many customers each choose their own task. When the seller is one person, that premise does not hold.

A&A perspective

What to do next. If you are still deciding the selling model itself — selling a tool versus taking on the work — read “AI-native service-company cases: what Advolve, Newfront and Lindy help founders compare” first. If the first offer is already settled and you are organising intake from inquiry through to the estimate, “Wire inquiry-to-quote with AI: fix missing information first at a small service firm” is the continuation. The whole picture from acquisition through retention is collected in “AI-native GTM: a practical guide for solo founders and small teams”. If you have written the offer sheet but cannot settle which task to target, that is within the scope of an initial free consultation.