Esc
  • Jump to
  • The board
  • All launchesSort and filter by week or category
  • Open statsEvery number, in public
  • Maker storiesApps that stopped hiding
  • Submit a launch
  • AICategory
  • AnalyticsCategory
  • API & BackendCategory
  • Audio & VoiceCategory
  • AutomationCategory
  • CommunityCategory
↑↓ to move↵ to openPress / anywhere
Sign in

Feature Request Reply & Decline Macros

Three direct founder replies for scoping a request, adding it to the backlog honestly, or saying no without burning customer goodwill.

Updated · Customers

Copyable template

Copyable reply template
--- MACRO 1: CLARIFY THE WORKFLOW ---
Hi [First Name],

Thanks for writing in about [requested feature]. Before I log this, could you share one line on what you are trying to get done when you hit this?

Sometimes a lighter workaround already exists in [Product Name] (like [existing feature or export]), and seeing your trigger helps me design the right fix if we build it.

[Your Name]

--- MACRO 2: LOGGED ON BACKLOG (NO FAKE ETA) ---
Hi [First Name],

Makes sense, and others have asked for [requested feature] too. I logged your case ([one-line summary]) on our backlog and tagged your account so I can email you if we ship it.

To be upfront, I cannot promise a ship date yet because we are focused on [current priority] for the next [timeframe]. Meanwhile, [practical workaround or honest note that none exists].

Thanks for steering [Product Name],
[Your Name]

--- MACRO 3: HONEST DECLINE ---
Hi [First Name],

Thanks for suggesting [requested feature]. I want to be straightforward: we are not planning to build this into [Product Name].

We are keeping [Product Name] focused on [core product scope], and adding [requested area] would complicate the workflow most teams rely on. If [requested feature] is required for your setup, [workaround via webhook/CSV or alternative tool] is the cleanest path right now.

Appreciate you flagging it,
[Your Name]

When to use this template

Use these three short replies whenever a customer emails support, comments on a roadmap, or asks for a custom workflow during a trial. Fast, candid answers build more trust than promising 'it is on the roadmap' for every idea.

Start with Macro 1 when a user pitches a solution instead of the underlying bottleneck. Use Macro 2 only when the idea fits your direction, and Macro 3 when building it would bloat your core tool.

How to fill each placeholder

  • [requested feature] and [one-line summary]: Repeat their request back in plain language so they know a human actually read their message rather than firing a canned ticket closer.
  • [existing feature or export]: Mention a real workaround only when it genuinely solves at least part of their pain today.
  • [current priority]: Naming the real work ahead in your queue makes a 'not right now' answer feel grounded and transparent.
  • [core product scope]: When saying no, frame the boundary around protecting simplicity and reliability for your core audience rather than dismissing their business.
  • [alternative tool]: Pointing a prospect to a better-fit product when a missing feature is a dealbreaker avoids bad-fit churn two weeks later.

Filled example (made-up product)

Example using a made-up team on-call calendar called ShiftSlate:

--- MACRO 1: CLARIFY ---
Hi Ben,

Thanks for writing in about custom payroll export columns. Before I log this, could you share a quick line on which payroll tool you are importing into and what format it expects?

Right now ShiftSlate exports a standard CSV of on-call hours by teammate, and seeing the exact columns you need helps me check whether our existing export covers it.

Sam

--- MACRO 2: LOGGED ON BACKLOG ---
Hi Ben,

Makes complete sense, and two other teams asked for Slack reminder digests before shift handoffs this month. I have logged your note (15-minute pre-shift DM to the incoming engineer) and tagged your account so I will message you directly if we build it.

To be upfront, I cannot give a ship date yet because I am wrapping up Google Calendar two-way sync over the next three weeks. In the meantime, our webhook trigger can post handoff events into a Slack channel.

Thanks for the suggestion,
Sam

--- MACRO 3: HONEST DECLINE ---
Hi Ben,

Thanks for suggesting built-in incident postmortem docs. I want to be straightforward with you: we are not planning to build a full documentation wiki inside ShiftSlate.

We are keeping ShiftSlate focused strictly on lightweight on-call rotations and handoff alerts. If you need structured postmortem templates linked to shifts, pairing our webhook with Notion or Linear is the cleanest route right now.

Appreciate you flagging it,
Sam

Mistakes to avoid

  • Telling every user 'Great idea, it is on our roadmap!' when you have zero intention of building it.
  • Giving an optimistic two-week ETA in a support reply and then missing it silently for six months.
  • Building a one-off complex toggle for a single $15/month account that adds permanent maintenance drag for everyone else.
  • Closing the thread without asking what problem sat behind the feature request, which often reveals a much simpler fix.

Pritam Ghosh runs Hauntboard and maintains these templates.

Published · Updated

Ready to put your launch in front of real visitors?

A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.

Launch free →

On the board

All →

Still hiding your app?

Put it on the board. Reviewed by a person, free to launch.

Launch free
Submit a launch