Industry packs

Industry packs set Gambit up for the way your industry sells, with the work types, fields, pipelines, views, dashboards, rules and AI prompts it needs, installed with a preview and removable later.

What a pack adds

A pack is ready-made configuration for one industry. Install it and Gambit adds, in one step:

• Work types and workflows, such as Quotes and SOWs for services firms.
• Fields your team already talks about, as native Jira fields you can search, filter and report on.
• Pipelines with the stages and win probabilities that fit the way you sell.
• Views and dashboards for the questions your managers ask every week.
• Metrics for Ask and Reports, defined once so a number such as net revenue retention is computed the same way everywhere.
• Health signals that tune each account's Health score to what matters in your industry.
• Rules that handle the routine work: filling in derived fields, reminding owners before dates slip and proposing next steps for a person to approve.
• AI prompts that make summaries, health reasons and drafts speak your industry's language.

Every pack also comes with an optional demo dataset of fictional companies and people, so you can try it before your own data arrives and remove the demo records whenever you are done with them.

Both packs, on every plan

The SaaS and Professional services packs each install whole on every Gambit edition, on the free tier and on Jira Free, with the same work types, fields, views and rules everywhere. Install either or both, in any order: a services firm that also sells software can run both side by side.

Free on Standard for sites of 1–10 users: the whole CRM, the SaaS and Professional services packs, and Ask for a report within a monthly AI allowance, without background capture, summaries or drafts.

Install with a preview

Members of rainbook-admins install packs from Settings › Packs, or during the setup wizard; creating the pack's Jira fields and workflows also needs a Jira admin.

1. Plan. Gambit reads your site and works out what each part of the pack will do: create something new, reuse a field or status you already have, or flag a conflict.
2. Preview. You see the exact Jira objects the pack will create or change, grouped and counted, with every reused item and every conflict named, and how many fields it adds to each space. Nothing is written yet.
3. Apply. Gambit writes the configuration from your browser in a safe order. If you close the tab or Jira gets busy, it picks up where it stopped, and running it again changes nothing.

Each pack adds at most 40 fields to a space, and the preview stops before any space goes past 400 fields or 40 work types, so there is always room for your own configuration.

Updates

When a pack improves, its pipelines, metrics, prompts and health model update on their own, unless you have customized them. A customized item keeps your version and shows Update available, with a diff and Use new version.

Changes to Jira configuration (new fields, options, statuses, work types, views or dashboards) always wait for an admin. Settings › Packs shows Upgrade with the release notes and the same preview. A field or status you edited in Jira is kept as you left it unless you choose Overwrite with pack version.

Remove a pack

Remove pack turns off the pack's rules, prompts, health signals, pipelines and metrics and hides its tabs in Gambit. Every field, work type and value stays in Jira, readable in JQL, filters and dashboards. Card and SSN masking keeps running.

If you want a tidy site afterwards, choose Remove unused pack configuration. Gambit removes only what the pack created and nobody has used: work types with no work items, fields with no values, and views and dashboards unchanged since install. Fields go to Jira's trash, where you can restore them. Gambit never deletes a work item, and never removes a field or status you already had.

If you uninstall Gambit, every pack field, work type, workflow, status, filter and dashboard stays in your Jira with all its values. Reinstall, and Gambit picks the pack back up instead of creating duplicates.

The pack catalogue