From your first install to a real advantage.

1. Your first answer in 5 minutes 5 min

1. Install OnSubject.AI from the download page and open it. Create your account when the app asks. Your 7-day trial of Ultimate starts right away.
2. Pick a Scenario from the list at the top of the window. Job Interview is a good first try.
3. Click Listen. To test it without a call, play any interview video in your browser. The transcript fills in as people speak, and their lines are labelled Them.
4. Press Answer after a question, or press its keyboard shortcut from any app. The answer appears in about a second, written the way you would say it.
5. Try typing. Type a question in the box under the transcript, for example "Why should we hire you?", and press Enter.

2. Write a Scenario that sounds like you 10 min

Click ＋ New Scenario, give it a name (for example "Job Interview · Contoso"), and fill in START-HERE.md. Keep it short and concrete: put the instructions here and the facts in files.

# [Scenario name]

## Who I am and what I want
I'm [name], [role]. In this conversation I [situation].
What I want: [your goal, your limits, what success looks like].

## How to answer
- Give me [the exact words to say / a line and bullet points].
- [Length]: short enough to say in [60] seconds.
- Use my documents for facts and numbers. Never invent anything.
- Tone: [warm, confident, concise]. Never [what to avoid].
- When [a specific situation], [what to do].

## Context
[Who's in the room, the agenda, what's at stake.]
<!-- Private notes for you only. They're never sent. -->

1. Add your files with Add files, or drop them into the Scenario folder. They can be your CV, a job description, an agenda, a contract, slides or spreadsheets.
2. Choose the answer style. Pick Spoken script only if you want the exact words, or Line to say + bullet points if you prefer to improvise around the facts.
3. Set the length. For spoken answers, 60 to 120 words is ideal. Go longer for technical topics.
4. Add names and jargon (like "Ionescu, Kubernetes, OTIF"), so that speech recognition spells them right.
5. Test it. Type 3 likely questions and read the answers aloud. If an answer doesn't sound like you, leave the answer as it is. Fix the instructions or the files instead.

3. Prepare for a job interview 20 min

The best thing that you can do is write a stories document. It holds 10 real situations from your career, each with a number in it. OnSubject.AI then finds the right one for each question.

# My career stories

## 1. [Short title] ([year], [company])
Situation: [the problem, with a number if you can]
What I did: [your actions, with "I", not "we"]
Result: [the outcome, with a number]
Good for: [leadership, conflict, failure, turnaround, deadline...]

## 2. A time I failed
Situation: ...
What I did: ...
What I learned: [and what I do differently now]
Good for: [weakness, failure, learning]

1. Create a Scenario for each company, with the job description, the company's site or annual report, and your notes from the recruiter call.
2. Write what you want in the "Who I am and what I want" section: the role, the team, remote days and your salary range. Then, when they ask, you'll have the words ready.
3. Rehearse the night before. Type the questions that you fear, and read the answers aloud. Fix your stories until they sound like you. Then clear the transcript, so that the interview starts as a new conversation.
4. In the interview, press Answer (or its keyboard shortcut) after each question. For a coding exercise or a case on screen, use a part of the screen.

4. Run structured interviews 15 min

1. Put your criteria in files: the job description, a scorecard (competencies and what each level sounds like), your green and red flags, and your question bank.
2. Tell it that you're the interviewer. In START-HERE.md, write: "Never answer for the candidate. Suggest my best next question. Then match what I heard to the scorecard, quoting the candidate's exact words."
3. Write fairness into the rules: "Use only the evidence. Never infer anything from age, accent, gender or background."
4. Let it read the whole interview. Raise the amount of conversation that each answer reads to 60 minutes (Settings › Audio & transcription). Then your summary at the end of the interview covers everything.
5. Before each interview, drop the candidate's CV into the folder. Afterwards, type "summary". The interview is already saved in the Scenario's conversations, ready for the debrief.

See how Priya does it, with her full START-HERE.md →

5. Meetings: answers, minutes and action points 10 min

