StackedCFO

A personal blog post by Casper Zhao

I almost walked away from a deal back in the day.

Not as a participant. As an advisor. The target company had $14 million in ARR, a product that enterprise customers genuinely loved, and a team that had built something real. The PE firm I was working with had signed an LOI at a valuation that would have changed the founder's life. We were three weeks from close.

Then the quality of earnings review started.

What we found was not fraud. It was not incompetence in the way most people imagine incompetence. It was something more common and more dangerous. It was a finance function that had grown through accretion rather than architecture. Each time the business hit a new complexity threshold, someone added a spreadsheet, a manual workaround, or a well-intentioned patch. None of these patches were wrong in isolation. All of them were wrong in aggregate.

The deferred revenue subledger did not tie to the general ledger. It had not tied for two and a half years. The variance was 4 percent, which sounds small until you realize that 4 percent of $8 million in deferred revenue is $320,000 of unexplained discrepancy. The revenue recognition policy memo had been written when the company sold only annual subscriptions, but the company had since introduced usage-based contracts with minimum commitments, hybrid pricing, and bundled professional services. The memo described a company that no longer existed. Commission capitalization schedules existed but the benefit period assumptions had never been documented, meaning the technical accounting advisor could challenge them and the company would have no defense.

The deal did not collapse. It retraded. The purchase price came down by $3 million. The closing timeline extended by five weeks. The founder hired a technical accounting consultant at his own expense to oversee remediation. The earnout structure was modified to include thresholds that became harder to hit after the standalone selling price methodology was revised.

I remember sitting in the conference room after the retrading call, looking at the financial statements spread across the table, and thinking: this was entirely preventable. Every single issue we found could have been addressed in an afternoon if someone had known to address it two years earlier. But no one knew. The controller was competent and honest. The CFO was experienced. The founder was smart. They simply did not have the framework to anticipate what would matter when scrutiny arrived.

That was the moment this book started forming in my mind. Not as a book. As a question. Why does the same pattern repeat across hundreds of transactions, dozens of audit engagements, and countless fundraising processes? Why do finance functions that seem to work fine under normal conditions collapse under the specific pressure of due diligence, audit, or IPO preparation? And why do smart, capable finance leaders consistently fail to see the gaps until a forcing event exposes them?

The answer, I realized, was that the knowledge required to build a SaaS finance function that withstands scrutiny exists in fragments. ASC 606 guidance lives in accounting firm white papers. Metric definitions live in investor blog posts. Technology evaluation lives in vendor comparison reports. Operational process design lives in the heads of individual practitioners who learned it through trial and error. No single source integrates all of these dimensions into a coherent framework that a finance leader can implement.

So I decided to write that source. What started as a question became an outline. What started as an outline became a forty-chapter manuscript. What started as a manuscript became the book that I am now writing about in this post.

The process of writing it took longer than I expected and taught me more than I anticipated. I want to share some of what I learned, because the lessons extend beyond the book itself.

The Pattern That Repeats

Across the transactions I worked on, the same failure modes appeared with predictable regularity. I started keeping a list, not because I planned to write a book, but because I wanted to understand whether what I was seeing was systematic or coincidental.

It was systematic.

Deferred revenue reconciliations that do not tie. Revenue recognition policies that were written once and never updated as the business evolved. Commission capitalization schedules with undocumented benefit period assumptions. Standalone selling price estimations that do not reflect actual market pricing. Contract modifications processed in the billing system but never reflected in revenue recognition schedules. Customer acquisition costs calculated differently by the finance team, the sales team, and the board. Net revenue retention numbers that cannot be reproduced from underlying contract data. Cohort analyses that suffer from survivorship bias or censoring errors. Billing platforms selected based on feature checklists rather than actual contract complexity. ERP implementations that replicate inefficient processes rather than redesigning them. Close processes that take fifteen days because no one has invested in pre-close activities or automation.

None of these are exotic problems. They are the ordinary consequences of building a finance function incrementally under growth pressure. When you are hiring your third sales representative, closing your first enterprise deal, and onboarding your second product line simultaneously, you do not stop to redesign your revenue recognition policy memo. You add a spreadsheet and move on. When you are processing five hundred invoices a month and your billing platform cannot handle proration for mid-term upgrades, you do not evaluate three alternative platforms. You calculate the proration manually and move on.

