Every job, done the expert way.
A playbook is the set of steps an expert takes for a job. Selixa follows it every time.
01
You ask.
In chat, like you’d ask a teammate.
02
It picks the playbook.
The one that fits the job, or your team’s own.
03
It runs the steps.
You see each one, with sources.
04
You approve.
Nothing changes in your tools until you do.
Playbooks
Proven playbooks from people who do the job.
Product, engineering, growth, SEO.
Product
Engineering
Security
SEO
Growth
Request
“why did trial-to-paid drop?”“why did trial-to-paid drop?”
Sara, in #growth
- Pull the funnelPostHog
- Find when it changedAnalysis
- Check what shippedGitHub
- Read the team’s threadsSlack
- Write it upWriting
Result
Trial-to-paid fell after the card step moved to day one of the trial.
- 14% → 9%trial to paid, last 30 days
- Oct 2the day it changed
- Recommendation
- Ask for the card at the end of the trial again, and test it on half of new trials.
Need something else? It does that too, across 1,600+ apps. See every playbook, or save your own
The library
Every playbook.
Each one carries the name of the person who wrote it. The first are Aamir’s. Experts we interview add theirs next.
Product
Investigate a metric
A number moved and nobody knows why.
- 1.Pull the funnel
- 2.Find when it changed
- 3.Check what shipped
- 4.Read the team’s threads
- 5.Write it up
You get the cause, the numbers, and what to do next, with sources.
By Aamir · Founder, Selixa
Competitor brief
Someone launched something and you need to know what it means.
- 1.Read our positioning
- 2.Scan their site and changelog
- 3.Compare pricing
- 4.Write the brief
You get a cited brief with three things to do.
By Aamir · Founder, Selixa
PRD from a thread
The team decided something in chat and it needs writing down.
- 1.Read the thread
- 2.Pull the related numbers
- 3.Draft problem, scope, success metric
- 4.List open questions
You get a PRD draft, saved to the library.
By Aamir · Founder, Selixa
Decisions into issues
A meeting or thread ended with decisions and owners.
- 1.Pick out the decisions
- 2.Draft one issue each, with an owner
- 3.Ask first
You get issues in your tracker, after you approve.
By Aamir · Founder, Selixa
Engineering
Ship a small fix
A typo, a label, a small bug nobody has time for.
- 1.Find it in a safe copy of the repo
- 2.Make the change
- 3.Ask first
You get a draft pull request, opened only once you approve.
By Aamir · Founder, Selixa
Run the standup
Every morning, without the meeting.
- 1.Post the plan
- 2.Send each person their row
- 3.Check in at 6 pm
- 4.Route blockers
You get a plan, check-ins, blockers sent to the right person, and the tracker up to date.
By Aamir · Founder, Selixa
Security
Security review of a change
A pull request touches login, payments or customer data.
- 1.Read the change and what it touches
- 2.Check auth, secrets and input handling
- 3.List risks by severity, with the fix
- 4.Ask first, then comment on the PR
You get a clear risk list on the pull request, posted once you approve.
By Aamir · Founder, Selixa
Triage dependency alerts
Security alerts are piling up and nobody knows which ones matter.
- 1.Pull the open alerts
- 2.Check which ones actually reach your code
- 3.Rank them by real risk
- 4.Draft issues with owners, ask first
You get the few alerts that matter, as issues with owners, after you approve.
By Aamir · Founder, Selixa
AWS security review
Your cloud grew fast and nobody has checked what’s exposed.
- 1.Read your infrastructure code and config
- 2.Check public buckets, open ports and IAM roles
- 3.Rank what’s exposed by real risk
- 4.Draft fixes with owners, ask first
You get a ranked list of what’s exposed in AWS and how to close it, after you approve.
By Aamir · Founder, Selixa
SEO
Page audit
A page should rank and doesn’t.
- 1.Pull search data for the page
- 2.Check titles, headings and speed
- 3.Compare with the pages that rank above it
- 4.List fixes by impact
You get fixes in order of impact, ready to turn into issues.
By Aamir · Founder, Selixa
Growth
Launch plan
Something is shipping and people need to hear about it.
- 1.Read the PRD
- 2.Pick channels
- 3.Draft the announcement, email and in-app copy
- 4.Set dates and owners
You get a launch plan with copy, dates and owners.
By Aamir · Founder, Selixa
Your playbooks
Set your process once. It follows it every time.
Say it once in chat. Your whole team works your way.
- Your documents, read first
- A model for each step
- Keep the better result, it remembers
When someone asks for
a competitor brief
Read first
Positioning v3Steps
- 1Read our positioning docAuto
- 2Check their pricing pageAuto
- 3Read their changelogAuto
- 4End with three things we should doCompare 2
Why it’s different
ChatGPT gives you advice. Selixa does the work.
ChatGPT or Claude
Selixa
Knows nothing about you
Knows your team, docs and decisions
Never hears your meetings
Sits in, and follows up after
Guesses the steps
Follows an expert’s playbook
Tells you what to do
Does it in your tools
Acts without asking, or not at all
Asks before every change
One chat, one person
Works for the whole team, product by product
Questions
The short answers.
Where do the playbooks come from?
The first ones come from Aamir, Selixa’s founder, written from the way Aamir does the work. Next come playbooks from experts we interview, each with their name on it. Your team can add its own.
What if no playbook fits?
It still does the job. For bigger work it shows the plan and the cost first.
Can I change a playbook?
Yes. Change the steps, the documents it reads first, or the model for each step. Every edit is a new version.
your next teammate knows the playbook.
Works with Slack, Linear, Notion and 1,600+ more apps