Article
Why I Built PayDM
Direct access to the right person is one of the hardest things to get when you start without a network. This is the problem PayDM was built around.
When you start something without a network, the hardest part is rarely the work. It is knowing whether the work is pointed in the right direction.
I ran into this constantly. I had precise questions — how to approach a specific decision, whether a problem I had been spending weeks on was worth solving at all — and I knew there were people who had already worked through the same thing. In theory they were reachable. Their profiles were public. Their inboxes existed. In practice, getting a considered answer from them was close to impossible.
That gap is where PayDM comes from.
Access is not a link
We tend to talk about access as if it were a technical problem that had already been solved. Anyone can send anyone a message. The address is right there.
But being able to send a message is not the same as being read, and being read is not the same as getting an answer. Access, in any useful sense, means someone deciding that your question is worth their attention over the hundred other things competing for it in the same hour. That decision is the scarce part. Nothing about a public profile guarantees it.
If you already have a network, that decision is often made for you. A mutual contact forwards the message. A name is recognised. A reply is expected because there is a relationship behind it, present or future. When you have none of that, you are asking a stranger to spend their attention on you for no reason other than goodwill. Sometimes that works. Mostly it does not, and it is not unreasonable that it does not.
Why the normal inbox fails here
The problem with DMs and email is not that people are unwilling to help. It is that the channel gives them nothing to work with.
An inbox arrives as an undifferentiated pile. A serious question that took someone an hour to formulate looks, from the outside, exactly like a pitch, a template, or a request for free work. Nothing in the message itself separates them. To find out which is which, the person receiving it would have to read everything carefully — and reading everything carefully is precisely what they do not have time to do.
So they triage. They answer the people they know, and the messages that are obviously short, and the rest goes unanswered. That is a rational response to volume. But it means the filter is not “is this question worth answering”. The filter is “does this person already have a way in”.
The result is that the people who would gain the most from a specific answer are systematically the least likely to get one.
Why attaching a price to a question makes sense
The change I kept coming back to is simple: let the person asking put something behind the question.
Paying to send a message does two things at once.
For the sender, it is a way to be taken seriously without a shared contact. You are not asking for a favour. You are making a request that carries its own weight, and you can ask the thing you actually want to ask instead of opening with a paragraph explaining why you deserve a reply.
For the recipient, it separates the pile. A paid message is a message someone was willing to commit to. That is not proof the question is good, but it is a real signal, and it comes with a concrete reason to spend the twenty minutes an answer would take. Attention that was previously either given away or not given at all becomes something that can be offered on defined terms.
I want to be careful about what this does and does not claim.
It does not mean everyone should be reachable, or that a price obliges anyone to answer. Plenty of people have good reasons to keep their attention closed, and that should remain their decision. It also does not mean money is what makes a question worth answering — most of the best conversations I have had started for free, and I would not want that to change.
What it means is narrower. For people who are willing to make part of their attention available, there should be a clean way to do it. Today that mechanism mostly does not exist, so the choice is between an inbox they cannot keep up with and no access at all.
What that led to
PayDM is built around that mechanism. Someone who receives a lot of requests has a profile. Someone who wants their answer pays to send a message or a question. The recipient can reply.
That is the whole structure, and keeping it that small is deliberate. The point is not to add another place to post, or another audience to build. It is to take a request that would have been lost in an inbox and turn it into something explicit: a defined question, with a defined value, that the person on the other side can decide to take or not.
Most of what I work on is about removing friction around that exchange rather than adding things on top of it.
What I would like it to make possible
The longer-term idea behind PayDM is that direct access should not depend entirely on already having an audience or a network.
That is a strong statement and I am not going to pretend it is a solved problem. But the current situation is worse than people usually admit. A large amount of useful knowledge sits with individuals who cannot answer at scale, and the informal system we use to route questions to them mostly rewards proximity. If you are near the right circles, you get answers. If you are not, you spend months finding out something you could have learned in one message.
I would like PayDM to make that second situation less common. Not by claiming that anyone can reach anyone, but by giving the people who are open to it a way to make that openness real, and by giving the people asking a way to be heard on the strength of their question rather than their contacts.
That was the reason to build it.
Aldrick Mellare — Founder of PayDM PayDM: paydm.app · Profile: paydm.app/aldrickmellare