About

I kept losing the people worth talking to

[FOUNDER NAME], who builds Xpush.
@[FOUNDER X HANDLE] on X.

I was building [WHAT I WAS BUILDING] and selling it on X, which meant posting every day and replying to anyone who showed up. It worked, slowly. The part that did not work was everything between those replies.

[THE MOMENT]. That was the point at which it stopped being a memory problem I could try harder at, and started being a tooling problem I could actually fix.

Because the thing nobody tells you about selling on X is that the writing is the easy half. Plenty of tools will help you write a post. None of them could tell me that the person who replied three weeks ago ran exactly the kind of company I was building for, and that I had never followed up.

So Xpush is two halves of one loop. A composer, because you still have to publish something worth replying to. And a relationship table underneath it, because a reply is a person, and a person you forget is a customer you never had. That loop is the whole product.

What it refuses to do

  • No auto-replies. The reply composer sharpens something you wrote. It will not write one for you, and X blocks sending replies through the API anyway.
  • No auto-follows, no auto-DMs. We do not even request the permissions that would make them possible.
  • No engagement pods, no bought followers. A number that came from a pod tells you nothing about whether anyone will buy.
  • No invented numbers. There are no testimonials on this site because nobody has approved one yet, and a metric with no reading shows an empty dial rather than a zero.

If you are posting to find customers and losing track of them the way I did, it is built for you. Tell me what it is missing — I am easy to reach.

— [FOUNDER NAME]