Support email is the product

We answer every customer email within 24 hours

That's the whole policy. Not a marketing promise, not a tiered SLA, not a "Premium Support" upsell. Every email that lands in support@simpleyetefficient.com gets a human response, from one of the two of us, within a day. We've done this for over a year without missing it.

I want to explain why. Because it's not customer service philosophy — it's a product philosophy — and it changed the way we build.

Email is the best telemetry we have

We don't ship analytics in our plugins. No call-home, no usage statistics, no crash telemetry. Some developers find this strange. The reason is simple: we don't want to build the version of SyE where we learn about our product from dashboards.

Email is what we learn from instead. When a customer writes in confused about the Biometrics setup flow, that email is the single most valuable document we'll see that week. It's not a data point — it's a narrative. "I tried X, expected Y, got Z, and now I'm stuck." That chain of cause and effect is the exact signal a dashboard can't give you.

We read every one. We archive them in a folder by plugin. Quarterly, we re-read them in bulk. The patterns that emerge become the roadmap.

The support-driven roadmap

Here are three features that shipped because of email patterns, not because of internal brainstorming:

• REST Express: coroutine mode. We originally shipped only async/await. One-third of support emails in the first two months were "how do I make this work in a project that uses coroutines?" We added coroutine generation as a first-class target in v1.1.
• Scene Compass: bookmark groups. We shipped flat bookmarks. Within a week, three customers independently asked for folders. Groups arrived in the next patch.
• Google Sign-In: custom URL scheme docs. The plugin worked on iOS out of the box if you configured your URL scheme correctly. Nobody did. We wrote a dedicated doc page, and support volume on that single topic dropped to near zero within a month.

None of these changes showed up in a dashboard. All of them showed up in inbox patterns.

The economic argument

People assume same-day support is expensive. In our case, it's cheaper than the alternative. Let me do the math.

We get roughly 50 support-worthy emails a month across all four plugins. Average response time is about 12 minutes of focused engineering thought per email. That's ten hours a month.

In exchange for those ten hours, we get: zero social media backlash, near-zero churn on support-sensitive customers, immediate roadmap intelligence, and referrals. A customer who sent in a frustrated email on Tuesday and got an engineer's response on Wednesday is more loyal than a customer who never had a problem.

Ten hours a month is the cheapest form of customer research and public relations we could buy.

The discipline

The thing that makes it sustainable is that we treat email like production code. We answer it during focused engineering time, not at the end of the day when we're tired. The reply is always (a) acknowledgment, (b) the answer or the next step, (c) an invitation to reply if it's not resolved.

No canned responses. No "your ticket has been logged." No escalation tiers. If we don't know the answer, we say so, and we come back in a day.

This is the single most important feedback loop in the entire operation. It's also the thing that won't scale past the two of us. If we ever hire, the new hire will not be the person who answers email. The founders will still answer the email, because the email is the product.