Branden Jenkins

For investors, they name two drivers of the premium: agent-driven products with a clear path to monetization, and AI working inside the business.

• The internal half shows up in changed roles: developers review AI output instead of writing every line, smaller sales teams run agentic workflows, and onboarding, first-tier support, and routine customer-success contact are automated.
• They acknowledge the claim is bold for a company more than a decade old and say they are making it anyway.

A vice president of account management, Jared Mackey, had run teams for a decade without writing code, then built a full internal app over one weekend so account managers could get data without filing a request. Jenkins spent two days in Claude Code building an agent that turns raw source code and Jira tickets into enablement content, while the CFO's finance team built their own agents at an offsite.

In Jenkins's investor-facing post, they trace the market's shift from post-Covid growth at all costs to capital efficiency to a large premium for AI. They argue the controllable response is to become AI-native rather than chase whatever investors value on a given day.

Read original · Original 2

Changing prices every month or quarter creates problems, they say, especially for the customer sold last month.

• What should be continuous is understanding where each account sits on the value gap: either packaged too high and not yet grown into it, or packaged too low and using far more than it pays for.
• Jenkins argues most companies cannot say which is true for any given account.
• The fallout is not usually a pricing dispute, but a customer comparing the platform to something unrelated and deciding the price should match.

A customer called to negotiate a lower price.

• Jenkins checked usage: the company runs $250 million in API calls a year and bills 4,500 customers a day through Maxio, and in their view was underpaying.
• They say that conversation only works with visibility into three things: what was sold, what the customer is entitled to, and what they actually use.

Read original

Their point is not that sellers should be constrained, but that flexibility should come from the billing system rather than from capping a representative's creativity. Companies that let the tail wag the dog, they say, only notice when a rep asks for something simple and finance says it cannot be done.

Maxio's CFO, Jon Cochrane, walked Jenkins through the same customer and the same deal in the pipeline, with four ways to book it: sell 12 months with two free, sell 14 months with two free, give free access for two months but get the signature today, or sell a 12-month term and defer the invoice for 60 days. The customer needed the same thing in every case, but each option starts revenue recognition differently, lands in ARR differently, and changes amortization and upsell timing.

Read original

The problem compounds with every new feature and packaging change.

• Account managers lose track of what a customer actually owns versus what they still need to buy, production access becomes an honor system, and customers either get frustrated or are quietly left behind.
• Jenkins's fix is to connect what a customer buys to what they can do: design the monetization plan, connect and meter the data sources, map the plan to the products, features, and usage limits it unlocks, then sync it to the systems the business already runs on.

Jenkins presents Maxio Entitlements as the mechanism that automatically closes the gap and syncs with ERP, GL, and CRM, so managers get the insight rather than a manual reconciliation.

Read original

In their experience, historical data that gets deferred never gets migrated, leaving two systems of record: the new one for current business and the old system or spreadsheets for anything requiring history.

• The consequences surface later, at close and audit time, when FP&A cannot model a renewal cohort, produce a clean deferred waterfall, or answer a board question that needs several quarters of context.
• Jenkins advises buyers to ask vendors whether they will help migrate all the history, and says an implementation partner who tells you to slow down may be the one looking out for you.

A VP of Finance halfway through selecting a billing platform faced a hard date when her current system would go dark.

• That system held more than two years of live contracts, with an unknown number more in Excel.
• Jenkins traces what happens if only current subscriptions are loaded: go-live works, everyone breathes for a quarter, then the first close takes days longer because the context lives in two places.

Read original

ERP, CRM, and billing systems already hold clean, dependable data, so AI should take verified output and help interpret it through variance analysis, trend spotting, board summaries, contract summaries, collection emails, and expense categorization.

• They recommend starting with high-friction, low-risk work and running a validation phase where wrong answers are fed back in and documented.
• Their view: finance teams that work this out first gain more time to think, not just cleaner reporting.

Jenkins quotes Maxio CFO Jon Cochrane saying, "I think I saved us 500 bucks," after a prospect's NDA arrived.

• Instead of routing it to outside counsel, Cochrane put his own template and the prospect's into Claude and asked for a review.
• The prospect's terms were already more generous than his own, and the only addition worth making was a cap on the trade secret term; the NDA was signed within two hours.
• Jenkins also describes a Slack setup where a team tags Claude to ask Maxio about customers, subscriptions, invoices, and contracts, and which invoices are pending before a billing run.

Read original · Original 2 · Original 3

They are explicit that this is not about running customer success with fewer people, but about giving the team more room for the irreplaceable part of the job. They are also candid about the current quality bar rather than presenting the transition as finished.

