Christine Dart

Instead, organize spending around a company-level constraint: acquisition that has become too expensive, enterprise sales that still needs heavy manual research, expansion signals that surface too late, or retention problems with no clear cause.

• Every investment thesis has to answer what changes if we fund it, how large the value pool is, how quickly we would know it worked, what has to change organizationally, and what we stop funding if it does work.
• They name a specific failure mode: AI makes an activity much more efficient while the old operating model keeps getting funded alongside the new one.
• The company has added a technology expense rather than transformed its economics.

The worked case is retention. Dart describes an AI-enabled system that layers product behavior, support history, CRM data and customer conversations to understand where an account sits in its adoption journey, recognize when a customer is struggling and choose the next intervention: an in-product prompt, a customer success manager stepping in, or marketing education about an undiscovered use case.

Read original

The conversation, they argue, is less about finding the successor to per-seat SaaS and more about a plainer question: who pays for usage?

• With seat pricing, the vendor absorbs more variability; with consumption pricing, more of it moves to the customer, who ends up hoping for adoption while watching the meter.
• The answer is not a pricing model alone but product and customer success work: helping buyers see which use cases justify the expense, where extra consumption stops producing proportional value, and what guardrails keep usage from becoming wasteful.

Dart cites Futurum research finding that when GenAI is priced separately, 42.3% of enterprise buyers prefer per-seat pricing, 36.6% prefer consumption, and 21.1% prefer outcome-based pricing.

• They read this as buyers favoring predictability when their own future usage is hardest to estimate.
• They also point to the Headspace AI mental health companion Ebb, which limits conversations to 30 minutes and frames the boundary as a chance to step away and reflect.
• For Dart, it is a product constraint that protects the experience and the economics at once.

Read original

That can produce real value and a large invoice at the same time, creating a modern adoption problem: a customer uses a product more than ever while becoming less comfortable with the economics behind it.

• In a usage-based model, rising consumption might show growing value or just a faster meter; vendors need to know which.
• Dart's operational test is whether the value produced is growing faster than the bill.

Dart contrasts the familiar SaaS moment of relief when a contract is signed with what agents do afterward.

• They close on the distinction between celebrating deeper adoption and making sure the customer feels the same way when the invoice arrives.
• The suggested response is to help customers identify which workflows produce meaningful returns, understand how those economics change at scale, and separate productive consumption from expensive activity.

Read original

Products that reach that point, they write, survive budget reviews, leadership changes and shifting priorities, and the relationship becomes sticky.

• A related post treats retention as a company-level economic outcome, arguing it should be funded as a capability that crosses the organization rather than as several departments each becoming incrementally more efficient.
• Dart then notes that AI agents have complicated the picture: more usage no longer automatically signals more value.

The retention argument uses the same cross-organizational system described in the investment post, built around a single economic outcome: getting more customers to value and keeping them there. The adoption argument focuses on embedding the product in important processes, spreading it across teams and making renewal the less painful option.

Read original · Original 2

It marks October 1st as Threshing Day, a reference to a fantasy series, and addresses the niche part of Dart's professional network that recognizes it, while telling everyone else to return to their usual programming about AI transformation and operational efficiency.

• The post jokes that selecting a dragon would involve a lengthy procurement process, an off-brand deck with too many slides, a pipeline conversion conundrum and someone asking to revisit the dragon decision next quarter.
• It closes with standards for the dragon and signet and asks readers which signet they would want.

The post's list of standards, no orange dragons and no inntinnsic signet manifestation, plus the invitation for readers to name the signet they would manifest, make it a community-facing post rather than a sample of professional analysis.

Read original

Start here for the argument behind the recommendations.

Dart poses a spending question — what would you do with an extra $3M for AI — and argues against splitting it into per-department efficiency budgets.

• Instead, organize the money around one company-level economic problem: acquisition cost, manual enterprise sales research, late-surfacing expansion opportunities, or poor retention.
• The post walks through retention as a worked example, describing an AI-enabled system that layers product behavior, support history, CRM data, and customer conversations to spot struggling accounts and choose the next intervention, whether in-product, a CSM step-in, or marketing education on an undiscovered use case.
• The sharpest part is the closing test: what do we stop funding if this works?
• Dart names the failure mode directly: if AI makes work faster while the old operating model keeps getting funded alongside the new one, the company has added a technology expense, not changed its economics.

For brands planning a campaign

Build a talk or workshop around one question the audience answers live: pick a company-level constraint, size the value pool, decide how quickly you would know it worked, and name what you would defund. That structure fits an executive audience better than a feature-level AI session.

Dart sets out the tension between vendors who want consumption-based pricing and buyers who want to know the bill in advance.

