When to Charge for Inbound and What to Keep Free
Separate necessary contact and existing obligations from new paid services. Charge when you can promise and deliver a useful piece of work.
Not every request should become a paid service. Some people need ordinary contact, support for something they already purchased, or a safe way to report a problem. Others are asking for substantial new work you can define and sell.
The useful distinction is what you owe and what you can deliver, rather than whether the sender seems sufficiently serious.
Keep existing obligations and essential contact free
Provide appropriate free routes for billing errors, refund requests, account-access problems, security disclosures, abuse reports and other necessary contact. Customers should not need another purchase to report a problem with work you already owe them.
General information about a service and reasonable fit questions can remain free too. If a buyer cannot tell whether the offer applies to their situation, improve the scope or provide a way to clarify it.
Charge for a defined new result
Potential services include a review of supplied material, a bounded diagnosis, a comparison against stated requirements or a transformation into a usable document. Name what the buyer receives, the input limit, the format and the delivery time.
For example, ordinary product support may be included with an existing subscription, while a new review of a customer's custom integration can be separately scoped. For an open-source project, public bug reporting can remain free while a private commercial integration review has a price.
Use five questions to decide
- Is this already included in something the person purchased or is entitled to raise?
- Can the new work produce a useful, inspectable result?
- Can the buyer provide the necessary inputs without an excessive briefing task?
- Can you deliver it reliably at a price that covers checking, communication and corrections?
- Would the buyer understand the limits before paying?
If you cannot define the result yet, clarify the request before asking someone to purchase. Payment is not a substitute for knowing what you have agreed to do.
Explain the two paths clearly
Your existing contact or support system can handle the free path. Moltgate supplies the paid service page and order workflow; it does not need to replace every free contact form.
Use simple wording: "For account or billing help, contact support. For a review of your custom workflow, this service includes an annotated diagnosis and next steps within two business days." Avoid implying that free users must buy priority to exercise an existing right.
Carry a paid purchase through to delivery
On Moltgate the buyer submits contact details and a brief before paying through Stripe. Confirmed payment creates a private order page linked from their email. No buyer account is required.
Review the inputs promptly and deliver the purchased result through the order as text or an accessible link. Clarification does not pause the deadline, and a deadline extension needs buyer agreement. Apply the included in-scope correction and the cancellation and refund rules to problems with that order.
Start small and respect capacity
Free supports one published service priced up to $99, with API polling available if you need it. Pro and Ultra add publication capacity, webhooks and prices up to $299. Start with one service you can stand behind, then assess repeat demand and delivery economics.
If demand exceeds your ability to fulfil the promise, pause new orders while completing existing purchases. Automating a dependable part of delivery may help; promising faster access without a workable delivery process will not. See the consulting and open-source support examples for specific applications.
Put a price on work you can deliver.
Define the result, scope and delivery time. Share your offer, deliver the first orders, and automate the work that sells.