Build an annual operating plan and budget from drivers - revenue drivers, a headcount plan with fully loaded cost and start-month timing, non-headcount opex by department, COGS, monthly phasing, scenarios, and cash runway - and reconcile top-down targets with bottom-up department requests, with approval and reforecast cadence. Use when asked to build next year's budget or annual operating plan, create a headcount plan and cost model, phase a budget by month, reconcile department requests with company targets, model base, upside and downside scenarios, or check runway under the plan. Do not use for explaining actual-versus-budget variances (budget-variance-explainer), marketing channel allocation (plan-marketing-budget), a 13-week cash forecast (build-cash-forecast), or support team sizing (plan-support-staffing).
Build an annual operating plan and budget from drivers - revenue drivers, a headcount plan with fully loaded cost and start-month timing, non-headcount opex by department, COGS, monthly phasing, scenarios, and cash runway - and reconcile top-down targets with bottom-up department requests, with approval and reforecast cadence. Use when asked to build next year's budget or annual operating plan, create a headcount plan and cost model, phase a budget by month, reconcile department requests with company targets, model base, upside and downside scenarios, or check runway under the plan. Do not use for explaining actual-versus-budget variances (budget-variance-explainer), marketing channel allocation (plan-marketing-budget), a 13-week cash forecast (build-cash-forecast), or support team sizing (plan-support-staffing).
Map and improve a business process end to end. Scopes it with SIPOC (Suppliers, Inputs, Process, Outputs, Customers), draws the current-state swimlane map, measures cycle time against touch time, handoffs, rework loops, and wait states, classifies waste with the lean waste categories, finds root causes with 5 whys and a fishbone, designs the future state, assigns RACI for the redesigned steps, adds controls, and produces an implementation plan with metrics. Use when a process is slow, error-prone, full of handoffs or approvals, or nobody can say who owns a step; when asked for a process map, value stream map, swimlane, SIPOC, bottleneck analysis, or process improvement. Do not use for documenting a settled process as a procedure (sop-writer), building a metric hierarchy (kpi-tree), or post-incident analysis of a single failure (incident-postmortem).
Map and improve a business process end to end. Scopes it with SIPOC (Suppliers, Inputs, Process, Outputs, Customers), draws the current-state swimlane map, measures cycle time against touch time, handoffs, rework loops, and wait states, classifies waste with the lean waste categories, finds root causes with 5 whys and a fishbone, designs the future state, assigns RACI for the redesigned steps, adds controls, and produces an implementation plan with metrics. Use when a process is slow, error-prone, full of handoffs or approvals, or nobody can say who owns a step; when asked for a process map, value stream map, swimlane, SIPOC, bottleneck analysis, or process improvement. Do not use for documenting a settled process as a procedure (sop-writer), building a metric hierarchy (kpi-tree), or post-incident analysis of a single failure (incident-postmortem).
Design a career ladder (leveling framework) for a job family. Sets individual contributor and manager tracks, the number of levels, and the dimensions that define them (scope, impact, complexity, autonomy, leadership and influence, craft), then writes observable level expectations that differ in kind between adjacent levels. Calibrates the draft against real anonymized examples, maps existing employees to levels, defines the promotion process and evidence standard, and links levels to salary bands. Use when asked to create or fix a career ladder, career framework, leveling guide, IC versus manager tracks, or promotion criteria, or when titles and levels are inconsistent across teams. Do not use for writing a single job description (job-description-writer), drafting an individual performance review (performance-review-draft), or pricing levels in pay ranges (design-comp-bands).
Design a career ladder (leveling framework) for a job family. Sets individual contributor and manager tracks, the number of levels, and the dimensions that define them (scope, impact, complexity, autonomy, leadership and influence, craft), then writes observable level expectations that differ in kind between adjacent levels. Calibrates the draft against real anonymized examples, maps existing employees to levels, defines the promotion process and evidence standard, and links levels to salary bands. Use when asked to create or fix a career ladder, career framework, leveling guide, IC versus manager tracks, or promotion criteria, or when titles and levels are inconsistent across teams. Do not use for writing a single job description (job-description-writer), drafting an individual performance review (performance-review-draft), or pricing levels in pay ranges (design-comp-bands).
Run, document, and speed up a month-end close for a small-to-mid-size company: a business-day close calendar (BD-3 to BD+10) with owners, pre-close and cutoff procedures, the core checklist (cash and bank reconciliations, AR and AP subledger ties, revenue recognition review, accruals, prepaids, fixed assets, payroll, intercompany, deferred revenue roll-forward, inventory), journal entry review standards, balance-sheet reconciliations, flux analysis against user-set thresholds, sign-off and lock, and a faster-close plan. Use when asked to build a close checklist or calendar, reconcile accounts, review journal entries, run a flux review, or shorten the close. Do not use to explain one budget variance (budget-variance-explainer), for a 13-week cash forecast (build-cash-forecast), or for accounting-standard opinions.
Run, document, and speed up a month-end close for a small-to-mid-size company: a business-day close calendar (BD-3 to BD+10) with owners, pre-close and cutoff procedures, the core checklist (cash and bank reconciliations, AR and AP subledger ties, revenue recognition review, accruals, prepaids, fixed assets, payroll, intercompany, deferred revenue roll-forward, inventory), journal entry review standards, balance-sheet reconciliations, flux analysis against user-set thresholds, sign-off and lock, and a faster-close plan. Use when asked to build a close checklist or calendar, reconcile accounts, review journal entries, run a flux review, or shorten the close. Do not use to explain one budget variance (budget-variance-explainer), for a 13-week cash forecast (build-cash-forecast), or for accounting-standard opinions.
Plan onboarding for a new employee in a specific role, and build a reusable onboarding program for a team. Covers pre-start logistics (equipment, system access, paperwork), day one, week one, role-specific 30/60/90-day outcomes, a buddy and manager check-in cadence, a learning plan, a first meaningful contribution, stakeholder introductions, success measures such as time to productivity and new-hire feedback, and the hiring manager's checklist. Use when someone is about to start or has just started, or when asked for an onboarding plan, 30-60-90 day plan, first-week schedule, new hire checklist, buddy program, or a standard onboarding template for a team. Do not use for writing the job description (job-description-writer), designing interviews (structured-interview-kit), or designing product onboarding for app users or customers.
Plan onboarding for a new employee in a specific role, and build a reusable onboarding program for a team. Covers pre-start logistics (equipment, system access, paperwork), day one, week one, role-specific 30/60/90-day outcomes, a buddy and manager check-in cadence, a learning plan, a first meaningful contribution, stakeholder introductions, success measures such as time to productivity and new-hire feedback, and the hiring manager's checklist. Use when someone is about to start or has just started, or when asked for an onboarding plan, 30-60-90 day plan, first-week schedule, new hire checklist, buddy program, or a standard onboarding template for a team. Do not use for writing the job description (job-description-writer), designing interviews (structured-interview-kit), or designing product onboarding for app users or customers.
Audit and rationalize a company's software and SaaS spend. Builds the inventory from accounts payable, corporate card and expense exports plus the SSO or identity provider app list, normalizes vendor names, categorizes tools, finds overlapping and duplicate tools, measures license utilization, builds a renewal calendar with notice periods and auto-renew terms, and ranks savings levers with labelled estimates and risk checks before cancelling, ending in an owner-per-app governance model. Use when asked to audit software spend, cut SaaS costs, find unused licenses or duplicate tools, build a renewal calendar, or set up software ownership. Do not use for choosing one vendor among options (vendor-comparison), negotiating a specific renewal (negotiate-tactically), or the annual budget (build-operating-budget).
Audit and rationalize a company's software and SaaS spend. Builds the inventory from accounts payable, corporate card and expense exports plus the SSO or identity provider app list, normalizes vendor names, categorizes tools, finds overlapping and duplicate tools, measures license utilization, builds a renewal calendar with notice periods and auto-renew terms, and ranks savings levers with labelled estimates and risk checks before cancelling, ending in an owner-per-app governance model. Use when asked to audit software spend, cut SaaS costs, find unused licenses or duplicate tools, build a renewal calendar, or set up software ownership. Do not use for choosing one vendor among options (vendor-comparison), negotiating a specific renewal (negotiate-tactically), or the annual budget (build-operating-budget).
Design salary bands (pay ranges) from a job architecture and market data. Confirms job families and levels first, ages survey data to a common effective date with a user-supplied annual factor, rates match quality, sets a pay philosophy percentile, then builds midpoints, range spread ((max - min) / min), midpoint progression, and overlap by level, with geographic differentials. Places current employees with compa-ratio and range penetration, handles red- and green-circle cases, costs bringing people to minimum, and adds pay-transparency and pay-equity review steps. Use when asked to build salary bands, pay ranges, a compensation structure, compa-ratios, or to find who is under or over range. Do not use for sales commission or variable pay plans (design-sales-compensation), defining levels and expectations (design-career-ladder), or writing an individual offer letter.
Design salary bands (pay ranges) from a job architecture and market data. Confirms job families and levels first, ages survey data to a common effective date with a user-supplied annual factor, rates match quality, sets a pay philosophy percentile, then builds midpoints, range spread ((max - min) / min), midpoint progression, and overlap by level, with geographic differentials. Places current employees with compa-ratio and range penetration, handles red- and green-circle cases, costs bringing people to minimum, and adds pay-transparency and pay-equity review steps. Use when asked to build salary bands, pay ranges, a compensation structure, compa-ratios, or to find who is under or over range. Do not use for sales commission or variable pay plans (design-sales-compensation), defining levels and expectations (design-career-ladder), or writing an individual offer letter.
Calculate how many agents a customer support or contact center team needs from its workload. Forecasts contact volume by week, day and interval, sizes phone and chat with Erlang C against a service-level target, sizes email and ticket queues with workload hours and response-time targets, then applies occupancy caps and shrinkage to reach FTE, hires and sensitivity. Use when asked how many support agents or FTE to hire, for a support staffing model or headcount plan, to hit an 80/20 service level, to plan peak-season coverage, or to see what happens if handle time or ticket volume changes. Do not use for customer replies (support-reply-drafter), support SOPs (sop-writer), a company-wide budget (build-operating-budget), or process mapping (map-business-process).
Calculate how many agents a customer support or contact center team needs from its workload. Forecasts contact volume by week, day and interval, sizes phone and chat with Erlang C against a service-level target, sizes email and ticket queues with workload hours and response-time targets, then applies occupancy caps and shrinkage to reach FTE, hires and sensitivity. Use when asked how many support agents or FTE to hire, for a support staffing model or headcount plan, to hit an 80/20 service level, to plan peak-season coverage, or to see what happens if handle time or ticket volume changes. Do not use for customer replies (support-reply-drafter), support SOPs (sop-writer), a company-wide budget (build-operating-budget), or process mapping (map-business-process).
Model the unit economics of a subscription or transactional business - contribution margin per customer or order, CAC (fully loaded vs. paid-only, blended vs. by channel), CAC payback on gross margin, LTV with its caveats, LTV:CAC, sensitivity tables, and segment and channel breakdowns. Use when asked to calculate CAC, LTV, payback period, contribution margin, or LTV to CAC ratio, to check whether customer acquisition is profitable, to compare unit economics by channel or segment, or to prepare unit economics for a board or investor review. Do not use for sizing a market (market-sizing), setting prices and packaging (develop-offers), building the annual budget (build-operating-budget), or measuring retention curves in depth (analyze-cohort-retention).
Model the unit economics of a subscription or transactional business - contribution margin per customer or order, CAC (fully loaded vs. paid-only, blended vs. by channel), CAC payback on gross margin, LTV with its caveats, LTV:CAC, sensitivity tables, and segment and channel breakdowns. Use when asked to calculate CAC, LTV, payback period, contribution margin, or LTV to CAC ratio, to check whether customer acquisition is profitable, to compare unit economics by channel or segment, or to prepare unit economics for a board or investor review. Do not use for sizing a market (market-sizing), setting prices and packaging (develop-offers), building the annual budget (build-operating-budget), or measuring retention curves in depth (analyze-cohort-retention).