Murmel Teams: one pool of minutes for your whole team

Until now, Murmel was built for one person with one account. That worked fine for the freelancer and the researcher, but not for the newsroom where four people work through interviews, or the municipality wanting to give twenty colleagues access. They ended up with four separate subscriptions, four invoices, and nobody with a view of the usage.

That changes today. With Murmel Teams you buy a plan for a number of seats, invite colleagues by email address, and share a single pool of minutes.

Why the pool is shared

This is the most important design decision, and it nearly went the other way. Giving everyone their own monthly quota was the obvious route: easier to explain, easier to build.

It just does not match how teams work. In practically every team I spoke to, one person does the bulk of the transcribing. The researcher running forty interviews this month hits the limit halfway through, while three colleagues barely touch their quota. With a personal allowance, that one heavy user is blocked while the team as a whole still has hours to spare.

So the pool belongs to the team, not to the person. Twenty Creator seats give twenty times forty hours per month, in one pot. Who spends it does not matter. Every month it is topped back up in full.

What it costs

The plan price times the number of seats, and nothing else. There is no separate team price list and no surcharge for collaborating:

• Basic from €9 per seat per month, 12 hours per seat
• Creator €29 per seat per month, 40 hours per seat
• Pro €59 per seat per month, 100 hours per seat
• Scale €99 per seat per month, 200 hours per seat

All amounts excl. VAT. Pay a full year up front in a single payment and 20% comes off, putting Basic at €86.40 per seat per year instead of €108.

One caveat, because it would otherwise be a surprise: paying yearly keeps the pool a monthly budget. You pay for the year in advance, but you do not receive twelve months of minutes on day one. The pool resets every month, exactly as it does on monthly billing, so a busy spring cannot drain the autumn.

Adding colleagues

As team administrator you enter email addresses, several at a time. Everyone receives an invitation link. If someone has no Murmel account yet, one is created the moment they accept: no separate sign-up beforehand.

A pending invitation holds the seat, so you can never hand out more than you bought. Only once someone accepts is the seat actually occupied, and withdrawing an invitation frees it again.

The team overview shows how many minutes each member used this period. Not to keep score, but because with a shared pot you want to see where it goes, and whether more seats are needed.

Adding seats and cancelling

If the team grows, buy extra seats: you pay pro rata for the rest of the period and the pool grows straight away. Shrinking takes effect at the next renewal, since the current period is already paid for. You can cancel up to the next charge, and the team keeps working until that period ends.

Paying by invoice

Municipalities, universities and healthcare organisations rarely pay by credit card. For them a team can run on invoice: get in touch with the number of seats and the plan you want, and the team will be set up with an invoice to follow. A data processing agreement (GDPR), help with a DPIA and a tailored SLA are all negotiable.

What does not change: audio is processed in the Netherlands, is not used for AI training unless you explicitly enable it, and is deleted after 7 days by default. That applies to every team member just as it does to an individual account.

Get started

Set up your team at app.murmel.nl/teams. Pick a plan, pick the number of seats, and invite your colleagues. The pool is available immediately.

Run into something, or does the model not fit how your team works? Let me know through the contact form. The shared pot exists because users explained why a per-person quota breaks down in practice.