We build software for people.
Every feature in Scribe, Lists, and the rest of Tetrix started as a conversation with someone using the product. This is where that conversation begins.
Great software is a feedback loop. The best tools get that way because the people building them listen closely, respond quickly, and treat every report as a signal. That's how Tetrix is built.
Your feature requests shape the roadmap. Your bug reports move to the top of the queue. We read everything.
What happens to your response
Every submission lands directly with the team. Feature requests get weighed against what's already planned. Bug reports get reproduced, diagnosed, and fixed. If you leave an email, we may follow up with a clarifying question.
Your response is private. We don't sell it, share it, or use it to train anything. It's used for one purpose: making Tetrix better.
Which form should I pick?
- Feature request — a specific thing you want Scribe, Lists, or another Tetrix app to do.
- Bug report — something is broken, missing, or behaves unexpectedly.
- Writing habits & friction — a research survey on how you write today and what slows you down.
- Software taste & switching — what makes you try a new app, stay with one, or walk away.
- Pricing & value — how you think about paying for software.
- The ecosystem question — whether apps that work together beat best-in-class separate apps.
- AI & automation attitudes — where the line is between helpful and too much.
Prefer email? support@tetrix.tech goes to the same inbox.