Commercial Planning Model Principal — Revenue Timing and Service Capacity

The mandate

A commercial service business forecasts revenue from pipeline and signed contracts, while delivery capacity is planned in a separate process. The two views disagree about when customer work can begin and how much revenue the available resources can support. The principal will deliver a controlled model linking those facts, with explicit treatment of mobilisation delays and different demand confidence levels. Specialist accountability covers the modelling method, testing and transfer, while management retains sales commitments, resource approval and the operating forecast issued to executives.

The five-month engagement begins on 26 October 2026, reserving three working days a week. The ₹50,00,000 project fee is divided into 25%, 40% and 35% payments against three accepted artifacts. Bengaluru is the principal working location, with finance-user workshops and delivery-owner reviews included. The CFO supplies a bounded customer-service perimeter, historical contract movements, commercial stage definitions, capacity records and named owners able to resolve inconsistencies. The project will not assume that a pipeline probability makes a delivery start operationally possible.

Milestone one, on 10 December 2026, produces the signed input map, planning definitions and reconciled historical sample. Milestone two, on 11 February 2027, delivers a tested prototype that joins demand classes to capacity and mobilisation constraints. Milestone three, on 26 March 2027, provides the accepted model, scenario guide and independent user-run results. Commercial planning and delivery-capacity owners jointly verify their inputs; the CFO accepts the complete package. Tests use agreed historical cases and changed assumptions, not a promise that future sales or revenue will meet a target.

The model must distinguish signed work, conditional demand, available capacity and resources requiring approval. Controllers validate any interpretation affecting the relationship to recognised income. Scope excludes sales execution, staffing decisions, accounting policy change and enterprise software deployment. A new service class or materially different country process requires written scope, price and timing approval. Transfer is complete when nominated finance users can refresh inputs, run agreed scenarios and explain a revenue shortfall caused by capacity or timing without the principal operating the model for them.

What you will own

• Map the agreed customer-service perimeter and input ownership for the first milestone, identifying contradictory start dates, duplicate demand and missing capacity records before those gaps are hidden inside calculated revenue.
• Reconcile a historical planning sample to source records and controller-approved financial interpretations, recording where contract value, activity delivered and recognised revenue legitimately differ rather than forcing them into one measure.
• Build the second-milestone prototype with separate demand confidence, mobilisation timing and approved-capacity logic, making resource dependencies explicit when an attractive sales outlook exceeds what the delivery organisation can credibly support.
• Test historical and synthetic cases jointly with commercial and capacity owners, including delayed mobilisation, cancelled demand and constrained resource scenarios whose expected treatment is agreed before model results are assessed.
• Deliver scenario documentation that distinguishes forecast choice from operational commitment, enabling finance to recommend alternatives without treating a modelled resource increase as approval to recruit or make customer promises.
• Transfer the final package through independent user runs, retaining refresh logs, exception explanations and test evidence so the CFO can judge capability from observed use rather than workshop attendance alone.
• Maintain a written issue and change record covering unavailable inputs and added service complexity, proposing explicit scope decisions instead of silently expanding the model or compensating for missing facts with invented assumptions.

Candidate qualifications

• Demonstrate senior FP&A, commercial-finance or business-planning responsibility in technology, advertising, industrial services or a comparable demand-led business. Show a model connecting revenue timing to a real operating constraint, with your personal method and decision contribution clear. Prior delivery should include disagreement between commercial expectations and executable capacity, not simply a sales forecast adjusted with an unexplained utilisation percentage.
• Have rigorous financial modelling and management-accounting competence supported by relevant professional preparation or equivalent senior practice. Explain your approach to source reconciliation, demand confidence and timing logic. You must know when recognised income requires a controller's conclusion and preserve that boundary while building management scenarios; mathematical consistency alone does not make a commercial revenue assumption operationally or financially valid.
• Provide evidence of reproducible acceptance testing, including cases designed before final results were known. Describe an input defect or apparently plausible model output that your tests exposed and how you resolved it with the actual owner. The project requires documented logic and honest limitations, with enough transparency for finance users to understand a constrained forecast without trusting the specialist's assertion that the model is correct.
• Reserve the weekly capacity from the agreed start and demonstrate a successful transfer to internal users. Explain how you tested independent refresh and interpretation rather than counting training sessions. Confidential customer information, controlled working files and constructive engagement with sales and delivery specialists are essential. You must deliver finite artifacts while leaving staffing, client commitments and executive forecast approval with the sponsor's authorised leaders.

Application

Applications for this mandate are received in one way only: through the India Board Terminal's application process. It is automated end to end. Your Executive Passport travels to the mandate holder in its confidential form, your answers to the three questions below are read before anything else in your file, and every stage that follows is recorded on your applications page.

There is no address to write to and no intermediary to call. The mandate holder reads what the Terminal delivers and nothing else, which is what keeps the process the same for every applicant and keeps your name out of it until you release it. Applications close on 11 October 2026. Mandate reference CVU-CON-2026-IND-244.