We’re building the best way for your whole organization to respond, review and learn from incidents. This is where we talk about how and why.
Reducing our pager load
What we did when we were getting paged too much
Lisa Karlin Curtis
Making Go errors play nice with Sentry
Getting Go errors to work well with Sentry is hard. This post explains how we got them playing nicely by deduping stacktraces.
Lawrence Jones
How to get everyone at the company to value writing
Once a month, the whole of our company downs tools, and spends the whole day writing. We call it Content Day!
Stephen Whitworth
How to build a strong incident response process
When building an incident response process, it’s easy to get overwhelmed by all the moving parts - but less is more. Here are three things to do that will set you up for success.
Lisa Karlin Curtis
4 principles for hiring our first 50 people
In this post, we'll talk about the principles we're using to hire our first 50 employees here at incident.io
Jack Villiers
What's a fair compensation for being on-call?
In this guide, we'll cover the various options for paying folks who are on-call, along with some advice, trade-offs and pitfalls to avoid.
Chris Evans
A B2B sales stack from Seed to Series A
A bullet-proof formula for an early-stage startup sales stack. In this article, we’ll take you through some tips on how to pick the right sales tools to take you from seed to series A.
Yann Sarfati
Rolling out Roles
Take a peek behind the scenes at how we built user roles into our product, and rolled them out to our existing users
Isaac Seymour
Finding a pricing model that’s just right
Getting your pricing right is critical to the success of any SaaS company, but finding a model that works can be tough.
Katie Hewitt
Stay in the loop: subscribe to our RSS feed.