Tejas Parikh

Once those questions are settled, software becomes a question—and often not the answer. The same approach appears in two examples: price and capacity.

The board asks what happens if the company holds price on its largest renewal, and the model cannot answer quickly.

• Tejas Parikh traces the number to a commercial system or a spreadsheet owned outside finance, while the forecast holds a copy that was correct in August.
• In a second example, capacity is not recorded, nobody updates it when work is won, and the forecast has no capacity line.

Read original · Original 2

If the input sits in one identifiable place but nobody owns approval, the fix is ownership: name the approver, agree on a turnaround, and the same request can be answered next week without touching the model.

• If the driver is embedded in several places or entered as a blended rate nobody can decompose, the fix is design: source it once and reference it everywhere.
• Choose per driver, not per model.

Redesign takes weeks and buys traceability.

• Clarifying ownership takes a conversation and buys speed.
• In the capacity case, Tejas Parikh frames the same choice as approval speed: faster answers come from fewer approvals; traceable answers come from more.

Read original · Original 2

Three records do three jobs: the approved budget stays exactly as approved as the commitment baseline; the latest forecast carries the new assumption and a named owner; an action log records what management is doing about it. Accountability and an honest forecast only look like opposites when nobody has decided who may approve a material change to an assumption.

A contract start date moves by a month, six weeks after board approval, and nothing has gone wrong.

• The budget stays as approved, the forecast carries the new start date, and the action log records resequenced delivery, a revised recruitment date, or a conversation with the customer.
• A finance leader in a payments business described, in a research discussion, connecting monthly results to the rest of the year and holding leaders accountable for both budgets and forecasts.

Read original

Tejas Parikh proposes connecting the operational change to a named decision owner, a real set of options, a trigger, and a review date. Nothing saves automatically: somebody has to decide which team owns the capacity decision.

A start date slips by three weeks. Tejas Parikh proposes a response of their own, distinct from the Head of Finance's approach at a recruitment business, where disconnected source data meant rebuilding the model whenever the scenario changed.

Read original

Reviews usually treat all three as one. Tejas Parikh proposes tracking four fields against each material variance: the outcome achieved, the commitment still outstanding, the decision owner, and the date by which funds are released or recommitted.

A finance leader at a technology business described in a research discussion how budgets committed to projects that never happened went on to prevent other initiatives from being funded. The budget stayed fully occupied even though the project never started.

Read original

This sits alongside the two recurring research themes Tejas Parikh names: slow scenario responses and assumptions nobody owns. The second is cheaper to fix, yet fixed less often.

The capacity post asks readers to record what the decision turned out to be. The variance method ends with a date by which funds are released or recommitted, while the contract post notes that a revised revenue date does not release committed cost on its own.

Read original · Original 2 · Original 3

Newcomers should start here: it demonstrates the diagnostic move that runs through the other posts—find the driver, its source, and its owner before replacing the tool.

The board asks what happens if the company holds price on its largest renewal.

• The model cannot answer quickly.
• Tejas Parikh traces where price actually lives and who can change it, rather than starting with the model.
• The number usually sits in a commercial system or a spreadsheet owned outside finance, while the forecast holds a copy that was correct in August.
• The post separates two fixes.
• If the input sits in one identifiable place but nobody owns approval, the fix is ownership: name the approver, agree the turnaround, and the same request becomes answerable next week without touching the model.
• If price is embedded in several places or entered as a blended rate nobody can decompose, the fix is design: separate the driver, source it once, and reference it everywhere.
• The trade-off is real: redesign costs weeks and buys traceability; clarifying ownership costs a conversation and buys speed.
• They also name two recurring research themes: slow scenario responses and assumptions nobody owns.
• The second is cheaper to fix, but gets fixed less often.

For brands planning a campaign

For a portfolio operations workshop, start with the driver the board asks about most.

• Name the approver, set a turnaround, and decide whether the problem is ownership or design.
• A campaign can teach this trade-off without presenting software as the first answer.

Start here for a practical example of diagnosing the issue before buying software.

A board question about taking on work without hiring takes a week to answer, and the room concludes the planning tool is not good enough.

• Tejas Parikh traces the problem instead.
• Capacity is not recorded anywhere, so there is no data.
• Nobody updates it when work is won, so there is no process.
• The forecast carries no capacity line, so the model cannot flex.
• Only then does technology become the question—and by that point, it often is not the answer.
• Each gap has a smallest useful intervention and an owner.
• The post names a trade-off: fewer approvals bring faster answers; more bring traceability.
• The choice should be made per driver, not per model.
• It ends by asking readers to record the decision, because that outcome informs the next assumption review—a step most teams skip.

For brands planning a campaign

A workshop can have companies list capacity data, the update process, the forecast line, and the decision owner before making any tooling decision. The campaign angle is simple: the smallest useful fix may be outside the tool, and approval speed is a deliberate choice for each driver.

Read it to see how a scenario leads to a decision owner.

A start date slips by three weeks.

