Pitch Your Next Business Line — Internal Idea Submission

1. Submission Overview and How This Form Works

This intake form collects the information a review panel needs to understand, compare, and shortlist new business line ideas submitted to the internal pitch competition. Please answer as completely and candidly as you can. Where a number is an estimate, an approximate figure is perfectly acceptable — mark it as an estimate in the related comment field.

The form is organised into five comprehensive sections: (1) Team Lead and Cross-Functional Members, (2) Market Problem and Proposed Solution, (3) Target Customer and Internal Synergy Analysis, (4) Resource and Prototype Budget Needs, and (5) Executive Sponsor Endorsement. Fields marked as required must be completed before the submission can be forwarded for review.

Please note: this form is an internal planning and discussion tool. It does not create any commitment, approval, funding decision, or guarantee of acceptance. All figures, projections, and statements are the submitter's own estimates and will be discussed and validated during the review process.

 

Working title of your business line idea

Date of submission

Which competition round are you submitting to?

 

Please tell us what you are hoping to achieve with this submission so we can route it to the right review track:

How did you hear about the pitch competition?

 

Please tell us the source:

2. Section 1 — Team Lead and Cross-Functional Members

Strong ideas are usually carried by a small, cross-functional team. This section captures who is leading the idea, who else is contributing, and what time and skills the team can realistically commit.

 

Team lead full name

Employee or staff identifier

Current job title

Primary department or function

Work email address

Preferred contact number or internal extension

How many years have you worked in the organisation?

What is your current working arrangement?

 

Please describe your working arrangement:

Approximately what percentage of your working time can you commit to this idea per month?

Have you previously submitted an idea to an internal pitch or innovation programme?

 

Please briefly summarise the previous idea and its outcome, and what you learned from the experience:

 

What motivated you to submit an idea this time?

Team or project name (if you have one)

How many people in total are contributing to this idea, including yourself?

Team member roster and contributions

Member name

Department or function

Role on this project

Hours committed per week

Relevant skills or experience

Prior pitch experience?

A
B
C
D
E
F
1
Jordan Lee
Operations
Team lead and product owner
8.0
Process design, vendor management, five years in service operations
2
Priya Raman
Finance
Commercial modelling
4.0
Business case development, pricing analysis
3
 
 
 
 
 
4
 
 
 
 
 
5
 
 
 
 
 
6
 
 
 
 
 
7
 
 
 
 
 
8
 
 
 
 
 
9
 
 
 
 
 
10
 
 
 
 
 

Which functions are already represented in your team?

 

Please name the additional function represented:

Which functions would you still like to recruit into the team?

 

Please name the additional function you would like to recruit:

Is there a named deputy or backup lead who can represent the idea if you are unavailable?

 

Please give the deputy's name and department:

 

How do you plan to keep the idea moving forward during periods when you are unavailable?

How did the team come together, and how do you divide responsibilities and decisions?

Does any team member have a personal, financial, or family interest that could be seen as influencing this proposal?

 

Please describe the situation briefly so the review panel can consider it openly. Disclosure here is treated as a good-faith planning note and does not by itself disqualify an idea:

Which pitch or showcase formats could your team attend?

Please rank the mentoring or support topics that would help your team the most, from most useful (1) to least useful.

Customer research and interview techniques

Financial modelling and business case building

Prototype design and rapid testing

Storytelling and presentation coaching

Stakeholder engagement and change readiness

Data, technology and security planning

3. Section 2 — Market Problem and Proposed Solution

This section is the heart of the submission. Reviewers want to understand the problem you have observed, the evidence behind it, and the solution you propose — including what is genuinely new and what assumptions still need to be tested.

 

In your own words, what problem or unmet need are you addressing?

Who primarily experiences this problem?

 

Please list the groups affected and roughly how significant the problem is for each:

What evidence supports your view of the problem? (Select all that apply)

 

Please describe the other evidence source:

Please summarise the strongest piece of evidence you have, including any numbers, sample sizes, or time periods.

How severe is the problem for the people who experience it, in your assessment?

How often does the problem occur?

What happens today when people try to solve this problem? What workarounds do they use?

Describe your proposed solution in plain language, as if explaining it to someone outside your field.

What type of offering is this?

 

Please describe the combination you have in mind:

How new is this idea relative to what the organisation already offers?

How would you rate the level of innovation in this proposal?

What stage is the idea at today?

 

Please summarise what the early results showed, including anything that surprised you:

Does the idea build on prior work, a previous project, or something already documented inside the organisation?

 

Please describe the prior work and where it can be found, so reviewers can build on it rather than duplicate it:

What are the three most important assumptions behind this idea that still need to be tested?

What are the main risks you can foresee? (Select all that apply)

 

Please describe the other risk:

For the top two risks you selected, how would you reduce or manage them?

Is there anything about this idea that could affect how customers experience our existing products or services?

 

Please describe the potential effect and how you would manage it:

In one or two sentences, why should this idea matter to the organisation right now?

4. Section 3 — Target Customer and Internal Synergy Analysis

A promising idea usually sits at the intersection of a clearly defined customer group and capabilities the organisation already has. This section explores both sides of that equation, along with competitive context and realistic commercial expectations.

 

Who is the primary target customer for this business line?

 

Please describe the mix and which group is most important to the idea's success:

Describe your ideal customer or user in practical terms — their situation, their goals, and what a typical day looks like for them.

Roughly how many potential customers or users could this idea reach in its first year?

How did you estimate that number?

 

Please describe your reasoning so reviewers can judge how firm the estimate is:

Do you have evidence that the target customer would be willing to pay for this?

 

Please describe the evidence — for example letters of interest, pilot commitments, survey responses, or comparable spending behaviour:

 

What is your plan for testing willingness to pay before committing significant resources?

What pricing approach are you considering?

 

Please describe the pricing options you are weighing and what would help you decide:

What is the approximate price point you have in mind per customer or per unit?

