Rule 01
Replies are signal.
Reach flatters. A reply proves someone cared. Reports rank posts by conversations started.
// metric · replies per post
Spec 02 · About the product
Wrenchat started from that question. Scheduling and replies belong on the same sheet. So we built one place for both, and a report that counts conversations.
01 / The problem
Small teams ship posts on schedule and lose the conversation underneath them.
Nobody trusted it. Posts went out from whichever app was open.
A question under a carousel sat for two days. Nobody was assigned.
Big numbers. No answer to the real question: which post started a conversation?
Sign-off scattered across threads. The draft never knew who said yes.
02 / Principles
Every feature has to pass them. Most ideas don't.
Rule 01
Reach flatters. A reply proves someone cared. Reports rank posts by conversations started.
// metric · replies per post
Rule 02
No orphaned comments. Assign it, resolve it, see who answered.
// inbox · owner + status
Rule 03
Timing suggestions come from 30 days of audience activity. Override any of them.
// timing · your call
Rule 04
Calendar, inbox, approvals and reports share one workspace and one source of truth.
// workspace · one sheet
03 / Build + support
Wrenchat is made for marketing teams of two to twenty. It does a few jobs and finishes them. Support is read and answered by people who use the product.
Fig. 06 · Approvals queue · cropped
04 / Where it goes
Direction, not promises with dates. Each item has to earn its place against the four rules.
Top posts by replies, exported as a client-ready PDF or CSV.
Rules that assign comments and DMs to the right owner on arrival.
Turn a comment into a ticket, a report into a channel post, in one click.
Shared answers for the questions your team gets every week.
05 / Start
Pick the plan that fits your profile count. Fill the first week before the weekend.
Get started