> ## 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.

# Getting started

> Create your first Mibyan output, review it, improve it, and prepare it for export

## The short version

Every useful Mibyan session starts with a goal. You write the request, Mibyan creates an output, and you keep refining it until it is ready to use.

<Steps>
  <Step title="Sign in and open the workspace">
    Open Mibyan and sign in with the available account option. Once you are inside, start from the main composer or an existing conversation.
  </Step>

  <Step title="Choose the output you want">
    Decide whether you need a document, presentation, spreadsheet, HTML page, website, or strategic answer. Naming the format early helps Mibyan pick the right path.
  </Step>

  <Step title="Write a complete first request">
    Include the audience, language, tone, length, market, and required sections. If you are not sure, ask Mibyan to interview you before creating the final output.
  </Step>

  <Step title="Review the preview">
    Look at the result as a draft. Check structure, accuracy, missing sections, tone, formatting, and whether the output matches your goal.
  </Step>

  <Step title="Ask for precise edits">
    Use direct feedback such as "make the executive summary shorter", "add a risk table", or "turn this into a 10-slide investor deck".
  </Step>

  <Step title="Export or reuse">
    When the result is ready, export it or use it as context for the next output in the same conversation.
  </Step>
</Steps>

## Strong prompt examples

<CardGroup cols={2}>
  <Card title="Investor deck" icon="presentation">
    Create a 12-slide investor pitch deck for an Oman-based parcel delivery app. The audience is seed investors. Include the problem, solution, market, business model, traction assumptions, financial model, go-to-market plan, team slide, and funding ask.
  </Card>

  <Card title="Feasibility study" icon="file-lines">
    Write a detailed feasibility study for a specialty coffee shop in Muscat. Include startup costs, monthly operating costs, target customers, competitor analysis, pricing, risks, and a 90-day opening plan.
  </Card>

  <Card title="Landing page" icon="browser">
    Build a responsive landing page for a legal consulting service. Use a calm professional tone, explain the services clearly, include FAQs, and add a contact section.
  </Card>

  <Card title="KPI spreadsheet" icon="table">
    Create a monthly KPI sheet for a B2B sales team with 20 rows. Include target, actual result, achievement percentage, owner, risk level, and executive notes.
  </Card>
</CardGroup>

## What to include in every serious request

* **Outcome:** what the final output should be.
* **Audience:** who will read or use it.
* **Context:** company, market, sector, region, or project background.
* **Format:** document, deck, table, page, website, or summary.
* **Length:** number of pages, slides, sections, rows, or words.
* **Tone:** formal, analytical, persuasive, concise, premium, friendly, or executive.
* **Constraints:** budget, deadline, local regulations, brand direction, required sources, or business assumptions.

## A weak prompt versus a strong prompt

<CodeGroup>
  ```text Weak theme={null}
  Write a business plan.
  ```

  ```text Strong theme={null}
  Write a 7-section business plan for a home maintenance marketplace in Oman. The audience is potential angel investors. Include the market problem, customer segments, service model, pricing, operations plan, launch roadmap, risks, and a concise financial assumptions table. Use a confident but realistic tone.
  ```
</CodeGroup>

## First-run checklist

Before exporting your first result, confirm:

* The title and sections match your goal.
* The output uses the right language and tone.
* The numbers, names, and claims are reasonable.
* The most important audience question is answered early.
* The result has a clear next step: send, present, revise, publish, or export.

<Tip>
  If the first output is close but not perfect, do not start over. Ask for one focused revision at a time. Iteration is usually faster and produces a stronger final result.
</Tip>