How would customers most likely discover and buy this offering? (Select all that apply)

 

Please describe the route to customer you are considering:

Competitive and alternative landscape

Existing alternative or competitor

What it does well

Where it falls short

How our idea differs

A
B
C
D
1
Reactive maintenance contracts
Familiar pricing, established service teams
Intervention happens after failure, limited prevention
Predictive alerts and fixed-price prevention plans
2
Customer-managed spreadsheets
Low direct cost, fully under customer control
Manual effort, no early warning, inconsistent records
Automated monitoring with shared visibility and simple reporting
3
 
 
 
 
4
 
 
 
 
5
 
 
 
 
6
 
 
 
 
7
 
 
 
 
8
 
 
 
 
9
 
 
 
 
10
 
 
 
 

What would make a customer switch from their current approach to yours?

Which existing organisational assets or strengths would this idea rely on? (Select all that apply)

 

Please name the other asset or strength:

Please rate how strongly you agree with each statement about internal synergy.

Strongly disagree

Disagree

Neutral

Agree

Strongly agree

Not enough information yet

The idea uses capabilities we already have rather than building everything new

The idea strengthens or deepens existing customer relationships

The idea could reduce costs or effort in an existing part of the business

The idea fits with the direction the organisation is already moving

The idea could be delivered without disrupting current operations

The idea creates a foundation that other teams or offerings could build on

Could this idea take revenue or attention away from an existing offering?

 

Please describe which offering could be affected and how you would manage the transition or overlap:

 

What makes you confident the idea is additive rather than substitutive?

How well does this idea fit with the organisation's stated priorities?

 

Please describe the tension you see and how you believe it could be resolved:

When could a first version realistically reach customers?

Illustrative revenue outlook (your own estimates)

Period

Expected units or active subscriptions

Average revenue per unit

Projected revenue

A
B
C
D
1
Year 1
250
$1,200.00
$300,000.00
2
Year 2
700
$1,200.00
$840,000.00
3
Year 3
1200
$1,200.00
$1,440,000.00
4
 
 
 
$0.00
5
 
 
 
$0.00
6
 
 
 
$0.00
7
 
 
 
$0.00
8
 
 
 
$0.00
9
 
 
 
$0.00
10
 
 
 
$0.00

Please explain the key drivers behind these projections and any conditions that would change them significantly.

How would you measure success in the first year? (Select all that apply)

 

Please name the additional success measure:

What would a realistic first-year success target look like for the measures you selected?

5. Section 4 — Resource and Prototype Budget Needs

Reviewers understand that early figures are estimates. This section asks what you would need to take the idea to the next step, how you would use those resources, and what a first prototype or pilot would demonstrate. Please state figures in your local working currency and note the currency used.

 

Currency used for all figures in this section

Total funding or budget you are requesting for the next stage

What is the smallest budget that would still let you test the core idea?

Budget breakdown by category

Cost category

What it covers

One-off or recurring

Estimated amount

Supplier identified?

A
B
C
D
E
1
Prototype materials and equipment
Sensors, gateway devices and installation supplies for a 10-site trial
One-off
$8,500.00
2
External specialist support
Data engineering support for the monitoring dashboard
One-off
$12,000.00
3
Customer research and testing
Interviews, incentive costs and usability sessions
One-off
$3,000.00
4
Software and hosting
Cloud hosting and monitoring tools during the pilot
Recurring
$2,400.00
5
 
 
 
 
6
 
 
 
 
7
 
 
 
 
8
 
 
 
 
9
 
 
 
 
10
 
 
 
 

Where would the funding come from? (Select all that apply)

 

Please name the other funding source:

Has any part of this budget been discussed with a budget holder already?

 

Who did you speak with, and what was the general response?

 

Who would you need to involve, and what would you want to show them first?

People and time needed

Role or skill needed

Likely source or department

Percentage of working time

Duration in months

Current availability

A
B
C
D
E
1
Data engineer
Information technology
30
4
Confirmed in principle
2
Service operations specialist
Operations
20
4
To be confirmed
3
Commercial analyst
Finance
15
3
Confirmed in principle
4
 
 
 
 
 
5
 
 
 
 
 
6
 
 
 
 
 
7
 
 
 
 
 
8
 
 
 
 
 
9
 
 
 
 
 
10
 
 
 
 
 

What facilities, equipment or technology would the prototype need? (Select all that apply)

 

Please name the other facility or equipment need:

Describe the prototype or pilot you would build with these resources.

What is the main question the prototype or pilot should answer?

 

Please list the questions in order of importance:

What data or technology would the idea depend on? (Select all that apply)

 

Please name the other data or technology dependency:

Would the idea involve handling information about identifiable individuals, such as customers or colleagues?

 

Please describe what information would be involved and how you would expect to handle it. The review panel can help you identify which internal teams should be consulted early:

Would you need external suppliers, vendors or partners to deliver the prototype?

 

Please describe the type of supplier or partner, the approximate spend, and whether any are already known to the organisation:

Which internal reviews or approvals might be relevant before this idea could be piloted? (Select all that apply)

 

Please name the other review or approval:

Indicative timeline and milestones

Milestone

Target completion date

Owner

What done looks like

A
B
C
D
1
Confirm problem evidence with customer conversations
4/30/2027
Team lead
At least 12 conversations completed and summarised
2
Build prototype version one
7/31/2027
Data engineer
Dashboard running at ten test sites
3
Run pilot and review results
10/31/2027
Team lead
Pilot report with findings and a go or stop recommendation
4
 
 
 
 
5
 
 
 
 
6
 
 
 
 
7
 
 
 
 
8
 
 
 
 
9
 
 
 
 
10
 
 
 
 

How confident are you that the timeline above is realistic?

If the approved budget were around 30% lower than requested, could the idea still be tested in a meaningful way?

 

Please describe the reduced version you would run and what you would expect to learn from it:

 

Please explain which elements are essential and cannot be reduced without losing the value of the test:

What would make you stop or significantly change this idea after the prototype or pilot?

6. Section 5 — Executive Sponsor Endorsement

An executive sponsor adds context, credibility and practical support to a submission. This section records who is endorsing the idea, on what basis, and what support they are able to offer. Sponsors are asked to confirm that they have reviewed the submission and that their comments reflect their own view; this is an internal review note and not a legal attestation.

 

Executive sponsor full name

Sponsor job title

Sponsor department or business unit

Sponsor work email address

What is the sponsor's relationship to the team lead?

 

Please describe the relationship:

Has the sponsor been involved in shaping the idea so far?

 

Please describe how the sponsor has contributed, for example feedback sessions, access to contacts, or review of early drafts:

 

When and how do you plan to brief the sponsor on the idea?

In the sponsor's words, why does this idea matter to the business?

How strongly does the sponsor support progressing this idea to the next stage?

What support can the sponsor realistically offer? (Select all that apply)

 

Please name the other form of support:

Does the sponsor have budget authority that could cover part of the request in Section 4?

 

Please indicate the approximate range the sponsor could consider and any conditions attached to it:

 

Who would the sponsor approach to secure funding, and what would strengthen that conversation?

Would the sponsor attend the pitch session or showcase event?

 

In what capacity would the sponsor take part?

 

Is there an alternative representative the sponsor would send in their place?

Sponsor comments, conditions or reservations about the proposal:

The sponsor confirms that they have reviewed this submission, that the statements attributed to them reflect their own view, and that they understand this endorsement is an internal review note rather than an approval or funding commitment.

Sponsor signature

Date of sponsor endorsement

7. Supporting Materials, Declaration and Next Steps

Optional supporting materials help reviewers understand the idea quickly. A short deck or one-page summary is usually more effective than a long document. Please keep any attachments brief and free of information that should not be shared beyond the review group.

 

Pitch deck or slide summary (optional)

Choose a file or drop it here
 

One-page idea summary or executive brief (optional)

Choose a file or drop it here
 

Sketch, mock-up, diagram or photo that illustrates the idea (optional)

Choose a file or drop it here

Supporting research, data extracts or customer feedback summary (optional)

Choose a file or drop it here
 

Link to any additional materials, if hosted internally

I confirm that the information in this submission is a good-faith description of our idea and our own estimates, and that I understand the review panel may ask questions, request changes, or decide not to progress the idea.

I confirm that the team members listed are aware of this submission and willing to be contacted about it.

Team lead signature

Date signed

How would you prefer to receive updates about your submission? (Select all that apply)

Would you like to be matched with a mentor or review buddy before the pitch session?

 

Which areas would you most like mentoring support in?

Is there anything else the review panel should know before reading this submission?

How clear and easy to complete was this submission form?

Any suggestions for improving this form for future rounds?

Analysis for New Business Line Idea Submission Form for Internal Pitch Competition

Important Note:

This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.

AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.

This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.

Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.


 

Overall Form Analysis

This intake form is a well-structured and thoughtfully designed tool for collecting new business line ideas from employees in the context of an internal corporate pitch competition. The form is organised into five comprehensive sections plus a submission overview and a closing section for supporting materials and declarations. It balances depth of information with practical usability, guiding submitters through team composition, problem definition, solution description, market and synergy analysis, resource needs, and executive sponsorship. The overall design demonstrates a strong understanding of what a review panel needs to compare and shortlist ideas fairly, while also respecting the submitter's time and encouraging candid, good-faith responses.

 

One of the form's most effective design choices is its opening section, which sets clear expectations. The introductory paragraphs explain the purpose of the form, clarify that estimates are acceptable, and explicitly state that the submission does not create any commitment, approval, or funding decision. This transparency reduces anxiety for submitters and encourages honest, complete responses. The form also uses conditional follow-up logic extensively — for example, asking for additional detail when a respondent selects Other or a specific option — which keeps the form concise for straightforward cases while still capturing nuance when needed.

 

Submission Overview and How This Form Works

Working title of your business line idea — This field gives the submission a concise, memorable identifier that reviewers can use to track and refer to the idea throughout the evaluation process. A working title also helps the submitter frame their concept clearly from the outset. The placeholder example is helpful and sets a reasonable expectation for length and specificity.

 

Date of submission — Capturing the submission date supports chronological record-keeping and helps organisers manage round deadlines and review sequencing. It is a straightforward but essential administrative anchor for the process.

 

Which competition round are you submitting to? — This routing question ensures submissions are directed to the appropriate review track. The inclusion of a Not sure option with a follow-up text field is a thoughtful design choice that accommodates uncertainty without blocking submission. This helps organisers understand the submitter's expectations and route the idea appropriately.

 

How did you hear about the pitch competition? — This optional question supports internal communications planning by identifying which channels are most effective at reaching potential submitters. The conditional follow-up for Other keeps the list clean while capturing additional sources.

 

Section 1 — Team Lead and Cross-Functional Members

This section is well designed to capture the human dimension of the proposal. Strong ideas typically require cross-functional collaboration, and the form recognises this by collecting detailed information about the team lead, contributing members, time commitments, and functional representation.

 

Team lead full name, Employee or staff identifier, Current job title, Primary department or function, and Work email address — These identity fields establish who is accountable for the submission and provide the review panel with clear contact and organisational context. Collecting the employee identifier in addition to the name supports internal record-keeping and helps avoid ambiguity when multiple employees share similar names.

 

Preferred contact number or internal extension — This optional field provides an alternative communication channel, which can be useful for scheduling discussions or clarifying details. Keeping it optional respects that not all employees may wish to share a phone number.

 

How many years have you worked in the organisation? — This contextual question helps reviewers understand the team lead's institutional knowledge and familiarity with internal processes. Allowing decimal values accommodates part-year experience accurately.

 

What is your current working arrangement? — Understanding the team lead's employment type gives reviewers context about availability and potential constraints. The conditional follow-up for Other captures nuances not covered by the standard options.

 