• Revenue moves with it.
• The team, contracted capacity, and service obligations do not move on their own.
• Tejas Parikh cites a conversation with a Head of Finance in a recruitment business, who described disconnected source data and rebuilding the model whenever the scenario changed.
• Parikh proposes a response that connects an operational change to a named decision owner, a real set of options, a trigger, and a review date.
• There is no automatic saving: a revised revenue date does not release committed cost by itself; somebody has to decide.
• The post asks which team owns the capacity decision when a contract slips.

For brands planning a campaign

A portfolio reporting template can add a trigger, decision owner, options, and review date to any contract slip.

• A workshop can test whether teams know who owns the capacity decision.
• The secondary campaign idea is accountability where operations meet finance.

Start here for the distinction between a commitment baseline and the current expectation.

A contract start date moves by a month, six weeks after the board approved the budget.

• Nothing has gone wrong; the world carried on.
• Tejas Parikh argues that three records should now do three different jobs.
• The approved budget stays exactly as approved.
• It is the commitment baseline, and the signed-off version is not edited quietly.
• The latest forecast moves: it reflects the current expectation, carries the new start date, and names somebody against the changed assumption.
• The action log records what management is doing about it: resequenced delivery, a revised recruitment date, or a conversation with the customer.
• Parikh cites a research discussion with a finance leader in a payments business, who described connecting monthly results to the implications for the rest of the year and holding leaders accountable for both budgets and forecasts.
• The post argues that accountability and an honest forecast are not in tension; they only appear to be when nobody has decided who may approve a material change to an assumption.

For brands planning a campaign

A portfolio reporting standard can use three records: commitment baseline, latest forecast, and action log.

• A workshop can apply that structure to one live contract change and assign an approver for the changed assumption.
• A campaign can frame forecast discipline as a decision-rights problem, not a reporting problem.

Start here for the variance-review method and the distinction between savings, delays, and released funding.

An underspend can hide a missed investment decision.

• Tejas Parikh cites a 2026 research discussion with a finance leader at a technology business, who described budgets committed to projects that never happened preventing other initiatives from being funded.
• Parikh argues that an underspend has at least three meanings, though reviews usually treat them as one.
• Genuine efficiency means the outcome was delivered for less cost—worth understanding and repeating.
• Timing means the work has slipped, the commitment is still live, and the money is spoken for even though it has not moved.
• Released funding means the work is not happening, the commitment has lapsed, and capital is idle because nobody has formally freed it.
• The practical fix is to track four fields against each material variance: the outcome achieved, the commitment still outstanding, the decision owner, and the date by which funds are released or recommitted.
• The post asks whether a review distinguishes savings, delays, and money available to redeploy.

For brands planning a campaign

A workshop can apply the four fields to one material variance.

• A portfolio reporting campaign can show how to separate genuine savings from slipped commitments and idle capital.
• The secondary application is a review agenda that turns underspend into a redeployment decision.

If an owner is missing, the fix is ownership; if price is blended across several places, redesign the process to source the driver once.

• The same pattern appears in a capacity example: capacity is not recorded, nobody updates it when work is won, and the forecast has no capacity line.
• Technology becomes the question only after the data and ownership gaps are visible.

Trace each assumption through systems, owners, and forecast lines, then name the smallest useful intervention and its owner.

For brands planning a campaign

A portfolio operations workshop can map a board-visible driver’s source, approver, and update cadence before anyone considers new planning software.

Examples: Source 1 · Source 2

Faster answers come from fewer approvals; traceable answers come from more. Decide per driver, not per model.

For brands planning a campaign

For private equity portfolio teams deciding where to spend effort, this supports starting with ownership and cadence for the driver the board keeps asking about, then redesigning only drivers with embedded or blended inputs.

Examples: Source 1 · Source 2

The approved budget stays as the commitment baseline and is not quietly edited.

• The latest forecast moves and names an owner for the changed assumption.
• The action log records management’s response, such as resequenced delivery or a revised recruitment date.
• A payments finance leader described connecting monthly results to rest-of-year implications and holding leaders accountable for both budgets and forecasts.

For brands planning a campaign

Portfolio reporting can use the three-record model to separate board-approved commitments, current expectations, and management actions. This reduces quiet edits and makes assumption ownership visible.

Examples: Source 1

A Head of Finance in a recruitment business described disconnected source data and rebuilding the model whenever the scenario changed.

• Tejas Parikh proposes connecting an operational change to a named decision owner, real options, a trigger, and a review date; this is not a description of that person’s process.
• A revised revenue date does not release committed cost by itself.

For brands planning a campaign

A workshop exercise can take a slipped contract or delayed start and produce a decision owner, options, trigger, and review date. The same fields can carry into portfolio reporting.

Examples: Source 1

Tejas Parikh describes a technology-business example in which committed budgets for projects that never happened kept preventing other initiatives from being funded. The practical fix is to track four fields against each material variance: outcome achieved, commitment still outstanding, decision owner, and the date funds are released or recommitted.

