Örlög — a Skald product
A guided interview about how your business actually works, and a complete multi-agent architecture in return — named roster, governance, cost guards, and the order to build them in.
Free to complete. You only pay if you want the document.
Before you answer anything
Pick whichever business is closest to yours. These are worked examples, not output from your answers — but they are the real structure, at the real level of detail.
Closest to your business
A roster of this shape
Eir
Support replies · build first
Drafts answers from your own course material, and cites the page it used
Heimdall
Inbox triage
Sorts the overnight pile into three stacks before you open your laptop
Snotra
Billing sorter
Batches pause and refund requests into one list you clear in a sitting
Bragi
Repurposing
Turns the newsletter you already wrote into the week of captions
Norse theme · 4 agents · sized to a $150/month budget · hub and spoke
To be straight with you: yours will not look like any of these. That is the point — the roster comes out of your own walkthrough of your own worst task, which is why the interview asks for one. It takes under ten minutes, and the document is built while you wait.
Örlög
or·lög · Old Norse
In Old Norse, örlög is the primal law — the foundational layers laid down at the beginning, before anything grows. Ör, original. Lög, law, layers, the same root as our word law.
It is what the Norns draw from when they carve a person’s fate. The wyrd is the living weave, always moving. The örlög is the pattern underneath it — the terms set down first, from which everything else unfolds.
Which is exactly what you are handed here. The roster, the governance, the constraints, decided before anything runs. The blueprint is your örlög. The business you build on it becomes your wyrd.
The method
There is a version of this product that reads your answers and returns something confident and generic — six agents with sensible names, a paragraph each, nothing you could not have written yourself after an afternoon of reading. That version is easy to build and worth nothing.
The difference is in what the system refuses to do. Every agent you are given carries an explicit list of what it is not responsible for, drawn from the red lines you named. Every one has a rule for what happens on a bad day — when the tool is down, when the answer is not in your material, when the question is one it should not touch.
An agent that ends its turn having produced nothing is how work silently stops. An agent that invents an answer to avoid that is worse.
That principle, and the dozen behind it, came out of running a real multi-agent system in production — the escalation caps, the spend breakers, the roster design rules. Not theory. Encoded operational experience, applied to your business rather than a hypothetical one.
What arrives
Three to seven named agents. Charter, inputs, outputs, and what each one must never do — the field that stops an agent drifting into work you would never have given it.
How they coordinate, what happens when one fails, the escalation cap that stops a stuck loop becoming an invoice, and where you stay in the loop.
A per-task ceiling, a daily breaker, and a three-month forecast. Real numbers you can set today, not a range.
Click-by-click setup for your technical level, the exact first message to send each agent, and what a good answer back looks like.
Thirty, sixty, ninety days — starting with the single agent that buys back the most time, and nothing else until that one works.
The honest comparison
Including the row where this one loses.
| Free tutorials | A consultant | Trial and error | Örlög | |
|---|---|---|---|---|
| Costs | Nothing | $10,000+ | Months, plus API spend | $99–$555 |
| Fits your business | No — written for everyone | Yes | Eventually | Yes — built from your own answers |
| Says what agents must not do | Rarely | If you ask | You find out the hard way | Every agent, every time |
| Sets spend limits | No | Sometimes | No | Three real numbers, sized to your budget |
| Someone to ask afterwards | No | Yes | No | On the reviewed tier, yes |
| Builds it for you | No | Yes | You are building it | No — you get the plan, not the system |
Who made this
The methodology behind Örlög is not a framework I read about. It is what was left after running a multi-agent system through real operational pressure — the rules that held, and the ones that had to be added after something broke.
That is also why the document tells you what it cannot do. I would rather sell you something honest about its limits than something impressive that leaves you stuck in week two.
— Rachel
What it costs
Every tier gets the full architecture. What changes is how much of the standing-up you do alone.
Blueprint
$149
The full architecture, and everything you need to stand it up yourself.
Blueprint+
$249
Everything above, plus the prompts you will actually use every day.
Reviewed
$555
Blueprint+ with a written pass from Rachel, and one revision.
5 per week — a real calendar
We build the first agent together, and shape the engagement around what you actually need. It starts with a conversation rather than a checkout page.
Questions
The interview is fourteen questions and most people finish in under ten minutes. The document is generated while you wait — a minute or two — and you can close the tab; it finishes without you and is there when you come back.
No. Örlög generates the architecture — nothing to host, nothing that breaks at two in the morning. You get the plan and the setup instructions.
That is the default. The interview asks your comfort level and the setup instructions change accordingly — the no-code track is click-by-click, with the exact first message to send each agent.
Then we will not write you a document. If there is not enough there to build something specific, you get one follow-up question rather than something generic. That is a deliberate choice and it costs us sales.
You will see your agents named, and your own business restated back to you, before any card comes out. If that restatement does not sound like your business, do not pay us.
Begin the interview