Jordan Zamir

Buying a revenue recognition module does not mean it handles everything natively.

• Under ASC 606, revenue is recognized when the service is delivered, not when the invoice goes out, and bundles must be split into distinct performance obligations recognized by standalone selling price.
• ERPs are built around the general ledger and invoices, so they hold what needs to be billed but not the contract that produced the bill.
• Finance staff end up opening signed PDFs or CRM records and retyping delivery dates, bundled services, and obligations—sometimes into a data model that cannot represent the pricing at all.
• Payment collection and revenue recognition are not the same thing.
• Zamir's conclusion: one contract and billing source of truth should feed both billing and recognition.
• The post closes with a pitch for Turnstile.

A $15,000 annual deal billed upfront should be recognized as $1,250 a month as the service is delivered. Zamir says the manual work has not gone away; it has moved "from an Excel model to a more expensive piece of software," leaving "three accountants in a trench coat doing most of the heavy lifting manually."

Read original

Approval processes therefore get heavier as companies grow, even when the underlying risk has changed.

• The goal is not a complex multi-tiered matrix, but to route fewer deals to humans over time while still catching exceptions that carry real risk.
• Three habits follow: set a clear standard deal baseline with three to five core triggers, such as deep discounts or unusual payment terms, and no more than two review levels; audit exception logs with finance and revenue operations each quarter; and prune rules that fire constantly but are almost always approved, because they tax the team without protecting the business.
• The post points to a longer blog post on right-sizing approvals by company stage.

If requests for Net 45 terms on large enterprise deals are approved ninety percent of the time, stop approving them manually and fold those terms into the standard deal definition.

Read original

Pasting data into a chat prompt every day is "just digital manual labor," not an efficiency gain.

• The real gain comes from turning prompts into repeatable skills connected directly to operational data.
• The post describes the daily reality these skills are meant to replace: a dozen tabs open before anyone can answer a meaningful question, checking CRM pipeline, billing collections, the close calendar, bank portals, and spreadsheets.
• Guest presenter Andy Aupperlee leads the announced session, sharing practical AI patterns; the views and build are presented as their demonstration, not Zamir's.
• Advertised takeaways include the difference between a standard prompt and a reusable skill, a starter prompt script, a framework for saving and automating the briefing, and access to a recording and templates.
• Zamir calls it a live, practical build with "no sales pitch," though one of the connected data sources is Turnstile, their own product.

Andy Aupperlee opens Claude with four connected sources—a Google Sheet, an Excel file, a CRM, and Turnstile—and runs a prompt to produce a single-page briefing covering key metrics, flagged operational risks, and high-priority action items for the day.

Read original

It offers the clearest statement of the argument running through Zamir’s other posts.

Zamir challenges the familiar claim that revenue recognition is solved when a company upgrades from QuickBooks to a full ERP such as NetSuite, Campfire, or Rillet.

• Buying a revenue recognition module does not mean it handles everything natively.
• The post lays out what ASC 606 requires: a $15,000 annual deal billed upfront must be recognized at $1,250 a month as the service is delivered, while a software-plus-implementation bundle must be split into distinct performance obligations and recognized at different rates based on standalone selling price.
• That requires a source of truth that captures the contract as signed.
• ERPs are built around the general ledger and invoices, so they rarely hold that original deal context.
• In practice, someone on the finance team opens signed PDFs or CRM records and retypes bundled services, delivery dates, and performance obligations into the accounting system—sometimes into a data model that cannot represent the pricing in the first place.
• Zamir’s core point: when the process depends on a person translating contracts into the accounting system, the manual work has not disappeared; it has moved from an Excel model to more expensive software.
• The closing pitch, promoted through Turnstile, is for one contract and billing source of truth feeding both billing and revenue recognition.

For brands planning a campaign

A vendor selling to finance teams can use the distinction between ERP data and contract data to reframe messaging for prospects who assume new accounting software will solve their revenue recognition problem. The argument suits explainer content that leads with the ASC 606 arithmetic and introduces the product second, or a demo script built around a bundled software-plus-implementation deal.

The post turns a policy complaint into three testable habits rather than an argument about culture.

The post starts with how approval processes age: adding a rule is easy because each one addresses a real or perceived risk, but removing one is hard because no revenue leader wants to be the person who took away a control.

• As companies grow, approval matrices get heavier even when the underlying business has changed.
• Zamir reframes the goal: a good approval process routes fewer deals to people over time while still catching exceptions that carry real risk.
• They offer three habits.
• First, start with a minimal process: define the standard deal baseline, choose three to five triggers such as deep discounts or unusual payment terms, and cap reviews at two levels so the company does not give up early-stage speed.
• Second, audit exceptions in quarterly logs: if a specific exception, such as Net 45 terms on large enterprise deals, is approved ninety percent of the time, stop approving it manually and fold it into the standard deal definition.
• Third, prune rules that are always allowed: a trigger that fires constantly and is nearly always approved taxes the team rather than protecting the business.
• The post points to a longer blog post on right-sizing approvals by company stage.