At a customer success gathering in Atlanta, Jenkins describes three agents in motion: new customer environments that spin up when a deal closes and pull call transcripts, deal notes, and agreements into a pipeline; agents that align customer questions and requirements with source code and customer environments; and agents that build bespoke training materials from a customer's configurations, personas, and workflows. They note more than 1,000 reviews across G2 and Capterra averaging 4.3, call that good but not good enough, and introduce Robert Williams as the new head of Customer Success.

Read original · Original 2

Jenkins separates the market narrative from the operational work.

• They say investors now pay a premium for two things: agent-driven products with clear monetization, and AI embedded in internal operations.
• The post names specific shifts, such as moving developers from writing code to reviewing AI output, using leaner sales teams with agentic workflows, and automating onboarding, tier-one support and routine customer-success touchpoints.
• It ends by asking readers how they are making their organization AI-native.

For brands planning a campaign

For a finance and revenue leaders webinar, this offers a ready-made topic spine: product monetization, org design and measurable internal efficiency. It closes with a question rather than a product pitch.

Speaking at Jefferies' Office of the CFO Summit at the NYSE, Jenkins argues that changing prices every month or quarter creates more problems than it solves.

• What should be continuous is tracking each customer's value gap: whether they are packaged too high and have not grown into it, or packaged too low and are using more than they pay for.
• They give one example: a customer doing $250 million in API calls a year and billing 4,500 customers a day through Maxio asked for a discount, while Jenkins's read was that the customer was underpaying.
• The post says the conversation only works with visibility into what was sold, what the customer is entitled to, and what they actually use.

For brands planning a campaign

A pricing strategy talk can focus on value-gap monitoring and packaging fit, rather than a generic annual-review debate. The example gives finance leaders a practical reason to examine entitlement and usage data before conceding on price.

Jenkins describes a VP of Finance halfway through choosing a billing platform, with a hard deadline before the current system goes dark.

• The company has two-plus years of live contracts in the current system and an unknown number in Excel.
• They argue against loading only active subscriptions and bringing historicals in later, because deferred historical data often never gets migrated.
• The result is two systems of record: one for current billing, one for history.
• Jenkins ties that to Q1 close problems, FP&A renewal cohort modeling, clean deferred waterfalls for audits, and board forecast questions that need several quarters of context.

For brands planning a campaign

This gives a webinar a concrete migration-risk segment: ask vendors whether they will help move all history, not just get the system live. It also supports a speaker angle on why implementation expertise and data migration deserve as much scrutiny as software features.

Jenkins describes a deal where the customer wants a deferred start date while the software goes live immediately, effectively asking for two months free on a 12-month term.

• They list four ways the sales representative could book it: sell 12 months with two free, sell 14 months with two free, give free access for two months but get the signature today, or sell a 12-month term and defer the invoice for 60 days.
• All four work for the customer, but each changes revenue recognition timing, ARR treatment and amortization.
• Jenkins says the deciding factor is whether finance can record the deal, recognize the revenue and collect on it without capping a seller's creativity.

For brands planning a campaign

This is a strong example for a finance and revenue leaders session on billing systems and revenue operations. It shows how a speaker can make accounting consequences tangible without turning the talk into a product demo.

Jenkins starts with a real frustration: someone gave AI revenue data, it hallucinated a $2 discrepancy, added hours of work and made the finance team wary.

• They argue the mistake was asking AI to do the wrong job.
• Systems of record such as ERP, CRM and billing software should hold clean, dependable data; AI should use verified outputs to help with narrative, variance analysis, trend spotting and board summaries.
• The post suggests starting with high-friction, low-risk work such as summarizing vendor contracts, drafting collection emails and categorizing expense data, then running a validation phase where wrong answers are fed back and documented.

For brands planning a campaign

For an AI-native operations webinar, this offers a CFO-friendly trust framework instead of generic AI enthusiasm. It can anchor a segment on where to start, how to validate and why clean data plumbing comes before automation.

Jenkins explains Claude Tag in Slack: a user tags @Claude with a task, Claude works in the thread, posts progress and anyone in the channel can steer it.

• The post covers setup steps involving a Claude owner and a Slack admin, channel selection, a monthly spend limit, and connections to tools such as Salesforce or HubSpot, Dropbox for signed agreements, and Maxio for customers, subscriptions, invoices and contracts.
• Finance questions include which invoices are pending before tomorrow's billing run, which customer invoices are open, and which subscriptions renew next month.
• RevOps questions include briefing an account before a renewal call and listing past-due subscriptions by owner.

