Submitting feature requests
The fastest way to get a feature considered is to tell us about it with context — what you're trying to do, why your current workaround doesn't cut it, and how often it comes up.
Where to submit
- In-app — click the ? menu → Suggest a feature. Lands directly in our backlog.
- Email —
feedback@schedulin.app. - Twitter / X — DM @schedulin.
What's helpful in a request
- The job, not the feature. "I need to publish the same post to 10 client accounts on a staggered schedule" is more useful than "add a stagger button."
- Current workaround. What are you doing today instead?
- Frequency. Daily? Weekly? Quarterly?
- Who else is affected. Just you, or a team-wide pain point?
How we prioritize
Roughly:
- Volume — how many users are blocked or slowed by the gap.
- Severity — is there a workaround, or is the user genuinely stuck?
- Alignment — does it fit Schedulin's direction (publishing, collaboration, AI-assisted content)?
- Effort — small things that unlock common workflows go fast.
Roadmap and recent ship list: schedulin.app/changelog.
What we usually don't build
- One-network-specific features that aren't available via the API (we follow the API surface).
- Custom branding inside the product UI itself (white-labeled exports are different — see Agency workflow).
- Feature parity with every Buffer/Hootsuite niche feature. We prefer to build the best version of the features we have than thin coverage of everything.