For brands planning a campaign

Useful for positioning against enterprise-heavy competitors with a staged approach to approvals, and for content aimed at founders or revenue operations leads at growing companies. The ninety-percent-approved test gives a webinar or calculator-style asset a concrete mechanism to build around.

The post outlines the approach Zamir sees as the real productivity gain and points readers to a session they can assess for themselves.

The post describes a daily routine: checking the CRM for pipeline movement, the billing system for overnight collections, the close calendar, bank portals, and spreadsheets before answering any meaningful question.

• By then, much of the morning is gone.
• Zamir contrasts this with the common advice to type one-off prompts into a chat window, calling that digital manual labor rather than an efficiency gain.
• The improvement, they argue, comes from turning prompts into repeatable skills connected to operational data.
• The post announces a live session on November 12 in which Andy Aupperlee connects Claude to four data sources—a Google Sheet, an Excel file, a CRM, and Turnstile—and runs a prompt to produce a single-page briefing covering key metrics, flagged operational risks, and high-priority actions.
• The stated takeaways are the difference between a standard prompt and a reusable skill, a starter prompt script, a framework for saving and automating the briefing, and access to the recording and templates.
• Ask for the prompt text and registration link, which the post refers to as being in the first comment.

For brands planning a campaign

A starting point for co-marketing around AI in finance operations, especially for vendors whose product can appear as one connected source in a recurring briefing. Treat the post as an announcement tied to a person and a specific setup; the instructional content is in the linked session.

They say ERPs are built around the general ledger and invoices, so they know what needs to be billed but not the terms of the contract behind the bill.

• Finance staff then open signed PDFs and CRM records to retype delivery dates, bundled services, and performance obligations by hand — moving "from an Excel model to a more expensive piece of software."
• Their example: a $15,000 upfront annual deal should be recognized at $1,250 a month as the service is delivered, while software bundled with implementation must be split into distinct performance obligations recognized by standalone selling price.
• Payment collection, they stress, is not the same thing as revenue recognition.

A worked numerical example, a named comparison of three ERP options, and a closing statement of the problem a contract-based billing system solves.

The post ends with a direct pitch for Turnstile, making it an educational argument with a vendor call to action rather than neutral analysis.

For brands planning a campaign

A brand selling billing, CPQ, or revenue software can challenge the "just upgrade your ERP" assumption. The strongest content angle is a contract-data-to-billing demonstration: show structured contract terms flowing into revenue schedules without retyping, using the $15,000 annual deal as a test case buyers can check against their own pricing.

Examples: Source 1

As companies grow, approval processes get heavier even when the underlying risk changes.

• Three habits follow.
• First, start with a minimum process: a clear standard-deal baseline, three to five core triggers such as deep discounts or unusual payment terms, and no more than two review levels.
• Second, have finance and revenue operations audit exceptions quarterly — if Net 45 terms on large enterprise deals are approved ninety percent of the time, make them standard instead of routing each one to a human.
• Third, prune rules that fire constantly but are almost always approved, because they tax the team without catching risk.
• The goal is to route fewer deals to humans over time while still catching exceptions that carry real risk.

A numbered three-part framework, a concrete approval-rate threshold used as a decision rule, and a pointer to a longer blog post.

For brands planning a campaign

This is useful material for sales operations, CPQ, and deal-desk tooling campaigns.

• The angle is fewer, better-targeted controls rather than more approvals, backed by the quarterly exception-log review.
• A brand could ask Zamir to build a decision framework for when an exception becomes standard policy — a concrete deliverable tied to approval-workflow or revenue-operations products.

Examples: Source 1

Their example is an automated morning briefing built in Claude from four connected sources — a Google Sheet, an Excel file, a CRM, and Turnstile — that produces a one-page briefing on key metrics, flagged operational risks, and daily priorities.

• The session is presented as a live build with no sales pitch, led by named collaborator Andy Aupperlee.
• Advertised takeaways include the starter prompt script, a framework for saving and automating the briefing, and the recording and template materials.
• The intended audience is finance leaders who sign off on metrics or manage teams that spend hours assembling data each morning.

A live demonstration with a guest presenter; the post announces registration, names the tools used, and lists practical takeaways.

The demonstration uses Zamir's own product as a connected data source, so the "no sales pitch" framing describes the session format, not the surrounding content. Ask whether a version using the brand's own data source is possible.

For brands planning a campaign

Zamir can lead a co-hosted live-build session for a finance or operations software brand.

• The prompt script, template, and recording are partnership deliverables to negotiate.
• Zamir also names collaborators, so a brand should plan for a two-person format.
• Since they explicitly advertise "no sales pitch," a campaign that depends on hard product messaging inside the session is a poor match.

Examples: Source 1

