SYSTEM CONTROLLER
The finance function is the operating system of every company. It processes every transaction, governs every dollar, and produces the information that every decision depends on. Yet most controllers inherit the function rather than design it. They manage what exists rather than build what the company needs. The System Controller Masterclass changes that. It is a 30-module professional education series that teaches controllers, finance directors, and aspiring CFOs to design, operate, optimize, and scale the financial operating system of a company from startup through IPO. The masterclass is built on a single premise: the modern controller is not a scorekeeper. The modern controller is an enterprise systems architect who designs the chart of accounts, governs the close process, builds the internal controls, manages the audit, partners with the business, communicates with the board, and prepares the company for whatever comes next, whether that is an acquisition, an international expansion, or the public markets. The curriculum teaches every one of these capabilities through a structured, cumulative approach where each module builds on the prior one. Thirty modules span seven parts. Part One (Foundations) establishes the controller’s role, the team design, and the performance framework. Part Two (Architecture) builds the chart of accounts, the multi-entity structure, the accounting policies, and the judgment discipline that the auditor will test. Part Three (Core Cycles) governs every major transaction cycle: order-to-cash, revenue recognition, procure-to-pay, cost and margin, payroll, equity compensation, treasury, and ERP systems. Part Four (Systems and Data) addresses data governance, metrics, analytics, and AI-enabled automation with the governance framework that prevents ungoverned output at machine speed. Part Five (Control and Assurance) builds the internal control framework, governs the audit relationship, manages tax and regulatory compliance, and designs the enterprise risk program. Part Six (Planning, Partnering, and Communication) constructs the financial plan with rolling forecasts and scenario analysis, builds the cross-functional partnerships that ensure the controller is consulted before decisions are made, and designs the board package and investor communications. Part Seven (Scale and Succession) prepares the function for M&A, global expansion, and IPO readiness, builds the leadership capability that produces a team rather than a dependency, and maps the controller-to-CFO transition. Every module follows a consistent 17-part instructional structure. Each includes a proprietary named framework (such as the CLOSE Operating Model, the CONTROL ENVIRONMENT Architecture, or the BRIEF Communication Model), a self-assessment instrument, a continuing case company (Kestrel Systems, Inc.) that accumulates complexity across all 30 modules, a separate case study company, a simulated executive discussion, and a Controller Lab artifact that produces a reusable deliverable the controller can implement the following week. The writing style is direct, declarative, and vendor-neutral. The content is systems-oriented, connecting every process to the processes upstream and downstream. The approach is practical: every recommendation explains why it exists, what it costs to implement, and what it costs to skip. The masterclass does not teach accounting theory. It teaches the applied discipline of building and operating the financial function that a scaling company requires. The System Controller Masterclass is designed for controllers at companies between twenty and two hundred million dollars of revenue, finance directors preparing for the controller role, and controllers preparing for the CFO transition. It is equally relevant for the controller at a 30-person startup building the function from scratch and the controller at a 500-person company redesigning the function for the next stage of growth. The curriculum meets the professional where they are and builds toward where the company needs them to be.
The Controller as Enterprise Systems Architect
The foundation determines whether the finance function operates as a system or as a collection of tasks performed by individuals. Part One establishes the controller's role as an enterprise systems architect, introduces the System Controller Framework that governs every subsequent module, designs the finance organization with the right roles at the right stage, and builds the high-performance team through the PERFORM Model. These four modules answer the question every new controller faces: what should I build first? The answer is the team, the structure, and the operating model that make everything else possible. Controllers who skip the foundation and jump to the processes discover that processes without the right people and the right structure produce compliance without capability.
The System Controller Framework
The foundation determines whether the finance function operates as a system or as a collection of tasks performed by individuals. Part One establishes the controller's role as an enterprise systems architect, introduces the System Controller Framework that governs every subsequent module, designs the finance organization with the right roles at the right stage, and builds the high-performance team through the PERFORM Model. These four modules answer the question every new controller faces: what should I build first? The answer is the team, the structure, and the operating model that make everything else possible. Controllers who skip the foundation and jump to the processes discover that processes without the right people and the right structure produce compliance without capability.
Designing the Finance Organization: Roles by Stage
The foundation determines whether the finance function operates as a system or as a collection of tasks performed by individuals. Part One establishes the controller's role as an enterprise systems architect, introduces the System Controller Framework that governs every subsequent module, designs the finance organization with the right roles at the right stage, and builds the high-performance team through the PERFORM Model. These four modules answer the question every new controller faces: what should I build first? The answer is the team, the structure, and the operating model that make everything else possible. Controllers who skip the foundation and jump to the processes discover that processes without the right people and the right structure produce compliance without capability.
Building the High-Performance Finance Team: The PERFORM Model
The foundation determines whether the finance function operates as a system or as a collection of tasks performed by individuals. Part One establishes the controller's role as an enterprise systems architect, introduces the System Controller Framework that governs every subsequent module, designs the finance organization with the right roles at the right stage, and builds the high-performance team through the PERFORM Model. These four modules answer the question every new controller faces: what should I build first? The answer is the team, the structure, and the operating model that make everything else possible. Controllers who skip the foundation and jump to the processes discover that processes without the right people and the right structure produce compliance without capability.
Chart of Accounts Design: The LEDGER Design Principles
Architecture is the design layer that sits between the organizational foundation and the operational processes. Part Two builds the chart of accounts using the LEDGER Design Principles, designs the multi-entity and multi-currency consolidation framework, documents the accounting policies through the POLICY Lifecycle, and introduces the JUDGMENT Protocol for technical accounting decisions that require professional judgment. These modules produce the infrastructure the auditor will evaluate and the board will rely on. A chart of accounts that cannot segment revenue by product, a consolidation that cannot eliminate intercompany transactions, or a judgment memo that does not exist when the auditor asks for it are architectural failures that no amount of operational effort can overcome. Build the architecture before building the operations.
Multi-Entity and Multi-Currency Consolidation
Architecture is the design layer that sits between the organizational foundation and the operational processes. Part Two builds the chart of accounts using the LEDGER Design Principles, designs the multi-entity and multi-currency consolidation framework, documents the accounting policies through the POLICY Lifecycle, and introduces the JUDGMENT Protocol for technical accounting decisions that require professional judgment. These modules produce the infrastructure the auditor will evaluate and the board will rely on. A chart of accounts that cannot segment revenue by product, a consolidation that cannot eliminate intercompany transactions, or a judgment memo that does not exist when the auditor asks for it are architectural failures that no amount of operational effort can overcome. Build the architecture before building the operations.
Accounting Policy Documentation: The POLICY Lifecycle
Architecture is the design layer that sits between the organizational foundation and the operational processes. Part Two builds the chart of accounts using the LEDGER Design Principles, designs the multi-entity and multi-currency consolidation framework, documents the accounting policies through the POLICY Lifecycle, and introduces the JUDGMENT Protocol for technical accounting decisions that require professional judgment. These modules produce the infrastructure the auditor will evaluate and the board will rely on. A chart of accounts that cannot segment revenue by product, a consolidation that cannot eliminate intercompany transactions, or a judgment memo that does not exist when the auditor asks for it are architectural failures that no amount of operational effort can overcome. Build the architecture before building the operations.
Technical Accounting Decisions: The JUDGMENT Protocol
Architecture is the design layer that sits between the organizational foundation and the operational processes. Part Two builds the chart of accounts using the LEDGER Design Principles, designs the multi-entity and multi-currency consolidation framework, documents the accounting policies through the POLICY Lifecycle, and introduces the JUDGMENT Protocol for technical accounting decisions that require professional judgment. These modules produce the infrastructure the auditor will evaluate and the board will rely on. A chart of accounts that cannot segment revenue by product, a consolidation that cannot eliminate intercompany transactions, or a judgment memo that does not exist when the auditor asks for it are architectural failures that no amount of operational effort can overcome. Build the architecture before building the operations.
The Month-End Close: The CLOSE Operating Model
Core Cycles is the operational heart of the masterclass. Eight modules govern every major transaction cycle the controller manages. The CLOSE Operating Model accelerates the month- end close to seven business days. The REVENUE CYCLE Architecture and the RECOGNIZE Checklist govern order-to-cash and ASC 606 revenue recognition. The PURCHASE CYCLE Architecture governs procure-to-pay with three-way matching and fraud prevention. The MARGIN Architecture connects product cost to customer profitability. The PEOPLE COST Architecture governs payroll, benefits, and the fully loaded cost that every hiring decision should reference. The EQUITY Governance Model addresses stock compensation, 409A valuations, and cap table management. And the CASH Governance Model designs the treasury function with the 13-week cash forecast. Each module produces a Controller Lab artifact that the controller can implement within days of completing the module.
Order-to-Cash: The REVENUE CYCLE Architecture
Core Cycles is the operational heart of the masterclass. Eight modules govern every major transaction cycle the controller manages. The CLOSE Operating Model accelerates the month- end close to seven business days. The REVENUE CYCLE Architecture and the RECOGNIZE Checklist govern order-to-cash and ASC 606 revenue recognition. The PURCHASE CYCLE Architecture governs procure-to-pay with three-way matching and fraud prevention. The MARGIN Architecture connects product cost to customer profitability. The PEOPLE COST Architecture governs payroll, benefits, and the fully loaded cost that every hiring decision should reference. The EQUITY Governance Model addresses stock compensation, 409A valuations, and cap table management. And the CASH Governance Model designs the treasury function with the 13-week cash forecast. Each module produces a Controller Lab artifact that the controller can implement within days of completing the module.
ASC 606 Revenue Recognition: The RECOGNIZE Checklist
Core Cycles is the operational heart of the masterclass. Eight modules govern every major transaction cycle the controller manages. The CLOSE Operating Model accelerates the month- end close to seven business days. The REVENUE CYCLE Architecture and the RECOGNIZE Checklist govern order-to-cash and ASC 606 revenue recognition. The PURCHASE CYCLE Architecture governs procure-to-pay with three-way matching and fraud prevention. The MARGIN Architecture connects product cost to customer profitability. The PEOPLE COST Architecture governs payroll, benefits, and the fully loaded cost that every hiring decision should reference. The EQUITY Governance Model addresses stock compensation, 409A valuations, and cap table management. And the CASH Governance Model designs the treasury function with the 13-week cash forecast. Each module produces a Controller Lab artifact that the controller can implement within days of completing the module.
Procure-to-Pay: The PURCHASE CYCLE Architecture
Core Cycles is the operational heart of the masterclass. Eight modules govern every major transaction cycle the controller manages. The CLOSE Operating Model accelerates the month- end close to seven business days. The REVENUE CYCLE Architecture and the RECOGNIZE Checklist govern order-to-cash and ASC 606 revenue recognition. The PURCHASE CYCLE Architecture governs procure-to-pay with three-way matching and fraud prevention. The MARGIN Architecture connects product cost to customer profitability. The PEOPLE COST Architecture governs payroll, benefits, and the fully loaded cost that every hiring decision should reference. The EQUITY Governance Model addresses stock compensation, 409A valuations, and cap table management. And the CASH Governance Model designs the treasury function with the 13-week cash forecast. Each module produces a Controller Lab artifact that the controller can implement within days of completing the module.
Product Cost to Customer Profitability: The MARGIN Architecture
Core Cycles is the operational heart of the masterclass. Eight modules govern every major transaction cycle the controller manages. The CLOSE Operating Model accelerates the month- end close to seven business days. The REVENUE CYCLE Architecture and the RECOGNIZE Checklist govern order-to-cash and ASC 606 revenue recognition. The PURCHASE CYCLE Architecture governs procure-to-pay with three-way matching and fraud prevention. The MARGIN Architecture connects product cost to customer profitability. The PEOPLE COST Architecture governs payroll, benefits, and the fully loaded cost that every hiring decision should reference. The EQUITY Governance Model addresses stock compensation, 409A valuations, and cap table management. And the CASH Governance Model designs the treasury function with the 13-week cash forecast. Each module produces a Controller Lab artifact that the controller can implement within days of completing the module.
Payroll, Benefits, and Fully Loaded Cost: The PEOPLE COST Architecture
Core Cycles is the operational heart of the masterclass. Eight modules govern every major transaction cycle the controller manages. The CLOSE Operating Model accelerates the month- end close to seven business days. The REVENUE CYCLE Architecture and the RECOGNIZE Checklist govern order-to-cash and ASC 606 revenue recognition. The PURCHASE CYCLE Architecture governs procure-to-pay with three-way matching and fraud prevention. The MARGIN Architecture connects product cost to customer profitability. The PEOPLE COST Architecture governs payroll, benefits, and the fully loaded cost that every hiring decision should reference. The EQUITY Governance Model addresses stock compensation, 409A valuations, and cap table management. And the CASH Governance Model designs the treasury function with the 13-week cash forecast. Each module produces a Controller Lab artifact that the controller can implement within days of completing the module.
Stock Compensation, 409A, and Cap Table: The EQUITY Governance Model
Core Cycles is the operational heart of the masterclass. Eight modules govern every major transaction cycle the controller manages. The CLOSE Operating Model accelerates the month- end close to seven business days. The REVENUE CYCLE Architecture and the RECOGNIZE Checklist govern order-to-cash and ASC 606 revenue recognition. The PURCHASE CYCLE Architecture governs procure-to-pay with three-way matching and fraud prevention. The MARGIN Architecture connects product cost to customer profitability. The PEOPLE COST Architecture governs payroll, benefits, and the fully loaded cost that every hiring decision should reference. The EQUITY Governance Model addresses stock compensation, 409A valuations, and cap table management. And the CASH Governance Model designs the treasury function with the 13-week cash forecast. Each module produces a Controller Lab artifact that the controller can implement within days of completing the module.
Treasury and the 13-Week Forecast: The CASH Governance Model
Core Cycles is the operational heart of the masterclass. Eight modules govern every major transaction cycle the controller manages. The CLOSE Operating Model accelerates the month- end close to seven business days. The REVENUE CYCLE Architecture and the RECOGNIZE Checklist govern order-to-cash and ASC 606 revenue recognition. The PURCHASE CYCLE Architecture governs procure-to-pay with three-way matching and fraud prevention. The MARGIN Architecture connects product cost to customer profitability. The PEOPLE COST Architecture governs payroll, benefits, and the fully loaded cost that every hiring decision should reference. The EQUITY Governance Model addresses stock compensation, 409A valuations, and cap table management. And the CASH Governance Model designs the treasury function with the 13-week cash forecast. Each module produces a Controller Lab artifact that the controller can implement within days of completing the module.
ERP and Finance Systems: The SYSTEMS Lifecycle Model
Systems and data are the infrastructure that every process in Parts Two and Three depends on. Part Four addresses three capabilities: ERP and finance systems selection, implementation, and lifecycle management through the SYSTEMS Lifecycle Model; data governance, metric definitions, and analytical practices through the DATA Authority Model; and AI-enabled automation with the governance framework (the AUTOMATE Decision Model) that ensures automation is governed before it is deployed. These modules are relevant to every controller who manages a system migration, defines a KPI, or evaluates an AI tool. The central insight is that technology without governance produces output at machine speed, and ungoverned output that is wrong is worse than manual output that is right.
Data Governance and Metric Definitions: The DATA Authority Model
Systems and data are the infrastructure that every process in Parts Two and Three depends on. Part Four addresses three capabilities: ERP and finance systems selection, implementation, and lifecycle management through the SYSTEMS Lifecycle Model; data governance, metric definitions, and analytical practices through the DATA Authority Model; and AI-enabled automation with the governance framework (the AUTOMATE Decision Model) that ensures automation is governed before it is deployed. These modules are relevant to every controller who manages a system migration, defines a KPI, or evaluates an AI tool. The central insight is that technology without governance produces output at machine speed, and ungoverned output that is wrong is worse than manual output that is right.
AI-Enabled Automation: The AUTOMATE Decision Model
Systems and data are the infrastructure that every process in Parts Two and Three depends on. Part Four addresses three capabilities: ERP and finance systems selection, implementation, and lifecycle management through the SYSTEMS Lifecycle Model; data governance, metric definitions, and analytical practices through the DATA Authority Model; and AI-enabled automation with the governance framework (the AUTOMATE Decision Model) that ensures automation is governed before it is deployed. These modules are relevant to every controller who manages a system migration, defines a KPI, or evaluates an AI tool. The central insight is that technology without governance produces output at machine speed, and ungoverned output that is wrong is worse than manual output that is right.
Internal Control and SOX Readiness: The CONTROL ENVIRONMENT Architecture
Control and assurance is the verification layer that confirms every process in the prior modules is working as designed. Part Five builds the internal control framework and SOX readiness through the CONTROL ENVIRONMENT Architecture, governs the external audit relationship through the AUDIT Relationship Model, manages tax and regulatory compliance through the COMPLY Governance Model (including multi-state nexus, income tax provision, and transfer pricing), and designs the enterprise risk program through the RISK Governance Model covering fraud prevention, cybersecurity, insurance governance, and board-level risk reporting. These four modules produce the governance infrastructure that the auditor tests, the board oversees, and the IPO requires. The controller who builds this infrastructure two years before the IPO avoids the five-month delay that the controller who builds it during the IPO invariably encounters.
Governing the External Audit: The AUDIT Relationship Model
Control and assurance is the verification layer that confirms every process in the prior modules is working as designed. Part Five builds the internal control framework and SOX readiness through the CONTROL ENVIRONMENT Architecture, governs the external audit relationship through the AUDIT Relationship Model, manages tax and regulatory compliance through the COMPLY Governance Model (including multi-state nexus, income tax provision, and transfer pricing), and designs the enterprise risk program through the RISK Governance Model covering fraud prevention, cybersecurity, insurance governance, and board-level risk reporting. These four modules produce the governance infrastructure that the auditor tests, the board oversees, and the IPO requires. The controller who builds this infrastructure two years before the IPO avoids the five-month delay that the controller who builds it during the IPO invariably encounters.
Tax and Regulatory Compliance: The COMPLY Governance Model
Control and assurance is the verification layer that confirms every process in the prior modules is working as designed. Part Five builds the internal control framework and SOX readiness through the CONTROL ENVIRONMENT Architecture, governs the external audit relationship through the AUDIT Relationship Model, manages tax and regulatory compliance through the COMPLY Governance Model (including multi-state nexus, income tax provision, and transfer pricing), and designs the enterprise risk program through the RISK Governance Model covering fraud prevention, cybersecurity, insurance governance, and board-level risk reporting. These four modules produce the governance infrastructure that the auditor tests, the board oversees, and the IPO requires. The controller who builds this infrastructure two years before the IPO avoids the five-month delay that the controller who builds it during the IPO invariably encounters.
Enterprise Risk, Fraud, and Cybersecurity: The RISK Governance Model
Control and assurance is the verification layer that confirms every process in the prior modules is working as designed. Part Five builds the internal control framework and SOX readiness through the CONTROL ENVIRONMENT Architecture, governs the external audit relationship through the AUDIT Relationship Model, manages tax and regulatory compliance through the COMPLY Governance Model (including multi-state nexus, income tax provision, and transfer pricing), and designs the enterprise risk program through the RISK Governance Model covering fraud prevention, cybersecurity, insurance governance, and board-level risk reporting. These four modules produce the governance infrastructure that the auditor tests, the board oversees, and the IPO requires. The controller who builds this infrastructure two years before the IPO avoids the five-month delay that the controller who builds it during the IPO invariably encounters.
Budgeting, Rolling Forecasts, and Scenarios: The PLAN Governance Model
Parts One through Five built the backward-looking and governance capabilities. Part Six builds the forward-looking and advisory capabilities that transform the controller from a reporter into a strategic partner. The PLAN Governance Model designs the annual budget in six weeks, builds the rolling forecast that updates monthly, and introduces scenario analysis with trigger points. The PARTNER Influence Model builds the cross-functional relationships that ensure the controller is consulted before decisions are made, not informed after. And the BRIEF Communication Model redesigns the board package from a forty-page data dump into a fifteen- page decision tool that the board reads, discusses, and acts on. These three modules address the capabilities that separate the controller who reports the numbers from the controller who shapes the decisions that produce them.
Cross-Functional Business Partnering: The PARTNER Influence Model
Parts One through Five built the backward-looking and governance capabilities. Part Six builds the forward-looking and advisory capabilities that transform the controller from a reporter into a strategic partner. The PLAN Governance Model designs the annual budget in six weeks, builds the rolling forecast that updates monthly, and introduces scenario analysis with trigger points. The PARTNER Influence Model builds the cross-functional relationships that ensure the controller is consulted before decisions are made, not informed after. And the BRIEF Communication Model redesigns the board package from a forty-page data dump into a fifteen- page decision tool that the board reads, discusses, and acts on. These three modules address the capabilities that separate the controller who reports the numbers from the controller who shapes the decisions that produce them.
The Board Package Redesign: The BRIEF Communication Model
Parts One through Five built the backward-looking and governance capabilities. Part Six builds the forward-looking and advisory capabilities that transform the controller from a reporter into a strategic partner. The PLAN Governance Model designs the annual budget in six weeks, builds the rolling forecast that updates monthly, and introduces scenario analysis with trigger points. The PARTNER Influence Model builds the cross-functional relationships that ensure the controller is consulted before decisions are made, not informed after. And the BRIEF Communication Model redesigns the board package from a forty-page data dump into a fifteen- page decision tool that the board reads, discusses, and acts on. These three modules address the capabilities that separate the controller who reports the numbers from the controller who shapes the decisions that produce them.
Scaling for Acquisition, Expansion, and IPO: The SCALE Readiness Model
The final part prepares the controller and the function for the next stage. The SCALE Readiness Model assesses whether the function can handle an acquisition, an international expansion, or an IPO. The LEAD Operating Model builds the leadership capability that produces a team rather than a dependency on one person. The ASCEND Readiness Model maps the controller-to-CFO transition with the specific skills, experiences, and mindset shifts the CFO role requires. And the capstone laboratory tests the full curriculum through a comprehensive case that requires the participant to apply every module to a single company under real constraints. Part Seven answers the question that every ambitious controller asks: what comes next? The answer is scale, succession, and the transition from operating the financial system to leading the financial strategy.
Leading the Finance Team: The LEAD Operating Model
The final part prepares the controller and the function for the next stage. The SCALE Readiness Model assesses whether the function can handle an acquisition, an international expansion, or an IPO. The LEAD Operating Model builds the leadership capability that produces a team rather than a dependency on one person. The ASCEND Readiness Model maps the controller-to-CFO transition with the specific skills, experiences, and mindset shifts the CFO role requires. And the capstone laboratory tests the full curriculum through a comprehensive case that requires the participant to apply every module to a single company under real constraints. Part Seven answers the question that every ambitious controller asks: what comes next? The answer is scale, succession, and the transition from operating the financial system to leading the financial strategy.
The Controller-to-CFO Transition: The ASCEND Readiness Model
The final part prepares the controller and the function for the next stage. The SCALE Readiness Model assesses whether the function can handle an acquisition, an international expansion, or an IPO. The LEAD Operating Model builds the leadership capability that produces a team rather than a dependency on one person. The ASCEND Readiness Model maps the controller-to-CFO transition with the specific skills, experiences, and mindset shifts the CFO role requires. And the capstone laboratory tests the full curriculum through a comprehensive case that requires the participant to apply every module to a single company under real constraints. Part Seven answers the question that every ambitious controller asks: what comes next? The answer is scale, succession, and the transition from operating the financial system to leading the financial strategy.
Capstone Laboratory: The Integrated System Controller Case
The final part prepares the controller and the function for the next stage. The SCALE Readiness Model assesses whether the function can handle an acquisition, an international expansion, or an IPO. The LEAD Operating Model builds the leadership capability that produces a team rather than a dependency on one person. The ASCEND Readiness Model maps the controller-to-CFO transition with the specific skills, experiences, and mindset shifts the CFO role requires. And the capstone laboratory tests the full curriculum through a comprehensive case that requires the participant to apply every module to a single company under real constraints. Part Seven answers the question that every ambitious controller asks: what comes next? The answer is scale, succession, and the transition from operating the financial system to leading the financial strategy.