What problem would this startup solve for you?
I've been helping someone out who has recently launched a new service for making transactional emails quick, simple, and beautiful. It looks great, and I can see how useful it would be.
We've been batting ideas back and forth about who would use it, and why. But we think it's not entirely clear, and we're a little stumped about where he should focus his energies. I thought the smart people at Indiehackers might have some insight.
So, we're looking for:
- Feedback on the landing page.
- What problem it would solve for you (and why?).
- Free beta users. Email the founder on hello@tagmail.io with a mention of Indiehackers, and he'll set you up.
We know that from a validation point of view this is kind of ass-backwards. But at the moment we're looking for feedback on what he has right now, rather than suggestions on how to better validate it.
p.s. I have no vested interest here. I'm not receiving any payment or anything. Just genuinely interested in seeing it succeed.
I can share a perspective here, but I'm probably not in their target audience, so keep that in mind :)
I've had a similar idea in mind for a long time now, but I've approached it slightly differently. I have an open-source tool, Enveloper (https://github.com/outstack/enveloper) that also exposes an API to send transactional emails.
It's different in that it's definitely not a no-code or low-code option, and there aren't any built-in templates to choose from.
On the landing page, I think the 4-step illustration explains what it does well, but I'm not sure about the large animation. It's a collection of transactional emails, but I'm not sure it explains what the product does. I'd maybe like to see somehow the templating aspect illustrated there.
Also, in the "not convinced" section where I might put my email, I'm not sure what will happen next. Will I have to ask a question, will someone try to sell to me? Can you reassure me somehow about what I'm getting into in one line?
I do actually use my open-source tool in a few real projects, but I'm a developer, so I don't need the no-code aspect. What it might provide if we were to use it would be a level of collaboration between client and developer or designer and developer.
If you're going for the no-code market, I'd maybe like to see how it could interact with other services. I can see that I can connect mailgun or something, which is great, but how do I trigger an email?
If there was a Zapier option, or specific integrations with other services, I could see how I would connect the two, but otherwise, if I couldn't code, I wouldn't know if I could use Tagmail or not.
I hope that helps a little, and if you've got any follow-up questions, I'm here!
This is great insight, thanks Adam!
He's not an IH member, so I'll feed this back to him directly. I may even be able to convert him to membership... ;-)
Your comment about the triggers rang a bell with me particularly. When I showed it to my CTO yesterday that was his first question. Without triggers it's difficult to maximise its usefulness.
p.s. Yes, I think the CEO here is definitely looking at the template thing as a strong USP, so I can see how that differs from what you're building.
Yeah, exactly. Any developer would be able to trigger an email, but in the no-code space, I don't think you can assume that.
Good point!