---
title: "Start here: examples"
description: "Copy a request to try in Ask, Learn, Code, Mayz, Experts, Workers or Machines, see what a good request looks like, and what real runs gave back."
new_in: "3.1"
---

These are **examples to type as they are**, grouped by the part of Ysra that
runs them, with what real runs gave back and what they cost. Use them to try a
part for the first time, or to see what a good request looks like. The
**What you need** column says whether an example works with nothing but an
account, once a tool is connected in **Settings → Integrations**, or with the
desktop app or the CLI. To choose a part first, see
[When to use what](index.md#when-to-use-what).

## Which part runs what

| Part | What it does |
|---|---|
| [Code](../developer/index.md) | Give Ysra a change to make in your code; it makes it on your computer (desktop app or CLI) or [in Ysra’s cloud](../developer/cloud.md), checks it, and hands you the change. |
| [Ask](../knowledge/index.md) | Ask a question; Ysra answers from the web, your files and your company’s tools, with sources, and can answer with a chart, a View or a document. |
| [Learn](../learn/index.md) | Study a course from your own files, or learn a topic step by step, with a tutor. |
| [Experts](../knowledge/experts.md) | Set up how Ysra answers one kind of question, once, and reuse it. |
| [Workers](../workers/index.md) | A job Ysra does on a schedule, started from Ask, stopping for your approval before anything is sent. |
| [Machines](../machines/overview.md) | Let Ysra work on your servers, one approved command at a time. |

## Ask

| For | Try | What you need |
|---|---|---|
| Operations | “Compare three payroll providers for a 25-person company in France. Give me a spreadsheet with price, setup time and what each is missing, with sources.” | Nothing more |
| Legal and admin | “Read this contract and list the five clauses I should worry about, with the page for each.” (attach the PDF) | Nothing more |
| Sales | “Research this company before my call tomorrow: what they sell, who runs it, recent news. One page, as a PDF.” | Nothing more |
| Events | “Plan the budget for a 3-day conference for 120 people in Lisbon. A spreadsheet with venue, catering, travel and a 10% reserve.” | Nothing more |
| Education | “Make a 4-week study plan for a beginner learning statistics, with one free resource per topic.” | Nothing more |
| Support | “What are customers complaining about most this week?” | Slack or Gmail connected |
| Engineering managers | “What changed in our Jira project since Monday, and what is stuck?” | Jira connected |
| Anyone | “How do I let Ysra work on a folder on my office server?” | Nothing more. See [Ysra help](../knowledge/help.md) |
| Finance | “Chart our revenue by month from revenue.xlsx, as columns, and say which months stand out.” (attach the file) | Nothing more. See [Views](../knowledge/views.md) |
| Planning | “Make me an interactive loan calculator: amount, rate and years as sliders.” | Nothing more. See [Views](../knowledge/views.md) |
| Presentations | “Turn this report into a 10-slide deck for Monday's team meeting.” (attach the report) | Nothing more. See [Documents and slides](../knowledge/documents.md) |

## Learn

| For | Try | What you need |
|---|---|---|
| A course | **New notebook** in Learn, with your lecture notes ticked, then **Guide** and **Cards** on the first chapter. | Course files in **Library → Files** |
| Exam practice | A **Practice** exam on a chapter, then **Mark my answer** with a photo of your working. | A notebook |
| Something new | **Learn a new topic**: “Fourier series”. | Nothing more |
| Homework help | Turn on **Learn mode** in Ask and ask: “How do I solve 2x² − 3x − 5 = 0?” | Nothing more |

## Code

On the web app’s Start page, **Try it in Code** opens Code in
[Ysra’s cloud](../developer/cloud.md) with the example written in the start
box: pick a GitHub repository or **New cloud project**, read it, and send.
In the desktop app or the command line, open the folder first.

| For | Try | What you need |
|---|---|---|
| A small business with no code yet | “Build a one-page website for a bakery: opening hours, a menu with prices, a map, and a contact form.” | The desktop app or the command line, with an empty folder open |
| Any team with code | “The test `test_checkout_total` is failing. Find out why, fix it, and show me what you changed.” | The desktop app or the command line, with the repository open |
| Product teams | “Add a ‘Remember me’ checkbox to the sign-in form. Keep the existing style. Then commit it on a new branch.” | The desktop app or the command line, with the repository open |
| New joiners | “Explain how a payment goes through this codebase, step by step, with the files involved.” | The desktop app or the command line, with the repository open |
| Maintenance | “Update the date library to its latest version and fix whatever breaks.” | The desktop app or the command line, with the repository open |
| Analysts | “Write a script that reads `orders.csv`, removes duplicate rows, and writes `orders_clean.csv`. Run it on the file and tell me how many rows were removed.” | The desktop app or the command line, with the folder open |
| Releases | “Deploy this to staging with our deploy script and tell me the address.” | The desktop app or the command line, with your own deploy tools installed and signed in. See [Deploy from your computer](../developer/deploy.md) |
| No computer at hand | “Build a one-page website for a bakery: opening hours, a menu with prices, a map, and a contact form.” | The web app on a plan with cloud, **New cloud project** under **Where**. See [Code in Ysra’s cloud](../developer/cloud.md) |

## Mayz

| For | Try | What you need |
|---|---|---|
| Before a release | Start a review with **Look at: Security**, or run `ysra mayz <folder> --focus security`. Mayz reports what to fix first, with evidence, and changes nothing. | The desktop app or the CLI with the folder open, or a cloud thread. See [Mayz reviews](../developer/mayz.md) |
| After a Code thread | **Review this with Mayz** under the finished task. | A finished Code task |

## Experts

Create each one in **Experts** with the instructions shown, then ask
it the sample question. See [Experts](../knowledge/experts.md).

| Expert | Instructions, in short | Ask it | What you need |
|---|---|---|---|
| Contract reviewer | “Review contracts against our standard terms (attached). List differences, most serious first.” | “Review this supplier agreement.” | Your standard terms as a file |
| Onboarding buddy | “Answer new joiners’ questions from the staff handbook (attached). Say when the handbook doesn’t cover it.” | “How do I book holiday?” | The handbook as a file |
| Wedding quotes | “Write quotes from our price list and menus (attached). Always check the bookings sheet for the date.” | “180 guests on 14 June, halal, budget 90,000. What can we offer?” | The price list, menus and bookings sheet as files |
| Release status | “Answer where the current release stands. Use Jira and Slack. Lead with the date and what blocks it.” | “Are we on track for Friday?” | Jira and Slack connected |
| Support digest | “Summarise the week’s support conversations: top five problems, how many people, one quote each.” | “This week’s digest, please.” | Gmail or Slack connected |

An Expert built on your own files, like the onboarding buddy, can also answer
people outside your team through a link or a chat on your website. See
[Public Experts](../knowledge/public-experts.md).

## Workers

| Worker | What it does, and when | What you need |
|---|---|---|
| Competitor watch | Every Monday: what changed on three competitors’ websites, with sources. | Nothing more |
| Website watch | Every 15 minutes: checks that your website still answers, and records when it doesn’t. | Nothing more |
| Price watch | Every morning: the price of ten products on a supplier’s site, and what changed since yesterday. | Nothing more |
| Daily incident brief | Every weekday at 08:00: a brief of yesterday’s incidents from Slack and Jira; asks before posting it to Slack. | Slack and Jira connected |
| Inbox triage | Every morning: reads the support mailbox and writes a draft reply to each new message; sends only the drafts you approved. | Gmail for a Worker connected |
| Customers at risk | Every Friday at 16:00: who complained this week and why; asks before posting to Slack. | Slack and Jira connected |

Type the job in Ask, as it is in the second column; Ysra answers and offers a
Worker card to start. See [Start a worker from Ask](../workers/create.md).

## Machines

| For | Try | What you need |
|---|---|---|
| IT and operations | “Check free disk space on every machine and tell me which are above 80%.” | A gateway with machines |
| Operations | “Restart the web service on `shop-1` and confirm the site answers afterwards.” As a runbook: a plan, a dry run, then one approved step at a time. | A gateway |
| A small team | “Put the contents of this folder on `web-1` as the new site, and keep the old one so I can go back.” | A gateway |

See [Machines](../machines/overview.md) and [Machines and gateways](../gateways/overview.md).

## What real runs gave back

These examples were run as written on 12 October 2026. What came back, and
what each cost:

| Example | What came back | Credits |
|---|---|---|
| Payroll providers in France | A workbook comparing the three, with published prices, an estimated monthly cost for 25 people, setup times, extra fees, a checklist for France and a sheet of its 21 sources. The answer named the best starting point for a France-only company and what to confirm first. | 78 |
| Five clauses to worry about (a sample supply agreement) | The five clauses, each with its section: one-sided termination, prices changed at seven days’ notice, a quarterly minimum with a 70% shortfall charge, exclusivity with no exceptions, and delivery and liability. Then three more to negotiate, and a note to have a local lawyer check it before signing. | 6 |
| A company brief before a call | A PDF with what the company sells, who runs it, recent news and questions for the call, from 25 sources. The notes ran onto a second page, and the answer said so instead of calling it finished. | 47 |
| Conference budget in Lisbon | A workbook with venue, catering and travel, a 10% reserve worked out in the sheet, and a total per attendee. These are Ysra’s own estimates, without sources. | 19 |
| Letting Ysra work on a folder on a server | The steps, with links to the pages in these docs. | 2 |
| A bakery’s one-page website | The page, its styles, two photos made for it, and a contact form with 4 tests that pass. The thread ended with a receipt line: “Ran: the form's 4 tests (passed).” | 253 |
| Website watch and Competitor watch | The website watch recorded the site as up; the competitor watch reported what it found, with sources. | — |

Answers differ from run to run. A run that needs research costs more than a
short answer: see [Limits and costs](../workspace/limits.md#what-uses-credits).

## When you don’t know where to start

| Where | What it does | Cost |
|---|---|---|
| [Set up with Ysra](set-up-with-ysra.md) | A short talk about your company; proposes Experts, Workers and build ideas, and creates only what you keep. | Free, 3 a day |
| **Help → Ask Ysra** | Looks at what the account has connected and what is waiting, and says what to do first. See [Ysra help](../knowledge/help.md). | Free, 20 help questions a day |
| **Help → Start here: examples to run** (web app) | These examples, each marked with whether the account can run it now. Trying one puts its text in the right box, unsent. A Code example offers **Get the apps** instead. | — |

## Related

- [What Ysra is](index.md) — when to use each part.
- [Quickstart](quickstart.md) — a first Code thread, step by step.
- [Start a Worker from Ask](../workers/create.md) — turning a job into a Worker.
- [Limits and costs](../workspace/limits.md) — what each kind of work uses.