Each decision is rational in context. The accumulation is irrational in aggregate. And the accumulation remains invisible because growth masks it. Revenue is increasing. Cash is accumulating. Investors are satisfied. The board is happy. Everything looks fine because the forcing event has not arrived.

The forcing event is the moment when someone examines your finance function with forensic intent. An auditor testing revenue recognition across a sample of contracts. A quality of earnings advisor tracing deferred revenue from contract origination through modification through recognition. An IPO readiness assessment evaluating internal controls against SOX requirements. A due diligence team requesting cohort data that you have never properly captured.

At that moment, the patches fail. The spreadsheets do not tie. The policy memos do not address current contract types. The reconciliations have variances that no one can explain. The metrics cannot be reproduced. And the cost of fixing these problems under time pressure, with a deal or a funding round or a public offering hanging in the balance, vastly exceeds the cost of preventing them.

I have watched this pattern repeat enough times to know that it is not bad luck. It is structural. The knowledge to prevent it exists, but it is not accessible in a form that practicing finance leaders can use. That is the gap this book attempts to close.

What I Learned Writing It

I expected writing this book to be an exercise in organizing knowledge I already possessed. I was wrong. The process of structuring the material revealed gaps in my own understanding that years of practice had allowed me to overlook.

The first gap was in how I thought about the relationship between accounting standards and business strategy. I had always treated ASC 606 as a compliance framework. You identify contracts, identify performance obligations, determine transaction prices, allocate prices, and recognize revenue. The steps are mechanical. The application requires judgment, but the framework is fixed.

Writing Chapter 2, I realized that this view is incomplete. ASC 606 is not merely a compliance framework. It is the technical architecture that shapes every financial statement, every board presentation, and every investor conversation. The way you identify performance obligations determines your revenue recognition profile. The way you estimate standalone selling prices determines how revenue flows between subscription and professional services. The way you handle contract modifications determines whether upgrades accelerate or defer revenue. These are not compliance decisions. They are strategic decisions that affect how the business is perceived and valued.

A finance leader who treats ASC 606 as compliance will make decisions that are technically defensible but strategically suboptimal. A finance leader who treats ASC 606 as architecture will structure contracts, pricing, and modifications to optimize both compliance and business outcomes. The difference is not in accounting knowledge. It is in mental model.

The second gap was in how I thought about technology. I have implemented ERP systems, evaluated billing platforms, and built API integrations. I considered myself technology-fluent. Writing the technology chapters, I realized that my fluency was operational rather than architectural. I knew how to use the tools. I had not fully articulated the principles that govern how the tools should be selected, integrated, and governed.

The distinction matters because operational fluency enables you to execute projects that someone else has designed. Architectural fluency enables you to design projects that someone else will execute. A finance leader who relies on IT or engineering to design finance technology architecture will get whatever IT or engineering prioritizes, which may not align with finance needs. A finance leader who can articulate the business requirements, evaluate vendor proposals, and govern integration architecture will get a finance technology stack that serves the function.

The third gap was in how I thought about leadership. I had managed finance teams through transformations, audits, and system implementations. I considered myself an effective leader. Writing the leadership chapters, I realized that I had been effective in spite of an incomplete framework, not because of a complete one.

Change management, I discovered, is not a soft skill that some leaders possess intuitively and others lack. It is a discipline with identifiable components: stakeholder mapping, communication planning, resistance diagnosis, training design, adoption measurement, and continuous improvement. A leader who applies these components systematically will achieve better transformation outcomes than a leader who relies on charisma and instinct. The book forced me to articulate these components explicitly, which has already improved my own practice.

The fourth gap was in how I thought about the future. I had been watching the emergence of autonomous accounting platforms, generative AI in finance, and real-time payment infrastructure with professional interest but without strategic framework. Writing the emerging fintech chapter, I realized that these technologies are not incremental improvements to existing processes. They are transformative shifts that will redefine what finance functions do and who does it.

A finance leader who views AI as a tool that will help their team work faster is thinking too small. AI will eliminate most transaction processing work within five years. The question is not how to use AI to do the same work more efficiently. The question is what the finance function becomes when transaction processing is no longer its primary activity. The answer, I believe, is that finance becomes an analytical and strategic function that focuses entirely on interpretation, judgment, and influence. The teams that prepare for this transition now will thrive. The teams that resist it will be automated into irrelevance.