For brands planning a campaign

A portfolio variance review can classify below-plan spend as savings, delay, or money available to redeploy, using four fields to keep idle capital from remaining unowned.

Examples: Source 1

Recurring subjects include FP&A, CFO work, private equity, scenario planning, forecasting, and budget accountability. Several posts draw on 2026 research discussions with finance leaders, then distinguish Tejas Parikh’s own reading.

Short illustrative example, trace to the driver or owner, explicit trade-off, closing decision question.

The corpus contains short text posts only, with no dated progression, long-form research reports, or transcripts, so changes over time cannot be mapped from this evidence.

For brands planning a campaign

A brand can evaluate Tejas Parikh for short-form educational posts and workshop prompts on assumption ownership, variance review, and scenario planning. For long-form research reporting, ask for a sample.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

Parikh's posts identify slow scenario responses and unowned assumptions as recurring problems. Shcherbakova names transformation fatigue as a business risk affecting trust, productivity and adoption, and closes a series arguing that the future finance function is defined by its capacity for change, not by how much change it launches.

Shcherbakova stays at the level of the function and its capacity to change, while Parikh works through one board question at a time, ending with a specific record, owner or field to fix. Shcherbakova's posts are thematic assessments with broad hashtag reach; Parikh's are worked examples with a diagnostic step readers can apply to one driver.

Read original · Original 2

Mahmood's warning that an AI planning tool will supply a confident answer while account data is six months old and capacity figures are guesses echoes Parikh's point that traceable and fast answers require different fixes.

Mahmood works in sales planning and RevOps, covering territory, quota, headcount and comp, and writes as a product builder showing peers what they have made. Parikh stays in corporate finance and FP&A, framing the remedy as a decision about ownership or design inside existing records, not as a new tool.

Read original · Original 2

Spira's governed deal path—what was proposed, what changed, who approved it, what was contracted—follows the same instinct as Parikh's four fields for a material variance and three records separating an approved budget from a current forecast.

Spira applies this to revenue operations and commercial approvals, including quote versions, discounts and audit trails, while also promoting a deal-governance product. Parikh applies it to forecast assumptions and budget variances without a product to sell, building posts around a single worked example rather than a list of failure symptoms.

Read original · Original 2

The posts describe finance operating in permanent change — AI, automation, ESG reporting, cloud systems, shared services, cost pressure, and data governance — and argue that transformation fatigue is a business risk affecting trust, productivity, adoption, and value creation.

• They end on change capacity as the defining factor for the future finance function.
• For a portfolio operations team whose companies have stacked ERP, reporting, and cost programmes and are watching adoption stall, that framing opens a sharper conversation than a driver trace.

The framing stops at the argument.

• It does not give the workshop the operational steps to name a driver's approver, separate the commitment baseline from the latest forecast, or classify a variance with fields and a release date.
• Nor does it show how to translate those steps into a portfolio reporting template.
• Tejas Parikh's posts end each example with a decision question and produce reusable artefacts — a three-record model and a four-field variance review — making them closer to the deliverable.
• Choosing Shcherbakova means accepting a discussion-led session and building the templates yourself.

Examples: Source 1 · Source 2

The posts describe territory exports, pipeline pulls, and comp files arriving with mismatched rep names; a smart team spending six weeks reconciling them by hand; leadership questions each costing three days of rework; and a plan locked because the team ran out of time, not because anyone proved it right. Hassan Mahmood also describes a system that shows the math behind every number and says when the data cannot support an answer — the same traceability principle needed for a session on territory, quota, headcount, and comp.

The posts are commercially tied to a named product, and the second invites direct messages from enterprise sales planning and RevOps leaders.

• A portfolio session built on them tends to come with a tooling decision attached, narrowing the scope to sales planning rather than finance-led budget and forecast governance.
• Tejas Parikh's posts make the same traceability argument without a product behind them and stay on the budget, forecast, and variance side — the language of finance-led budget and forecast governance.
• Choosing Hassan Mahmood buys deeper sales-planning detail and a working demonstration; the trade-off is narrower scope and a vendor conversation within the session.

Examples: Source 1 · Source 2

The five-step order of operations (definitions, architecture, process, measurement, leverage) addresses the ownership gap in portfolio governance, and the interview test for a first operations hire is concrete enough to use in a session.

The framing is tied to revenue operations, and the deal-governance post is built around a named product.

• The sequencing argument concerns hiring, not portfolio reporting.
• Applying it to board-level assumption ownership and variance review requires translation: the definitions step covers lead, opportunity, stage, and commit, not price drivers, capacity lines, or the four variance fields a portfolio review template needs.
• Its audit trail applies to commercial deals, not budget baselines and forecasts.
• Tejas Parikh's posts already use finance's language and produce baseline, forecast, and variance artefacts.
• Choosing Leore Spira buys a stronger audit trail and a disciplined sequencing argument; the trade-off is a conversion step before either fits a portfolio reporting session.

Examples: Source 1 · Source 2