These aren’t statements for a conference-room wall. They’re the rules we use when deciding what to build, what to reject, and what to fix next.
We’re a small, developer-led company guided less by industry trends and growth playbooks than by one question:
Will this make the product meaningfully better for the people using it?
When we make a mistake, we acknowledge it clearly. We explain what happened, who was affected, what we’re doing about it, and how we’ll keep it from happening again.
Quietly fixing a problem isn’t enough. Trust requires transparency, especially when the news is uncomfortable.
Not every useful idea has to be invented here. But we won’t add something merely because another product has it.
We find the frustrating parts, the unnecessary steps, and the opportunities everyone else missed. Then we build our version to be faster, clearer, or more powerful.
For us, small teams mean fewer meetings, clearer ownership, and a much shorter distance between the person hearing about a problem and the person who can fix it.
We’d rather have a small group of capable people who care deeply than a large organization where responsibility becomes difficult to find.
Good software shouldn’t merely report an error after it happens. It should help prevent the error in the first place.
That means thoughtful defaults, useful warnings, clear previews, and safeguards that protect users without getting in their way.
GMass evolves constantly because the way people use email constantly changes.
We release improvements continuously, revisit old decisions, and refine features long after they launch. “It already works” isn’t a reason to stop asking whether it could work better.
GMass isn’t allowed to outsource its email to another email platform. The emails we send as a company have to go through GMass.
If something is awkward, unreliable, or missing, we experience it ourselves. Our product has to be good enough for our own business, not just good enough for a demo.
We use AI where it produces a better result. We don’t add it to every screen, rename ordinary automation “AI,” or make a reliable workflow unpredictable just because AI is fashionable.
Some problems benefit enormously from AI. Others are still solved better by good engineering and a button that does exactly what it says.
Email is powerful because it gives people direct access to one another. That access deserves respect.
We don’t sell email lists. We don’t sell domains to burn through. And we don’t support tactics such as automated warm-up that manufacture engagement and degrade the email ecosystem for everyone.
No legitimate email platform can guarantee amazing deliverability. Your reputation, recipients, list quality, content, sending behavior, and domain configuration all influence where your messages land.
We give you unusually powerful tools to understand and improve the factors within your control. We show you what’s happening and help you make better sending decisions.
A campaign send is the culmination of real work. Watching it go out should feel informative, reassuring, and maybe even a little fun.
Business software doesn’t have to be joyless. We care about live progress, useful statistics, clear status updates, and the feeling that the product is actively working with you.
We value the shortest reliable path from intention to result.
When software can infer the right choice, automate repetitive work, or eliminate five unnecessary steps, it should. Complex capabilities don’t need to require complicated processes.
We make GMass better. We don’t sell lists, domains, or a pile of adjacent services merely because they could increase revenue.
But we don’t force GMass into one narrow category, either. We build a flexible, general-purpose email tool and let our users decide what it can become.
Product decisions come from technical understanding, direct user feedback, and close attention to how GMass behaves in the real world.
We don’t sit in a conference room and strategize about how to manufacture growth. We strategize about how to create more user happiness. Growth should be the consequence of a product people value.
