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
Every Codex Concept Explained for Non-Coders
A comprehensive tutorial explaining 18 core Codex concepts for non-technical users, organized into four parts covering basics (projects, agents, agent loops, goals), environments (on-premises vs. cloud, working trees), customization (AI models, effort levels, permissions, skills), and scaling tools (browser, sites, subagents, scheduled tasks, voice mode).
Claude Code Mods Are Game Changers. This One Saves Me Money.
Claude Code now supports mods that allow customization of the Cloud desktop app. A user demonstrates a cache management mod that tracks usage data, displays costs, monitors session limits, and provides notifications before cache expiration to help optimize spending.
5 Claude Code Mods That Everyone Needs
The video demonstrates five useful Claude Code modifications (mods) that are plugins enabling customization of the Claude desktop application interface. The creator showcases practical mods including Cache Keeper for token management, Recording Mode for privacy, Goal tracking interface, and Collision Guard for file conflict detection, explaining how anyone can create mods using plain language.
How to Actually Build & Sell Software with AI as a Non-Techie
Dave Fabrikant, a 10+ year Python programmer and AI engineer, discusses how AI coding tools have transformed software development from a specialized skill into an accessible field for non-technical founders. He explains the progression from personal tools to scalable products, emphasizing architecture, security best practices, and the shift from specification-driven to intent-based development.
I Tested Codex's NEW $500/mo Ultrafast mode
A reviewer tests Codex's new $500/month Ultrafast mode, which claims to be 8x faster than standard mode. While results vary by task complexity, Ultrafast delivers significant speed improvements but at substantially higher resource consumption, making it suitable primarily for time-sensitive projects.