Writing the book made me a better practitioner. Not because I learned new facts. Because I was forced to organize what I knew into a framework that others could follow, and the act of framework construction exposed the inconsistencies and gaps in my own thinking.

The Question I Get Asked Most

When I tell people I have written a technical book about SaaS finance, the most common question is: who is this book for?

The answer is narrower than it appears and broader than most people expect.

The narrow answer is that the book is for finance leaders in subscription-based technology companies. Controllers, VP Finance, CFOs, and revenue accounting specialists who are responsible for building and operating finance functions that serve SaaS organizations. These readers will find the most direct application of the material, because the book addresses their specific challenges with their specific context.

The broader answer is that the book is for anyone who participates in the evaluation, financing, or acquisition of subscription businesses. Private equity associates conducting due diligence on SaaS targets. Venture capital analysts evaluating unit economics of portfolio companies. Investment bankers preparing companies for public offerings. Audit partners specializing in technology clients. Corporate development teams at strategic acquirers. These readers will not implement the frameworks, but they will use them to assess whether the companies they evaluate have implemented them.

The unexpected answer is that the book is for founders and CEOs who do not have a finance background but are responsible for the financial trajectory of their companies. These readers may skip the technical accounting chapters and focus on the metric framework, the unit economics deep dive, the pricing strategy chapter, and the leadership chapters. They will not become accountants by reading these sections, but they will become better consumers of financial information and better evaluators of finance talent.

I considered writing different books for different audiences. A technical manual for controllers. A strategic guide for CFOs. An investor's primer for due diligence teams. I decided against this because the fragmentation of knowledge across audiences is part of the problem. Controllers who do not understand what investors care about build functions that satisfy auditors but fail due diligence. CFOs who do not understand the technical accounting details make strategic decisions that create compliance problems. Investors who do not understand operational finance make valuation decisions based on metrics they cannot properly evaluate.

The book integrates these perspectives because the finance leader's job integrates them. A controller who reads only the operational chapters will miss the strategic context that gives their work meaning. A CFO who reads only the strategic chapters will lack the technical foundation that makes strategy executable. The comprehensive scope is not a marketing feature. It is a structural requirement for the book to achieve its purpose.

What I Hope It Changes

I do not expect this book to become a bestseller in the way that business books become bestsellers. It is too technical for casual readers, too dense for airport bookstores, and too specific to a particular business model for general business audiences. I am comfortable with this because the book was not written for casual readers. It was written for practitioners who need a reference that matches the complexity of their work.

What I do expect is that the book will change how specific finance leaders approach specific decisions. A controller who reads the deferred revenue chapter will implement a monthly reconciliation that they had been performing annually. A VP Finance who reads the technology chapters will evaluate billing platforms using their actual contract scenarios rather than vendor demos. A CFO who reads the unit economics chapter will segment their CAC by channel and discover that their most expensive channel produces their lowest-LTV customers. A founder who reads the IPO readiness chapter will begin SOX preparation eighteen months before their anticipated offering rather than six.

Each of these changes prevents a specific failure mode that I have watched cost companies money, time, and reputation. The aggregate impact of these changes across the readers who implement them is the measure of the book's success. Not copies sold. Not reviews posted. Not speaking invitations generated. The number of finance functions that operate more effectively because someone read this book and applied what they learned.

I also hope the book changes how finance leaders think about their role. The stereotype of the finance function as a backward-looking custodian of historical records is persistent and damaging. It attracts talent that prefers predictability to impact. It encourages leaders to optimize for accuracy rather than influence. It produces functions that are competent but invisible, reliable but irrelevant to strategic decisions.

The finance leader who reads this book will recognize that their role is not to report what happened but to shape what happens next. The accounting standards are the foundation, not the ceiling. The technology is the enabler, not the purpose. The metrics are the language, not the message. The leadership is the capability that transforms all of these into business outcomes.

This is the finance leader that subscription companies need. This is the finance leader that the subscription economy rewards. This is the finance leader that I hope this book helps create.

What Comes Next

The book is done. The work is not.

The subscription economy continues to evolve. New business models emerge. New accounting standards are proposed. New technologies mature. New regulations expand. The specific guidance in this book will require updating as these changes occur. I plan to maintain the book through periodic revisions, incorporating new developments and refining existing guidance based on reader feedback.

