Rootly GTM brain

category

market profile

• text: Engineering teams must coordinate paging, investigation, communication and retrospective work during service incidents.
• text: Rootly sells to startups through enterprise teams and targets replacement of established paging tools.

personas

• title: Head of SRE or platform engineering
  pains:

  • Slow detection and escalation prolong outages
  • Responders lack context across alerts, code changes and prior incidents
  • Manual retrospective work consumes engineering time
• title: On-call engineer or incident commander
  pains:

  • Alert noise and unclear ownership interrupt sleep
  • Coordinating responders and status updates competes with troubleshooting
• title: Security operations leader
  pains:

  • Cross-team incidents need repeatable coordination and documented follow-up

icp

• text: Technology companies operating customer-facing services with a dedicated or emerging on-call rotation, from startups to enterprises.
• text: Engineering and security organizations already coordinating work in Slack, Microsoft Teams or Google Chat.

message pillars

• text: Unify AI with on-call and incident response.
• text: Bring investigation context and suggested fixes into the workflow.
• text: Reduce switching friction with migration support.
• text: Make incident response calm and repeatable.

objections

• objection: Replacing the current paging platform is disruptive.
  response: Review migration scope and use the advertised migration and contract buyout options where eligible.
• objection: AI recommendations may be unreliable during a critical outage.
  response: Evaluate suggestions against historical incidents and require responders to verify the evidence and proposed fixes.
• objection: The cost grows with our on-call roster.
  response: Compare the published per-user product prices and request enterprise or bundle pricing for the actual roster.

competitors

• name: PagerDuty
  why: Established on-call and incident response platform explicitly targeted for replacement.
• name: incident.io
  why: Chat-native incident management and on-call alternative.
• name: FireHydrant
  why: Incident response and on-call platform.
• name: Opsgenie
  why: On-call alerting alternative mentioned in migration stories.

influencers

• name: JJ Tang
  url: https://ca.linkedin.com/in/jjrichardtang
  why: Co-founder and CEO who posts about incident management and sales.

keywords

• incident management software
• on call scheduling software
• PagerDuty alternative
• AI incident response
• Slack incident management
• SRE incident automation
• automated incident retrospective

voice

• Confident and direct
• Reliability-focused
• Empathetic to responders

signals

• text: A company is replacing PagerDuty or Opsgenie or faces an upcoming renewal.
• text: Rapid engineering growth makes informal incident coordination and rotations hard to manage.
• text: Platform leadership is measuring incident response times or standardizing retrospectives.

stack

• Slack
• Microsoft Teams
• Google Chat

pricing

motion

channels

• SEO
• LinkedIn
• Webinars
• Customer stories
• Partnerships

confidence

Founders

• name: Quentin Rousseau
  title: Founder and CTO (YC S21)
  role: CTO
  bio: - Early Site Reliability Engineer (SRE) at Instacart and built resilient systems now handling millions of orders. - 2x Co-Founder at Rootly (YC S21) and PopSQL (YC S19). - Originally from France, loves rock climbing, and unsurprisingly great wine!
• name: JJ Tang
  title: Founder
  role: Founder
  bio: Building Rootly - a modern on-call and incident management platform used by top YC companies like Dropbox, Lattice, Webflow, Faire, but also Figma, LinkedIn, and 100s more. Other than making Rootly my personality, I love cycling and my adorable dog, Nova.