Series B Startup Announces IPO Plans, Discovers Its Revenue Recognition Policy Is a Slack Thread

SATIRE — At 9:04 a.m. on Monday, Nimbus Orchard, a Series B software company with 143 employees, three finance people, and a valuation large enough to make everyone use the phrase “public-company trajectory,” announced that it was beginning IPO readiness. At 9:11, the newly hired VP of Finance asked for the company’s revenue recognition policy. At 9:12, someone replied with a link to a Slack thread titled: “rev rec question lol.”

The thread, created seventeen months earlier by a sales operations manager who has since become Head of Monetization Systems, contained 46 messages, two screenshots of contract language, a GIF of a man falling through a ceiling, and the governing principle: “We usually book it when the customer is happy-ish.”

IPO readiness begins with a ceremonial search for the spreadsheet

The company had understood IPO readiness to mean selecting an investment bank, updating the pitch deck fonts, and asking outside counsel whether the founders could continue posting boat photos. Finance had a different interpretation. It began with an archaeological dig through Google Drive, NetSuite attachments, old billing exports, and a folder named FINAL_final_DO_NOT_DELETE_2.

The first discovery was that the company had a policy, in the broad spiritual sense. It had never been written as a policy because everyone involved had been “aligned.” The alignment was maintained through a quarterly meeting called Revenue Sync, attended by Accounting, Sales, Legal, Deal Desk, Customer Success, and occasionally a Product manager who came to explain why the product had become an entirely different product.

The second discovery was that every department had correctly followed the policy it believed existed. Sales believed revenue began when a contract was signed, unless the customer asked for an implementation. Customer Success believed revenue began when the implementation was complete, unless there was a pending feature. Accounting believed revenue began when it received sufficient evidence that something had happened. Legal believed the contract was enforceable, except where Commercial had modified it in a “small, customer-friendly way.”

There was no conflict, exactly. There were merely six internally consistent universes sharing a general ledger.

The hiring plan immediately becomes a controlled emergency

By Tuesday, the CFO had opened requisitions for a Director of Technical Accounting, a Revenue Accounting Manager, an SEC Reporting Manager, a SOX Program Lead, a Billing Operations Manager, and a Senior Accountant described as “comfortable with ambiguity.” The last phrase meant the candidate would be asked to reconcile contracts whose payment terms were stored in Salesforce, invoicing instructions were stored in email, acceptance terms were stored in Notion, and actual customer behavior was stored in the hearts of the account executives.

The job descriptions required public-company experience, pre-IPO experience, SaaS experience, ASC 606 experience, NetSuite experience, Salesforce experience, an ability to influence cross-functional stakeholders, and preferably “the calm of a person who has seen a revenue waterfall calculated in a pivot table with merged cells.”

Candidates who asked whether the role had direct reports were told, “Not today, but you’ll have substantial ownership.” Candidates who asked whether the company had a documented revenue policy were told, “That is one of the exciting greenfield opportunities.” Candidates who asked why the role had been open for eight months were told that the company was being thoughtful about fit, which was technically true: it was still looking for someone who could be both a revenue recognition specialist and a medium-sized consulting firm.

The interview process tests judgment under fictional conditions

Applicants advanced to a case study: a 73-page customer agreement for a product called Nimbus Orchard Enterprise Infinity, with subscriptions, usage tiers, implementation services, training, credits, a reseller arrangement, a side letter, a promise of future functionality, and an appendix whose final page read simply, “Commercial terms as discussed.”

The instructions said: “Please spend no more than 90 minutes.” The deliverable requested a revenue memo, standalone selling price analysis, contract asset rollforward, disclosure implications, controls gap assessment, implementation plan, audit committee slide, and a short explanation suitable for Sales that would not make Sales stop selling.

During the debrief, the panel asked the candidate to “walk through their thought process.” This meant the candidate would explain why the conclusion depended on facts not provided, while the Head of Sales explained that all missing facts were immaterial because the deal was strategically important. The General Counsel would agree, carefully, in a way that created three additional questions.

The strongest candidates did not insist on a single answer. They identified the decision points, named the documentation required, explained who had to own each judgment, and asked whether the company could enforce its contract approval process. This made the panel briefly silent, as nobody had previously considered contract approval a process rather than a mood.

The contract option offers immediacy, plus a laptop-shaped riddle

To move faster, Nimbus Orchard brought in an interim revenue consultant on a six-month contract. The consultant was promised an urgent, high-impact mandate and received both: a 14-tab workbook called Revenue Schedule Master, read-only access to the billing system, and a Slack message at 11:43 p.m. asking whether deferred revenue could be “made more investor-friendly.”

For finance candidates considering this type of assignment, the contract-versus-permanent distinction is usually less philosophical than advertised. A contract role can be a defined cleanup, implementation, close stabilization, audit remediation, transaction project, or coverage need. It can also be a permanent job wearing a temporary badge while leadership waits to see whether the work requires authority, headcount, or an exorcism.

Before accepting, the consultant asked who could make decisions on policy, systems, contracts, and headcount. The company named seven people. None had the same answer. The consultant added a ninth workstream: governance.

The offer arrives with an equity explanation and a new close calendar

When Nimbus Orchard finally chose a permanent Director of Revenue Accounting, the offer process featured the standard components: base pay, bonus, equity, a title that had changed twice during interviews, and a promise that the company was “very close” to hiring the team needed to support the role.

The candidate negotiated less around broad adjectives and more around operating facts. What would they own on day one? Who would approve accounting conclusions? Would implementation and billing report into the role, partner with it, or continue to send urgent messages from parallel organizational dimensions? Was there budget for systems support and outside technical accounting help? What did “IPO readiness” mean in the next twelve months: documented policies, a faster close, audit support, controls, reporting infrastructure, or simply a calendar invite with bankers?

These questions were characterized internally as “very senior.” This was meant as a compliment, though it also meant the candidate had noticed the job was not merely to recognize revenue. It was to create the conditions under which revenue could be recognized repeatedly, consistently, documentedly, and without an emergency meeting called “Quick Rev Rec Alignment.”

The non-satirical part

A startup does not become ready for outside scrutiny because it hires one technically strong finance leader or announces an IPO goal. Readiness is built through clear ownership, durable documentation, systems that reflect the business, and decisions that can survive turnover. The person hired to build that structure should know whether leadership is prepared to give them the authority, resources, and time to do it.