Once a project has been introduced into ShipGlows, keep its pitch current. If the fiche grows stale, the system ends up reasoning from an outdated version of the project.
The goal is not to rewrite the whole presentation every time. The goal is to keep a simple reference card that stays unambiguous about:
- what the project is
- who it is for
- what problem it solves
- what angle it takes
- where the source of truth lives
Why the refresh matters
Projects change quickly. A first pitch version can work at launch, but it becomes incomplete as soon as the product, audience, or positioning moves.
When you keep the pitch current, ShipGlows can:
- classify the project more accurately
- avoid reasoning from an outdated version
- recognize useful overlaps between projects
- propose better routes for sources, emails, or content ideas
What to update
A good project pitch fits into a few elements:
- project name
- reference URL
- audience
- business angle
- internal framing note
- status
That format is intentionally short. It carries enough information without bloating the fiche.
When to refresh
Refresh the pitch when:
- the audience changed
- the product promise changed
- the angle changed
- the file is a few months old
- ShipGlows still seems to reason from the older version
In that case, do not rewrite everything. Update the existing fiche.
The simple principle
A well-kept project corpus means:
- one pitch per project
- one current version
- one explicit source of truth
- one refresh when the project evolves
With that in place, ShipGlows does not need to guess. It can classify, compare, and route against a clean base.