For brands planning a campaign

This is a practical demo hook for a finance and revenue webinar: billing answers where the team already talks. It also offers a product-led example of AI operations without claiming features beyond those described in the post.

Jenkins says companies launching usage-based or AI pricing often focus on tiers, rates and packaging, leaving provisioning for later.

• That creates problems with every new feature or packaging change: account managers lose track of what customers own and what they need to buy, production access becomes an honor system, and customers get frustrated or left behind.
• Jenkins presents Maxio Entitlements as a way to connect what customers buy to what they can do, from design and data-source connections through metering, mapping products and features, and syncing to ERP, GL and CRM.

For brands planning a campaign

A pricing and packaging talk can cover the gap between monetization design and actual customer access. It gives the speaker a specific operational problem to discuss before any product mention.

Jenkins calls Maxio an AI-native company despite its being more than a decade old, and says the people piece matters most.

• The post offers several examples: a VP of Account Management who had not written code built a full internal app over one weekend; Jenkins spent two days in Claude Code building an agent that turns raw source code and Jira tickets into enablement content; and the CFO's finance team built its own agents at an offsite.
• Jenkins links that internal work to a customer problem: finance teams losing time chasing payments, checking invoices and manually tying billing back to the general ledger.

For brands planning a campaign

This supports a webinar theme on AI adoption culture, not just AI tooling. Named internal examples give the speaker material for a practical segment on how teams build capability, while the customer problem connects the discussion to finance workflows.

Jenkins describes a customer success gathering in Atlanta and the question of how to make the team AI-native.

• The post says AI should give the team and customers fast, accurate answers without replacing relationships, clearing friction so trusted people can spend more time compounding value.
• It names three agents: one that spins up new customer environments when a deal closes and pulls call transcripts, deal notes and agreements into a pipeline; one that aligns customer questions and requirements with source code and environments; and one that builds bespoke training materials from configurations, personas and workflows.
• Jenkins also mentions 1,000+ reviews across G2 and Capterra, a 4.3 average, and the arrival of a new head of Customer Success.

For brands planning a campaign

This gives a webinar a customer-success angle on AI-native operations: automation that supports human relationships rather than replacing them. It also offers a concrete service-operations example to compare with finance automation.

Jenkins quotes the CFO saying, "I think I saved us 500 bucks," after a prospect's NDA arrived.

• Rather than send it to outside counsel and wait for comments, the CFO put the company template and the prospect's NDA into Claude and asked for a review.
• The response came faster, and the prospect's terms were already more generous; the only worthwhile addition was a cap on the trade secret term.
• The NDA was signed within two hours.
• Jenkins ties the story to a four-session series on AI-powered CFO workflows.

For brands planning a campaign

This is a familiar, low-risk example for a finance webinar on AI workflows. It shows a time and cost saving without overstating what AI can do in legal review.

In one post, they contrast traditional SaaS growth and retention metrics with the multiples AI-native companies command, then name two proof points investors look for: monetizable agent-driven products and internal AI-driven efficiency.

• Examples include developers reviewing AI output instead of writing all the code, leaner sales teams using agentic workflows, and automated onboarding and routine support.
• Another post makes the AI-native case for Maxio and offers concrete team examples, including a sales leader building an internal app over a weekend and an agent Jenkins built to turn source code and Jira tickets into enablement content.

Uses before-and-after contrasts: traditional SaaS KPIs versus AI-native multiples, and old roles versus agent-assisted roles.

{'note': 'The valuation framing reflects Jenkins’s read of investor behavior and Maxio’s positioning, not independent market data.'}

For brands planning a campaign

A strong webinar or keynote topic for finance, revenue, and operating leaders.

• The most useful angle is not “AI is important” but what changes inside a SaaS company’s product, finance, sales, and customer teams when AI becomes part of the operating model.
• Ask Jenkins to use team-level examples rather than valuation claims alone.

Examples: Source 1 · Source 2

They argue that pricing changes should be intentional, not constantly tweaked, while understanding the value gap should be continuous.

• Every customer is either packaged for more than they have grown into or packaged for less than they use.
• Jenkins cites a customer with $250 million in API calls a year, billing 4,500 customers a day, who asked for a discount.
• The conversation works, they say, only with visibility into what was sold, what the customer is entitled to, and what they actually use.

Starts with a live event question, challenges its framing, then gives a customer example and three data points to track.

For brands planning a campaign

Well suited to a pricing and packaging session for finance and revenue leaders.