Approximately what percentage of your working time can you commit to this idea per month? — This is a practical and important question. It helps reviewers assess the realistic capacity of the team lead to drive the idea forward alongside their existing responsibilities. The framing as an approximate percentage is appropriately flexible.

 

Have you previously submitted an idea to an internal pitch or innovation programme? — The yes/no branching with tailored follow-up questions is an excellent design choice. It captures relevant experience and learning from past attempts, or motivation for first-time submitters, without forcing unnecessary detail.

 

Team or project name (if you have one) — An optional but useful field for teams that have already established an identity. It helps with internal referencing and can signal a level of team cohesion.

 

How many people in total are contributing to this idea, including yourself? — This gives reviewers a quick sense of team scale. It complements the detailed roster table that follows.

 

Team member roster and contributions — This table is one of the form's strongest structural elements. It captures each contributor's name, department, role, weekly hours, relevant skills, and prior pitch experience in a single, scannable format. The pre-populated example rows are helpful for guiding submitters on the expected level of detail. This structured approach supports fair comparison across submissions.

 

Which functions are already represented in your team? and Which functions would you still like to recruit into the team? — These two multiple-choice questions work well together. They give reviewers a clear picture of the team's current cross-functional coverage and its gaps. The conditional follow-ups for Other ensure that functions outside the standard list are captured.

 

Is there a named deputy or backup lead who can represent the idea if you are unavailable? — This question addresses continuity risk in a practical way. The branching follow-ups — asking for the deputy's details or the continuity plan — demonstrate thoughtful design that adapts to the respondent's situation.

 

How did the team come together, and how do you divide responsibilities and decisions? — This open-ended question provides qualitative context about team dynamics and governance. It helps reviewers assess whether the team has a clear working model, which can be an indicator of execution readiness.

 

Does any team member have a personal, financial, or family interest that could be seen as influencing this proposal? — This disclosure question is framed sensitively and constructively. The follow-up text explicitly states that disclosure is treated as a good-faith planning note and does not disqualify the idea, which encourages transparency without creating a punitive atmosphere.

 

Which pitch or showcase formats could your team attend? — This logistical question helps organisers plan session scheduling and format allocation. The multiple-choice format covers a good range of options including virtual and written-only formats.

 

Please rank the mentoring or support topics that would help your team the most — This ranking question is a smart addition. It helps organisers match teams with appropriate support resources and demonstrates that the competition is invested in the team's development, not just the idea's evaluation.

 

Section 2 — Market Problem and Proposed Solution

This section is the analytical core of the submission. It is well designed to elicit a clear problem statement, supporting evidence, a plain-language solution description, and an honest assessment of assumptions and risks.

 

In your own words, what problem or unmet need are you addressing? — This is the foundational question of the entire submission. Asking for the submitter's own words encourages authentic, specific descriptions rather than generic statements. The placeholder example is concrete and illustrative.

 

Who primarily experiences this problem? — Identifying the affected group helps reviewers assess the scope and relevance of the problem. The conditional follow-up for multiple affected groups is a well-designed branching mechanism.

 

What evidence supports your view of the problem? — This multiple-choice question with a comprehensive list of evidence types encourages submitters to ground their claims in observable data or experience. The mandatory status ensures that every submission includes at least some basis for the problem assertion.

 

Please summarise the strongest piece of evidence you have — This follow-up pushes submitters to go beyond listing evidence types and actually present their strongest data point. The placeholder example demonstrates the expected level of specificity.

 

How severe is the problem for the people who experience it, in your assessment? — The 10-point rating scale allows for nuanced self-assessment. Framing it as the submitter's assessment is appropriately humble and avoids overclaiming.

 

How often does the problem occur? — Frequency context helps reviewers understand whether the problem is chronic and pervasive or rare but high-impact. The option Not yet clear — needs further research is an honest and useful inclusion.

 

What happens today when people try to solve this problem? What workarounds do they use? — Understanding the current state and existing workarounds is essential for evaluating whether the proposed solution offers genuine improvement. This question is well placed after the problem description.

 

Describe your proposed solution in plain language — Asking for plain language is an excellent design choice. It ensures that the solution can be understood by reviewers from diverse functional backgrounds and tests whether the submitter truly understands their own concept.

 

What type of offering is this? — This classification question helps reviewers categorise and compare ideas. The comprehensive list of offering types covers a wide range of possibilities, and the conditional follow-up for combinations captures hybrid models.

 

How new is this idea relative to what the organisation already offers? — This question helps reviewers assess the degree of novelty and potential disruption. The options range from entirely new to repackaging existing offers, providing useful spectrum coverage.

 

How would you rate the level of innovation in this proposal? — The descriptive rating scale is well designed, moving from incremental improvement to transformative. This self-assessment helps frame expectations and can prompt more ambitious thinking.

 

What stage is the idea at today? — Understanding the current maturity level helps reviewers calibrate their expectations and feedback. The conditional follow-up for early results captures valuable pilot data.

 

Does the idea build on prior work, a previous project, or something already documented inside the organisation? — This question helps avoid duplication and encourages leveraging existing institutional knowledge. The follow-up asking for the location of prior work is practical and helpful.

 

What are the three most important assumptions behind this idea that still need to be tested? — This is one of the most valuable questions in the form. It encourages critical thinking and intellectual honesty. The numbered placeholder example sets a clear expectation for structured responses.

 

What are the main risks you can foresee? — The comprehensive risk categories cover demand, technology, cost, delivery, data, internal dynamics, dependencies, reputation, and timing. This encourages thorough risk identification.

 

For the top two risks you selected, how would you reduce or manage them? — This follow-up pushes beyond identification to mitigation planning. It helps reviewers assess the team's problem-solving maturity.

 

Is there anything about this idea that could affect how customers experience our existing products or services? — This question demonstrates awareness of cross-portfolio impact and helps reviewers identify potential cannibalisation or enhancement effects.

 

