Get Rootly's Incident Communications Playbook

Don't let an incident catch you off guard - download our new Incident Comms Playbook for effective incident comms strategies!

By submitting this form, you agree to the Privacy Policy and Terms of Use and agree to sharing your information with Rootly and Google.

Get to know

Nuno Tomás

Quick facts

🧗🏻
Founder at isDown.app
🧑‍🧑‍🧒‍🧒
Family man
🦠
First attempt in 2020
🇵🇹
Based in Lisbon, Portugal

Five Question with Nuno

Could you share a little bit more about yourself and how you ended up becoming a founder?

I started as a software engineer 20 years ago. Just developing for others, went through like a career of doing agency work. Then at some point I was like, okay, I, I really want to do something on my own. So I was like let's do this. But then COVID hit and after three months, I was like, okay, I don't have the money to stay on.

So I went back to a regular work. I found an awesome company to work with. But after two years I was like, okay, no. It's now or never. I'm almost 40. This is my dream. I will succeed or fail miserably, but at least I will try.

How do you feel your engineering background has informed isDown.app and the way you think about the product?

I’ll give you my honest take: being a technical founder is great. It was really easy to bring up the product up because I had even experienced of the pain myself. So I can relate to our customers very easily. Everyone has had the same experience of waking up in the middle of the night and not understanding what's going on.

How do you handle conflicting priorities in incident communication, like transparency versus business concerns?

Dealing with conflicting priorities in incident communication is tough. Engineers and support teams usually want transparency to reduce confusion and tickets, while sales teams worry it might make us look bad. I think it really comes down to education—helping people understand SaaS isn’t like electricity, where it’s either on or off. Software is more nuanced, and being upfront builds trust.

At the end of the day, incidents are inevitable if we want to keep improving. Complex systems break sometimes—it’s just how it works. The key is communicating openly so customers know what’s going on. It’s not about perfection; it’s about building a relationship where people feel informed and supported.

What are some of the biggest challenges you’ve faced as a technical founder?

Being a technical founder helped me because I could do everything on my own from the start to have a base product. But then the technical me was also really bad at sales, really bad at marketing and so on. So, I fell into that stigma of, Oh, I'll build it and people will show up. So that's the part of being a technical founder, which isn't that great.

Do you see a solution for reducing alert fatigue for on-call teams?

One of the best ways to reduce alert fatigue is to filter out the noise. We built a feature that lets users pick only the services or regions they care about, so they don’t get bombarded with irrelevant alerts. If everything’s an alert, nothing is, and constant notifications just train people to ignore them. By focusing on what actually matters, teams can stay sharp and avoid unnecessary distractions.