I am also building a practice around the frameworks the book describes. StackedCFO was founded to deliver the kind of finance leadership that the book advocates. Not traditional accounting oversight, but integrated finance architecture that combines accounting standards, technology systems, analytical frameworks, and strategic partnership. The book provides the knowledge. The practice applies it.

If you are a finance leader in a subscription business, I hope you read the book. I hope you find it useful. I hope you implement the frameworks that apply to your context. I hope you reach out with questions, challenges, and counterarguments. The book is a starting point, not a final answer. The conversation it starts is more valuable than the text it contains.

If you are a founder, CEO, or investor evaluating subscription businesses, I hope the book gives you the analytical vocabulary to assess finance functions with the same rigor you apply to product, market, and team. The finance function is not a cost center to be minimized. It is a capability to be evaluated, invested in, and leveraged. Companies that understand this build finance functions that create competitive advantage. Companies that do not build finance functions that create remediation costs.

The Monday morning email that I described in the prologue does not have to arrive. The retrading, the delays, the remediation, the reputation damage. These are not inevitable consequences of growth. They are preventable outcomes of inadequate infrastructure. The infrastructure can be built before it is needed. The knowledge required to build it is now available. The decision to apply it belongs to you.

A personal note from Casper Zhao

The first book was supposed to be enough.

The argument was clean and complete. The bank has already formed a view of you before you walk into the room. That view is built from analyses you have never seen. Every one of those analyses can be reproduced in advance by anyone willing to do the work. A borrower who has done that work can sit down with their own financials and construct a reasonable approximation of the credit memo the bank will write about them.

That was the system. The system covers the ordinary case. An operating company with a revolving line and a term loan. A relationship manager who returns calls. A renewal that arrives on schedule every twelve months. Most banking relationships are that case most of the time.

I believed, when the first book was finished, that the system was the whole story. I was wrong.

The Tuesday Afternoon

The moment that changed my mind was not a dramatic one. It was a phone call from a client on a Tuesday afternoon in October.

The client was the CFO of a distribution company doing about $32 million in revenue. The company had a $4 million revolving line with a regional bank. The relationship was seven years old. The compliance history was clean. The grade was a four. The renewal was routine, or should have been.

The CFO said: "The leverage ratio is 4.23 times. The covenant is 4.00 times. The compliance certificate is due in forty-five days. What do I do?"

The first book would have told her what the leverage ratio meant, how the bank computed it, and why the covenant was set where it was. The first book would have explained the system. The first book would not have told her what to do in the next forty-eight hours.

What she did, before she called me, was call the relationship manager. The RM said she would "look into it." The CFO waited three days. The RM called back and said the file had been flagged for the credit officer. The credit officer wanted a call. The CFO went into that call with no preparation, no documentation, and no plan. She explained that the leverage spike was caused by a one-time legal settlement and a delayed customer payment. The credit officer asked for a written explanation and a forward projection. The CFO sent a three-paragraph email and a spreadsheet that showed EBITDA recovering in the next two quarters.

The bank issued a waiver. The waiver fee was $25,000. The grade migrated from four to five. The next renewal came with a 35 basis point pricing increase and a tightened leverage covenant.

The CFO called me after the renewal, not before. She said: "I feel like I handled that wrong, but I don't know what I should have done differently."

She was right on both counts. She had handled it wrong. And the reason she did not know what to do differently was that no book, no resource, no playbook existed that told her. The first book explained the system. It did not provide the procedure.

That phone call was the moment I started writing the second book.

What the First Book Did Not Cover

The first book covered the ordinary case. The ordinary case is what happens when the system works. The renewal arrives on schedule. The covenants are in compliance. The grade is stable. The commitment letter arrives with terms that are within the expected range. The borrower signs it. The relationship continues.

The ordinary case is most of the relationship, most of the time. But the ordinary case is not what determines whether the relationship survives.

The relationship survives or dies in the moments that break the ordinary case. The covenant violation discovered on a Tuesday afternoon. The acquisition that has to be financed in six weeks. The term sheet with nine pages of conditions precedent and no explanation of which three matter. The personal guarantee that has quietly outlived the loan it was written against. The credit cycle that turns while the borrower is still operating on last year's assumptions. The bank merger that changes the credit policy overnight. The field exam that reduces availability by $600,000 on a Monday morning. The revolving line that shows zero available on a Tuesday at 2:40 in the afternoon and payroll is due on Friday.

