10 Candles for Atlas CRM!

‍Celebrating the Numbers and the People

In 2015, inside Avisi (yes, our parent company), we were doing what many teams do when work grows faster than structure. Sales notes lived in emails. Deals in spreadsheets. Support history somewhere in Jira. Context everywhere except where decisions were made. It wasn’t dramatic, just the slow drip of small frictions that cost you a morning.

So we tried something simple. Put the customer inside our work. Not “integrate.” Not “sync.” Just live where the work already lives. That first build became Atlas CRM. We shipped it to solve our own pile of annoyances, then made it available to anyone else who was tired of the same pile. Turns out a lot of people were interested.

That’s the part we’re celebrating today. Ten candles on the cake. Here’s what makes it real.

Numbers that shaped the product

Today Atlas CRM runs in 2,000+ active installations with 65,000+ users. Together they’ve logged 13M+ customer and sales interactions. Not vanity, just a trail of who said what, why a deal stalled, and when to nudge instead of guess.

• 8M+ linked Jira issues tie work to revenue so priorities aren’t just vibes.
• 3.5M+ contact updates keep data clean and cut down on “who is this again” moments.
• 800k+ companies tracked so accounts have a memory.
• 120k+ comments keep conversations where the work happens.
• 15k wins and 12k losses recorded. We celebrate the first and learn from the second.
• 5.5k linked Confluence pages connect docs, decisions, and deals.

Every line is a skipped goose chase. One less “who owns this.” One fewer “forward me that email.” One more “we already have that.”

How a day looks when the customer lives inside the work

Other CRMs promise a single source of truth. Atlas CRM just puts the truth where you already are. Here’s what that looks like on a normal Tuesday.

• Sarah the sales manager opens Atlas CRM and sees the day in one glance: stages, stalls, two deals worth a call. She tags a teammate. No slack-hunting, just @mention and move on.
• Alicia the sales rep picks it up. Last night’s emails are already logged in the Interactions timeline from Gmail or Outlook. A support note pops up in the same view. One click links the people, the deal, and the Jira issue. Reminder set. Next step clear.
• Amit in customer success starts onboarding without “send me the doc” messages. The company and contact are there, linked to the right Confluence pages.
• Josh in support opens a JSM ticket and sees the useful kind of history: recent calls, open issues, deal value. No “can you forward me the thread.” He prioritizes correctly and writes a reply that makes sense on the first try.
• Charles in engineering doesn’t ship into a void. The Jira ticket shows which customer it’s for and what’s at stake. The fix matches reality, not a guess.
• Barry in product sees patterns, not anecdotes. Multiple Interactions pointing to the same friction land in planning without a game of telephone.
• Lina in marketing checks which campaign sourced qualified opportunities before lunch, not next week. Adjustments happen while the budget is still in the building.
• Janelle in leadership ends the day with a forecast that isn’t a surprise. The celebration is on time. So are the questions.

Fewer “did you see my email” ghosts in the afternoon.

Ten candles, ten milestones

• 2015 – Atlas CRM launched as the first-ever native CRM for Jira.
• 2016 – Confluence integration released; customer data now links across issues and pages.
• 2017 – Template builder introduced.
• 2018 – Translations and sales modules released.
• 2019 – Server & Data Center versions released.
• 2020 – Shipped Interactions for Server/DC, including files, comments, language packs, and API updates.
• 2021 – Sales pipelines became fully customizable, from 1 to 20 stages.
• 2022 – Dashboards, reminders, automations, and API released.
• 2023 – Interactions introduced as a core feature across companies, contacts, and sales.
• 2024 – Gmail and Outlook add-ins launched; Custom JQL and JSM tickets-to-Interactions released.
• 2025 – Collaboration update: @mentions, new commenting UI, Notification Center.
• 2025 – Resolved our 3,500th customer support ticket—always at our customers’ side.
• 2025 – Reached 2,000+ active installations and 65,000+ users.
• 2026 (upcoming) – Atlas CRM will be fully Forge-ready, future-proofed on Atlassian’s modern cloud app platform.

Numbers, and people

Numbers are one way to tell the story. Another is to look at who trusts Atlas CRM with their customer relationships.

Organizations like USDA, Save the Children, McKinsey & Company, Chapman University, Draper, Maritech, Wicked Fox, EDC, MCK Suppliers, and GTA all run their customer data inside Jira and Confluence with Atlas CRM. They could pick from a shelf full of CRMs, but they chose the one that doesn’t ask their teams to leave Atlassian behind.

Closer to home:

• Hankamp Rehab, tracking demo equipment and warranty renewals so nothing slips through the cracks.
• Ataraxis PEO, moving from reactive firefighting to proactive service by pulling all client context into JSM.

The logos prove the scale. The case studies prove the impact. And the numbers — 8 million linked Jira issues, 3.5 million contact updates, 120,000 comments — show the sheer volume of real work that now happens with customer context in view.

Behind each number is a team that wanted fewer blind spots and found them here.

Notes from inside the house

We are Avisi Apps, but Atlas CRM is not just an app. It is ten years of people showing up with their piece of the puzzle.

The developers who built and rebuilt until the code held. The product leads who kept asking what problem we were really solving. The business developers who carried the story into boardrooms and partner calls. The marketers who gave it a voice and made sure it was heard. The support team who turned tickets into trust.

Ten years in, Atlas CRM is the sum of those choices and those people. The names matter as much as the milestones, because without them, the candles on the cake would not be lit.

What’s next?

By 2026, Atlas CRM will light its next candle by going Forge-native. That means it will sit even closer to Jira and Confluence, with customer context showing up in the places people already work. The navigation will shift, the screens will look different, and yes, it might take a moment to get used to. But once it clicks, it will feel like the CRM was always part of the room.

We are also making Atlas CRM smarter in ways that actually save time. Teams should spend less time updating systems and more time focusing on their customers. In the coming years, Atlas CRM will help automate more of the background work and surface the insights that matter.

Sales teams will keep getting a stronger hub for their day. From relationships to follow-ups to tracking progress, the pieces will live together instead of apart.

And we’ll keep shipping the unglamorous things too. Better imports. Smarter defaults. The kind of details you only notice when they’re missing.

As the product evolves, we’re investing more than ever in design and customer feedback. The best ideas rarely come from a roadmap session. They come from a Tuesday when someone ran into a problem and told us about it.

The vision hasn’t changed in ten years. Keep the customer inside the work. Keep context close at hand. Keep improving in ways that matter.

A simple invitation

If you’re already on Atlassian, you don’t need another place to manage customers. You need the customer inside the place you already manage everything else. That’s been the idea since our first “please stop the copy-paste” moment at Avisi in 2015.

Ten years later, the idea still works. The numbers agree. The people do too.

Ten candles for Atlas CRM also mean ten candles as part of the Atlassian story. Without Jira, Confluence, and the Marketplace, Atlas CRM wouldn’t exist. So while we’re celebrating, we’re also raising a glass to Atlassian for building the ecosystem that made this decade possible.

Blow out the candles, keep the flame. Here’s to the next ten!