# Jordan Zamir

Jordan Zamir writes about finance operations for growing companies, including revenue recognition, deal approvals, and practical ways to use AI in finance workflows.

- Profile: https://b2binfluencer.marketing/creators/jordan-zamir/
- LinkedIn: https://www.linkedin.com/in/jzamir
- Topics: artificial-intelligence, sales, revenue-operations
- Based on 10 dated posts, latest 2026-10-07

## Summary

Jordan Zamir is useful for educational finance operations content on revenue recognition, deal approvals, and practical AI workflows.

- Best for: A B2B SaaS billing, revenue recognition, CPQ, or deal-desk campaign for finance and revenue operations teams.
- Not for: An ERP vendor wanting a paid placement saying its ERP alone fixes ASC 606.
- Check first: Confirm audience composition, media kit, rate card, and examples of sponsored placements.

### Takeaways

- $15,000 annual contract billed upfront becomes $1,250 monthly revenue as service is delivered.
- Approval rule approved 90% of the time may belong in standard policy, not manual exception.
- AI finance session proposes live Claude build from Google Sheet, Excel, CRM, and Turnstile.

## Main ideas

- **A bigger ERP does not fix revenue recognition—the signed contract does**: Zamir argues that upgrading from QuickBooks to a full ERP such as NetSuite, Campfire, or Rillet does not solve revenue recognition; it misidentifies the problem. 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.
- **Approval rules should get lighter as a company scales, not heavier**: Zamir argues that approval rules accumulate for an asymmetric reason: adding a trigger is easy because every rule points to a real or perceived risk, while removing one is hard because no revenue leader wants to be the person who took away a control. 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.
- **Repeatable, data-connected AI skills beat one-off prompts**: Zamir contrasts two uses of AI in finance. 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.

## Work to read

- [Why moving to a real ERP does not fix revenue recognition](https://www.linkedin.com/posts/jzamir_rev-rec-is-solved-all-we-have-to-do-is-activity-7512858895707537408-fdoY)
- [Approval rules accumulate and slow down sales cycles](https://www.linkedin.com/posts/jzamir_approval-rules-tend-to-accumulate-over-time-activity-7513222035137785856-IQwB)
- [Building an automated morning briefing in Claude from existing finance data](https://www.linkedin.com/posts/jzamir_if-you-run-finance-at-a-growing-company-activity-7513583678984359936-Wgb6)

## Brand relationships

- **Turnstile** (disclosed_partnership)
- **Claude** (mention)

## Partnerships

Zamir's posts don't describe sponsorship formats, packages, or partnership terms. They show first-party outreach: a post promoting Turnstile's billing and revenue recognition product, and an invitation to a live session on November 12 with Andy Aupperlee on building an automated morning briefing in Claude from existing data sources, presented as a practical build with no sales pitch. Both are product- and event-led marketing, not paid placements from outside brands. Before committing budget to a paid placement, ask Zamir directly about accepted formats, pricing, deliverables, and terms.

## Alternatives

- Matt Barnard: Choose Matt Barnard when the campaign is about controlling software and AI spend at scale, not teaching revenue recognition. 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.
- Shefali Korke: Choose Shefali Korke when the campaign targets private-equity diligence, post-close value creation, or revenue leakage inside acquired software companies. 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?”
- Tatiana Finkelsteyn: Choose Tatiana Finkelsteyn when the campaign is about enterprise telecom cost visibility and lifecycle management. 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.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/