Those situations do not yield to general principles. They require specific procedure. And procedure is what the first book did not provide.

The Gap in the Literature

When I started researching whether a procedural playbook for advanced commercial borrowers existed, I found three categories of books.

The first category was academic. Textbooks on commercial lending, credit analysis, and banking regulation. These books are written for banking students and credit analysts in training. They explain the theory behind the underwriting process. They do not tell a borrower what to do when the covenant trips on a Tuesday afternoon. They are not designed to.

The second category was generic. "How to get a business loan" books aimed at first-time borrowers and small business owners who have never been through a commercial credit process. These books cover the basics: what a term sheet is, what a personal guarantee is, what the SBA does. They do not cover what to do when the bank sends a forbearance agreement at 4:47 on a Friday afternoon with a cover letter requesting execution by the following Wednesday. They are not designed to.

The third category was legal. Bankruptcy treatises, workout law handbooks, and UCC Article 9 guides written for attorneys. These books are technically excellent and practically inaccessible to a borrower who is not a lawyer. They assume the reader already knows the legal framework and is looking for the specific case law or statutory interpretation. They do not tell a borrower when to retain counsel, what type of counsel to retain, or how to manage the engagement so the matter does not escalate into litigation. They are not designed to.

The gap was clear. There was no book that sat between the academic textbook and the legal treatise. No book that said: here is the specific procedure, with the specific timeline, the specific documentation, and the specific negotiation sequence, for the specific situation you are facing on a Tuesday afternoon.

That gap is what this book fills.

What Is Different About This Book

The first book taught the borrower to think like a banker. This book teaches the borrower to act like one.

The distinction matters. Thinking like a banker means understanding the analytical framework the bank uses to evaluate the credit. Acting like a banker means understanding the procedural framework the bank uses to manage the credit when the analytical framework produces a result the borrower did not want.

The procedures in this book are not general advice. They are specific protocols with specific steps, specific timelines, and specific documentation requirements. The covenant violation playbook tells the borrower exactly what to do in the first forty-eight hours after discovering a violation, including which documents to pull, which calculations to verify, and which letter to draft before the compliance certificate is due. The 72-hour liquidity lockdown tells the borrower exactly what to do in the first seventy-two hours after the revolving line shows zero available, including which four diagnostic categories to check, which 13-week cash forecast to build, and which vendors to call with which specific message. The forbearance negotiation framework identifies the eight sections of a standard forbearance agreement and tells the borrower which provisions are negotiable, which are not, and which one is an absolute red line that should never be signed.

Each procedure is designed to be executed on the day the situation arrives. Not after reading the whole book. Not after consulting an attorney. On the day.

That design choice was deliberate. The borrower who discovers a covenant violation on a Tuesday afternoon does not have time to read a book about banking theory. They have time to open the book to Chapter 15, read the forty-eight-hour protocol, and execute it. The borrower who receives a forbearance draft at 4:47 on a Friday afternoon does not have time to study the history of forbearance law. They have time to open the book to Chapter 17, read the eight-section framework, and mark up the draft before the Wednesday deadline.

The book is organized for reference, not for sequence. The chapters are self-contained by design. The reader who needs the acquisition financing framework does not need to read the insurance covenant chapter first. The reader who needs the multi-lender standstill sequence does not need to read the relationship lifecycle chapter first. Each chapter opens with the situation it addresses, provides the procedure, and closes with the tool the reader needs to execute it.

The Score Card

If I had to pick one tool from the book that I believe will change the most relationships, it would be the self-rated credit score card in Chapter 1.

The score card is a five-category, one-hundred-point framework that lets a borrower approximate the bank's internal risk grade before the bank completes its own assessment. The five categories are cash flow coverage, industry conditions, collateral position, capital and guarantor strength, and character and reporting quality. Each category is worth twenty points. The composite maps to the bank's grading scale: 90 to 100 is a grade three, 75 to 89 is a grade four, 60 to 74 is a grade five, 45 to 59 is a grade six, and below 45 is special assets territory.

