> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mibyanai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Outputs

> The documents, decks, spreadsheets, pages, and websites you can create with Mibyan

## What is an output?

An output is the work product Mibyan creates for you inside a conversation. It can be a document, deck, spreadsheet, page, or website. Outputs are previewable, editable, and reusable as context for follow-up requests.

Think of the first version as a strong draft. Your job is to review it, give precise feedback, and guide it toward the final format you need.

## Output types

<CardGroup cols={2}>
  <Card title="Documents" icon="file-lines">
    Best for reports, feasibility studies, business plans, proposals, memos, contracts, policies, articles, and structured long-form writing.
  </Card>

  <Card title="Presentations" icon="presentation">
    Best for pitch decks, company profiles, board updates, sales decks, training slides, launch decks, and visual narratives.
  </Card>

  <Card title="Spreadsheets" icon="table">
    Best for KPI trackers, financial assumptions, comparison tables, budgets, operating plans, pricing models, and lists.
  </Card>

  <Card title="HTML pages" icon="browser">
    Best for one-page prototypes, landing pages, campaign pages, service pages, and visual drafts that need immediate preview.
  </Card>

  <Card title="Websites" icon="globe">
    Best for simple multi-page sites such as home, services, about, FAQ, and contact pages.
  </Card>

  <Card title="Strategic answers" icon="lightbulb">
    Best for brainstorming, planning, analysis, decision support, and turning vague ideas into a clearer brief.
  </Card>
</CardGroup>

## How to request each output

<AccordionGroup>
  <Accordion title="Documents">
    Name the document type, audience, required sections, length, tone, and any local context. For formal work, ask for a table of contents, executive summary, risks, assumptions, and next steps.
  </Accordion>

  <Accordion title="Presentations">
    Specify the audience, number of slides, presentation goal, story arc, required sections, and visual direction. For investor decks, include stage, market, business model, traction, and funding ask.
  </Accordion>

  <Accordion title="Spreadsheets">
    Describe the rows, columns, calculations, assumptions, and how the sheet will be used. If the numbers are estimated, ask Mibyan to label assumptions clearly.
  </Accordion>

  <Accordion title="Pages and websites">
    Describe the target user, message hierarchy, sections, call to action, brand tone, language, and device priorities. Mention if the page should be Arabic, English, RTL, or bilingual.
  </Accordion>
</AccordionGroup>

## Reviewing outputs

Use this review pass before you export or share anything:

* **Structure:** does the output include the right sections in the right order?
* **Audience fit:** would the intended reader understand and trust it?
* **Completeness:** are important details missing?
* **Tone:** does it sound formal, persuasive, concise, or detailed enough?
* **Accuracy:** do names, numbers, dates, locations, and claims need checking?
* **Actionability:** does the output end with clear decisions, next steps, or deliverables?

<Warning>
  Mibyan can help draft and organize complex work, but important legal, financial, medical, or regulatory content should still be reviewed by a qualified person before use.
</Warning>

## Editing an existing output

You do not need to rewrite the whole prompt. Refer to the current output and ask for the exact change:

```text theme={null}
Keep the same structure, but make the executive summary shorter and more suitable for a CEO.
```

```text theme={null}
Add a risk table with probability, impact, mitigation, and owner.
```

```text theme={null}
Turn this document into a 10-slide presentation for investors.
```

```text theme={null}
Use the same content, but rewrite it in a more premium marketing tone.
```

## Best practices

* Start with a clear first version, then iterate.
* Ask for questions first when the task is ambiguous.
* Provide local context when the output depends on market realities.
* Separate content feedback from formatting feedback.
* For high-stakes work, ask Mibyan to produce assumptions and review notes alongside the output.