You do it yourself
- Evenings and weekends go on invoices, replies and reminders.
- The routine exists only in your head.
- Nobody takes over when you are away.
You explain how the work is done. The agent is built while you talk, then handles the routine work. Nothing is sent or booked until you say yes.
Invoices in the sandbox
Drawn view with example data: this is what a run looks like in the sandbox.
Coming December 2026You connect them yourself, with your own account. Each connection declares what it may read and write before you say yes.
Every routine costs something: evenings, a salary or the work that never gets done. Here is how the three most common ways of getting the work done compare.
The comparison is general. Use your own figures in the calculator further down.
You need no IT department and no code. Agentsmedjan is made for the person who owns the process, the person who approves and the person who reviews, and for you if you want help with your own day-to-day.
Invoices read and posted, ready to approve, instead of an evening of PDFs.
Invoice, amount and account on one screen. Approve, edit or reject.
Every decision in an exportable log that cannot be changed afterwards.
The spec in YAML, versioned. Yours, exportable, readable.
Two agents for your own inbox and your bookings, paid by card, no lock-in.
The example is supplier invoices, something nearly every company spends time on every month. The film shows the whole way, from the first question to the first invoice that is booked after your yes.
AgentsmedjanWhat should the agent do?
Take care of the supplier invoices: read them, post them and book them once they are approved.
AgentsmedjanHow do the invoices come in?
As PDFs to our invoice email address.
AgentsmedjanHow do you know which account an invoice goes to?
It depends on the supplier. We follow the BAS chart of accounts in Fortnox.
AgentsmedjanWho approves them, and what do you do when something is wrong?
Hanna approves everything. If something is missing I ask whoever placed the order.
What I understood
Examples from last month
Run the examples to see what the agent does with them. Nothing is booked for real.
Handed over · Propose the posting
LF-1045 · Exempel IT AB
The supplier has no account in your chart of accounts yet. The agent did not guess: it handed the invoice over to you.
Would have booked · LF-1043Mocked
| Account | Debit | Credit |
|---|---|---|
| 6110 Office supplies | 3,480.00 | |
| 2641 Input VAT | 870.00 | |
| 2440 Accounts payable | 4,350.00 |
The voucher is created only once the agent is in production and the invoice is approved.
Waiting for your approval
Exempel Kontorsvaror AB · SEK 2,990
Booked and logged
Productionno invoices yet today· SEK 46 this month
A drawn film with example data. It will be replaced by a recording from the product once the interview and the sandbox are live.
Approval before every outgoing action is a rule in the spec today, and will be enforced by the engine when production opens. Your data is stored in Stockholm.
An exportable log that only grows. Off switch and pause per agent. AI calls in the EU with no storage and no training on your data.
The agent posts the invoice. It is booked only once someone has approved it.
Coming early 2027Off switch and pause per agent, right on the card.
Coming spring 2027Production 9 invoices today
The DPA and the terms are accepted when the organisation is created.
Coming when production opensEvery decision in an exportable log that cannot be changed afterwards.
Coming December 2026The sub-processors are listed with their regions on the security page.
Log, process document, spec and examples.
For the owner, the auditor and the new colleague, always up to date when the agent changes.
The overview shows every agent: its status, today’s runs, what is waiting for your approval and what the agent has cost this month. The off switch is on the card.
Drawn view of the overview in the app. Screenshots with demo data will replace it before launch.
Templates for routines most people will recognise. The interview adapts them to the way you work.
Reads the invoice, proposes the posting and books it once it is approved.
Finds overdue invoices and writes the reminder. You approve before it is sent.
Sorts the inbox: what needs a reply, from whom and with what information.
Takes in the claim, fetches the delivery and warranty period, suggests an action and a reply.
Answers booking requests and reminds you of follow-ups, for you as a private individual.
Reads the change order request, looks up the project and prices, writes the reply. You approve.
A worked example of the time an agent frees up, with your own figures.
Run. One case the agent takes care of from start to finish, for example an invoice that is read, posted and handed over for approval. Each such case counts as one run, however many steps it has. Re-running the same example in the sandbox does not count.
Hours = cases × 4.33 × (minutes today − minutes with an agent) ÷ 60. SEK = hours × hourly cost.A worked example, not a promise. Measure it yourself: the sandbox shows what the agent does with your own cases.
Building and testing the agent costs nothing, for as long as you like. You start paying when the agent is connected to your real systems and begins working for real. That is what we call production.
Production opens for pilot companies in spring 2027.
Run. One case the agent takes care of from start to finish, for example an invoice that is read, posted and handed over for approval. Each such case counts as one run, however many steps it has. Re-running the same example in the sandbox does not count.
One process in production. The owner and a colleague approve.
Agent in production. An agent is a digital colleague that handles one routine for you, such as supplier invoices. In production it works for real in your systems. A draft is built and can be tested on examples, but does nothing for real.
Run. One case the agent takes care of from start to finish, for example an invoice that is read, posted and handed over for approval. Each such case counts as one run, however many steps it has. Re-running the same example in the sandbox does not count.
Users. The people at your company who can sign in and approve what the agent proposes, such as approving an invoice. Everyone who approves counts as a user.
Price published when production opens
Register interestSeveral processes, several approvers. The typical plan for 5–49 employees.
Agent in production. An agent is a digital colleague that handles one routine for you, such as supplier invoices. In production it works for real in your systems. A draft is built and can be tested on examples, but does nothing for real.
Run. One case the agent takes care of from start to finish, for example an invoice that is read, posted and handed over for approval. Each such case counts as one run, however many steps it has. Re-running the same example in the sandbox does not count.
Users. The people at your company who can sign in and approve what the agent proposes, such as approving an invoice. Everyone who approves counts as a user.
Support. The help centre is guides and answers to common questions. Email is a reply from a person within the stated time. Priority means your case is taken before others.
Price published when production opens
Register interestThe whole business on agents. SLA, a named contact and self-hosting.
Agent in production. An agent is a digital colleague that handles one routine for you, such as supplier invoices. In production it works for real in your systems. A draft is built and can be tested on examples, but does nothing for real.
Run. One case the agent takes care of from start to finish, for example an invoice that is read, posted and handed over for approval. Each such case counts as one run, however many steps it has. Re-running the same example in the sandbox does not count.
Users. The people at your company who can sign in and approve what the agent proposes, such as approving an invoice. Everyone who approves counts as a user.
Custom connections with a permission declaration. You can build a connection to a system we do not have ready. Each such connection declares what it may read and write before someone at your company approves it.
SLA and named contact. An SLA is a written agreement on response times and availability. A named contact is a person at our end who knows your setup and whom you contact directly.
Price published when production opens
Register interestFree forever: the interview, the canvas and the process document, with 3 agents in draft and 50 sandbox runs per month. For individuals there is the Personal plan with two agents, paid monthly by card with no lock-in. See the Personal plan
No. You answer questions about how your team works today. The spec is there for anyone who wants to read it, but nobody has to write code.
No. Everything that leaves your company goes through an approval. It is a rule in the spec today and will be a rule in the engine when production opens, not a setting that can be forgotten.
In Stockholm. AI calls are made in the EU, with no storage and no training on your data. The sub-processors are listed with their region on the security page.
Fortnox, Microsoft 365, Google Workspace (Gmail, Calendar, Drive), email and webhooks first; REST/OpenAPI and database reads from the Team plan up. You connect them yourself, sign in with your own account and see what each connection is allowed to do.
A trigger that starts the agent and reaches an end: done, handed over to a person, or rejected. Reruns in the sandbox do not count.
It pauses and hands over to the person you have chosen, with a summary of where things stand. The process continues manually until you say otherwise.
Yes. When you leave, you get the log, the process document, the spec and the examples. Your data is deleted 30 days after the agreement ends, with written confirmation.
Yes, with the Personal plan: two agents for your own errands, card payment, no lock-in. It opens together with production.
Build your first agent in a conversation. Run it with approvals, a log and an off switch.