ITI Board Agents Reference Guide
π Universal Inputs (Used by All Agents)
| Variable |
Description |
Why It Matters |
{{proposal_summary}} |
Concise overview of what is being proposed (1-2 paragraphs) |
Every agent needs to understand the core initiative before evaluating it through their functional lens |
{{proposal_owner}} |
The director-level employee responsible for the proposal |
Establishes accountability; agents assess whether the owner has appropriate authority |
{{contributors}} |
Team members and stakeholders involved |
Reveals cross-functional involvement and whether the right expertise has been consulted |
{{decision_ask}} |
The specific decision or approval being requested |
Clarifies scope of evaluation; prevents scope creep in the review process |
{{risks_and_mitigations}} |
Top 3-5 risks with mitigation strategies |
Every agent stress-tests whether risks are adequately identified for their domain |
{{opportunity_cost}} |
What the organization will NOT do if approved |
Forces explicit trade-off thinking; helps prioritize against competing initiatives |
{{dependencies}} |
Teams, systems, vendors required for success |
Reveals hidden constraints; critical for assessing execution feasibility |
π― Strategic & Planning Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{problem_statement}} |
Clear articulation of the problem or opportunity |
CEO |
CEO evaluates whether this is worth solving at the strategic level |
{{strategic_priorities_alignment}} |
How the proposal maps to top priorities/OKRs |
CEO CPO |
Ensures initiatives advance stated strategy, not distractions |
{{strategic_intent}} |
The broader strategic purpose |
Board |
Board assesses long-term competitive positioning |
{{alternatives}} |
Other options considered, including “do nothing” |
CEO CFO Board |
Validates due diligence; reveals whether the best option was chosen |
{{why_now}} |
What changed that makes this urgent or timely |
CPO |
Helps prioritize; prevents “solutions looking for problems” |
{{context}} |
Business environment and situational factors |
Board |
Board needs context for pattern-matching from other companies |
{{reversibility}} |
How easily the decision can be undone |
Board |
Distinguishes one-way doors from two-way doors; affects risk tolerance |
π° Financial & Resource Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{time_horizon}} |
Duration over which costs/benefits unfold |
CFO CHRO |
Affects financial modeling, hiring, and change management scope |
{{cost_breakdown}} |
Itemized one-time and recurring costs |
CFO CHRO |
CFO validates completeness; CHRO assesses people-related costs |
{{headcount_plan_and_loaded_costs}} |
New roles with fully-burdened costs |
CFO CHRO |
CFO verifies accuracy; CHRO assesses hiring feasibility |
{{revenue_or_savings_drivers}} |
Unit economics explaining value generation |
CFO |
CFO validates assumptions are reasonable and evidence-based |
{{adoption_assumptions}} |
Expected uptake rates and growth projections |
CFO CMO CPO |
All stress-test whether projections are realistic |
{{pricing_and_margin_assumptions}} |
Pricing structure and expected margins |
CFO CRO |
CFO validates profitability; CRO assesses market acceptance |
{{cash_flow_timing}} |
When costs hit and revenue realizes |
CFO |
Critical for treasury planning and working capital |
{{payback_period}} |
Time to recover initial investment |
CFO |
Key financial metric for investment decisions |
{{roi_npv_irr}} |
ROI, NPV, IRR calculations |
CFO |
Standard metrics for comparing investment alternatives |
{{budget_request}} |
Specific funding amount requested |
CFO |
Determines approval authority and budget allocation |
{{resourcing_and_budget}} |
People, time, budget, vendors needed |
CEO COO |
Validates that execution is properly resourced |
π
Execution & Timeline Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{scope_in}} |
What is explicitly included |
CEO COO |
Defines boundaries; prevents scope creep |
{{scope_out}} |
What is explicitly excluded |
CEO COO |
Sets expectations; identifies what’s deferred vs. abandoned |
{{milestones}} |
Key deliverables with target dates |
CEO CTO Board |
Enables progress tracking and accountability checkpoints |
{{milestones_with_owners}} |
Milestones with specific people responsible |
COO |
COO validates ownership is explicit, not assumed |
{{milestones_timeline}} |
Combined milestones and timeline view |
CCO CPO CRO |
Customer-facing leaders assess timing alignment |
{{timeline}} |
Overall duration and key dates |
CEO COO CTO GC |
All assess whether timeline is realistic |
{{critical_path}} |
Sequence of dependencies determining timeline |
COO CTO |
Identifies the longest chain; reveals what cannot slip |
{{gates}} |
Go/no-go milestone criteria |
COO |
Defines decision points for course correction |
{{mvp_scope}} |
What’s in v1 vs. later iterations |
CPO |
Ensures appropriate scoping; prevents feature bloat |
π₯ Customer & Market Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{target_segments}} |
Specific customer segments being served |
CMO CRO |
Marketing and sales need clear targeting for GTM |
{{target_users}} |
Specific personas, use cases, or user types |
CPO |
Product validates user definition is specific, not generic |
{{affected_segments}} |
Customer segments impacted by the change |
CCO |
Customer success assesses which accounts need attention |
{{customer_problem_jtbd}} |
The job-to-be-done customers are solving |
CMO CPO |
Validates product-market fit and messaging alignment |
{{customer_evidence}} |
Data from interviews, surveys, NPS, tickets |
CCO CMO CPO CRO |
All customer-facing leaders require evidence over opinions |
{{market_context}} |
Market size, category dynamics, trends |
CMO |
Marketing needs context for positioning strategy |
{{competitive_landscape}} |
Competitors and alternatives including status quo |
CMO |
Critical for differentiation and messaging |
{{value_prop}} |
One-sentence value proposition |
CMO |
Marketing tests whether positioning is clear |
{{differentiation}} |
Why this is better than alternatives |
CMO CPO |
Both assess whether value proposition is defensible |
π€ Customer Success & Retention Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{retention_impact}} |
How the proposal affects retention/churn |
CCO |
Core CCO concern; protecting earned revenue |
{{expansion_opportunity}} |
Potential for upsell/cross-sell |
CCO CRO |
Both assess growth potential in existing accounts |
{{existing_account_risk}} |
Risks to current customer relationships |
CCO |
Identifies accounts needing proactive attention |
{{churn_considerations}} |
Churn risks or mitigation strategies |
CRO |
Revenue protection is critical for financial health |
{{adoption_friction}} |
Learning curve or barriers to adoption |
CCO |
Customer success must plan for enablement |
{{migration_requirements}} |
What existing customers need to transition |
CCO |
CCO plans customer communications and support |
{{customer_communication_plan}} |
How and when customers will be informed |
CCO |
Critical for managing customer expectations |
π Sales & Revenue Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{revenue_type}} |
Category: new logo, expansion, retention, acceleration |
CRO |
Determines sales motion and forecasting approach |
{{projected_revenue_impact}} |
Expected annual revenue contribution |
CRO |
Core metric for revenue leader evaluation |
{{time_to_revenue}} |
When first deals close, pipeline builds, full ramp |
CRO |
Reality-checks revenue projections against ramp curves |
{{deal_size_assumptions}} |
Expected ACV/TCV per deal |
CRO |
Key variable in revenue modeling |
{{win_rate_assumptions}} |
Expected conversion rates |
CRO |
CRO validates against historical performance |
{{pipeline_assumptions}} |
Expected pipeline generation |
CRO |
Foundation of revenue projections |
{{sales_motion_changes}} |
Changes to playbooks, talk tracks, demos |
CRO |
Assesses enablement burden and sales cycle impact |
{{enablement_requirements}} |
Training, collateral, and tools for sales |
CRO |
CRO ensures sales team can execute |
{{competitive_win_factors}} |
Why we win against competitors |
CRO |
Sales positioning and competitive strategy |
π Go-to-Market Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{channels}} |
Primary marketing/distribution channels |
CMO |
Determines GTM strategy and resource allocation |
{{funnel_assumptions}} |
Awareness-to-conversion assumptions |
CMO |
Marketing validates whether funnel math works |
{{pricing_packaging}} |
Pricing structure and packaging approach |
CMO |
Affects positioning and competitive dynamics |
{{enablement_plan}} |
How customer-facing teams will be prepared |
CMO COO |
Both assess whether GTM teams are ready |
{{launch_plan}} |
Milestones and activities for launch |
CMO |
Marketing orchestrates GTM activities |
{{marketing_resourcing_budget}} |
Marketing-specific resource requirements |
CMO |
Validates marketing can support the initiative |
βοΈ Technical & Engineering Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{current_state}} |
What systems/capabilities exist today |
CTO |
Baseline for understanding change magnitude |
{{proposed_solution}} |
High-level technical approach |
CTO |
CTO evaluates architectural soundness |
{{architecture_components}} |
Systems, services, and integrations involved |
CTO |
Validates design is complete and coherent |
{{build_vs_buy}} |
Rationale for building vs. purchasing |
CTO |
CTO validates the make/buy decision |
{{engineering_resourcing}} |
Engineering team allocation and capacity |
CTO CHRO |
Both assess whether engineering can deliver |
{{data_plan}} |
Data quality, access, migration, retention |
CTO |
Critical for many initiatives; often underestimated |
{{security_and_compliance}} |
Security controls and compliance requirements |
CTO |
Non-negotiable for CTO approval |
{{reliability_slos}} |
Service level objectives (availability, latency) |
CTO |
Defines operational expectations |
{{scalability_assumptions}} |
Expected load and growth patterns |
CTO |
Prevents performance surprises |
{{tech_debt_impact}} |
Whether this creates or reduces tech debt |
CTO |
CTO protects long-term system health |
π§ Operational Readiness Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{ops_impact}} |
Impact on current operations and bandwidth |
COO |
COO assesses operational disruption |
{{process_changes}} |
Changes to workflows and procedures |
COO CHRO |
Both assess change magnitude and readiness |
{{systems_changes}} |
Changes to tools and technology |
COO CHRO |
Both assess training and adoption needs |
{{support_model}} |
Who supports post-launch and with what SLAs |
COO CCO |
Both ensure ongoing operations are planned |
{{support_readiness}} |
Support team training, staffing, knowledge base |
CCO |
CCO ensures support can handle volume |
{{training_plan}} |
How affected employees will be trained |
COO CHRO |
Both ensure teams can execute |
{{documentation_plan}} |
Documentation and enablement materials |
CCO |
Critical for customer and employee success |
π Change Management & People Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{change_management_plan}} |
How organizational change will be managed |
COO CHRO |
Both ensure change is planned, not chaotic |
{{teams_impacted}} |
Which teams will experience change |
CHRO |
CHRO assesses organizational disruption |
{{hiring_plan}} |
New roles or backfills needed |
CHRO |
CHRO validates hiring timeline is realistic |
{{capacity_plan}} |
What stops or slows to make room |
CHRO |
Realistic about bandwidth constraints |
{{skills_gaps}} |
Current capabilities vs. requirements |
CHRO |
CHRO plans training and development |
{{leadership_readiness}} |
Whether managers can lead this change |
CHRO |
Critical for execution success |
{{change_narrative}} |
The story for employeesβwhy this, why now |
CHRO |
CHRO validates messaging will land |
{{communications_plan}} |
Who hears what, and when |
CHRO |
CHRO orchestrates internal communication |
{{employee_experience_impact}} |
Effects on workload, morale, engagement |
CHRO |
CHRO protects organizational health |
βοΈ Legal & Compliance Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{jurisdictions}} |
Geographic regions where this applies |
GC |
Determines applicable laws and regulations |
{{user_types}} |
B2B/B2C, minors, employees, etc. |
GC |
Different user types have different protections |
{{regulated_areas}} |
Industry regulations that apply |
GC |
Identifies compliance requirements |
{{data_types}} |
Types and sensitivity of data involved |
GC |
Determines privacy and security obligations |
{{data_flow}} |
How data moves: collect β store β process β share |
GC |
Critical for privacy compliance assessment |
{{third_parties}} |
Vendors, partners, subprocessors involved |
GC |
Extends legal obligations to third parties |
{{contracts_impacted}} |
Customer, vendor, partner agreements affected |
GC |
GC identifies renegotiation needs |
{{new_agreements_needed}} |
MSA, DPA, SOW, etc. required |
GC |
GC manages contracting workload |
{{ip_considerations}} |
Open source, licensing, content creation |
GC |
Protects intellectual property |
{{approvals_needed}} |
Procurement, security, privacy, board approvals |
GC |
Maps governance requirements |
π Governance & Reporting Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{success_metrics}} |
Leading and lagging indicators of success |
CEO CMO CPO |
All assess whether success is measurable |
{{expected_upside}} |
Best-case scenario and its likelihood |
Board |
Board evaluates risk/reward ratio |
{{benchmarks}} |
Comparable initiatives from other companies |
Board |
Board applies pattern recognition |
{{evidence}} |
Customer and market evidence supporting proposal |
Board |
Board requires evidence over assertions |
{{ownership}} |
Who is accountable for each aspect |
Board |
Board validates governance clarity |
{{reporting_plan}} |
How progress will be communicated |
Board |
Board needs visibility into execution |
π¦ Product-Specific Inputs
| Variable |
Description |
Agents |
Why It Matters |
{{solution_description}} |
What is being built |
CPO |
CPO validates solution matches problem |
{{user_outcomes}} |
Jobs-to-be-done that will be satisfied |
CPO |
Ensures focus on outcomes vs. features |
{{user_journey}} |
End-to-end user experience flow |
CPO |
CPO validates complete experience design |
{{roadmap_alignment}} |
Which priority/OKR this serves |
CPO |
CPO ensures strategic coherence |
{{platform_considerations}} |
Ecosystem and platform implications |
CPO |
CPO evaluates broader product strategy fit |
{{design_requirements}} |
Design scope and timeline |
CPO |
CPO validates design is planned |
π Summary: Most Common Variables
| Variable |
# Agents |
Used By |
{{proposal_summary}} |
11 |
All Agents |
{{proposal_owner}} |
11 |
All Agents |
{{contributors}} |
11 |
All Agents |
{{decision_ask}} |
11 |
All Agents |
{{risks_and_mitigations}} |
11 |
All Agents |
{{opportunity_cost}} |
10 |
CEO CFO COO CTO CMO CPO CRO CCO CHRO Board |
{{dependencies}} |
8 |
CEO CFO COO CTO CPO CRO CCO CHRO |
{{timeline}} |
7 |
CEO CFO COO CTO CMO GC Board |
{{milestones}} |
6 |
CEO COO CTO CPO CRO Board |
{{success_metrics}} |
5 |
CEO CMO CPO CRO CCO |
{{customer_evidence}} |
4 |
CCO CMO CPO CRO |