The score card is not the bank's model. It is an approximation of the bank's model, calibrated to be useful to the borrower rather than to the regulator. It will not produce the same number the bank produces. It will produce a number that is directionally accurate enough to tell the borrower whether they are moving toward a better grade or a worse one, and which specific inputs are driving the movement.

That directionality is the information this book was written to give.

The borrower who runs the score card quarterly, identifies the two sub-scores with the lowest point totals, and executes two or three targeted actions per quarter to improve those sub-scores will see the composite move. The composite can move one full notch in as few as three quarters when the borrower is specific about the inputs. I have watched it happen. The borrower who does not run the score card discovers the grade migration when the commitment letter arrives with worse terms than the prior year, and believes the bank acted arbitrarily.

The bank did not act arbitrarily. The bank applied a framework the borrower could have applied first.

The Relationship Profitability Model

The second tool I would highlight is the relationship profitability model in Chapter 5.

Two borrowers with identical credit profiles can receive materially different spreads from different banks. The difference is not in the credit file. The difference is in the relationship profitability model that neither borrower has ever seen.

Banks do not price loans in isolation. They price relationships. The loan is one component of a profitability calculation that includes deposit income, fee income, capital allocation, loan loss provision, and servicing cost. A relationship that generates $80,000 of total annual income for the bank and requires $35,000 of capital cost has a return on risk-adjusted capital of approximately 129 percent. That is an excellent banking relationship. A relationship that generates $46,000 of net interest income only, with no fee income and no deposits, and requires $35,000 of capital cost, has a return of about 31 percent. The bank keeps that relationship because it is profitable, but it is the least valuable relationship in the portfolio.

The borrower who understands this model can reverse-engineer the bank's pricing. The conversation stops being "your spread is 60 basis points above the other bank" and becomes "our relationship generates $101,700 in total annual income against $113,300 in total cost. If we move $400,000 in additional operating deposits and add lockbox and positive pay, the relationship profit turns positive and the return improves to 11 percent. At that contribution level, the 285 basis point spread is supportable."

That conversation is built on the bank's own arithmetic. The relationship manager who hears it knows the borrower has done the math the bank does internally. The credit officer who sees the analysis in the pre-meeting memo knows the borrower is negotiating from the same framework the committee uses to approve pricing.

The borrower who controls the relationship inputs controls the pricing conversation. The borrower who does not understand the model argues about the spread in isolation and loses.

The Compound Effect

The most important argument in the book is the one that is invisible in any single renewal cycle and decisive across a decade.

Consider two borrowers with identical credit profiles at year one. Both are grade four. Both have $4.5 million facilities. Both have leverage ratios of 3.5 times against a 4.0 times covenant. Both have personal guarantees of $4.5 million. Both have pricing at SOFR plus 275 basis points.

The first borrower manages the relationship reactively. The compliance certificate is filed on the due date. No management commentary accompanies it. The renewal meeting is prepared for in the two weeks before it occurs. The commitment letter is signed without negotiation. The guarantee is never discussed. The pricing grid is never referenced. The score card is never run. The forward income statement is never prepared.

The second borrower manages the relationship proactively. The compliance certificate is filed one week early, accompanied by a one-page management commentary memo. The score card is run quarterly. The forward income statement is prepared before every renewal. The pre-meeting memo is delivered six weeks before the renewal date. The relationship profitability assessment is presented at every renewal conversation.

By year four, the second borrower has secured a pricing step-down of 25 basis points because the leverage ratio crossed the grid threshold and the borrower requested the reduction. The first borrower is still at SOFR plus 275 because the bank did not volunteer the step-down and the borrower did not ask.

By year six, the second borrower has negotiated a seasonal covenant amendment that accommodates the Q3 leverage peak, eliminating the annual waiver conversation. The second borrower has also negotiated a capped guarantee at 75 percent of the outstanding balance, reducing personal exposure by $1.1 million. The first borrower still has a full unlimited continuing guarantee.

By year eight, the second borrower has secured a two-year maturity commitment. The first borrower is still on annual renewal. The second borrower's grade has migrated to a three. The first borrower is still at a four.

By year ten, the second borrower has accumulated approximately $180,000 in interest savings and has reduced personal guarantee exposure by $2.2 million. The second borrower has spent approximately 21 hours per year on the internal credit function, totaling 210 hours across the decade. The first borrower has spent approximately 8 hours per year, totaling 80 hours.