• Focus on the operating discipline of tracking the value gap account by account, rather than repricing cadence.
• Pair the topic with a concrete prompt about what data a finance team needs to answer a discount request.

Examples: Source 1

As features and packaging change, account managers lose track of what customers own versus what they need to buy, and production access becomes an honor system. Jenkins presents Maxio Entitlements as the fix: connect what a customer buys to what they can do, map the monetization plan to products, features, and usage limits, and sync it to ERP, GL, and CRM systems.

Frames the problem as a compounding operational failure, then walks through a connect-map-sync approach.

For brands planning a campaign

Useful for a RevOps or monetization webinar on making pricing model changes operational.

• Jenkins can speak to the execution gap between pricing strategy and entitlement systems.
• Ask them to distinguish general pricing advice from a Maxio product walkthrough.

Examples: Source 1

All four meet the customer’s need, but each affects revenue recognition, ARR, and amortization differently. Jenkins’s conclusion: once a company has recurring agreements, finance systems, and investors who read the numbers, what it can sell depends on whether finance can record the deal, recognize revenue, and collect.

For brands planning a campaign

A precise topic for a CFO, finance, or RevOps audience: how billing and revenue systems constrain or enable sales creativity.

• Ask Jenkins to walk through one deal structure and show where finance, sales, and systems need to agree.
• The example is concrete but anonymous; ask for a current, permitted customer example.

Examples: Source 1

Their argument: AI was asked to do the wrong job.

• Systems of record—ERP, CRM, and billing software—should handle clean, dependable numbers; AI should use verified output to help with variance analysis, trend spotting, board summaries, contract summaries, collection emails, and expense categorization.
• Jenkins suggests starting with high-friction, low-risk work and running a validation phase in which wrong answers are fed back and documented.
• Related posts show a CFO using Claude to review an NDA and save outside-counsel time, and a Slack-based Claude integration for asking billing questions about customers, subscriptions, invoices, and contracts.

States the common objection, reframes the problem, then gives three implementation rules and examples.

For brands planning a campaign

A practical finance AI adoption topic with built-in objections and examples.

• The strongest framing is “which finance tasks should AI do, and which should stay in systems of record?”
• Use Jenkins’s NDA and billing-query examples to move from theory to workflow.

Examples: Source 1 · Source 2 · Source 3

The temptation is to load active subscriptions first and migrate historical data later.

• Jenkins argues that deferred historical data often never gets migrated, leaving two systems of record: the new one for current billing and the old system or spreadsheets for history.
• That creates audit, forecasting, and board-reporting problems.
• Jenkins advises asking vendors whether they will help migrate all history, and says implementation partners who tell buyers to slow down may be protecting them.

Uses a buyer scenario, names the common shortcut, then traces the downstream consequences at close and audit.

For brands planning a campaign

A candid migration-readiness topic for finance leaders evaluating billing or revenue systems.

• Position Jenkins as a speaker on implementation risk, not just software features.
• Ask for specific migration decision points and questions buyers should ask vendors.

Examples: Source 1

They say AI should give teams and customers fast, accurate answers without replacing the relationship; its job is to clear friction so trusted people can spend more time compounding value.

• Examples include agents that spin up new customer environments from call transcripts, deal notes, and agreements; agents that align customer questions with source code and environments; and agents that build bespoke training materials from customer configurations and personas.
• They also note more than 1,000 reviews across G2 and Capterra with a 4.3 average and call that good but not good enough.

For brands planning a campaign

Good for a customer success, retention, or support operations session.

• Jenkins can discuss where agents handle onboarding, requirements, and training while humans maintain high-touch relationships.
• Ask how the team measures whether agents improve customer outcomes, not just internal speed.

Examples: Source 1 · Source 2

Their natural format is a first-person executive narrative built around a customer conversation, a finance workflow, or a contrarian framing of a common question. They often end with a direct question to the audience.

Event recaps and webinar promotion posts show the format Jenkins already uses publicly.

For brands planning a campaign

A moderated webinar, fireside chat, or panel fits better than a scripted product demo.

• The campaign should give Jenkins a finance-leader audience, a specific prompt, and room for concrete examples.
• Promotion should include the event registration or replay details if the session is part of a series.

Examples: Source 1 · Source 2 · Source 3

Posts use first-person language such as “our CFO,” “our customer success org,” and “I am proud that Maxio is…”

View example

The post does not state Jenkins’s title there.

View example

View example

Jenkins also describes building an internal agent with Claude Code, and a post credits Maxio’s CFO with using Claude for NDA review. The posts do not state contract terms.

View example

View example