• The post cites Futurum research on GenAI priced separately: 42.3% of enterprise buyers preferred per-seat pricing, compared with 36.6% for consumption and 21.1% for outcome-based pricing.
• Dart observes that buyers favour predictability when their own future usage is hardest to estimate.
• They reframe the debate away from finding per-seat's successor and toward a plainer question: who pays for usage?
• The post also gives a concrete product example: the Headspace AI companion Ebb caps conversations at 30 minutes and frames the limit as a prompt to step away.
• Dart reads this as a constraint that protects the experience and the economics at once.
• The suggested B2B equivalent is product controls and usage alerts paired with customer success coaching on which AI use cases justify their consumption.

For brands planning a campaign

This is the most directly usable asset for an AI pricing brief.

• The Futurum figures give a session a defensible data point, and the Ebb example gives it a design pattern a product or CS leader can debate.
• Confirm the Futurum source and date before quoting the numbers on a slide.

It explains why rising usage is no longer automatically good news.

Dart describes the familiar post-signature shift from winning the deal to embedding the product, then introduces agents as a complication: agents consume software differently from people, retrieving context, calling APIs, retrying actions, and continuing after the human who started the process has moved on.

• That can create real value or extraordinary invoices.
• The post sums up the problem: a customer can be using your product more than ever while becoming less comfortable with its economics.
• In a usage-based model, a rising curve might signal growing value or simply a faster meter.
• Vendors need to tell the difference, helping customers find the workflows producing meaningful returns and understand how those economics change at scale.
• The closing question is operational: is the value produced growing faster than the bill?

For brands planning a campaign

Use this as a follow-on to the pricing post: pricing design answers who pays for usage, and this post answers how to keep a usage-based customer comfortable after they have signed. Together, they give a talk on AI pricing and adoption a two-part arc.

It shows the voice a general reader would encounter alongside the pricing and investment material.

A short, self-aware post marking October 1st as Threshing Day, a reference to the Fourth Wing books.

• Dart jokes that only the niche of the professional network who knows the reference gets to abandon normal business discourse for the day, and imagines a Threshing run derailed by procurement, an off-brand deck, and someone asking to circle back on the dragon decision in Q4.
• It ends with standards for the dragon and signet — no orange dragons, no inntinnsic signet — and asks what signet readers would manifest.

For brands planning a campaign

This is not a campaign fit for an AI pricing brief, and it should not be presented as one.

• Its value is range: it shows the B2B commentary sits next to a fandom-adjacent, comic voice, which matters if a brief needs a human-sounding speaker rather than a pure analyst.
• Treat it as audience texture, not a sample of the professional work.

Instead, investment should focus on one company-level problem: expensive acquisition, manual enterprise research, expansion signals that surface late, or poor retention with no explanation.

• They list the questions such a thesis must answer: what changes if we fund it, how large is the value pool, how quickly will we know, what must change organizationally, and what we stop funding if it works.
• The worked example is an AI-enabled retention system that combines product behavior, support history, CRM data and customer conversations to spot struggling accounts and choose the next intervention—in-product, through a CSM, or via marketing education.

Opens with a concrete dollar question, builds a worked retention scenario, then closes on the harder question of what the company is willing to stop funding.

For brands planning a campaign

Suitable for a keynote or working session on AI investment priorities for executive teams, with the retention scenario ready to use as a case study.

Examples: Source 1

Vendors want consumption-based payment; buyers want to know the bill in advance.

• They note the spread of usage-based pricing, credits and outcome pricing, and cite a Futurum finding that when GenAI is priced separately, 42.3% of enterprise buyers prefer per-seat pricing, 36.6% prefer consumption and 21.1% prefer outcome-based pricing.
• The proposed answer is not purely a pricing-model choice: product and customer success should help buyers identify which use cases justify the spend, where extra consumption stops producing proportional value, and what guardrails prevent wasteful usage.
• Headspace's AI mental health companion Ebb, which caps conversations at 30 minutes and frames the limit as a chance to step away and reflect, is an example of a constraint that protects the experience and the economics at once.

Anchors the argument in a named third-party survey and one product example, then translates the consumer constraint into a B2B equivalent: controls, alerts and customer-success coaching.

For brands planning a campaign

Fits a pricing and packaging session or product-marketing brief on AI monetization, especially where a vendor must explain usage-based costs and set customer-facing guardrails.

Examples: Source 1

That can create real value and a large invoice at the same time, leaving a customer using a product more than ever while becoming less comfortable with the economics.

• They ask what a rising usage curve actually accomplishes, with the closing test being whether the value produced is growing faster than the bill.
• The suggested response is to help customers identify the workflows producing meaningful returns, understand how the economics change at scale, and separate productive consumption from expensive activity.

For brands planning a campaign

Useful for a session on usage-based revenue operations and the customer-value story around AI agents, aimed at product, finance and customer-success audiences.

Examples: Source 1

Embedding the product in important workflows, expanding usage across teams, and becoming painful to remove are presented as what makes a relationship sticky enough to survive budget reviews, leadership changes and shifting priorities.

• A related post argues that retention is a company-level economic outcome worth funding as a cross-organizational capability rather than as a set of departmental efficiencies.
• They also observe that AI has complicated the picture, because more usage is no longer automatically a signal of growing value.

