Tutor playbook
How to learn with Freya Larsen
A practical, profile-specific playbook for learning Economics basics, business math, spreadsheet reasoning, data-informed decisions with Freya Larsen through focused chat, voice lessons, classroom tools...
Freya Larsen
Economics and business math tutor
On this page
Best fit
Is Freya Larsen right for your goal?
Learners who want numbers to feel practical instead of abstract.
- Learning focus
- Economics basics, business math, spreadsheet reasoning, data-informed decisions
- Best level
- High school, college foundations, and adult learners
- Lesson format
- Scenario walkthroughs, spreadsheet examples, chart interpretation
- Languages
- English, Danish basics, Swedish basics
Lessons use vivid examples and creative connections, turning abstract ideas into material the learner can picture and remember.
- Microeconomics basics
- Business math
- Percentages and rates
- Spreadsheet reasoning
- Chart interpretation
Before lesson one
Plan a focused first session
Specific evidence gives Freya a better starting point than a broad request to teach the whole subject. Use this four-part setup.
-
Arrive with evidence
Bring a code sample, error, command, diagram, dataset, requirement, or system behavior. A real sample gives Freya something concrete to diagnose.
-
Define one result
Aim for one working technical artifact plus a clear explanation of why it behaves that way. Put that result in the Plan tab before expanding the lesson.
-
Attempt before the model
Show what you currently think or can do. Ask for a hint or question before requesting the completed answer.
-
Leave with retrieval
Explain the lesson back, save the hardest point as a review card, and schedule the smallest useful follow-up.
Choose the right lesson mode
Text chat
Pasting errors, comparing approaches, reviewing code carefully, and preserving exact commands or explanations.
Paste the exact material and state the feedback format you want.Voice call
Thinking through architecture, explaining a bug aloud, interviewing, and checking conceptual understanding.
Think aloud and ask Freya to pause after each correction or question.Classroom
Shared code, architecture diagrams, debugging traces, documentation, and testable worked examples.
Share each workspace explicitly so the tutor can see the latest version.Repeatable value
Use Freya's lesson rhythm
A good session should produce something you can attempt, inspect, and revisit. This profile is designed around the following rhythm.
- Start
- Pick one confusing business or economics problem and name the decision hidden inside it.
- Work
- Scenario setup, formula walkthrough, chart check, interpretation, and one explain-it-back prompt.
- Continue
- Small spreadsheet tasks, chart notes, and short decision summaries.
Collaborative classroom
Use each classroom tool with a purpose
The whiteboard opens as the main lesson surface. Workspaces are shared deliberately: use Show tutor or Update tutor after changing the board, Notebook, Document, Code Lab, or SVG Studio so Freya sees the current version.
Whiteboard
ClassroomTrace state, data, control flow, dependencies, and assumptions before changing code or infrastructure.
Best move: Draw or place the first version yourself, then use Show tutor or Update tutor so Freya can respond to the current board.Code Lab
ClassroomUse Code Lab for the smallest reproducible example, keep line numbers visible, and ask for tests or checkpoints before a full solution.
Best move: Keep one task active, ask for the smallest useful hint, and make a second attempt before requesting a complete model.Practice
ClassroomPredict the result first, run or inspect the example, explain the difference, and then solve one nearby variation.
Best move: Ask Freya to adjust difficulty after each attempt and explain the exact cue that should transfer to the next example.Notebook and Document
ClassroomKeep a debugging log with symptoms, hypotheses, evidence, the smallest useful change, and the lesson to reuse later. Write the requirement, architecture decision, API contract, or explanation beside the implementation so intent stays testable.
Best move: Keep your wording and decisions visible. Share the workspace with the tutor before asking for a revision or structured feedback.Review Cards and Transcript
ClassroomSave commands, patterns, failure modes, and explain-it-back questions as review cards after the code works.
Best move: At the end, turn only the highest-value ideas and repeated mistakes into cards, then use the transcript to recover evidence or phrasing.SVG Studio
ClassroomTurn architecture, data flow, state, and dependencies into a clean diagram that stays beside the code.
Best move: Ask Freya to label boundaries and failure points, then explain the diagram without looking at the implementation.Freya's methods
Profile-specific teaching tools
These methods come directly from this tutor profile. The surface label shows where to make the result visible during a classroom lesson.
AI board
Builds tables, formulas, and chart explanations step by step.
Try it with Microeconomics basics in Whiteboard, make one attempt yourself, then ask Freya to correct only what blocks the next step.Scenario desk
Turns word problems into business cases with clear variables.
Try it with Microeconomics basics in Practice, make one attempt yourself, then ask Freya to correct only what blocks the next step.Practice mode
Creates similar economics and business math exercises with hints.
Try it with Microeconomics basics in Practice, make one attempt yourself, then ask Freya to correct only what blocks the next step.Ready to use
Prompts that fit this tutor
These prompts use Freya Larsen's actual subjects, lesson format, and adaptive classroom lab. Replace the topic with your own material when needed.
Pick one confusing business or economics problem and name the decision hidden inside it.
I want to improve Microeconomics basics. Use Scenario walkthroughs, spreadsheet examples, chart interpretation. Check what I can already do, let me attempt something, and give one correction at a time.
Open Code Lab for Business math. Keep the task small, make me explain my choices, and finish with three review cards and one next-session goal.
Progress evidence
Know whether the lessons are working
Do not measure progress only by how clear the explanation felt. Look for changes in what you can retrieve, decide, produce, or explain without support.
- Predicts behavior before running the example
- Finds the failing boundary with fewer hints
- Explains tradeoffs instead of naming tools only
- Builds a nearby variation without copying the model
Responsible use
Use Freya as a tutor, not an authority
Supports learning and analysis practice; does not provide financial, tax, legal, or investment advice.
Freya is a fictional AI tutor profile for economics, business math, and spreadsheet learning support.
Put the guide into practice
Start one focused lesson with Freya
Bring one real example, choose one result, and keep your first attempt visible. You can review the full profile before opening chat or voice.