In one or two sentences, why should this idea matter to the organisation right now? — This closing question for the section is powerful. It forces the submitter to distil their value proposition to its essence, which is exactly what reviewers need for initial screening.

 

Section 3 — Target Customer and Internal Synergy Analysis

This section effectively bridges external market opportunity and internal organisational fit. It is well structured to capture customer definition, commercial expectations, competitive context, and synergy with existing capabilities.

 

Who is the primary target customer for this business line? — This classification question helps reviewers quickly understand the market orientation of the idea. The comprehensive options cover internal and external audiences, and the conditional follow-up for mixed audiences captures nuance.

 

Describe your ideal customer or user in practical terms — Asking for practical, day-in-the-life descriptions encourages vivid and specific customer understanding rather than abstract demographic labels. The placeholder example is excellent in demonstrating this.

 

Roughly how many potential customers or users could this idea reach in its first year? — This optional numeric field gives reviewers a sense of scale. Its optional status is appropriate since early-stage ideas may not have reliable estimates.

 

How did you estimate that number? — This follow-up question is a strong design choice. It helps reviewers assess the reliability of the estimate by understanding its basis. The range of estimation methods is comprehensive.

 

Do you have evidence that the target customer would be willing to pay for this? — The branching follow-ups are well designed — asking for evidence if yes, or the testing plan if no. This captures both validation status and forward-looking thinking.

 

What pricing approach are you considering? — This question helps reviewers understand the commercial model. The options cover a wide range of pricing structures, and the conditional follow-up for undecided pricing captures the deliberation process.

 

What is the approximate price point you have in mind per customer or per unit? — This optional currency field provides concrete commercial context when available.

 

How would customers most likely discover and buy this offering? — Understanding the go-to-market channel helps reviewers assess commercial feasibility and alignment with existing distribution capabilities.

 

Competitive and alternative landscape — This table is a well-designed element. It captures competitors, their strengths, their weaknesses, and how the proposed idea differs. The pre-populated example rows demonstrate the expected depth of analysis and are highly illustrative.

 

What would make a customer switch from their current approach to yours? — This question probes the value proposition from the customer's perspective. It is a critical question for assessing market viability and is appropriately mandatory.

 

Which existing organisational assets or strengths would this idea rely on? — This multiple-choice question helps reviewers assess how well the idea leverages existing capabilities. The comprehensive list covers brand, relationships, networks, data, technology, operations, suppliers, expertise, and intellectual property.

 

Please rate how strongly you agree with each statement about internal synergy — This matrix rating question is an excellent structured assessment tool. The six sub-statements cover capability reuse, customer relationship depth, cost reduction, strategic fit, operational impact, and platform potential. The Not enough information yet scale option is a thoughtful inclusion.

 

Could this idea take revenue or attention away from an existing offering? — This candid question addresses potential cannibalisation directly. The branching follow-ups are constructive and solution-oriented.

 

How well does this idea fit with the organisation's stated priorities? — This question helps reviewers assess strategic alignment. The option for conflicts with a current priority is a brave and useful inclusion that encourages honest assessment.

 

When could a first version realistically reach customers? — This timeline question helps reviewers assess urgency and feasibility. The option Depends entirely on resources approved is realistic and honest.

 

Illustrative revenue outlook (your own estimates) — This table with a built-in formula for projected revenue is a practical and efficient design element. The pre-populated example rows demonstrate expected structure and help submitters think in terms of units, price, and revenue.

 

Please explain the key drivers behind these projections — This follow-up adds necessary context to the numerical estimates and helps reviewers understand the assumptions underlying the projections.

 

How would you measure success in the first year? — This multiple-choice question covers a balanced range of success metrics including customers, revenue, satisfaction, cost savings, retention, adoption, market position, and learning. It helps reviewers understand what the team values.

 

What would a realistic first-year success target look like? — This follow-up pushes for specificity and helps calibrate expectations.

 

Section 4 — Resource and Prototype Budget Needs

This section is practical and detailed, designed to capture what the team needs to take the idea to the next step. It covers funding, budget breakdown, people and time, facilities, prototype description, dependencies, and timeline.

 

Currency used for all figures in this section — This mandatory field is a smart administrative choice. It ensures that all financial figures in the section are interpreted correctly, which is especially important for organisations operating across multiple regions.

 

Total funding or budget you are requesting for the next stage — This headline figure gives reviewers a quick sense of the resource ask. Its mandatory status ensures every submission includes a clear financial request.

 

What is the smallest budget that would still let you test the core idea? — This optional question is excellent for understanding the team's flexibility and prioritisation. It can reveal whether the team has thought about a minimum viable test.

 

Budget breakdown by category — This table is well structured with columns for cost category, description, one-off or recurring classification, estimated amount, and supplier identification status. The pre-populated example rows demonstrate the expected level of detail.

 

Where would the funding come from? — Understanding the funding source helps reviewers assess feasibility and potential conflicts with existing budgets.

 

Has any part of this budget been discussed with a budget holder already? — The branching follow-ups are constructive — asking about the response if discussed, or the plan if not. This helps reviewers understand the level of financial groundwork already done.

 

People and time needed — This table captures the human resource requirements with role, source, time percentage, duration, and availability status. It complements the team roster in Section 1 by focusing on additional needs.

 

What facilities, equipment or technology would the prototype need? — This multiple-choice question covers a comprehensive range of physical and digital resources. The option for None is a useful inclusion for software-only ideas.

 

Describe the prototype or pilot you would build with these resources — This mandatory open-ended question is essential for understanding what the investment would produce. The placeholder example is concrete and helpful.

 

What is the main question the prototype or pilot should answer? — This question focuses the prototype on a clear learning objective. The options cover problem validation, usage, willingness to pay, cost feasibility, and system compatibility. The conditional follow-up for multiple questions asks for prioritisation.

 

