We are excited to share our interview with Spike.sh, a simple incident alerting platform built for growing teams. Spike.sh integrates with your monitoring tools and sends alerts on phone call, SMS, Slack and MS Teams, and allows you to create flexible on-call schedules with ease. Read on to hear from Pru about his experience growing and developing Spike.
Hi Pruthvi, please feel free to introduce yourself and tell us more about Spike.
I'm Pru, the co-founder of Spike.sh, which is an incident management and automation platform. Spike.sh integrates with your software stack and alerts you on phone call, SMS, Slack and more when there are any issues.
What makes Spike different from its competitors?
Spike.sh is unique in the category for three things - ease of use, developer first approach and automation.
We've made Spike.sh to be fast to set-up and easy to use so that dev teams can focus on making great software. For example, we're the only incident management platform with templates for escalations, on-call and alert rules.
We are taking a developer first approach with Spike.sh so software engineers, devops and SRE team members can highlight the work they do to solve issues on Spike.sh.
And finally, we want to free dev teams from the busywork of solving the same incidents over and over. We're building a powerful incident automation platform so that developers can build and share automations to resolve common incidents.
What has been your approach to evaluating sales tools at Spike?
We like to adopt tools that can help automate processes for us - that way, we can punch above our weight as a team.
What has been the biggest barrier to successful sales tool adoption, overall?
I think the popular sales tools tend to be too complex and overkill for growing startups like ours. We would like to use simpler but powerful tools to help achieve our goals.
How much of your customer acquisition efforts rely on content marketing? How do you maximize its impact and lifetime value?(audience reach, conversions, SEO, etc.)?
Content marketing is a big priority for us because we believe that the best way to reach our audience of software developers is to write content that they find useful.
Do you personalize your sales content per prospect, and if so, how?
We personalise some content for prospects, but not as much as we would like to.
How has COVID-19 impacted your sales and marketing operations and how have you adapted?
As a result of the pandemic, we find that teams are more willing to look into tools like ours that help them solve problems in a remote setting. So we've focused on educating our target users on how they can use Spike.sh effectively, by engaging with the community on different forums.
What are some of the key sales tasks and workflows that you have fully automated? How was your sales productivity affected by this?
We are still in the process of automating our sales workflows.
What are some of the biggest bottlenecks you faced when trying to scale sales enablement campaigns? How did you overcome them?
I think we've not reached this step yet, so it could be a bit early to answer this.
What are some uniquely creative ways you might have used in the past to overcome objections or to close an important deal?
We try to highlight the cost of not using a product like Spike.sh, as the impact of major incidents can be huge for most businesses.
What is next for Spike?
We are focused on making Spike.sh into a powerful incident automation platform for dev, devops and SRE teams. We think we are still just scratching the surface with what is possible with powerful incident management for software teams.