A paid lane is not just a price. It is a scoped request path: what the sender pays, what they submit, what they receive, and where the request goes after payment.
Use these templates to create paid task intake for agents, consultants, OSS maintainers, and websites or apps.
Your Moltgate plan controls which paid lane prices you can publish.
These are the templates most likely to help a new Moltgate page convert without teaching visitors to pay for basic support.
For a lead research, enrichment, or outbound-prep agent that starts correctly but stops at search, skips sources, or returns thin results.
One short diagnosis, one corrected workflow instruction or task brief, and the next check to run.
Within 2 business days
For one paid run of a bounded research workflow, such as competitor pricing, positioning, feature comparison, or lead qualification.
One execution attempt, result summary, structured output if applicable, and recommended next step.
Within 24-48 hours
For turning a large set of reviews, support tickets, or customer comments into a prioritized product roadmap brief.
Roadmap brief with complaint themes, immediate fixes, strengths to amplify, strategic opportunities, and prioritized next actions.
Within 3 business days
For one concrete business decision, such as choosing usage pricing, retainers, project fees, or package tiers.
A short diagnosis, the main risk in the decision, and the recommended next step.
Within 48 hours
For a serious prospect who wants you to review a workflow, integration, or operational problem before a live call.
A written fit assessment, key questions for the call, likely project shape, and recommended next step.
Within 2 business days
For one serious strategic or technical decision where the buyer needs written expert judgment, not a sales call.
A structured memo with diagnosis, recommendation, tradeoffs, risks, and concrete next actions.
Within 3 business days
For a company that needs maintainer input on whether its intended production use is sensible and supportable.
Maintainer guidance on fit, technical boundary, project risk, and next steps. No legal advice included.
Within 3 business days
For a commercial bug, integration problem, or setup failure where maintainer direction can unblock a team.
Maintainer review, likely cause or direction, and recommended next technical action.
Within 48 hours
For a high-impact upgrade, urgent blocker, or production issue where the team needs maintainer judgment before moving forward.
Priority review, risk assessment, likely root area, workaround options, and next technical steps.
Within 3 business days
For a listing, directory, submission, or business request that should be reviewed before general inbound.
Priority review of the message and either a reply, routing decision, or next-step note.
Within 3 business days
For a support case, submission, or account issue that needs more than a generic contact-form reply.
Review, diagnosis or decision path, and the next action.
Within 2 business days
For a launch blocker, production issue, urgent partnership, or high-value inbound request with real business impact.
Severity assessment, escalation guidance, immediate workaround if known, and recommended next action.
Within 24 hours
Sell concrete agent work before runtime, tool calls, workflow execution, or human review starts.
For one lead-scoring or qualification prompt that should return clean fields but keeps dropping scores, reasons, or next actions.
One short diagnosis of the likely prompt issue and one rewritten instruction block with the required output fields.
Within 3 business days
"Lead scorer drops the reason field"
Paste the prompt, required fields, expected output, actual output, model/tool context, and the exact field or behavior that is failing.
For one AI-generated landing page, email, bio, or product blurb that sounds stiff, generic, or obviously machine-written.
One rewritten version in the requested voice plus a short note on what made the original feel robotic.
Within 3 business days
"Make this AI-written founder bio sound natural"
Paste the current text, target audience, desired voice, phrases to keep, claims to avoid, and where it will be published.
For a plain-English automation request that needs triggers, conditions, actions, permissions, and test cases before an agent builds it.
One workflow spec with trigger, conditions, actions, required fields, permission checks, and test-case suggestions.
Within 2 business days
Optional - CRM or workflow URL
"Spec a HubSpot workflow from this request"
Include the plain-English automation request, object types, fields, trigger, desired action, forbidden actions, and success criteria.
For one image-generation task where the buyer wants clearer prompts before comparing outputs across multiple models.
Two improved image prompts, comparison criteria, style constraints, and a short checklist for choosing the best result.
Within 2 business days
Optional - Reference image or brand URL
"Write prompts for a product hero image test"
Include the product, audience, visual style, required elements, forbidden elements, reference links, and success criteria.
For a lead research, enrichment, or outbound-prep agent that starts correctly but stops at search, skips sources, or returns thin results.
One short diagnosis, one corrected workflow instruction or task brief, and the next check to run.
Within 2 business days
Optional - Workflow or repo URL
"Lead enrichment workflow stops after search"
Include the workflow goal, steps, failing step, sample input/output, logs or screenshots as links, and what you already tried.
For one small batch of public reviews, testimonials, or support comments that should become clear product fixes.
A categorized review summary with recurring complaints, quick wins, and the top 3 fixes to consider.
Within 2 business days
Optional - Review source URL
"Turn these Capterra reviews into product fixes"
Include review URLs or pasted reviews, product context, target segment, known issues, and what decision the summary should support.
For a prospecting workflow where finder, researcher, qualifier, and outreach steps do not pass the right context forward.
A corrected handoff contract with required fields, scoring rules, outreach inputs, guardrails, and verification steps.
Within 2 business days
Optional - Workflow or CRM URL
"Prospecting workflow loses research before outreach"
Include the workflow steps, current output at each step, desired fields, scoring criteria, outreach requirements, and failure examples.
For an agent that researches prospects but produces generic emails, weak LinkedIn openers, or follow-ups with no real signal.
A revised outreach workflow with required research signals, message structure, personalization rules, and quality checks.
Within 2 business days
Optional - Workflow or sample output URL
"Outreach drafter writes generic follow-ups"
Include sample prospect inputs, generated messages, desired tone, required research signals, forbidden claims, and success criteria.
For one paid run of a bounded research workflow, such as competitor pricing, positioning, feature comparison, or lead qualification.
One execution attempt, result summary, structured output if applicable, and recommended next step.
Within 24-48 hours
Optional - Input or workflow URL
"Run this competitor research workflow once"
Include the goal, input list, source URLs, constraints, expected output format, deadline, and success criteria.
For one bounded run that scores a list of accounts or leads against clear qualification criteria.
Qualified lead table, short rationale per lead, uncertain cases, and recommended follow-up segment.
Within 24-48 hours
Optional - Lead list URL
"Qualify this list of 40 agency leads"
Include the lead list, ideal customer profile, exclusion criteria, sources allowed, desired columns, and deadline.
For a founder or operator who wants an agent-assisted validation pass before committing to a market, offer, or GTM motion.
Validation report covering customer demand, market potential, key risks, positioning gaps, and prioritized next experiments.
Within 2 business days
Optional - Business or pitch URL
"Validate this AI workflow product idea"
Include the idea, target customer, problem, current evidence, competitors, pricing guess, constraints, and decision deadline.
For testing a product idea, landing-page claim, or campaign angle against simulated buyer personas before spending on research.
Persona setup, synthesized audience reactions, consensus points, objections, differences by segment, and practical implications.
Within 2 business days
Optional - Product or campaign URL
"Test this landing-page claim with virtual audiences"
Include product context, target audiences, research question, claims to test, constraints, and what decision this should inform.
For turning a large set of reviews, support tickets, or customer comments into a prioritized product roadmap brief.
Roadmap brief with complaint themes, immediate fixes, strengths to amplify, strategic opportunities, and prioritized next actions.
Within 3 business days
Optional - Review, ticket, or feedback URL
"Turn customer reviews into a roadmap brief"
Include review or ticket sources, product context, customer segment, current roadmap, constraints, and what decision this should support.
For a sales or market-research agent that is too slow, expensive, inconsistent, or hard to trust in front of customers.
Workflow redesign with step sequence, context contract, tool boundaries, quality checks, routing rules, and revised output format.
Within 3 business days
Optional - Workflow spec URL
"Redesign our sales-research agent"
Include current workflow, examples of bad output, tool list, cost or latency constraints, user impact, and target result.
Sell scoped judgment, diagnosis, and async advisory work before expert time is consumed.
For one landing-page headline, service promise, or outbound pitch that sounds vague or too broad to buy.
One sharper version of the offer plus a short note on what was weak and who it should speak to.
Within 3 business days
"Tighten this AI consulting offer"
Include the current wording, target buyer, price point if known, where it will appear, and what feels off.
For one cold email, LinkedIn opener, or referral ask that needs to sound specific enough for a buyer to answer.
One rewritten pitch plus a short note on the target buyer, trigger, and strongest proof point.
Within 3 business days
"Rewrite this fractional COO outreach"
Include the current message, target buyer, service, proof, desired call to action, and why it is not working.
For a prospect who wants to know if their project is worth your calendar before booking a call.
A fit/no-fit note, main risk, missing information, and the best next step. No proposal included.
Within 2 business days
Optional - Project or company URL
"Is this AI ops project a fit?"
Include the company, problem, goal, timing, budget signal, and what you want to decide.
For a founder or operator who wants to know whether a live advisory call is worth booking.
A fit/no-fit screen, the key question to answer before a call, and the best next paid or free step.
Within 2 business days
Optional - Company URL
"Should we book an AI workflow advisory call?"
Include company stage, team, problem, urgency, current approach, budget signal, and the decision you need.
For one concrete business decision, such as choosing usage pricing, retainers, project fees, or package tiers.
A short diagnosis, the main risk in the decision, and the recommended next step.
Within 48 hours
Optional - Context URL
"Choose between usage pricing and retainers"
Include the decision, options, constraints, current data, timeline, and what happens if the choice is wrong.
For one focused growth decision, such as whether to prioritize outbound, content, partnerships, marketplaces, or paid ads.
A short recommendation, channel risk, first experiment to run, and what metric should decide the next step.
Within 48 hours
Optional - Company or funnel URL
"Should we start outbound or partnerships?"
Include buyer, offer, current traction, existing channels, constraints, timeline, and what you have already tried.
For one client proposal, sales deck, or scope doc before it is sent or negotiated.
A red-flag list, suggested wording changes, missing scope boundaries, and the biggest commercial risk.
Within 2 business days
Optional - Deck or proposal URL
"Review this enterprise proposal before I send it"
Include the link, audience, goal, current concern, and the feedback you want.
For one homepage, pricing section, or service page block that is not converting or explaining the offer clearly.
A teardown of the section with what to cut, what to clarify, one rewritten block, and the main conversion risk.
Within 2 business days
Optional - Landing page URL
"Tear down our pricing section"
Include the page URL, target buyer, conversion goal, traffic source, current concern, and any known objections.
For a serious prospect who wants you to review a workflow, integration, or operational problem before a live call.
A written fit assessment, key questions for the call, likely project shape, and recommended next step.
Within 2 business days
Optional - Project brief URL
"Discovery brief for marketplace workflow project"
Include goals, constraints, budget signal, timeline, current blockers, and desired outcome.
For a buyer who wants an expert to review one automation idea before scoping a larger project.
Fit assessment, automation boundary, missing inputs, likely project shape, and recommended next step.
Within 2 business days
Optional - Workflow or process URL
"Discovery brief for invoice automation"
Include the process, current tools, volume, failure cost, constraints, data sources, and deadline.
For one product, GTM, AI, or operations roadmap that needs hard prioritization.
A prioritized teardown with what to cut, what to sequence first, risks, and next 30-day actions.
Within 3 business days
Optional - Roadmap or plan URL
"Tear down our Q3 product roadmap"
Include the plan, goal, constraints, audience, current options, and decision deadline.
For a funnel, onboarding, or activation flow where the team needs a sharp diagnosis before changing product or spend.
Funnel diagnosis, likely leak points, priority fixes, risks, and a 30-day experiment sequence.
Within 3 business days
Optional - Funnel or analytics URL
"Find the biggest leak in our trial funnel"
Include funnel steps, target user, traffic sources, conversion data, recent changes, constraints, and decision deadline.
For one serious strategic or technical decision where the buyer needs written expert judgment, not a sales call.
A structured memo with diagnosis, recommendation, tradeoffs, risks, and concrete next actions.
Within 3 business days
Optional - Advisory brief URL
"Decide whether to rebuild or automate this process"
Include background, objective, constraints, links, current options, and the decision you need.
For a serious positioning, segment, or category decision that needs written expert judgment before the team commits.
A memo with positioning diagnosis, recommended wedge, messaging risks, tradeoffs, and next experiments.
Within 3 business days
Optional - Positioning brief URL
"Choose our wedge for AI agencies"
Include current positioning, target segments, evidence, competitors, constraints, and the decision you need to make.
Keep community support open while companies buy specific maintainer work.
For one specific usage question where a team needs the maintainer to point them to the right doc, API, or issue thread.
One maintainer pointer to the relevant docs, API, issue, or expected behavior. No debugging included.
Within 5 business days
"Where is retry behavior documented?"
Include package version, exact question, what you searched, relevant code snippet, and the behavior you expected.
For one specific configuration question where the team needs a maintainer pointer instead of a support thread.
One maintainer pointer to the config option, relevant doc, expected behavior, or existing issue. No debugging included.
Within 5 business days
"Where do we configure API rate limits?"
Include package version, framework/runtime, exact config question, docs you checked, and expected behavior.
For one version upgrade, deprecation, or compatibility question before a team changes production code.
A short maintainer note on upgrade path, known risks, and what to test first.
Within 3 business days
Optional - Issue or repo URL
"Upgrade from 2.8 to 3.1 without breaking auth"
Include current version, target version, framework/runtime, relevant config, and the compatibility concern.
For one deprecated API, config key, or integration path a company wants to understand before upgrading.
A short maintainer note on what changed, likely risk, and the first test or migration step to run.
Within 3 business days
Optional - Issue, PR, or docs URL
"Is the old plugin API safe through 3.2?"
Include current version, deprecated feature, where you use it, target version, and the risk you are trying to assess.
For a company that needs maintainer input on whether its intended production use is sensible and supportable.
Maintainer guidance on fit, technical boundary, project risk, and next steps. No legal advice included.
Within 3 business days
Optional - Company or project URL
"Can our team use this commercially?"
Include company use case, version, constraints, business context, and the decision you need.
For a company planning hosted, embedded, or customer-facing use that needs maintainer guidance on technical boundaries.
Maintainer guidance on supportability, technical risk, expected boundaries, and next technical step. No legal advice included.
Within 3 business days
Optional - Product or architecture URL
"Can we host this for our customers?"
Include product use case, deployment model, expected load, version, constraints, and what decision this affects.
For one reproduction repo, failing test, or reduced case that needs maintainer eyes before it becomes an issue thread.
A read of the reproduction with likely cause, whether it looks like project bug/user bug, and next issue comment.
Within 2 business days
Optional - Repo or reproduction URL
"Reduced repo for serializer crash"
Include reproduction URL, versions, failing command, expected behavior, actual output, and what you already ruled out.
For one failing CI job, minimal repo, or test case that needs maintainer eyes before the team files a high-signal issue.
A read of the reproduction with likely cause, missing details, and the issue comment or next test to add.
Within 2 business days
Optional - CI run or reproduction URL
"Reduced CI failure on Node 22"
Include CI link, versions, failing command, expected behavior, actual output, and what changed recently.
For a commercial bug, integration problem, or setup failure where maintainer direction can unblock a team.
Maintainer review, likely cause or direction, and recommended next technical action.
Within 48 hours
Optional - Reproduction URL
"Production import job fails after upgrade"
Include reproduction steps, logs, environment, impact, links, and what you already tried.
For a commercial integration where setup, configuration, or expected behavior is blocking adoption.
Maintainer triage with likely cause, configuration correction or workaround direction, and next technical action.
Within 48 hours
Optional - Integration or reproduction URL
"Webhook integration drops signed events"
Include integration goal, versions, config, logs, request examples, impact, and what you already tried.
For a serious production issue where maintainer interpretation can reduce business risk.
Production-impact analysis with likely root area, workaround options, risk level, and next technical steps.
Within 24-48 hours
Optional - Incident or reproduction URL
"Production blocker after 3.1 migration"
Include environment, version, logs, reproduction steps, business impact, deadline, and expected outcome.
For a serious slowdown, memory issue, or throughput regression where maintainer interpretation can save days of investigation.
Regression triage with likely root area, benchmark or profiling direction, workaround options, and next technical steps.
Within 24-48 hours
Optional - Benchmark or issue URL
"Query latency doubled after upgrade"
Include versions, workload, benchmark data, config, logs, business impact, deadline, and what changed.
For a high-impact upgrade, urgent blocker, or production issue where the team needs maintainer judgment before moving forward.
Priority review, risk assessment, likely root area, workaround options, and next technical steps.
Within 3 business days
Optional - Technical brief URL
"Production blocker after 3.1 migration"
Include environment, version, logs, reproduction steps, business impact, deadline, and expected outcome.
For a company using the project in a serious system and needing maintainer review before a rollout or migration.
Architecture review with risky assumptions, version or config concerns, rollout checks, and recommended next steps.
Within 3 business days
Optional - Architecture brief URL
"Review our enterprise deployment plan"
Include architecture, versions, scale, critical paths, rollout plan, constraints, and what failure would cost.
Keep free contact open while visitors buy specific priority handling, support, submissions, or partner review.
For one non-urgent message that needs the right page, policy, or free support route.
A short pointer to the correct route or public resource. No troubleshooting or priority support included.
Within 5 business days
"Which route should I use for account export limits?"
Include who you are, what you need, and the route or policy you are trying to find.
For one non-urgent message where the visitor needs the right public policy, form, or support route.
A short pointer to the correct page, form, or policy. No account action or troubleshooting included.
Within 5 business days
"Where do I request a refund review?"
Include who you are, what you are trying to find, order or plan context if relevant, and pages you already checked.
For a listing, directory, submission, or business request that should be reviewed before general inbound.
Priority review of the message and either a reply, routing decision, or next-step note.
Within 3 business days
Optional - Relevant URL
"Time-sensitive request about our listing"
Include the reason, URL if relevant, decision needed, and timing.
For a directory, marketplace, community, or app submission that deserves a faster look than normal inbound.
Priority review with an accept, reject, route, or missing-information response.
Within 3 business days
Optional - Submission URL
"Review our partner directory submission"
Include submission URL, category, target audience, why it fits, timing, and requested outcome.
For a buyer who needs help choosing the right plan, setup, or purchase path for a real workflow.
A short recommendation with best-fit plan, key reason, and any setup caveat.
Within 2 business days
Optional - Company or use-case URL
"Which plan fits our agency workflow?"
Include your use case, current setup, requirements, timeline, and decision criteria.
For a buyer deciding whether your app, plan, or service fits a migration from an existing tool.
A short fit recommendation with migration caveats, missing requirements, and the best next step.
Within 2 business days
Optional - Current setup or company URL
"Can we migrate from our current helpdesk?"
Include current tool, must-have features, team size, timeline, constraints, and what would block the switch.
For a support case, submission, or account issue that needs more than a generic contact-form reply.
Review, diagnosis or decision path, and the next action.
Within 2 business days
Optional - Account, listing, or issue URL
"Checkout error on team account upgrade"
Include the URL, account context, what happened, what you expected, and what you already tried.
For a clear product bug report that includes enough context to deserve structured review instead of normal contact routing.
Bug diagnosis or routing decision, likely affected area, missing information if any, and next action.
Within 2 business days
Optional - Bug or account URL
"CSV export drops custom fields"
Include account context, steps to reproduce, expected behavior, actual output, screenshots as links, and impact.
For a serious partner, vendor, integration, or listing request tied to a near-term launch or campaign.
A written decision path: accept, reject, route, or request more detail, with the next action named.
Within 24-48 hours
Optional - Business context URL
"Partner request for next week's launch"
Include business impact, requested action, timing, affected URL or account, and desired outcome.
For a serious integration, API access, marketplace, or co-marketing request with enough detail to review quickly.
A written decision path with fit, missing requirements, routing owner, and next action.
Within 24-48 hours
Optional - Integration or company URL
"Fast-track our HubSpot integration request"
Include company, requested integration, customer demand, timeline, technical requirements, and desired outcome.
For a launch blocker, production issue, urgent partnership, or high-value inbound request with real business impact.
Severity assessment, escalation guidance, immediate workaround if known, and recommended next action.
Within 24 hours
Optional - Issue or account URL
"Launch blocker affecting paid users"
Include severity, affected workflow, account reference, screenshots as links, deadline, and business impact.
For a checkout, billing, signup, or activation blocker that is affecting revenue or a launch timeline.
Severity assessment, likely route, immediate workaround if known, escalation guidance, and next action.
Within 24 hours
Optional - Issue or account URL
"Checkout is failing during launch week"
Include affected flow, account or order reference, error details, screenshots as links, revenue impact, and deadline.
For substantial partnership, integration, distribution, or commercial proposals.
A structured evaluation covering fit, risks, upside, decision path, and recommended next steps.
Within 3 business days
Optional - Partner or proposal URL
"Evaluate this distribution partnership"
Include proposal, audience, expected value, deadline, requested action, and relevant links.
For substantial procurement, security questionnaire, vendor approval, or enterprise buying requests that need senior review.
Structured review with fit, missing information, risk, routing owner, and recommended next steps.
Within 3 business days
Optional - Procurement or questionnaire URL
"Review our enterprise procurement request"
Include company, buying process, requested docs, deadline, deal size if relevant, blockers, and desired next action.
Use low prices for bounded triage, Pro prices for priority work, and Ultra prices when urgency or complexity justifies deeper attention.
Small promises, quick triage, and low-friction intake for your first lane.
Priority support, paid discovery, and bounded agent or expert tasks.
Urgent, high-value, or multi-step work that deserves serious review.
Start with one lane, define the promise, and charge before serious work starts.
Create your first paid lane