What data or technology would the idea depend on? — Understanding dependencies helps reviewers assess technical feasibility and potential integration challenges.

 

Would the idea involve handling information about identifiable individuals? — This question demonstrates awareness of data handling considerations. The follow-up text helpfully notes that the review panel can assist in identifying which internal teams to consult, which is supportive rather than punitive.

 

Would you need external suppliers, vendors or partners to deliver the prototype? — This question captures external dependencies and potential procurement needs.

 

Which internal reviews or approvals might be relevant before this idea could be piloted? — This multiple-choice question encourages submitters to think about governance and compliance considerations. The Not sure option is a helpful inclusion that invites guidance rather than blocking progress.

 

Indicative timeline and milestones — This table captures milestones with target dates, owners, and completion criteria. The pre-populated example rows demonstrate the expected structure and level of detail.

 

How confident are you that the timeline above is realistic? — This self-assessment question adds a layer of honesty to the timeline and helps reviewers calibrate their expectations.

 

If the approved budget were around 30% lower than requested, could the idea still be tested in a meaningful way? — This question is a practical stress test that reveals the team's flexibility and prioritisation. The branching follow-ups capture either the reduced version or the essential elements.

 

What would make you stop or significantly change this idea after the prototype or pilot? — This optional question encourages pre-commitment to decision criteria, which is a sign of mature project thinking.

 

Section 5 — Executive Sponsor Endorsement

This section captures the endorsement and support of a senior leader, adding credibility and practical backing to the submission. It is well designed to record the sponsor's identity, relationship, support level, and formal confirmation.

 

Executive sponsor full name, Sponsor job title, Sponsor department or business unit, and Sponsor work email address — These identity fields establish who is endorsing the submission and provide clear contact information for the review panel.

 

What is the sponsor's relationship to the team lead? — Understanding the relationship helps reviewers assess the nature and depth of the sponsorship. The options cover direct management, functional leadership, related area leadership, programme sponsorship, mentoring, and peer relationships.

 

Has the sponsor been involved in shaping the idea so far? — The branching follow-ups capture either the nature of prior involvement or the plan for briefing the sponsor. This helps reviewers understand the level of sponsor engagement.

 

In the sponsor's words, why does this idea matter to the business? — This mandatory question captures the sponsor's perspective in their own voice, which adds a valuable external validation dimension to the submission.

 

How strongly does the sponsor support progressing this idea to the next stage? — The 5-point rating scale provides a clear measure of sponsor enthusiasm, which can be an important signal for reviewers.

 

What support can the sponsor realistically offer? — This multiple-choice question covers a comprehensive range of support types including funding, people, data, customer access, coaching, introductions, visibility, and obstacle removal. The option for Nothing beyond endorsement is an honest inclusion.

 

Does the sponsor have budget authority that could cover part of the request in Section 4? — This question links the sponsorship section back to the budget section, creating a coherent narrative across the form. The branching follow-ups are practical and constructive.

 

Would the sponsor attend the pitch session or showcase event? — This logistical question helps organisers plan events. The branching follow-ups capture the sponsor's participation role or alternative representation.

 

Sponsor comments, conditions or reservations about the proposal — This optional field gives the sponsor space to add nuance, conditions, or caveats to their endorsement, which promotes honest and balanced communication.

 

The sponsor confirms that they have reviewed this submission — This checkbox confirmation is a clear and appropriate way to record the sponsor's attestation. The text explicitly notes that this is an internal review note rather than an approval or funding commitment, which sets correct expectations.

 

Sponsor signature and Date of sponsor endorsement — These formal elements complete the endorsement record and provide a clear audit trail for the submission.

 

Supporting Materials, Declaration and Next Steps

This closing section is well designed to capture optional supporting materials, formal declarations, communication preferences, and form feedback.

 

Pitch deck or slide summary, One-page idea summary or executive brief, Sketch, mock-up, diagram or photo, and Supporting research, data extracts or customer feedback summary — These optional upload fields give submitters flexibility in how they present their idea. The guidance to keep attachments brief and avoid sensitive information is practical and helpful.

 

Link to any additional materials, if hosted internally — This optional field accommodates submitters who have materials stored in internal systems.

 

I confirm that the information in this submission is a good-faith description — This mandatory declaration checkbox sets clear expectations about the nature of the submission and the review process. The language is appropriately balanced.

 

I confirm that the team members listed are aware of this submission — This optional checkbox promotes team awareness and consent without being overly burdensome.

 

Team lead signature and Date signed — These formal elements complete the submission record.

 

How would you prefer to receive updates about your submission? — This multiple-choice question respects the submitter's communication preferences and helps organisers plan their outreach.

 

Would you like to be matched with a mentor or review buddy before the pitch session? — This question demonstrates that the competition invests in submitter development. The conditional follow-up for mentoring areas is a thoughtful addition.

 

Is there anything else the review panel should know before reading this submission? — This catch-all question gives submitters space to add context that does not fit elsewhere, which can prevent important information from being lost.

 

How clear and easy to complete was this submission form? and Any suggestions for improving this form for future rounds? — These feedback questions show a commitment to continuous improvement and help organisers refine the form over time.

 

Overall Strengths and Areas for Consideration

This form demonstrates several notable strengths. Its five-section structure mirrors the natural flow of a business case — from team and problem to solution, market, resources, and sponsorship — making it intuitive for submitters and efficient for reviewers. The extensive use of conditional follow-up logic keeps the form concise for straightforward cases while capturing nuance when needed. Pre-populated example rows in tables provide clear guidance on expected detail levels. The form's tone is encouraging and transparent, explicitly stating that estimates are acceptable and that the submission does not create commitments. The inclusion of mentoring requests, form feedback, and communication preferences shows a user-centred approach that goes beyond mere data collection.

 

