Paid questions for creators: when should you charge for an answer?

The question is the product, not the person

Most creators who consider charging for DMs start from the wrong question: "how much is my time worth?" That number matters eventually, but it is the second question, not the first. The first is narrower: which questions, specifically, are worth someone paying for an answer?

This distinction matters because a paid inbox that accepts anything behaves exactly like a free inbox, just slower to fill up. If the scope is "ask me anything," you will receive everything, including the messages a paid model was supposed to filter out. The value in a paid question model comes from treating the question itself as the unit being sold, priced and scoped, rather than treating payment as a generic toll on access to a person.

Concretely, that means deciding in advance what kind of question you are willing to sell a written answer to, and saying so on your profile, before a single message arrives.

Questions that are worth a paid answer

Three properties tend to show up together in a question worth charging for.

• It is specific to you. Someone is asking because of what you did, not because of what anyone in your field would say. "You switched from agency work to product in your third year — what would you have done differently at month six?" only has one accurate answerer.
• The answer is not published anywhere. If the question is already covered by your content, a pinned post, or a five-second search, the sender should not pay, and you should not want them to.
• It changes a decision. A useful test: would the person act differently after reading your answer? If the honest answer is no, the question is closer to a compliment than a request.

An illustrative example: imagine a small SaaS founder who receives a question like "I'm about to switch our billing provider mid-contract-cycle — did that break anything for you when you did it, and what would you check first?" That is a paid question. It is specific, undocumented, and the answer would plausibly change what the sender does next.

Compare that with "how do I get more customers?" — a question so broad that any answer is generic advice, and generic advice is free everywhere. Charging for it would be charging for the illusion of a personal answer rather than the thing itself.

Vague questions vs specific questions

Vague questions are not bad questions to receive for free. They are simply not paid-question material: nobody's specific judgement is required to answer them, so nobody's specific judgement is worth paying for.

What not to charge for

• Things you have already written about. If your content answers it, link to the content instead of accepting the payment.
• Feelings, not facts. "I just wanted to tell you I love your work" is a compliment. Let people send those for free; charging for them is a strange incentive to run.
• Favours dressed as questions. "Would you look at my whole portfolio and give feedback on everything" is a review, not a question. Either scope it down to one specific piece, or say plainly that full reviews are not something you offer through paid questions.
• Anything that needs back-and-forth to even understand. If a question needs three follow-up questions before you can answer it, it was not ready to be asked yet.

Paid question vs tip, subscription, course and consulting call

Each of these is a legitimate way to monetize an audience or a skill. The mistake is treating them as interchangeable. A paid question that tries to also be a mini-consultation ends up under-priced for the effort and over-promised relative to what one written answer can realistically deliver.

Defining the scope before the first message arrives

Scope is what turns "I answer paid questions" into something a stranger can actually act on. Three things belong on a profile before you open a paid inbox:

• The two or three subjects you are useful on, named precisely rather than as a category. "Marketing" invites everything; "positioning for early-stage B2B tools" invites the right thing.
• The format the answer takes. A written answer to one question, not a document, not a multi-part breakdown, not a review of an entire project.
• What you explicitly will not answer. Naming the exclusions reduces the number of messages you have to decline after the sender has already paid.

A narrow, precisely worded scope produces fewer messages, and the ones that arrive are closer to something you actually want to answer. That trade — lower volume, higher relevance — is the entire point of pricing a question in the first place. The mechanics of setting a price alongside that scope are covered separately in how much to charge for a paid DM.

Written answers vs other formats

Some paid-question products on the market offer video responses instead of, or alongside, written ones. Written and video each suit different situations: a video can carry tone and nuance that text cannot, while a written answer is faster to produce, easier to reread, and easier to search back through later. Neither is universally better — it depends on the question and on what the person answering finds sustainable to produce at volume.

PayDM's model is a single written reply: the Creator sets a price, and the reply must be a personal written answer, delivered within 8 days, or the sender is refunded automatically. The mechanics of payment, refund and payout are documented in full on how PayDM works.

When the paid-question model does not fit

Being honest about the model's limits matters as much as explaining where it works.

• The request needs a live conversation. Diagnosing something ambiguous usually needs a back-and-forth, which a single written answer cannot provide.
• The sender needs to review a large amount of material. A full manuscript, a whole codebase, a complete business plan: none of that fits inside one answer, and pricing it as if it did produces a rushed, shallow response.
• You do not actually have specific, non-public judgement to offer. If your honest answer to most incoming questions would just repeat public information, a paid question model has nothing to sell yet. Build the specific expertise, or the audience that generates specific questions, before pricing access to it.
• The audience expects free access as part of the relationship. Some communities are built on the premise of a direct, free line to the creator. Introducing a price there is a bigger shift than it looks and needs to be communicated, not just switched on.

None of these are arguments against paid questions generally. They are reasons a specific question, or a specific creator at a specific stage, is not a good fit for it yet.