For owner-led firms of 5 to 50 people whose work runs on what a few people remember.
Bilið · The gap
Everything the firm knows lives in a hundred places.
- the quote no one can reconstruct
- the thread on somebody else’s laptop
- what was agreed on the call
- four years of project files
- the client’s whole history, in one head
- the lesson from the job that went wrong
And every AI meets your firm as a stranger. Brilliant, willing, and blank. It knows nothing of how you work, who you serve, or what you have already decided.
You do not need another app. You need a system built around the way your firm actually works.
What is missing is not intelligence. It is a foundation.
Kerfið · What it is
Your company’s own intelligence infrastructure.
Your work, your people, your clients, your history and the way this firm decides, brought together into one living system the company owns. Not an archive. The foundation your firm’s intelligence can build upon.
Where your work already lives. Read as it is, left where it is.
The firm’s agent and routines. While the office sleeps, it continues.
Voice or text, wherever they are.
One private system. One shared record. Entirely the company’s.
Verkin · What becomes possible
What becomes possible.
Proposal memory
The next proposal knows the last ones.
Past proposals, the client’s own language and the reasoning behind old pricing, assembled into a draft a person finishes and signs.
Client intelligence
The client’s whole history, in one view.
What was promised, what changed and why the work is shaped this way, drawn from the record the firm already owns.
Decision continuity
The reasoning survives the meeting.
Why the firm decided what it decided, kept with its sources, so nothing rests on one person’s memory.
Straumurinn · The inflow
And the firm’s world flows in on its own.
What flows in
- Company mail
- Calendar
- Meeting transcripts
- Voice notes
- Files
What comes back
- Knowledge
- Commitments
- Preparation
- Drafts
Mail, calendar, meeting transcripts, voice notes and files flow into the firm’s foundation, and come back out as knowledge, commitments, preparation and drafts ready for a person to sign.
Each source flows in only after the company connects it, and each person’s mail only with that person’s consent.
Sönnunin · The proof
The proof, before the commitment.
You should not have to buy a category to believe it. So the proof comes first.
First you are shown a system that already runs: the one this practice is built on, doing real work live. Then one real job of your firm’s is done from evidence the firm already owns. You see the result, then where every important claim came from, then a plain statement of what was deliberately left out.
What you send
- One live jobwork the firm already does, with a deadline
- A bounded set of sourcesa small pack, agreed in writing
- One voice notehow the work is done today
What comes back
- The work, completeddrafted from your own record, for a person to sign
- The source lineagewhere each important claim came from
- The boundarywhat was deliberately left out
No record is kept, nothing stays connected, nothing is deployed. The honesty is the mechanism: what the proof withholds is the reason the foundation exists.
Smíðin · The build
Built with you, from your firm’s own words.
We talk.
We build.
We do the first real piece of work together.
We stay while it becomes a habit.
Then we hand over the keys.
The first piece of work is chosen with you before anything is built: a job the firm already does every week, where the reasoning lives in people’s heads and the output has a deadline attached.
- The owner and a small trusted group
- Connectors that read where the firm already works
- Drafts a human signs
- One gated write path
- Routines that continue on their own
The first project, done together. Always real work, never a demo.
The keys become the company’s. The architect stays: it is part of your system, not part of us.
Frelsið · Why it remains yours
Software gives your firm access. Edda gives your firm ownership.
- Their platform
- Their ecosystem
- Their lifespan
- Your server
- Portable files
- Your foundation
Your Edda lives on infrastructure the company controls. You decide which services it connects to and what information may pass to them.
Firms where the reasoning behind a quote, a proposal or a decision lives in someone’s head, and where losing that person would cost real money. They do not need another app. They need a system built around the way the firm actually works. Every Edda is built personally, one company at a time. That keeps the number small by design.
A note from Kormakur
I first built Edda for myself. I was running several businesses at once, with years of conversations, documents, decisions and ideas spread across too many places. I did not need another tool. I needed one foundation beneath all of it. Today it runs beneath everything I do. What you are reading about is that same foundation, built for a company instead of a person: the same principles, the same craft, and the same handover at the end.
If this sounds like the foundation your firm has been missing, we should talk.
Reading this for yourself? Edda for Individuals.