From a user experience perspective, the form is comprehensive and will require significant time to complete — likely 45 to 90 minutes for a thorough submission. This is appropriate given the depth of information requested for a competitive evaluation, but organisers should be aware that the length may deter some potential submitters. The clear section headings, introductory paragraphs, and placeholder examples help mitigate this by guiding users through the process. The form could benefit from a progress indicator or estimated completion time at the outset to help submitters plan their effort. Additionally, while the form collects sensitive information such as employee identifiers and conflict-of-interest disclosures, the framing is constructive and the follow-up text reassures submitters that disclosure is treated in good faith. Organisers should ensure that the handling and access controls for submitted data are clearly communicated to submitters.

 

Mandatory Question Analysis for New Business Line Idea Submission Form for Internal Pitch Competition

Important Note:

This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.

Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.

Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.

 

Mandatory Question Analysis

Working title of your business line idea
Requiring this field ensures every submission has a clear, concise identifier that reviewers can use to track and reference the idea throughout the evaluation process. A working title also helps the submitter frame their concept from the outset. The necessity of this field is well established given the form's purpose as a competitive submission tool where ideas must be easily distinguishable.

 

Date of submission
Requiring the submission date supports chronological record-keeping and helps organisers manage round deadlines and review sequencing. This is a standard administrative requirement for any process involving time-bound submissions and is appropriate to make mandatory.

 

Which competition round are you submitting to?
Requiring this routing question ensures submissions are directed to the appropriate review track, which is essential for fair and efficient evaluation. Without this information, organisers would need to manually determine the correct track, potentially causing delays or misrouting. The inclusion of a Not sure option with follow-up text ensures that uncertainty does not block submission.

 

Team lead full name
Requiring the team lead's full name establishes clear accountability for the submission and provides the review panel with a primary point of contact. This is fundamental to any process where individual submissions are reviewed and discussed.

 

Employee or staff identifier
Requiring an employee or staff identifier supports internal record-keeping and helps avoid ambiguity when multiple employees share similar names. This is particularly useful in large organisations where name-based matching alone may be insufficient.

 

Current job title
Requiring the team lead's job title provides reviewers with organisational context about the submitter's role and seniority, which can inform their assessment of the team's capacity and perspective. This contextual information is valuable for comparative evaluation across submissions.

 

Primary department or function
Requiring the team lead's department or function helps reviewers understand the organisational origin of the idea and assess cross-functional relevance. This information supports routing, contextual evaluation, and potential follow-up with the relevant department.

 

Work email address
Requiring a work email address ensures the review panel has a reliable communication channel for follow-up questions, scheduling, and notifications. Given that this is an internal process, a work email is the most appropriate and expected contact method.

 

Approximately what percentage of your working time can you commit to this idea per month?
Requiring this field helps reviewers assess the realistic capacity of the team lead to drive the idea forward alongside existing responsibilities. This is an important practical consideration for evaluating execution feasibility. The necessity depends on the form creator's emphasis on realistic resource planning, but given the competitive evaluation context, it is a reasonable requirement.

 

How many people in total are contributing to this idea, including yourself?
Requiring the total contributor count gives reviewers a quick sense of team scale, which complements the detailed roster table. This summary figure helps with initial screening and comparison across submissions.

 

Which functions are already represented in your team?
Requiring this field ensures reviewers can assess the cross-functional coverage of the team, which is a stated emphasis of the form's design. Understanding which functions are represented helps evaluate the team's breadth of perspective and capability.

 

Which pitch or showcase formats could your team attend?
Requiring this logistical information helps organisers plan session scheduling and format allocation efficiently. Without this data, organisers would face significant coordination challenges when arranging pitch events.

 

In your own words, what problem or unmet need are you addressing?
Requiring this foundational question ensures every submission includes a clear problem statement, which is essential for any comparative evaluation of business ideas. Without a defined problem, reviewers cannot assess the relevance or urgency of the proposed solution.

 

Who primarily experiences this problem?
Requiring this question helps reviewers assess the scope and relevance of the problem by identifying the affected group. This is a core element of problem definition and is appropriate to require for fair evaluation.

 

What evidence supports your view of the problem?
Requiring at least one evidence source ensures that submissions are grounded in observable data or experience rather than unsubstantiated claims. This supports data quality and helps reviewers distinguish between well-researched and speculative proposals.

 

What happens today when people try to solve this problem? What workarounds do they use?
Requiring this question ensures reviewers understand the current state and existing alternatives, which is essential for evaluating whether the proposed solution offers genuine improvement. This context is fundamental to solution assessment.

 

Describe your proposed solution in plain language
Requiring a plain-language solution description ensures every submission includes a clear and accessible explanation of the proposed offering. This is essential for reviewers from diverse functional backgrounds to understand and compare ideas effectively.

 

What type of offering is this?
Requiring this classification helps reviewers categorise and compare ideas efficiently. Understanding the offering type is a basic but essential element of any business idea evaluation.

 

What are the three most important assumptions behind this idea that still need to be tested?
Requiring this question encourages critical thinking and intellectual honesty from submitters. Identifying key assumptions is a fundamental element of responsible idea development and helps reviewers assess the team's analytical maturity. This is well justified as a mandatory field given the form's emphasis on candid, well-considered submissions.

 

In one or two sentences, why should this idea matter to the organisation right now?
Requiring this concise value proposition statement ensures every submission includes a clear articulation of organisational relevance and urgency. This is particularly useful for initial screening and helps reviewers quickly assess strategic fit.

 

Who is the primary target customer for this business line?
Requiring this question ensures reviewers can quickly understand the market orientation of the idea. Target customer definition is a core element of any business case and is appropriate to require for comparative evaluation.

 

Describe your ideal customer or user in practical terms
Requiring a practical customer description ensures submissions include vivid and specific customer understanding rather than abstract labels. This depth of customer insight is essential for assessing market viability and is well justified as mandatory.

 

What would make a customer switch from their current approach to yours?
Requiring this question ensures submissions address the value proposition from the customer's perspective, which is critical for assessing market viability. Understanding the switching motivation helps reviewers evaluate competitive advantage.

 