1. Create one Scenario for each recurring meeting, with the project plan, the budget and the contracts. Update the files before each meeting. Last week's meeting is already there, because the Scenario remembers it.
2. Add 3 rules to START-HERE.md. First, answer questions with our numbers. Second, when a problem comes up, suggest options with their trade-offs. Third, when I type "recap", list the decisions, the action points with an owner and a date, and the open questions.
3. Let it read the whole meeting. Set the amount of conversation that each answer reads to 60 minutes.
4. During the meeting, press Answer when you're asked something. When someone shares a dashboard, use Answer + screen to include it.
5. Before it ends, type recap and paste the result into the team chat. The whole meeting is saved in the Scenario. Save puts a copy wherever you keep your minutes.

In a meeting room without a call, let your phone listen instead.

6. Q&A sessions and debates 15 min

Under pressure, a clear structure helps more than anything else. Give OnSubject.AI a structure that keeps you calm:

## How to answer
- First, acknowledge the concern in one sentence. Never mock it.
- Then give one fact, with its source (document and page).
- Then say what it means for the person asking.
- Use plain words and short sentences that I can say out loud.
- Never promise what isn't in my documents.
- If the answer isn't in my files, say I'll find out and follow up.
- Stay consistent with what I've already said.
- If they use a flawed argument (a logical fallacy), name it gently, in one sentence.

1. Collect the hard questions that people asked before (in minutes, emails and comments), and add them as a file.
2. Write your red lines: the things that you will never concede, promise or say.
3. Rehearse with someone who plays your toughest critic and types their questions.
4. On stage, keep your phone on the lectern and let it listen. The answers appear on the phone and stay off the projector.

7. Screens and photos 3 min

1. Answer + screen adds a screenshot of your monitor to the question. Choose the monitor in the ▾ menu next to the button. The menu shows a small picture of each one.
2. A part of the screen is in the same menu, and it has its own keyboard shortcut. When you use it, OnSubject.AI hides, the screen freezes, and you draw a box around the question. Move the box or resize it, then press Enter.
3. Use the same area again. OnSubject.AI remembers it. Press the keyboard shortcut, then Enter. This works well for a test that shows one question after another in the same place.
4. For paper or a whiteboard, tap Photo on your phone and choose Camera. Then tap anywhere on the screen to take the picture. It's answered at once.
5. From your phone, Photo › Screenshot answers with a screenshot of the PC, like Answer + screen. With 2 or more monitors, the phone shows a picture of each one, and you tap the one to capture.

8. Your phone as a companion 2 min

1. On the PC, turn on Settings › Phone › Let my phone connect. When Windows asks, allow OnSubject.AI on private networks.
2. On the phone, scan the QR code. The phone must be on the same Wi-Fi as the PC. The first time, the browser shows a warning. Tap Advanced › Proceed.
3. Optional: install the certificate from the setup page, so that the warning goes away for good. You can also add OnSubject.AI to your home screen.
4. To listen in a room, tap Listen and keep the phone near you, away from loudspeakers. After a few lines, it knows which voice is yours.
5. Swipe through the previous answers left and right, and the PC follows along. Tap a line to fix a word, or swipe a line left to remove it.
6. Close the PC's window if you like. OnSubject.AI keeps running in the background, and your phone shows everything.

Everything about the phone companion →

9. Big document sets and code repositories 10 min

1. Link a folder in the Scenario editor (Link a folder). It can be a knowledge base, a shared drive or a code repository. OnSubject.AI uses it where it is. To read only some types of files, add patterns like *.md;*.pdf or *.cs;*.md.
2. Let it index. Big sets are read once and indexed on your PC, which makes them quick to search. After that, only the files that changed are read again. The status bar shows how many documents are ready.
3. Add a map. At the top of the folder, put a README that explains what's where. It becomes a core document, which means that every answer reads it and knows where to look.
4. Ask precisely. If an answer misses the mark, type the key term, the ticket number or the product name in the question box. Deep search (on Pro and Ultimate) opens more documents when it needs to.

10. Make the transcript work for you 3 min

• Fix a misheard word by clicking the line and typing. Answers use your version.
• Remove noise and small talk with the ✕, so that answers focus on what matters. Undo brings it back.
• Answer an older question with the answer button on its line.
• Start a new conversation with Clear transcript between calls. The previous one stays saved in the Scenario.
• Click a follow-up question under an answer. It is added to the transcript as Follow-up and answered at once.
• Remove an answer that you didn't use (🗑), so that follow-ups don't build on it.
• Turn on the microphone (with headphones) when your own words matter for the next answer.

11. Hotkey cheat sheet

Every global shortcut can be changed or turned off in Settings › Hotkeys.