Narrow Is the Moat
Why we won't sell you a bigger package, even if you ask.
I get asked once a week whether we’ll do a bigger package. More workflows in one engagement. Longer timelines. Ongoing support bundled in. A “platform” instead of a sprint.
The answer is always no.
Not because we couldn’t take the money , we could. Plenty of customers would write a bigger check if we extended the scope to match it. The answer is no because every service business that fails fails for the same reason, and the reason is saying yes too often.
This is an essay about why narrow is the entire moat, not a constraint on it.
The five layers of narrowness
What we sell is one narrow AI workflow, shipped into a customer’s product, in ten business days. Five different things in that sentence are deliberately small. Each one of them is doing work.
One. Narrow customer. We sell to founder-CEOs of B2B SaaS companies with 5–50 employees. Not enterprises (their procurement cycle is longer than our delivery cycle). Not indie hackers (the work doesn’t make sense at their price point). Not pre-PMF startups (they need product-market-fit, not an AI workflow).
Two. Narrow offer. One workflow, not a roadmap. Not a strategy. Not a “transformation.” One specific process the customer’s team runs, with a clear input and a clear output.
Three. Narrow scope. A written Sprint Brief on Day 1, signed off in email by the decision-maker. Anything outside is a change order with its own scope conversation.
Four. Narrow workflow. Clear input, clear output, single user, measurable improvement. “For this user, when this input arrives, the workflow does this action and produces this output, so that this business value is captured.”
Five. Narrow promise. Staging, production, or a production-ready pull request , whichever the customer’s infrastructure supports. Not “guaranteed live in production,” because that promise depends on the customer’s own deployment pipeline, which is out of our control.
Each of these layers does specific work for the business. Let me walk through why.
Why narrow makes the offer credible
A two-week promise on something specific is believable. A two-week promise on something vague isn’t.
Imagine the same buyer reading two pitches:
“We’ll help you build an AI strategy for your product.”
“We’ll ship the investor update workflow into your founder’s dashboard in ten days, working code in your repo on Day 10.”
The first one could mean anything and probably won’t be done in two weeks. The second one is testable. The buyer’s bullshit detector relaxes immediately on the second one, because specificity is what disarms it.
You can’t sell a vague offer at our price point. The buyer doesn’t believe it. You can sell a very specific offer at three times the freelance rate, because the specificity is the proof of competence.
Why narrow makes the work shippable
Every “and also” added to a sprint is a future Day-9 crisis.
The math here is brutal and not negotiable. Engineering effort doesn’t compose linearly. Two workflows in ten days isn’t twice as hard as one workflow in ten days , it’s about three times as hard, because the two workflows interact, share data, share UX, share decision points. Each addition pulls every other deliverable’s timeline with it.
The narrow sprint ships on time. The “and also” sprint slips. The slipped sprint produces an unhappy customer and a damaged reference. The damaged reference produces fewer future sprints. Compound that over a year and the wide-sprint operator is out of business while the narrow-sprint operator is hiring a second engineer.
Why narrow makes the marketing crisp
Specific offers convert better than general ones. This isn’t preference , it’s measurable.
“We ship one AI workflow in 10 days” lands. The buyer can picture it. They know whether it applies to them, what it costs, and what they’d get back. They can forward it to a colleague with three sentences of context.
“AI consulting and implementation services” doesn’t land. The buyer can’t picture it. They don’t know whether it applies to them. They can’t describe it to a colleague. They tab away.
The marketing isn’t easier because we have less to say. It’s easier because narrow offers are easier to remember, easier to compare, and easier to recommend.
Why narrow makes the pricing defensible
A narrow scope justifies fixed pricing. A broad scope forces time-and-materials.
Time-and-materials is the standard model for most software consulting because the work is open-ended. It also makes the customer miserable, because the total cost is unknown until the engagement ends. Buyers who have been burned by a T&M consulting engagement (which is most experienced buyers) hesitate before committing to another one.
Fixed-price-for-fixed-outcome is only honest at narrow scope. We can quote a number with confidence because the scope is narrow enough to be predictable. The customer can compare that number against their alternatives and decide cleanly. They sleep well. We sleep well.
The minute the scope widens, fixed pricing becomes a gamble that bankrupts the operator or a buffer that makes the customer overpay. Neither is sustainable.
Why narrow makes the customer happy
They got the specific thing they asked for. Not a generic thing they have to adapt.
The customer who hired us to ship an investor update workflow gets an investor update workflow. The one who hired us to ship a support ticket triager gets a support ticket triager. The match between what they signed for and what they received is one-to-one.
This sounds obvious. It is the rarest thing in service work.
The customer who got exactly what they paid for refers other customers. The customer who got “approximately what they paid for, with some interesting additional pieces we threw in” doesn’t refer anyone, because they can’t summarize what they bought in a sentence.
What the narrow discipline forces on the operator
This is the harder part, and it’s where most service businesses give up.
The narrow discipline forces you to say no , repeatedly, to attractive opportunities, in the moment, when the money is on the table.
The prospect who wants two workflows for the same fee: no.
The prospect who wants the sprint to start three days early to fit their roadmap: no.
The fourth retainer customer who wants to sign this week even though we’re at capacity: no.
The enterprise that wants to expand the scope by 40% mid-sprint: change order, separate conversation.
Each “no” feels like lost revenue in the moment. None of them actually are. The “no” protects the timeline of the current customer (so they get what they paid for), the quality of the current deliverable (so the case study is real), and the capacity for the next right customer (so the pipeline doesn’t collapse).
Every service business that fails fails because it said yes too often. Yes to wrong customers. Yes to scope creep. Yes to capacity it didn’t have. The discipline of narrow isn’t a constraint on the product. It is the product.
The line worth remembering
You can’t sell a vague offer at a real price. You can’t ship a wide scope on a tight timeline. You can’t make a customer happy by giving them more than they asked for, if “more” means “later and in worse shape.”
Narrow customer. Narrow offer. Narrow scope. Narrow workflow. Narrow promise.
That’s not a limitation. That’s the moat.
If this topic is useful to you, I go deeper in my book, Forward Deployed AI Engineering: A Working Guide to the Hottest Job in Software.
It’s available now on Amazon: https://www.amazon.com/Forward-Deployed-AI-Engineering-Software/dp/B0H3VKKG38/