About
We built the tool that tells you not to post.
Crux exists because every other assistant in this category answers the same question — what should I write? — and none of them answer the one that decides whether it lands: is today worth it for me, specifically.
The idea came from a bad week.
Four posts in five days, each one on whatever was trending, each one written well and read by nobody who mattered. The posts were not the problem. The choice of subject was. Volume tools had made it trivially easy to say something and no easier to say something to the right room.
So the first thing we built was not a generator. It was a scorer — four axes, run against your own history rather than against a global trend list. The drafting came later, and only because a score you cannot act on is just a number.
What we will not build
Some features are easy, popular, and bad for you.
Full autopilot
We could post for you. An account that posts without its owner reading the room stops being worth following, and the failure mode is public and permanent. Every send stays manual.
Reply automation
Automated replies are the fastest way to convert an audience into an annoyance. Crux has no reply features and we do not plan any.
Vanity dashboards
Charts that only go up teach you nothing. Performance shows the days you did not post as empty tracks, and reports declines as plainly as it reports growth.
A data business
Your posts train your model and stay yours. We do not sell audience data, we do not pool accounts into a shared model, and the subscription is the only way Crux makes money.
How it pays for itself.
Subscriptions, and nothing else. No ads, no affiliate links in your drafts, no data resale, no free tier funded by selling what the free tier learns. The X API cost is billed to you at cost because marking it up would give us a reason to scan more than you need.
That last one matters more than it sounds. A tool that profits from its own API usage is a tool with an incentive to burn your budget.
Who builds it
A small team, on purpose.
Product and design
Team member name
Owns the scoring model and the interface decisions — including the rule that no score is ever shown as a bare number.
Engineering
Team member name
Owns the ingest pipeline, the API budget guard, and the fact that nothing in the queue can send itself.