A Pitch is a proposal for work to be done on one of Disco's products. It could cover the development of a new feature, the resolution of a couple of bugs, the rollout of some new infrastructure, or an overhaul of the documentation site.

It's similar to a scope of work and estimate for a client project, with a couple of key differences:

1. The work described in a pitch should be realistically achievable by a single team within a six week product cycle.
2. While the goals and boundaries of a pitch are very clear, the implementation of the pitch is left open to the development team.

Pitches can be prepared by product managers, the technical director, developers, or anyone else with a stake in a product. They should be thoroughly researched, refined, and estimated prior to being presented for consideration in a Pitch Meeting.

Pitch Template

<aside> ⚠️ This template is copied to each individual product's Pitches section. Any updates here should also be added to the Pitch templates in those sections.

</aside>

Nutshell

A one-sentence summary of what this pitch is all about.

Problem

What the key problem this pitch is trying to solve? What's its impact, and who is going to benefit from its solution? What effect will it have on the various product stakeholders?

Appetite

How much effort are we prepared to spend on solving this problem?

Solution

What's a solution to the problem that aligns with our appetite for solving it? Depending on the pitch in question, this solution may be a high-level set of goalposts or a more detailed set of requirements.

Nice to Haves / Exclusions

To keep this solution manageable, what are we explicitly excluding from scope here? What rabbit-holes should we be conscious of avoiding? What follow-on pitches might be created that will build on the work of this pitch?

Estimate

Given the appetite, approach, and exclusions above, what's a reasonable point estimate for the solution?

Tasks