For brands planning a campaign

Suits a customer-success or retention-track session, or content about onboarding and adoption programs for B2B software companies.

Examples: Source 1 · Source 2

They joke about approaching a dragon selection with the calm of someone destined for an enormous dragon, then undercut it with the realities of corporate B2B—procurement, an overlong deck, pipeline conversion and someone asking to revisit the dragon decision next quarter. A short list of personal standards closes the post with a question to readers about which signet they would want.

The post shows a personal, community-facing voice built around a shared professional reference.

For brands planning a campaign

Signals a lighter in-group register that can carry a community segment or event moment, useful where a brand wants a speaker who can mix analytical work with shared professional reference points.

Examples: Source 1

View example

It caps conversations at 30 minutes, framing the limit as both a user benefit and a way to control open-ended AI usage. The post uses this to illustrate a pricing-and-product principle.

View example

Readers looking at how AI-era pricing and metering work in day-to-day go-to-market will find the same subjects argued from an operational angle.

Kung's posts are problem statements that lead into a specific tool announcement, presenting the fix as something a vendor has built. Dart stays with the investment question and customer-value test, without pitching a product as the answer.

Read original · Original 2

Both treat uncontrolled consumption and the after-the-fact discovery of costs as the core problem, and want the number tied to teams and decisions rather than read off a bill once it arrives.

Barnard's vantage point is finance inside an operating company, and his posts end with spend visibility and approval workflows for finance leaders. Dart frames the choice for executive teams weighing which economic constraint to fund, and asks what should stop being funded if the bet works.

Read original · Original 2

Both write first-person LinkedIn essays that build a lesson from a personal moment. Dart's fantasy in-joke post turns an individual aside into a point for a specific slice of the audience, as Vicino does with birthdays and reflection.

Vicino's material focuses on achievement, purpose and self-management for operators and founders; Dart's focuses on AI economics, pricing and retention for B2B software teams. Vicino's reflective register contrasts with Dart's commercial analysis.

Read original · Original 2

The posts describe a pricing motion that was designed, configured and enabled but still failed when a sales representative quoted the old model.

• They present an AI-guided quote product as a way to put the playbook in plain language, price against a real catalog with multi-attribute pricing, bundles, ramps, commits and burndown before a quote exists, show which approvals will trigger, and route for signature.
• A second post describes a metering product that meters, rates and bills usage on the same engine that priced the quote, locks terms at close, and rates every usage event against that snapshot.
• For a B2B SaaS company that already knows its pricing model and needs a session on quotation enforcement, metering and revenue operations, Kung’s material is more directly operational than Dart’s.

The tradeoff is that the posts are framed around vendors and product launches.

• They show the tooling and internal process for carrying a pricing change through quoting, approvals and billing, but do not develop the buyer-side pricing problem at the center of Christine Dart’s posts: predictable bills, whether value grows faster than usage, or which of seat, consumption and outcome models a customer will accept.
• For a strategic talk on aligning customer value with AI costs, ask Kung for material on buyer psychology and pricing-model choice; the posts do not explain how buyers respond to those questions.

Examples: Source 1 · Source 2

The posts speak from a CFO position: the most common question is what the company is spending on AI and what to do about it, and the first half of the answer is usually more than expected.

• They describe token usage changing daily, spread across models and tools, with part of it buried inside SaaS already paid for, and argue for AI spend tied to teams and commitments in real time, with alerts before a threshold is crossed and a next savings move.
• A second post describes the same governance problem at scale: at 50 people every software purchase went through finance, at 500 that broke, and the fix is routing low-risk requests automatically while flagging high-value contracts with context and inline compliance checks.
• For a B2B SaaS buyer that needs a session on controlling AI cost across providers and building purchase logic into workflows, Barnard’s material is more directly financial and operational than Dart’s.

The tradeoff is that the posts cover cost control and procurement workflow, not how to price AI features or design usage-based commercial models.

• They do not address Christine Dart’s core questions: who absorbs usage variability, how buyers react to consumption pricing, or how product guardrails and customer success keep usage tied to value.
• A campaign on AI pricing strategy would get the finance side of the problem, but would still need material from Dart or another source on pricing-model choice and customer-value alignment.

Examples: Source 1 · Source 2

The posts are motivational and reflective: a 42-item list of lessons about agency, focus, obstacles, trajectory and starting again, and a personal account of reaching a summit and realizing achievement does not fill a hole that is not trophy-shaped. Those posts would fit a different campaign decision: a keynote on high performance, purpose, resilience or the difference between achievement and fulfillment for a founder or executive audience.

For a buyer seeking AI pricing and customer-value alignment, Vicino’s posts offer no B2B SaaS pricing, AI usage, metering, procurement or revenue-operations content. Ask for material from another source to cover that substance; Vicino’s posts do not compete with Christine Dart’s on this subject.

Examples: Source 1 · Source 2