https://www.youtube.com/watch?v=RvnQZQAHUDc
TLDR AI’s value depends less on token or seat pricing than on how well people direct it toward useful business outcomes. Companies should empower employees to identify the right tasks, verify AI’s work, and involve humans when needed, while experimenting with partnerships, embedded engineers, and outcome-based pricing to turn AI capability into measurable customer and business value.
Before choosing an AI tool or pricing model, identify the customer or business result you want to improve. Token usage measures computing activity, not whether the work created value or delivered a return. For example, a healthcare agent may be valuable because it helps patients understand bills and complete payments—not because of how many tokens it uses. Set a clear outcome and decide how you will measure it.
Per-token pricing can help manage usage, and per-seat pricing may fit familiar software arrangements, but neither automatically reflects business impact. Outcome-based pricing can work well for discrete, measurable services, such as resolving customer-support requests or collecting a payment. It is harder to apply to complex work, such as redesigning a manufacturing service program, where results have many causes. Choose a model that fits how clearly you can define and measure the outcome, and keep experimenting as you learn.
AI creates value when people decide what to investigate, what to delegate, and when human expertise is needed. Employees should check AI-generated findings against their domain knowledge, investigate important patterns, and intervene when a task requires judgment or direct customer engagement. In equipment maintenance, for instance, an AI agent can flag recurring failures, while an engineer verifies the pattern and determines its cause. Treat employees as managers of AI, not merely users of a tool.
Organizations that are less fluent in AI may benefit from embedded specialists or forward-deployed engineers. These teams work with business leaders and frontline employees to identify valuable opportunities, then build and test solutions using the company’s actual data and processes. This practical support helps close the gap between purchasing AI and putting it to effective use. As teams gain experience, they can take greater ownership of AI adoption.
Companies can deliver AI-enabled work as a service while learning which problems recur across customers. Moving too quickly to a standard product may limit insight into different needs, while staying in custom service work indefinitely can make successful solutions harder to scale. Use early projects to discover repeatable tasks, validate results, and understand what customers value. Then turn proven approaches into products or offerings when the evidence supports it.
Some AI opportunities may require a closer commercial relationship than a conventional software purchase. Embedded teams, outcome-based agreements, or joint ventures can combine an AI supplier’s expertise with a company’s operational knowledge. These arrangements may help share in the value created, but they also involve greater commitments and can be difficult to measure fairly. Define responsibilities, success measures, and risks before entering a deeper partnership.
Monitor whether AI is improving meaningful outcomes, not just reducing costs or increasing usage. Look for evidence such as faster service, better customer experiences, increased revenue, or capacity freed for work the company previously could not resource. Give frontline teams the support and authority to identify useful applications and share what works. When leaders connect those improvements to business results, they can make better decisions about investment and pricing.
Per-token pricing measures compute, not useful thinking or business impact; per-seat pricing mirrors SaaS but may not reflect the outcomes AI creates. In both models, companies still need to turn AI capability into valuable work.
Employees must decide what work to assign to AI, evaluate its results, adapt processes, and recognize when human expertise is needed. Their judgment helps direct AI toward meaningful outcomes.
Forward-deployed engineers can work with business leaders and frontline teams to identify opportunities, then build, test, and deploy solutions within the company’s actual data and processes.
Companies should balance customer-facing AI services with turning repeated successes into products, since moving too quickly to either model can limit learning. For some opportunities, deeper partnerships—such as embedded teams, outcome-based arrangements, or joint ventures—may be appropriate, though they require significant commitment and measurable outcomes can be difficult to define.
It can work well for discrete, measurable services, such as customer support or an agent that explains a medical bill and collects payment. It is harder to apply to complex work, such as redesigning a manufacturing service program, where results are less straightforward to measure.
Shopify COO Jess Hertz says engineers should use the best models for each situation while spending is monitored. Shopify kept head count flat as revenue grew 34% over roughly two years. Block reported 25% gross-profit growth after reducing its team and placing AI at the center of its business, though those results will need to be assessed over time.
Leaders should look beyond AI’s price and cost reduction. They can test whether AI frees capacity for revenue-generating work that was previously impossible to resource, then track the resulting customer and business value.
They may need partnerships, embedded engineers, or consulting support to build the capability to apply AI to important problems. They also need motivated, supported employees who can connect productivity gains to customer value and business results.