Guide
How to write a good feature request
The form asks three questions. Each needs at least 50 characters, and each maps to something we weigh when we prioritize. It takes a few minutes and gets your request acted on faster.
- 1
What are you trying to do?
Describe the moment. Who is doing it, where they are and what they're trying to get done. A good answer names a person and a job, not a feature.
Complete answer
“My reps are at the kitchen table at the end of an appointment. They want to leave the homeowner with something to look at after they walk out.”
Not enough
“We need an export option.”
- 2
What happens when you can't?
Describe what happens today instead. The workaround, the thing that gets skipped, the moment it falls apart. Be specific about who feels it and when.
Complete answer
“The rep texts a few photos from his phone or sends nothing. The homeowner sits down with their spouse that night with nothing in front of them and the whole story is gone.”
Not enough
“It doesn't work the way we need.”
- 3
What is it costing you?
Put a number on it. Minutes per appointment, deals per month, reps who give up on it, dollars. Your best guess counts. A blank does not. This is how we decide what to build first.
Complete answer
“I think we lose one or two deals a month at the second conversation, and every rep spends ten minutes after each appointment sending photos.”
Not enough
“It's frustrating.”
One more thing: add a screenshot or a short video
A picture of where you got stuck saves a round of questions. Attach the screen where you expected the option to be; videos under a minute are perfect.
What happens next
Every request carries a status that moves through three stages: To-do while we review it, In progress while we discover, design and build, and Complete once it ships or we decide not to build it and say why. Duplicates get merged so votes add up in one place.
Write Your Request