Atlassian: How to Influence Buying Criteria Before the Demo
- Mayur Kairamkonda
- Mar 3
- 1 min read

Most companies wait for a demo request before trying to influence the buyer.
Atlassian does the opposite.
Instead of starting with “Book a demo,” Atlassian publishes structured workshop formats inside its Team Playbook. These include:
How to run a project pre-mortem
How to prioritise initiatives
How to conduct a retrospective
How to align on goals
These are not promotional PDFs. They are ready-to-run facilitation guides.
Here’s what this does practically:
When a team runs an Atlassian play internally, they start using Atlassian’s language — alignment, visibility, backlog clarity, sprint cadence. That language shapes how they evaluate tools later.
By the time they shortlist vendors, they’re no longer asking:“Which software is cheaper?”
They’re asking:“Which platform supports the way we want to work?”
That shift is education-led prospecting.
Atlassian influences decision criteria before procurement starts.
What SMEs Can Copy
You don’t need global scale to do this.
If you’re a:
Cybersecurity firm → publish a “Board-Level Cyber Risk Workshop Template”
Cloud consultancy → publish a “Cloud Readiness Internal Assessment”
HR advisory → publish a “Quarterly Performance Calibration Agenda”
Make it structured. Make it usable. Remove fluff.
When buyers use your framework internally, you stop being a vendor — you become the reference point.
That reduces price comparison pressure dramatically.

Comments