The difference is 130 hours of work across ten years. The return on those 130 hours is approximately $230,000 in direct economic savings, $2.2 million in reduced personal exposure, and a banking relationship that has migrated from a grade four to a grade three with a two-year commitment and a capped guarantee.

The compound effect is not visible in any single renewal. It is visible only when the arc is traced from year one to year ten. The question is not whether the effort is worth it. The question is whether the borrower can afford to operate without it.

Who This Book Is For

This book is for the owner-operator who has a commercial banking relationship and has realized that the relationship is more complex, more consequential, and more manageable than they previously understood.

It is for the CFO who has been managing the banking relationship as one of many competing priorities and wants to convert that reactive posture into a proactive one without adding more than four to six hours per month of additional work.

It is for the controller who prepares the compliance certificate and wants to understand what the numbers mean to the bank before the bank's analyst sees them.

It is for the financial professional who advises commercial borrowers and wants a reference work that covers the situations the standard texts do not.

It is for the borrower who is about to sign a commitment letter and wants to know which provisions are negotiable before the expiration date forces a decision.

It is for the borrower who is in a covenant crisis and needs a procedure they can execute today, not a theory they can study at leisure.

It is for the borrower who is planning to change banks and wants to execute the exit in a way that preserves the option of return.

It is not for the first-time borrower who has never been through a commercial credit process. That borrower should read the first book. This book assumes the reader understands the system and is now looking for the procedures that apply when the system is not enough.

What I Learned Writing It

Writing this book taught me three things that I did not fully understand when I started.

The first is that procedure is more valuable than theory for borrowers in stress. A borrower in a covenant crisis does not need to understand the history of covenant architecture. They need to know what to do in the next forty-eight hours. The procedural format of this book, with its specific timelines and specific documentation requirements, is the format that serves the borrower in the moment the situation arrives. Theory serves the borrower in advance. Procedure serves the borrower on the day.

The second is that the compound effect of proactive relationship management is larger than I expected. The two-borrower decade comparison in the closing chapter was originally conceived as an illustrative device. As I built the numbers, I realized the illustration was understated. The actual compound effect, across borrowers I have observed, is larger than the book suggests. The 130 hours of additional work produce more than $230,000 in savings and more than $2.2 million in reduced personal exposure. Those numbers are conservative. The real numbers are higher, and they grow with the size of the facility and the length of the relationship.

The third is that the bank's internal framework is more consistent across institutions than I expected. The specific weights vary. The specific definitions vary. The specific thresholds vary. But the categories, the inputs, and the analytical logic are consistent enough that a borrower who learns the framework at one bank can apply it at another. This consistency is what makes the book generalizable rather than institution-specific. The procedures are designed to work at any commercial bank, because the underlying framework is the same at every commercial bank.

The First Book and the Second Book Together

The first book teaches the system. The second book teaches the procedures. The two together are the complete toolkit.

The system without the procedures is analytical understanding without operational capability. The borrower who understands the system but cannot execute the procedures can diagnose the problem but cannot solve it. The procedures without the system are tactics without a foundation. The borrower who can execute the procedures but does not understand the system can negotiate hard on the wrong terms.

The borrower who has both can do something that most commercial borrowers never do. They can sit across the table from a relationship manager and a credit officer and operate on the same analytical framework the bank is using. They can present a credit package that anticipates the bank's analysis. They can propose terms that are supported by the bank's own arithmetic. They can negotiate from a position of documented preparation rather than from a position of informational asymmetry.

That position is the one the bank always occupies. The system and the procedures together give the borrower the ability to occupy it too.

The meeting does not have to be over before it starts. Not if the borrower has done the work.

What to Do Next

If you have read the first book, this book is the next step. The system you learned in the first book is the foundation. The procedures in this book are the toolkit that sits on top of it.

If you have not read the first book, you can start here. The procedures are self-contained. But you will get more out of them if you understand the system they sit on top of, and the first book is where that system is explained.

If you are in a situation right now, a covenant crisis, a renewal that is coming, a term sheet you are trying to interpret, a bank merger that was just announced, open the book to the chapter that covers your situation. The chapters are designed to be read in the order the situation demands, not in the order they appear.

