How to turn free advice requests into paid offers

Recognising a real advice request

Not every message that ends in a question mark is an advice request. Before deciding whether something should be paid, work out what it actually is.

• A reaction. "This helped me so much, thank you." No question inside it. Reply warmly, nothing else needed.
• A lookup. "Which tool do you use for X?" One line, or a link to where you already said it. Free.
• A genuine advice request. "Here is my situation, here are the two options I am weighing, what would you do?" This needs you to read, think, and commit to a view. It is work.
• A disguised project. "Could you look over my portfolio / my whole funnel / my business plan and tell me what to fix?" This is a review or an audit wearing the clothes of a quick question.

Only the last two are candidates for a paid offer. The first two stay free because answering them costs you almost nothing and keeps your inbox a place people want to be. This is the same distinction covered from the pricing side in paid questions for creators.

What can stay free

Charging for the wrong things costs more goodwill than it earns. Keep these free on purpose:

• Quick factual answers you can give in a sentence without thinking hard.
• Anything your content already covers. Link the post. It helps them and costs you nothing.
• Encouragement and short relationship maintenance. The back-and-forth that is part of why an audience feels connected to you.
• The occasional deliberate favour. Answering something substantial for free now and then, because you want to, is a normal choice — not a leak in the system.

What deserves a paid answer

A request is fair to charge for when all three are true:

• It takes real time to answer well. You need to read something, think it through, and write a considered response — not fire back a reflex.
• The answer depends on your specific judgement. It is about their situation, and your experience changes what the right move is. Generic advice is free everywhere; this is not generic.
• It is not already published. If your content answers it, the honest move is to send the link, not the invoice.

Typical examples: "review my three best pieces and tell me which to lead with"; "I have competing offers, help me decide"; "look at my pricing page and tell me what is wrong"; "map out how you would launch this". Each is bounded, personal, and genuinely useful — exactly what a paid personal answer is for.

Setting the boundary without damaging the relationship

The relationship suffers when the boundary is improvised, inconsistent, or delivered as irritation. It holds when the boundary is decided in advance and applied the same way every time.

1. Write the line down for yourself. One sentence: what you answer for free, and what now goes through a paid option.
2. Put it where people see it before they message. A line in your bio, a note in your pinned post, a sentence in your newsletter. Public and calm, so it is not a surprise in the DMs.
3. Apply it evenly. Making exceptions for some people and not others is what actually causes resentment. Consistency reads as fair.
4. Keep a warm free tier. If short questions still get a friendly reply, the paid option reads as an upgrade for bigger asks, not a wall.

You are not closing the door. You are labelling which door leads to a guaranteed, considered answer.

Announcing the offer with tact

Announce it once, plainly, framed around what the other person gets:

• Lead with the benefit. "If you want a proper, personal answer to a specific question, you can now send it here and I will reply within a few days."
• Explain the why briefly and without complaint. "I get more of these than I can answer well for free, and I would rather give a real answer than a rushed one."
• Keep the free part visible. "Quick questions here are still open — this is for the bigger ones that need real time."
• Do not over-justify. One or two sentences. A long defensive explanation invites a debate you do not need to have.

Reply templates (English and French)

Adapt these to your own voice. The goal is a short, friendly redirect — not a form letter.

English

Genuine advice request:
"Happy to give this a real answer — it is a bit more than I can do well in the DMs. You can send it here and I will reply in writing within [X days]: [link]. Quick questions here are always open."

Disguised full project:
"This is really a full review rather than a quick question. I do those as a paid piece of work — here is what is included and the turnaround: [link]. If you would rather narrow it to one specific decision, I can take that here for free."

Regulated or high-stakes request:
"I can share general thoughts, but a decision like this should go to a licensed [professional] who can look at your full situation. Happy to point you toward what to ask them."

French

Vraie demande de conseil :
« Avec plaisir pour une vraie réponse — c'est un peu plus que ce que je peux traiter correctement en messages privés. Tu peux l'envoyer ici et je réponds par écrit sous [X jours] : [lien]. Les questions rapides ici restent toujours ouvertes. »

Projet complet déguisé :
« Là c'est plutôt une relecture complète qu'une question rapide. Je fais ça en prestation payante — voici ce qui est inclus et le délai : [lien]. Si tu préfères le ramener à une décision précise, je peux la prendre ici gratuitement. »

Demande réglementée ou à fort enjeu :
« Je peux donner un avis général, mais une décision comme celle-ci devrait aller à un [professionnel] habilité qui peut examiner toute ta situation. Je peux t'aider à préparer les bonnes questions à lui poser. »

Defining what the payment includes

Ambiguity here is what turns a paid answer into a frustrating back-and-forth. State, on the page and before payment:

• Format and length. "One written answer, roughly 300–600 words" or "a 5–10 minute voice note".
• Scope. One question, or one artefact reviewed once. Not an open thread.
• Turnaround. A date you can hit reliably.
• Follow-ups. Whether one clarifying reply is included, or each new question is a new request.
• What is excluded. Full project builds, ongoing support, anything requiring documents you will not have.

With this stated, both sides know when the transaction is complete, which is what keeps it comfortable.

Accepting, declining and refunding

Three outcomes, all normal:

• Accept. The question is in scope and clear. Answer it within your stated window.
• Decline. It is outside your scope, needs regulated advice, or is a project in disguise. Decline it and refund — a clear scope means this is rare, and a mismatched answer damages the offer more than a refund does.
• Refund. If you cannot give a useful answer, or you missed your deadline, refund without being asked. Reliability is the whole product.

On PayDM, declining a message refunds the sender automatically, and if no reply is sent within 8 days the sender is refunded in full without either party doing anything. The mechanics are on how PayDM works.