A second post advertises a 12 November session where a co-presenter builds an automated morning briefing in Claude using a Google Sheet, an Excel file, a CRM, and Turnstile, with the recording and template materials offered to registrants. Both posts promote Turnstile's product.

View example

Claude is the tool being demonstrated. The post describes the process, offers the recording and template materials, and calls the session "a live, practical build with no sales pitch."

View example

Where they trace how a signed contract becomes recognized revenue, Barnard shows how software spend and AI token usage go unmanaged across teams, arguing for building logic into the process rather than adding approval gates. Both treat finance as a design problem about where information lives, not just a reporting function.

Barnard recounts a problem he encountered as a company CFO and helped build a product around: controlling costs and purchasing. Zamir focuses on the accounting mechanics, working through contract terms, performance obligations, and how billing systems represent them.

Read original · Original 2

Both use a striking case to make the abstract problem concrete and frame their product as the thing that reads structured commercial data properly.

Korke's audience is private equity firms conducting diligence on a target, with the payoff of a valuation adjustment or recovery in the first ninety days.

• Zamir's audience is the finance team running its own books, with the payoff of a cleaner monthly recognition process.
• Korke's method relies on pattern detection across large transaction sets, while they reason from accounting rules and contract structure.

Read original · Original 2

Her conference spend-guessing game resembles Zamir's worked examples, using one memorable number to show how far an organization's understanding can drift from reality.

Finkelsteyn focuses on telecom and the spend, contracts, and infrastructure around it, not accounting standards or revenue recognition. She draws on years of observing enterprise buying across many organizations rather than a rule such as ASC 606, and proposes an ongoing advisory relationship rather than a data source of truth.

Read original · Original 2

The posts give a finance leader’s account of two scaling failures: at 50 people, every software purchase ran through the CFO; at 500, the same model slowed routine tool purchases and let a $50,000 commitment land on a corporate card without finance knowing.

• The proposed fix is routing logic inside the workflow: automatic approval for low-risk, low-value requests, fast flags to the right owner for high-value contracts, and compliance checks inline.
• A second post frames the most common CFO question as “What’s our AI spend, and what do we do about it?”, with token costs spread across many models and hidden inside existing SaaS.
• This is a stronger match for a procurement, spend-management, AI cost-optimization, or approval-automation campaign aimed at finance leaders who already understand their billing model.

You give up Zamir’s specific revenue-recognition teaching.

• Matt Barnard’s posts do not explain ASC 606 mechanics, contract-data flow, or how software and implementation are split into performance obligations.
• For a campaign focused on improving rev rec or connecting signed contracts to billing, Barnard supplies the approval and spend-visibility layer, not the revenue-recognition layer.
• Ask for another asset covering the contract-to-revenue schedule.

Examples: Source 1 · Source 2

The post gives a quantified diligence case: a $550M software company where analysis flagged $1.2M in annual unbilled contract escalators, $800K per year in pricing exceptions that never expired, and $1M in services delivered but never invoiced.

• It explains why traditional due diligence misses these patterns: deal teams sample invoices and review high-level financials rather than every contract term and transaction.
• It lists anomaly types such as recurring revenue that stopped without cancellation, expired terms with unchanged billing, unbilled usage overages, and temporary discounts that became permanent.
• This is a better fit when the buyer decision is “How do we find recoverable revenue before or after a deal?” rather than “How do we run monthly revenue recognition?”

The posts present a single, promotional case study aimed at PE firms and diligence teams, not accounting and revenue-operations teams running ASC 606 month to month.

• They do not cover deal approval design, standard deal baselines, or approval-trigger pruning.
• For a B2B SaaS vendor selling revenue-recognition software to finance teams, Shefali Korke can carry the diligence and revenue-leakage angle, but not the recurring close and billing-workflow angle.

Examples: Source 1 · Source 2

The posts compare five common models—aggregator, consultant, agent, TEM platform, and IT partner/MSP—and argue that each solves part of the telecom problem without providing a whole view.

• One post uses a healthcare analogy: the recommendation should follow the customer’s need, not the incentive of a single business model.
• The other describes a conference exercise called “Guess Your Telecom Spend,” where an infrastructure manager believed monthly telecom spend was about $20,000 and the real figure was closer to $170,000.
• It’s a concrete discovery and qualification exercise a brand could adapt, directly supporting content about visibility gaps across engineering, accounts payable, and leadership.

The posts focus on telecom, not SaaS revenue recognition or deal approvals.

• The buyer committee is IT, finance, and accounts payable working on connectivity, unified communications, and contact center spend—not the revenue-operations and accounting buyers seeking ASC 606 compliance, contract-data flow, or approval-trigger design.
• For a campaign promising ASC 606 compliance, contract-data flow, or approval-trigger design, Tatiana Finkelsteyn is not a substitute.
• She addresses a different problem within the same broad finance-and-operations audience.

Examples: Source 1 · Source 2