Files
BusinessNotes/wiki/sources/2026-06-15-selling-development-services-in-the-ai-era.md
EugeneTes 60176d2fdc all
2026-07-30 11:15:52 +02:00

11 KiB
Raw Permalink Blame History

Принципы продажи услуг разработки в эпоху ИИ (Principles of Selling Development Services in the AI Era)

#source #sales #positioning #pricing #outbound

Source Metadata

Core Claims

  1. Hourly development is dead. The buyer has a ~$200/mo alternative (AI). Competing on rate zeroes out margin.
  2. "Expensive" doesn't exist. "I don't see what for" exists. Test the objection: "If we guaranteed the result — is price still the problem?" Yes → they have no money. No → they never trusted the value.
  3. Business doesn't buy uniqueness, it buys a proven method. "Unique" reads to a buyer as "I'm afraid — don't experiment on me."
  4. AI expands the funnel rather than eating it. For every $1 a company spends on AI it spends ~$6 on specialists to configure it.
  5. Sell the result and accountability for it, not hours. Willing to take accountability → the AI era makes you rich. Unwilling → a 12-month death sentence.
  6. Category = pain + result, not technology. Commodity test: remove the word "development" and the stack name from your offer. What's left? Nothing → you're a commodity.
  7. 80% of sales success is WHO you talk to, not WHAT you say. If the offer won't sell, it's almost always the wrong audience.
  8. Sell to leadership, not to implementers. To an implementer your AI is a threat to their job and you are a risk. To leadership you deliver a KPI.
  9. Go where AI is powerless — narrow industry methodologies LLMs don't know.
  10. Originality is downstream of cloning, not upstream. Copy at 10,000% first, adapt second.
  11. Consistency beats intensity. 30 min/day > 5 hours once a month.

Key Evidence / Details

Finding pain with money attached — a pain qualifies only if all four hold: it recurs often; it costs the business money; it's already being solved with duct-tape workarounds; the founder understands its value. Missing any → not a client.

The spend-based opener: watch what they spend on, not what they say. Find an operational cost line → "How much do you spend on X?""And if you spent 10× less — would we talk?" Even if you're off by half, you still delivered 5×.

AI as a qualification filter — don't hide the AI, weaponize it. Give a working AI skill away free for 30 days:

Reaction Meaning
"It works" Your value isn't needed. Not a client.
"We never got to it" Task has no budget. Not a client.
"Weak, needs specifics" Target client.

Mining existing clients: the money is with your old customers. Call your 35 best and ask "what result were you paying me to get?"not "why did you choose us?", which only ever returns "good team".

Numbers cited (all uncited by the distillation):

  • ~80% of deals close after the 5th touch; most people quit after the 1st.
  • 91% of clients are willing to refer; only 11% are ever asked. The enthusiasm window right after delivery is short.
  • Cold-email subject line carries 47% of open rate — spend 50% of your time on it. "Quick question about [Company]'s checkout flow" >> "Ideas to improve your site".
  • Webinar formula: 60% teaching + 20% case study + 20% offer → 1525% conversion.
  • 3 channels × 90 days; don't add methods until these are mastered.

Productize after 23 identical projects — fixed price, fixed scope, a package name. Ladder: DIY → DWY → DFY (Done For You) = highest leverage. Benefit first, then feature. MVP in 714 days.

On cloning (the Pabrai method): clone from multiple sources (Buffett for investing, Munger for thinking, Graham for principles) — originality is an emergent property of the combination, because nobody assembled those same pieces the same way. Clone the boring parts: success is ~1,000 small decisions, not one brilliant one. Letter of the rules > spirit of the rules — at the start; "spirit of the rules" is for masters, and beginners use it to excuse skipping discipline. Gas-station parable: one station wipes windshields and checks tires free and has a queue; the one across the street watches this daily and never copies it, then goes bankrupt — not from missing information, but from ego.

Deal psychology: the client is not a prize — a deal is expertise exchanged for money, not charity from you nor a favor from them. Professionals choose which fights to enter (an athlete doesn't "participate in competitions", they go to win; a commander doesn't enter a battle without seeing the conditions for victory). If even one person bought, there's no reason others won't — the problem is never the product, it's WHO and HOW. "If you're at the level of an Indian dev, you are one — just more expensive." Knowing where the underwater rocks are is your expertise.

Minimum tactical kit: 23 case studies with Before/After numbers (without them you have nothing to sell a result with); a first-touch template, customized every time, never mass-mailed.

Anti-patterns table (verbatim structure):

Do Don't
Sell the result Sell hours or the stack
Category by pain+result Category "we build X on Y"
Solution or Staff Aug under separate brands Both models on one site
Customize every first touch Mass-mail one template
Price via value Price as a competitive weapon (= bankruptcy)
Narrow niche where AI is weak "We do everything for everyone"
Ask for referrals immediately Wait for "the right moment"
5 follow-ups before "stop" One shot and forget
3 channels × 90 days Change channels weekly

Connections

Open Questions

  • Every statistic here is now traceable to a named primary note but still not independently verified (80% / 5th touch, 91% vs 11% referrals, 47% subject line, 1525% webinar → 2026-06-15-17-ways-first-client; $1:$6 AI spend → 2026-06-15-rodenko-selling-development-expensively). Their root sources are promotional YouTube videos. Attributable, not confirmed — do not repeat as fact.
  • The 7 upstream notes live outside this vault. Resolved 2026-07-17: all seven are now ingested into raw/sources/ and summarized in wiki/sources/ (see Source Metadata). Claims can now be traced to their primary note.
  • Is "hourly development is dead" true across the board, or only for commodity work? Regulated/legacy/high-liability domains plausibly still bill hourly at healthy rates. 2026-07-06-sebastian-interview-ai-and-software-engineering adds partial counter-evidence (enterprise/COBOL holdouts).
  • The ~$200/mo AI alternative: is that a real substitute for a dev contract, or only for the low end of it? The claim is asserted, not demonstrated.
  • "Solution and staff aug under one brand will always collapse into staff aug" — stated as a law, with no counter-example examined.
  • "If you're at the level of an Indian dev, you are one — just more expensive" — recorded as written for fidelity. The underlying point is about commoditized skill level, but the phrasing trades on a nationality stereotype and shouldn't be reused in this vault's own writing.

Change Impact on Wiki

Co-first ingest into an empty vault (alongside 2026-07-17-design-the-perfect-offer).

Update 2026-07-17 (second batch): superseded as a primary source. With the seven upstream notes now ingested, this page is best treated as a derived index into them — concept pages that once cited it as primary now cite the specific note (2026-06-15-rodenko-selling-development-expensively, 2026-06-15-17-ways-first-client, 2026-06-15-how-to-get-rich-cloning, 2026-06-15-making-money-with-ai-2026). Its content is unchanged and still an accurate summary; only its citation status dropped from primary to secondary.