---
title: Q&A with Ewan Dennis
description: A Q&A with Ewan Dennis, Kumo’s new Solutions Engineer based near Glasgowas he reflects on his first 100 days.
---

[KumoMTA Blog](https://kumomta.com/blog)

# [Q&A with Ewan Dennis](https://kumomta.com/blog/qa-with-ewan-dennis)

 Written by [John Pinson](https://kumomta.com/blog/author/john-pinson) | Nov 18, 2026, 7:18:38 PM

Meet Ewan Dennis, Kumo’s new Solutions Engineer based near Glasgow. In this Q&A, Ewan reflects on his first 100 days, what brought him back to email, and why working with an open source community feels like a breath of fresh air.

 

Exciting times here at Kumo HQ! We’re growing our customer success team. If you are in our chats and message feeds, you have likely seen the name Ewan Dennis. We go way back with Ewan, being a key member of the customer success team at Message Systems / SparkPost in the 2010s. As the KumoMTA user base has grown exponentially over the past couple of years, we realized we needed some more skilled hands to meet demand for customer support and guidance. From long experience, we knew that Ewan was one of the best community-focused engineers in the business. We reached out, and happily for us and the Kumo user community, he agreed to come onboard. We’re very fortunate to have him on the team. Today, we’re happy to share a quick Q&A with Ewan. Based in his native Scotland near Glasgow, Ewan will focus on supporting Kumo users in the EMEA region, and is already heavily engaged with several of our customers in the U.K. and on the continent. What follows is a conversation we had with Ewan in early November, 2026, which has been edited slightly for length and clarity.

**You’ve been working in the financial sector at JP Morgan as a developer for the past few years. What brought you back to email?**

Mike, and Tom in particular \<laughs\>. Mike had hired me into Message Systems way back when. The three of us as a sales engineering team essentially followed the SaaS transformation very closely as Momentum became SparkPost, because we were right in the middle of it. I very much enjoyed traveling the world with them and working alongside them throughout that time. Those were some of the best professional experiences I'd had in the industry. My role at JP Morgan was exciting, but having the opportunity with Kumo to interact with the user community on a day-to-day cadence was an enormous draw for me. When Mike and Tom reached out, I was very much “Cool! Let’s do this!” And I mean, obviously I've enjoyed every minute of it since I came on. It's been a breath of fresh air, I have to say.

**Did you have any thoughts on Kumo's market strategy in terms of the open source approach as key to the company's business model?**

Yes. There's a whole class of conversation that happens with prospects, and with clients as well once they’re up and running. When you're working with a proprietary commercial product, the client has to extract some level of comfort, has to gain an understanding of the value or the behavior of the thing they're paying for. With Kumo, all of that is completely absent. Like you can immediately go and read and validate how this aspect of the platform functions. You can also read and validate what the process is for maintaining and growing the product over time. You can see it happen live. And so there's a whole class of early and later phase prospective conversations and discussions that just don't exist. That positive aspect was immediately apparent.

**I think we’ve all seen that the back-and-forth discussions happening through Discord and Discourse convey a sense that you can ask anything and get answers to your questions.**

Exactly. Being able to join and build a community is much easier. With a commercial vendor product, building agency can be kind of challenging: you often end up having to pay for a closed course program without fully knowing its behaviour. It's a "you pay your money, take your choice" type of thing. A little bit different than an open source offering that's managed like a product, but is also something that the community can rally around, be part of, and feel involved in. Most importantly, you can actually be heard in this community. And so there are a lot of benefits to the open source way.

**How about Kumo’s technological approach?**

I think the ensemble works well: modern architecture, Rust-based, config-as-code, open source. There are definitely pros and cons to working in the open. For instance, we see people using robots to configure their mail platform using implementation details from our GitHub repo, not based on documented behaviour. Given that our implementation varies over time, those results can be non-idiomatic and a mite brittle.

Overall though, a massive net pro is that we have an excellent consultation, service, and support model built on top of a strong open source product. And the founders' intent is to keep it that way, not to do a "here's a basic product which is open, but really we've got this extra product sitting on the sidelines which is actually the real thing". There’s no bait and switch with Kumo. It's a truly open product, which is partly a response to the recent history in the MailOps infrastructure industry. Not surprisingly, Kumo is resonating with the MailOps community, a group that has had to endure some unpleasant experiences in recent years with vendor lock-in, expensive license renewal negotiations, and ambiguous product roadmaps.

**What have you been working on since you came onboard?**

Let's see… where to start… I’m an aspiring generalist so it's been a bit of a mix. I have made some small contributions to the test framework, which was a good way to start cleaning out my rusty email pipes. I have a set of customers and prospects that I'm taking care of now, mostly in EMEA time zones. Tom hooked me up with people in the community, customers where he’s said "this is the right way to deploy.’ So, good opportunities to become knowledgeable about the platform’s capabilities and ways to generate value. Tom's been quite smart about positioning me there. I’ve also been doing a lot of training stuff, reading through the documentation, community blog posts and the like. Customer success generally is what Tom hired me for, and so I’ll be taking on more of that so that Tom and Mike have a bit more head space to concentrate on the bigger picture. As with any small org, it's pretty common for someone to have lots of different things happening all at once, and it makes it difficult to concentrate on the overall business.

**So, you’re involved in both pre-sale and post-sale interactions?**

Yeah, I expect to be doing a bit of both, but at the moment I’m mostly involved in post-sale customer support, integration work, that sort of stuff. So the early phase and sometimes steady state stuff. But yeah over time I expect to be involved earlier in the funnel also. Also, I’ll be handling events and industry conference stuff in Europe. I was at MAAWG Paris in October, and I also spoke at the Mautic World Conference in November.

**Welcome aboard Ewan!**

Thanks! Really glad to be here.

\------------------------------------------------------------------

KumoMTA is the first open-source MTA designed from the ground up for the world's largest commercial senders. Our experienced solutions engineers — including Ewan — help our users deploy, optimize, and get the most from KumoMTA. We are fueled by Professional Services and Sponsorship revenue.

[Join the Discord](https://discord.com/invite/tj4vrgC8k3) | [Review the Docs](https://docs.kumomta.com/) | [Read the Blog](https://kumomta.com/blog) | [Grab the Code](https://github.com/KumoCorp/kumomta) | [Support the team](https://donate.stripe.com/00g9AU5Dq7fresg7ss)

 

 

 

[View full post](https://kumomta.com/blog/qa-with-ewan-dennis)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "John Pinson"
  },
  "dateModified" : "2026-11-18T19:26:43.711Z",
  "datePublished" : "2026-11-18T19:18:38Z",
  "headline" : "Q&A with Ewan Dennis",
  "image" : {
    "@type" : "ImageObject",
    "height" : 941,
    "url" : "https://24054978.fs1.hubspotusercontent-na1.net/hubfs/24054978/Ewans%20100%20Days.png",
    "width" : 1672
  },
  "mainEntityOfPage" : "https://kumomta.com/blog/qa-with-ewan-dennis",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60.0,
      "url" : "https://24054978.fs1.hubspotusercontent-na1.net/hubfs/24054978/KUMO_Logo_NEW_Color.png",
      "width" : 220.56
    },
    "name" : "KumoMTA Blog"
  }
}
```