If you are not in a situation right now, start with Chapter 1. Run the score card. See where you stand. The score card takes forty-five minutes and produces a number that tells you whether your relationship is moving in the right direction or the wrong one. That number is the starting point for everything else in the book.

The compound effect begins with the first quarterly score card run. The 130 hours across a decade start with the first forty-five minutes.

The book is available now. The link is below.

If you have questions, if you are in a situation the book does not cover, if you want to share what you are seeing in your own banking relationship, reach out. The email is casper@stackedcfo.com. I read every message.

The first book was supposed to be enough. It was not. This book is the rest of the story.

I never saw anyone stopped for it.

EBITDA Theater is the novel I wrote about that pattern. Eight people find the same finding, from different chairs, at different points, and the book does not pretend that finding it and doing something about it are the same accomplishment.

If you have ever sat in a diligence room and felt the deal's own gravity pulling the room toward a number everyone already wanted, this book is for you.

Available now on Kindle and in paperback.

The AI angle

Every finance and diligence tool built on AI right now is being sold as neutral. Objective. The same technology, applied evenly.

It is not, and the reason is not the technology. It is the person holding it.

EBITDA Theater follows 3 characters who each build or use an AI diligence tool inside the same deal. One builds hers to find the truth. One builds his to survive it. One runs his own numbers through the same kind of system, not to be caught, but to anticipate exactly how he might be.

Same technology. Three different intentions. One number that will not stay hidden either way.

This is a novel about what AI actually changes in a room built to want the truth only when it is convenient, and what it does not change at all.

The personal note

I did not write this as another how to book.

I have written plenty of those. This one is fiction because the pattern I wanted to describe is not a checklist problem. It is a human one: a recurring cost, recharacterized as one time, by people who each had a defensible reason not to ask the question that would have ended it.

EBITDA Theater is my first novel. Every character, every firm, every transaction in it is invented. The mechanism is not. If you work in finance and something in this book feels familiar, that is not a coincidence you are imagining.

The reported earnings were $47.8 million. The adjusted number was $69.9 million. The difference was a story, and everyone in the room had a reason to believe it.

When Cabot Beacon closes its acquisition of Meridian Industrial Services, the deal looks clean. The addback bridge, the schedule that explains away $22.1 million in costs a buyer is told will not recur, has been reviewed, negotiated, and signed off by everyone whose job it was to catch a problem. It should have ended there.

It does not, because one vendor relationship, Castellan Technology, has been billed under 4 different descriptions across 4 consecutive fiscal years, and the person paid to notice that kind of pattern has just noticed it.

EBITDA Theater follows 8 people across the same transaction: the managing partner who has made this exact choice 7 times before in a 16 year career and calls it discipline, the independent advisor who built her own methodology specifically to catch what he is counting on nobody catching, the CFO who did not lie so much as frame, and the deal principal who will spend 18 months deciding whether protecting someone is the same thing as lying to them.

At the center of the novel is a question the finance industry is only beginning to face directly: artificial intelligence is incentive neutral. The same class of diligence tool, pointed by 3 different people at the same numbers, produces 3 different answers, not because the technology is biased, but because the people directing it are not. One character builds an AI methodology to find the truth. Another builds a private version of the same approach independently. A third runs an adversarial version of it against his own company's numbers, not to get caught, but to know exactly how.

Written by a former Quality of Earnings analyst who conducted this kind of review across more than 100 real transactions, EBITDA Theater does not soften the mechanics for a general reader. The addback bridges, the QoE conventions, the exact vocabulary of a real diligence room, all of it is drawn from how these deals actually work. The fiction is the characters. The mechanism is not.

Nobody in this book is a villain. Every person in it has a reason for what they do that a reasonable person could understand, which is precisely what makes the pattern so difficult to stop. The novel does not resolve into a courtroom reckoning or a clean moral verdict. It resolves the way these things actually resolve: a price gets adjusted, a career moves on, a methodology gets absorbed into a footnote of the next deal's diligence checklist, and the pattern, somewhere else, continues.

EBITDA Theater is for readers of workplace and finance fiction who want the real vocabulary of the deal room, not a simplified version of it, and for anyone who has ever sat in a room and felt a number get chosen before the meeting that was supposed to determine it.

Includes reader's exhibits: a timeline, a vendor pattern chart, a deal comparison, and a full character relationship map.

Link: https://www.amazon.com/dp/B0GX32V3LF