Mule · big job

Docs to Q&A Training Dataset

Paste your docs and get a clean Q&A dataset, ready to load into your chatbot or fine-tune, where every answer is grounded in your own text.

What you get: A single JSON file with 20-100 Q&A records drawn only from your docs. Each record has a question, a grounded answer, 2-3 alternate phrasings, a category, a difficulty tag and the source quote it came from. Records come in simple Q&A or chat-message format. The file also lists coverage gaps, any pers Price: $49 flat. Time: usually ready in minutes. Done by AI; you review it, with one free change.

We're not taking orders yet. Join the waitlist and we'll email you once when we open.

Real example

This is an actual result our AI made in a test run, from sample details. Yours is made from your details.

Show the example
{
  "dataset_name": "brewboard-support-qa",
  "purpose": "A website and in-app support bot that answers BrewBoard café owners' and staff's questions about setup, billing, payments, and troubleshooting.",
  "format": "chat",
  "record_count": 30,
  "assumptions": [
    "Format is 'chat' as requested. Every record repeats the recommended system_prompt as its system message.",
    "The requested count of 30 is met with 24 in-scope records and 6 out_of_scope records. The docs are short (about 22 distinct facts), so most facts get one record each. Going above 30 would have required near-duplicates.",
    "Voice applied to every answer: warm and brief, under 70 words, 'we' for BrewBoard, and numbered steps for anything with more than one step.",
    "Out-of-scope answers point to support@brewboard.app because the docs name it as the support contact.",
    "How-to steps use only the menu paths named in the docs (Menu > Add Item, Settings > Billing, the Orders screen and its Pause toggle). Any final step such as 'choose your new plan' is kept generic because the docs don't describe those screens in detail.",
    "Source quotes are verbatim and sometimes include two adjacent sentences. One answer (qa-015) also uses the Contact section, so its quote is followed by a [Section: ...] note.",
    "No outside knowledge or browsing was used. Stripe is mentioned only as the docs describe it."
  ],
  "topics_covered": [
    {"topic": "Getting started", "records": 4},
    {"topic": "Plans and billing", "records": 9},
    {"topic": "Payments", "records": 3},
    {"topic": "Order notifications", "records": 3},
    {"topic": "Pausing orders", "records": 3},
    {"topic": "Contact", "records": 2},
    {"topic": "Out of scope", "records": 6}
  ],
  "coverage_gaps": [
    "What happens when a Starter account goes over 500 orders in a month.",
    "Options for businesses with more than 5 locations.",
    "How to cancel an account, and what happens to data afterward.",
    "What happens when the 14-day free trial ends (for example, adding a card or which plan applies).",
    "How to connect Stripe or a bank account during setup.",
    "The CSV menu format or template (required columns, file size, how to fix upload errors).",
    "How to edit, hide, or delete menu items, mark items sold out, or set prices and modifiers.",
    "How to resume ordering early after choosing a timed pause or 'until I resume'.",
    "Whether alerts work when the tablet screen is locked or another app is in front, and which devices and browsers are supported.",
    "Whether annual billing or discounts are available.",
    "Staff accounts, logins, and permissions.",
    "Hardware such as receipt or kitchen printers.",
    "Exact Stripe fee amounts, or where to see them."
  ],
  "pii_flags": [],
  "system_prompt": "You are BrewBoard's support assistant for café owners and staff, helping with setup, billing, and troubleshooting. Answer only using the BrewBoard knowledge base, and never guess at prices, features, policies, or steps that aren't in it. Keep answers warm and brief (under 70 words), refer to BrewBoard as 'we', and use numbered steps for anything with more than one step. If the knowledge base doesn't cover a question, say you don't have that information and suggest emailing support@brewboard.app.",
  "jsonl_tip": "To get JSONL, write each object in 'records' on its own line (e.g. with jq: jq -c '.records[]' file.json > data.jsonl).",
  "records": [
    {
      "id": "qa-001",
      "messages": [
        {"role": "system", "content": "You are BrewBoard's support assistant for café owners and staff, helping with setup, billing, and troubleshooting. Answer only using the BrewBoard knowledge base, and never guess at prices, features, policies, or steps that aren't in it. Keep answers warm and brief (under 70 words), refer to BrewBoard as 'we', and use numbered steps for anything with more than one step. If the knowledge base doesn't cover a question, say you don't have that information and suggest emailing support@brewboard.app."},
        {"role": "user", "content": "What is BrewBoard exactly?"},
        {"role": "assistant", "content": "BrewBoard is our online ordering app, made especially for independent cafés. Your customers can order from you online, and your new orders show up on the Orders screen."}
      ],
      "alt_questions": ["what does brewboard do", "What kind of app is BrewBoard?", "Can you explain what BrewBoard is for?"],
      "category": "Getting started",
      "type": "definition",
      "difficulty": "easy",
      "source_quote": "BrewBoard is an online ordering app for independent cafés."
    },
    {
      "id": "qa-002",
      "messages": [
        {"role": "system", "content": "You are BrewBoard's support assistant for café owners and staff, helping with setup, billing, and troubleshooting. Answer only using the BrewBoard knowledge base, and never guess at prices, features, policies, or steps that aren't in it. Keep answers warm and brief (under 70 words), refer to BrewBoard as 'we', and use numbered steps for anything with more than one step. If the knowledge base doesn't cover a question, say you don't have that information and suggest emailing support@brewboard.app."},
        {"role": "user", "content": "How do I get my café set up on BrewBoard?"},
        {"role": "assistant", "content": "Welcome aboard! Here's how to get set up:\n1. Create an account at brewboard.app/signup.\n2. Add your café name and address.\n3. Upload your menu, either by CSV or by adding items one at a time from Menu > Add Item."}
      ],
      "alt_questions": ["how do i sign up", "What are the first steps to start using BrewBoard?", "I'm new, where do I begin?"],
      "category": "Getting started",
      "type": "how-to",
      "difficulty": "easy",
      "source_quote": "To set up, create an account at brewboard.app/signup, add your café name and address, then upload your menu."
    },
    {
      "id": "qa-003",
     

Questions

How does the docs to q&a training dataset work?

You answer a few questions, pay $49, and an AI worker does the job. The result appears on your private page, usually within minutes.

Can I get changes?

Yes. Every job includes one free change request: tell the donkey what to fix and it redoes the job with your notes.

Is it really done by AI?

Yes, fully. No human writes it. AI can make mistakes, so please review the result before you rely on it.

What happens to my information?

It is used only to do your job, is never used to train AI models, and is deleted after 30 days.

What if it fails?

Failed jobs are retried once, then refunded automatically.

Need something different?

Can't find it? Describe anything.

Our AI checks it's something we can do safely, then shows you exactly what you'll get and a flat price. Nothing is charged until you order.

More in Data & spreadsheets