Which existing organisational assets or strengths would this idea rely on?
Requiring this question helps reviewers assess how well the idea leverages existing capabilities, which is a stated focus of the form's design. Understanding internal synergy is important for evaluating feasibility and strategic fit.

 

Currency used for all figures in this section
Requiring the currency designation ensures that all financial figures in the resource section are interpreted correctly. This is a practical administrative requirement that prevents misinterpretation of budget data, particularly in organisations operating across multiple regions.

 

Total funding or budget you are requesting for the next stage
Requiring the headline funding figure ensures every submission includes a clear financial request, which is essential for resource planning and comparative evaluation. Without this figure, reviewers cannot assess the scale of investment required.

 

Describe the prototype or pilot you would build with these resources
Requiring this description ensures reviewers understand what the requested resources would produce. A clear prototype or pilot description is essential for evaluating whether the proposed investment is proportionate and well-targeted.

 

What is the main question the prototype or pilot should answer?
Requiring this question ensures the prototype has a clear learning objective, which helps reviewers assess whether the proposed test is well-designed and focused. This is an important element of responsible resource allocation.

 

Executive sponsor full name
Requiring the sponsor's full name establishes who is endorsing the submission and provides the review panel with a clear point of contact for sponsorship-related follow-up. This is fundamental to the endorsement process.

 

Sponsor job title
Requiring the sponsor's job title helps reviewers assess the level and nature of the endorsement, which adds credibility and context to the submission. Seniority of sponsorship can be an important signal for reviewers.

 

Sponsor department or business unit
Requiring the sponsor's department helps reviewers understand the organisational context of the endorsement and assess whether the sponsor has relevant domain knowledge or authority.

 

Sponsor work email address
Requiring the sponsor's work email ensures the review panel can contact the sponsor directly if clarification or confirmation is needed. This supports the integrity of the endorsement process.

 

What is the sponsor's relationship to the team lead?
Requiring this question helps reviewers assess the nature and depth of the sponsorship relationship, which informs their understanding of the endorsement's basis and reliability.

 

In the sponsor's words, why does this idea matter to the business?
Requiring the sponsor's perspective in their own words adds a valuable external validation dimension to the submission. This helps reviewers understand the strategic rationale from a senior leader's viewpoint and is well justified as mandatory.

 

The sponsor confirms that they have reviewed this submission
Requiring this confirmation checkbox ensures the sponsor has formally attested to reviewing the submission and that the statements attributed to them reflect their own view. This supports the integrity and accountability of the endorsement process. The text appropriately notes that this is an internal review note rather than an approval or funding commitment.

 

Sponsor signature
Requiring the sponsor's signature provides a formal record of endorsement and supports accountability. This is a standard element of any process involving formal sponsorship or approval.

 

Date of sponsor endorsement
Requiring the endorsement date supports chronological record-keeping and helps organisers track when sponsorships were confirmed relative to submission deadlines.

 

I confirm that the information in this submission is a good-faith description
Requiring this declaration checkbox sets clear expectations about the nature of the submission and the review process. It encourages honest, good-faith responses and helps manage expectations about the review panel's role. This is a reasonable and proportionate requirement for an internal submission process.

 

Team lead signature
Requiring the team lead's signature provides a formal record of submission and supports accountability for the content provided. This is a standard element of formal submission processes.

 

Date signed
Requiring the signing date supports chronological record-keeping and provides a clear audit trail for the submission.

 

Overall Mandatory Field Strategy

This form contains a substantial number of mandatory fields — approximately 40 across all sections. While each individual requirement is well justified given the form's purpose as a competitive evaluation tool, the cumulative effect of so many required fields may create significant completion friction, particularly for submitters who are balancing this task with their regular work responsibilities.

 

Balancing data collection depth against completion rates: The form's mandatory fields are concentrated in areas that are genuinely essential for fair evaluation — team identity, problem definition, solution description, customer understanding, budget basics, and sponsor endorsement. However, some fields that are currently mandatory could potentially be made optional without significantly compromising data quality. For example, Current job title and Primary department or function could be combined into a single field, and How many people in total are contributing to this idea could be derived from the team roster table rather than collected separately. Reviewing the mandatory list for consolidation opportunities could reduce the perceived burden without losing critical information.

 

Conditional logic for detailed information: The form already makes excellent use of conditional follow-up logic, which is a strong design choice. Consider extending this approach to some mandatory fields — for example, if a team has only one member, the team roster table and the total contributor count could be simplified or auto-populated. Similarly, if the idea is at an early stage, some of the more detailed commercial questions in Section 3 could be presented as optional with a note that more detail will be expected in later rounds.

 

Best practices for mandatory field selection and placement: The form generally follows good practice by placing mandatory identity fields early, mandatory analytical fields in the core sections, and mandatory formal elements (signatures, declarations) at the end. This structure helps submitters understand what is required at each stage. One area for consideration is the density of mandatory fields in Section 2 (Market Problem and Proposed Solution), which contains approximately 8 required fields. This is the most cognitively demanding section, and the high mandatory count may add pressure at the point where submitters need the most creative thinking space. Consider whether one or two of these fields — such as What happens today when people try to solve this problem? — could be made optional for early-stage submissions with the expectation that they will be completed in later rounds.

 

Overall observations on mandatory field volume and placement: The distribution of mandatory fields across sections is broadly balanced, with the heaviest concentration in Sections 1 and 2, which is appropriate given their importance to the evaluation. Section 5 (Executive Sponsor Endorsement) has a high proportion of mandatory fields, which is justified given the formal nature of the endorsement. However, organisers should monitor completion rates and feedback to determine whether the current mandatory set is proportionate. The form's own feedback questions at the end — asking about clarity and suggestions for improvement — provide an excellent mechanism for gathering this data and iterating on the mandatory field strategy over successive competition rounds.

 

To configure an element, select it on the form.

To add a new question or element, click the Question & Element button in the vertical toolbar on the left.