Both work from concrete artefacts rather than abstractions: Gardner reviews financial statements and lists the red flags they find, then examines how AI-built software changes the economics of an established vendor by comparing it with two decades of open-source adoption.

Gardner writes as an outside reviewer and adviser, looking at other companies' numbers and the software market from above with diagnostic checklists and market analogies.

• Jenkins writes from inside, as the chief executive of the company they describe.
• Their examples are deals, customer conversations, and product decisions at Maxio—not audit findings across a portfolio.

Read original · Original 2

Both write about finance leaders arriving in a new seat and finding that the reporting problem is really a trust problem. They illustrate the argument with specific process examples rather than general claims.

Arif writes from the client-services and accounting-firm side about the practice of accounting: bank reconciliations, AP and AR, variance commentary, and the first 90 days of a CFO.

• Jenkins writes from the software-vendor side, focusing on the billing, pricing, and revenue systems a finance team runs on—not the accounting process itself.
• Arif's teaching is process-level; Jenkins's is product- and deal-level.

Read original · Original 2

Saperia argues that demand in a services firm goes unrecorded because nothing forces it into a system, and that booked work is the closest thing such a firm has to ARR.

• Jenkins argues that finance's ability to record a deal, recognise the revenue, and collect on it limits what a sales team can offer.
• Both write short, first-person arguments for finance and operating leaders.

Saperia covers professional services firms and the operating discipline of PE-backed businesses, including closes, pipeline, and quality-of-earnings readiness.

• Jenkins focuses on SaaS, with AI inside the product and the operating model.
• Saperia's advice is about adopting a sponsor's accountability without a sponsor; Jenkins's is about pricing, entitlements, and AI-native operations.

Read original · Original 2

In her posts, she argues that most finance teams spend 80% of their time producing numbers and 20% explaining them, and that the fix is AI-assisted work with a human review step: AI flags bank reconciliation anomalies, pattern matching handles the obvious AP/AR work, variance commentary gets a first draft, and a person writes the narrative.

• A second post argues that a new CFO's first quarter is about alignment, not dashboards, because the real problem is that no one trusts the numbers.
• That makes her a better fit for a session aimed at controllers, finance managers, or newly appointed CFOs who need a practical operating model for AI in the close process.

You trade away the CEO-level operating view and pricing-strategy thread Branden Jenkins brings.

• Their posts do not discuss a pricing model, tell an AI-native company-building story, or say they have run a webinar series or spoken at a finance event.
• The two posts are short LinkedIn posts, so their examples are less developed than those in longer customer stories.
• Verify identity and commercial availability before booking.

Examples: Source 1 · Source 2

In his posts, he draws on having reviewed financial statements of over a thousand SaaS companies to list red flags: poor gross margin definition, weak bank reconciliations, disconnected income statement/balance sheet/cash flow, mixed cash and accrual accounting, and a stand-alone MRR report.

• He explains how AI product costs should be split between COGS and R&D, why bank recs validate the financials, and why a separate MRR report must reconcile to revenue.
• A second post asks whether AI will disrupt application software the way open source did, arguing that free code has captured only a small share of the market because vendors provide implementation, training, support, hosting, stability, and accountability.
• That makes him a better fit for a webinar aimed at CFOs, auditors, or investors who need to pressure-test reporting quality or think through AI's effect on software business models.

You trade away the pricing and value-gap material, customer-conversation style, and operating examples from inside a live SaaS company.

• The posts are analytical and checklist-driven; they do not say Jenkins has spoken or produced webinars, or give a particular audience size.
• With only two posts, any single topic gets limited depth.
• Verify identity and commercial availability before booking.

Examples: Source 1 · Source 2

In his posts, he contrasts SaaS metrics with professional services: SaaS demand records itself in the billing system, while in services demand is human work that never lands anywhere unless a person records it.

• He argues that a clean pipeline record protects margin and grows revenue, and that utilization tells you about last month's capacity while demand tells you where next quarter's revenue is coming from.
• A second post describes leaders who want to run like a PE-backed firm without a sponsor and argues that discipline holds when someone with real stake asks for the numbers on a fixed calendar.
• That makes him a better fit for a webinar on professional services operations, backlog, or sponsor-style accountability than for a session aimed at B2B SaaS finance and revenue leaders.

You trade away the B2B SaaS pricing and AI-native operations content needed for a campaign on those topics.

• The posts focus on professional services firms and PE-style operating discipline, not SaaS pricing, billing migration, or revenue recognition.
• Verify identity and commercial availability before booking.

Examples: Source 1 · Source 2