Go-to-market launch approvals in Jira

A go-to-market launch fails in the seams between teams: engineering is done but the sales deck is stale, PR has a date nobody told support about, legal saw v1 of the pricing page. The status lives in six tools and one overworked launch manager's head.

Greenlight turns the launch into a single board in Jira: one gate per team, each with an owner, a checklist, and a sign-off. The launch is ready when every required gate is green — and until then, everyone can see exactly what's missing and who's on the hook.

How Greenlight maps to a launch

• One gate per workstream. Product, marketing, PR, sales, legal, support — each team owns its gate and signs off when genuinely ready.
• Readiness is computed, not claimed. Checklist items, evidence links, and live-linked Jira issues drive each gate's progress automatically. No more "90% done" in a status meeting.
• The weekly digest does the chasing. Greenlight's hub (and its Rovo agent) summarizes what needs attention this week and groups the outstanding work by owner — your launch standup, pre-written.
• Slipped a week? Select the affected launches on the hub and shift all their target dates at once.
• At-risk flagging built in. A gate still unfinished as the target date closes in is flagged at-risk on the hub and in the daily sweep, so it surfaces before launch week, not during it.

Template pack: GTM launch

Start from the built-in Marketing Launch template, or recreate this fuller version via Administration → New global template:

Gate	Suggested owner	Checklist seeds	Required
Product readiness	Product manager	Feature complete behind flag · Success metrics defined · Rollout stages agreed	Yes
Marketing assets	Marketing lead	Announcement drafted · Landing page live · Campaign scheduled	Yes
PR & comms	PR lead	Press release approved · Briefings booked · Embargo date confirmed	Yes
Sales enablement	Sales lead	Deck updated · Pricing confirmed · Demo script rehearsed	Yes
Legal review	Legal counsel	Claims reviewed · Terms updated · Trademark cleared	Yes
Support enablement	Support lead	FAQ prepared · Macros updated · Team briefed	Yes
Localization	Localization lead	Strings translated · Regional pages reviewed	Optional

Leave Localization optional on the template and mark it required on the launches that actually ship in more than one language.

The launch-day question, answered

"Are we go for Tuesday?" becomes a link: the release page shows every gate, its owner, its evidence, and its sign-off state — plus a one-page readiness report if leadership wants the summary. After the launch, save the board as a template so the next one starts at 80%.