18 Months of Pricing AI Automations in 21 Mins
Nate shares 18 months of experience pricing over 100 AI automation systems, providing a framework for calculating project value based on client savings rather than hourly rates, and structuring payments in 30-day milestones to minimize financial risk.
Summary
Nate, who scaled an agency to $100,000+ monthly revenue before selling it, breaks down his methodology for pricing AI automation projects. He illustrates his approach with a real example: an appointment-setting agent saving a business $41,600 annually (20 leads/week × $40/hour labor × 52 weeks), which he priced at $5,500 (13% of annual value), resulting in a 7.5x return on investment. He argues for pricing based on client value rather than hourly rates, explaining that hourly billing perversely incentivizes slower work and penalizes efficiency gains. The core pricing strategy involves identifying the client's ceiling (the maximum value the automation creates) through discovery conversations using the LRP framework (listen, repeat, poke) and asking about current costs, pain points, and success metrics. He recommends pricing at 10-20% of first-year annualized value and presenting tiered options (starter, growth, scale) rather than single prices, as this psychologically shifts client decision-making from "should we work together" to "which tier should we choose." Payment structures should use objective milestones (deliverables verifiable without ambiguity) spaced 30 days apart to avoid scope creep and ensure consistent cash flow. He addresses cost separation—clients should maintain their own API keys and cloud billing accounts—and emphasizes the importance of measuring and communicating post-implementation results to justify pricing in future conversations. When clients balk at price, he recommends reducing scope rather than reducing cost to avoid training clients that prices are negotiable.
Key Insights
- The speaker calculated a project price at 13% of the client's annualized labor savings ($41,600), resulting in a 7.5x return on investment in the first year, and noted that 10x returns are the ideal 'golden rule' target.
- Hourly billing creates perverse incentives: it pays developers more to work slowly and less to work efficiently, so a faster developer produces less revenue than a slower one doing the same work.
- The speaker argues that 'cost doesn't justify price, price justifies cost'—meaning a vendor cannot raise prices simply because their internal costs increased; price is determined by client value, not supplier cost.
- Objective milestones must be provable and unambiguous (e.g., 'AI system in client hands that responds to queries within one minute') whereas subjective ones create disputes and scope creep (e.g., 'system working as expected').
- The speaker paid for all testing costs upfront rather than charging clients for testing before delivering any POC or value, viewing this as a better way to establish a partnership.
Topics
Transcript
[0:00] All right. So, I've sold over 100 AI automation systems and I've priced a ton of those wrong. I've undercharged, I've underscoped, and I've just thrown out random numbers that were kind of a guess and I couldn't explain when someone actually asked me like, "Hey, where'd you get that number from?" So, in this video, I'm going to talk about everything that I know about pricing AI solutions. I'm going to walk you through one real build that I sold, every single number, and by the end of this video, you'll be able to take any project, turn the client's own numbers into a price that you can actually defend, and then get paid in stages so you're…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Nate Herk | AI Automation
Fable 5 + Karpathy’s LLM Wiki is Basically Cheating
The video demonstrates how to build a personal LLM-powered knowledge base using Obsidian and Claude, inspired by Andrej Karpathy's approach. By ingesting various data sources (YouTube transcripts, PDFs, URLs) into an interconnected wiki structure, users can create a 'second brain' that helps AI agents understand context and relationships across knowledge domains.
How Claude is Creating a New Generation of Millionaires
Claude, an AI built by Anthropic, is enabling non-technical founders to build million-dollar software companies by automating development work. The transcript outlines why Claude is outpacing competitors, provides real examples like Vulcan, and offers a four-step framework for anyone to start building with Claude today.
How Anthropic Engineers Actually Prompt Fable 5
A guide to effectively prompting Claude Fable 5, covering six key techniques including providing context/intent, using negative prompting, letting the model act once ready, verifying outputs, avoiding reasoning requests, and keeping instructions concise. The speaker emphasizes that Fable 5 is expensive and should only be used 5-15% of the time, with pricing at $10 per million input tokens and $50 per million output tokens.
Stanford's Method Turns Claude Into a PHD Level Research Team
A researcher demonstrates the STORM method from Stanford, which uses five expert perspectives (practitioner, academic, skeptic, economist, historian) to create verified research reports. The method produces 25% more organized articles than competing approaches and is packaged as a reusable Claude skill that generates HTML briefings with peer-reviewed citations.
Is Claude Mythos Coming?
A YouTuber analyzes the brief appearance of 'Claude Mythos' on Anthropic's API, arguing it signals a marketing move rather than an imminent public launch. Despite competitive pressure from OpenAI and IPO timing, the creator believes Mythos capabilities will quietly fold into future Opus models rather than release publicly under that name. Three possible scenarios are outlined ranging from a limited gated release to Mythos remaining permanently restricted to vetted security partners.