A CRM inside Jira compared with a CRM beside it
Gambit is a CRM that runs inside Jira Cloud, built on Atlassian Forge. It needs no connector, because its deals, accounts and contacts are Jira work items. Records sit under the permissions your site already has. Your engineers see the customer on their own bugs.
Free on Jira sites of up to 10 users.
Priced on every user of your Jira site.
Jira admins set deal access with Jira's own permissions
Deals, accounts and contacts are Jira work items, so your Jira permissions and search apply to them as they stand. Each one has its Jira history. On Jira Standard and above, a rep can mark a deal private and pick the people who can open it.
On Jira Free, everyone on the site sees every record; private deals need Jira Standard or above.
Your engineers see which customers each bug affects
Open a P1 bug in Jira and the customer panel names each customer it affects. Each one shows its ARR, renewals due in 60 days and open deals. The panel shows on epics and other software work items too. Bugs and support requests created outside Gambit link to their account by the requester's email or organization.
On paid plans, a rep can log a customer's promise as a Jira work item, linked to the deal and to the epic that delivers it. When a deal is won, Start delivery sets up its delivery epic or space from a template, and you can undo it for 7 days.
Davis Hospitality is sample data.
Uninstall Gambit and your deals stay in Jira
Deals, accounts, contacts and email stay in Jira after you uninstall. They are Jira work items, and their files stay attached. Atlassian keeps Forge storage for at most 28 days after an app is uninstalled.
Gambit's own indexes and AI working state go when you uninstall, except what its nightly Gambit Archive item keeps.
Take these seven checks into each CRM vendor's demo
| Check | Gambit | Ask the vendor to show you |
|---|---|---|
| Where it runs | Deals are Jira work items. The core app's code, records and AI stay on Atlassian's Forge platform. | What a connector copies into Jira, and where the CRM's data and AI run. |
| Deal access | Your Jira permissions, plus private deals on Jira Standard and above. | A private deal, and the pipeline total for someone who can't open it. |
| Revenue on Jira work | The customer panel on P1 bugs, epics and other software work items. | A customer's ARR on a P1 bug, shown inside Jira. |
| Promises | On paid plans, track a customer's promise as a Jira work item linked to the deal and its epic. | A promise from a customer email, traced to its Jira epic. |
| Reports | Ask in plain words for a chart, then save it to a Jira dashboard. | A CRM chart on a Jira dashboard, opened by two people with different access. |
| Mail Sync, a separate app, connects to Google Workspace or Microsoft 365 with read-only access. | What the mail connection is allowed to change in a mailbox. | |
| Price | Free on Jira sites of up to 10 users. Priced on every user of your Jira site. Standard is $2.50 per user a month for 11 to 100 users. Mail Sync is billed separately, $0.25 per user a month at that size. | The price per user, and whether the connector costs extra. |
Capture needs a paid Gambit plan.
Microsoft 365 users connect their own mailbox wherever their IT allows it, or IT connects everyone; Google Workspace capture is connected by the IT admin; capture is labelled beta; personal Gmail opens after Google's review, with a waitlist.
For your Jira admin
Mail Sync requires an active Gambit subscription.
Gambit's AI is included in your subscription, with fair-use limits. Each person can run up to 25 Ask analyses a day, within a monthly fair-use limit for each person; questions that fit a report don't count. Summaries and other automatic AI draw on their own monthly pool. Your admins set how many analyses each person can run a day, and can give a person more. Reports, search and everything else keep working.
Questions and answers
Do we need a connector between Gambit and Jira?
No. Gambit runs inside your Jira Cloud site on Atlassian Forge, and deals, accounts and contacts are Jira work items. Jira search, permissions and dashboard gadgets work with them as they are. No records pass through a connector, so you have no sync to set up or keep running.
Is Gambit only for the sales team?
No. Reps work the pipeline. Your engineers see the customers, ARR and renewals behind each bug and software work item. Support requests land on the right account. Account managers see a 0 to 100 health score on each account. Sales managers ask for reports in plain words and save the charts to Jira dashboards.
Get on the Gambit mailing list
Gambit is on its way to the Atlassian Marketplace.