Mo prepares. You decide.

Mo is the assistant inside BrauMo. It answers questions about your brewery, prepares your morning, reads your documents into forms, drafts your paperwork and watches your cold room. Nothing an AI proposes applies by itself: you check it, then you save it.

Email and the business tick at Polar, then the download. Your 21 days start when you first open the app.

Every part is off until you switch it on AI jobs run on your own Anthropic key, with a daily limit you set Nothing an AI proposes saves itself
Mo at work in two and a half minutes. Real app screens, AI voice. Screens on this page are from a sample brewery. Where a screen shows Mo reading or writing, the words are an example.

What Mo does

Answers your questions

Ask in your own words. Mo looks things up in your records, answers in your language, and proposes changes you confirm.

See how

Reads your documents

A photo or PDF of a delivery note, a bill, an order or a certificate fills the form for you to check.

See how

Drafts your paperwork

A first draft of a corrective action, an SOP, a month in review, a sell sheet or a message to a customer.

See how

Works with your own AI

An AI client you already use reads BrauMo through Agent access, read-only. Anything it suggests waits for your approval.

See how

Prepares your morning

Seven routines make tasks, draft orders, follow-ups and a brief before you open BrauMo. Only the weekly review needs an AI key.

See how

Works without AI

Bank statements match supplier bills. Sensors watch your cold room and your tanks. A stalled ferment lists what to check.

See how

Ask Mo about your brewery

Mo is a chat inside BrauMo. Ask in your own words, in your language. When a question needs a number, Mo looks it up in your own records and answers from what it finds. It uses your own Anthropic key.

  • Production

    Batches and every reading on them, tanks and what is in them, recipes, ferment forecasts.

  • Stock

    Levels, lots near best-before, burn rate and run-out dates, and what the planned brews will need.

  • Quality

    What needs attention, each batch's CCP evaluation, the monthly scorecard, each recipe against its own history, loss and yield.

  • Sales and money

    Open invoices, what was delivered, and customers against their own ordering rhythm. A role that sees no prices is not shown these.

  • Where a number comes from

    What is drifting, and how an estimate is worked out: the forecast, the alcohol ceiling, evaporation, and where each one stops meaning anything.

What a lookup returns goes to Anthropic with your question, under your own agreement with them.

Mo's chat: a question about what to look at first, and Mo's answer from your alerts and your stock: the stalled ferment, readings due, the cold-room excursion, overdue invoices and two items low on stock.
An example: Mo looks up your alerts and your stock, then answers from what came back.
The AI assistant card in Settings, Alerts and Mo: the switch that enables Mo, the key field, the model picker, the daily question limit and the switch that lets an AI propose changes.
Settings, Alerts and Mo, AI assistant: the model, the daily limit and the switch that lets an AI propose changes.

Your key, your model, your limit

Mo runs on your own Anthropic key and you pay Anthropic per question. Pick the model that suits your budget: Claude Opus 5.5, Sonnet 5.5 or Haiku 5.5.

Set a daily limit; 0 means no limit. Every AI job counts against it. Switch Mo off and it makes no network calls.

Mo answers in the language you write in, and knows BrauMo itself, so it can tell you which screen to use.

Mo remembers

The conversation carries on where you left off. Tell Mo to remember something, or add a note yourself, and Mo honours it in every chat.

You can clear the conversation. The notes stay until you delete them.

The Things Mo remembers card on Mo's page: two notes, one typed by the brewer and one kept by Mo, and a field to add another.

Mo proposes. You confirm.

Tick “Let an AI propose changes” and Mo can suggest changes in the chat. Each one is its own card with Confirm and Dismiss. Nothing is saved until you click Confirm.

Mo's chat with two proposed cards: log pH 3.4 and Brix 5.5 on a batch, and draft a purchase order for 50 kg of cane sugar, each with Confirm and Dismiss buttons.
An example: Mo finds the batch in Fermenter 2, then proposes two cards. Each waits for its own Confirm.

Never an issued invoice, a HACCP or compliance record, a user, a deletion, a payment or anything that sends. A task or draft order made this way can be undone from Done for you. The two cards that touch money are not offered to a role that sees no prices.

Log a reading

pH, Brix, SG, TA or temperature on an existing batch.

Start a batch

From a recipe, in a tank, at a volume.

Add a task or a note

With a due date and a priority, so it lands on your task list.

Remember something

A durable note Mo honours in later chats.

Draft a purchase order

A draft only. Nothing is ordered or paid.

Record a supplier bill

From the supplier, the amount and the due date you give.

Change a setting

One of nine preferences, such as the date format, the temperature unit or the default starter share. Shown as now and would become.

Change a recipe target

One of nine QC targets, such as target pH or Brix. Never the ingredient rates or a declared limit.

Import stock or recipes

From a CSV, Excel or text file you attach, one sheet and up to 200 rows. You review the whole list first.

Send a photo. Check the form.

With your own Anthropic key, Mo reads a document into the form that records it. Every field Mo filled is tinted. Nothing is saved until you save the form. Photos go without their location.

A goods receipt form filled from a delivery note: supplier, lots, quantities and best-before dates tinted, with a note that one line matched no stock item.

Goods in

A photo or PDF of the delivery note becomes a goods receipt: supplier, lots and best-before dates. What Mo could not match is listed for you.

A supplier bill form filled from an invoice: supplier, invoice number, amount and date tinted for checking.

Supplier bills

The invoice fills the bill: supplier, number, dates and the amount to pay.

A new order form filled from a customer's e-mail: the customer and two quantities tinted, with notes that three cases of 24 are 72 bottles.

Customer orders

An e-mail, a message or a photo of an order becomes a new order or delivery. BrauMo finds the customer itself, so the model never sees your customer list.

A lab result form filled from a certificate, with a note that the certificate names another batch than the sample.

Lab certificates

The certificate fills a sample's result and report number. A certificate for another batch is pointed out.

A supplier's edit form filled from its organic certificate: the certificate number and the end date of the approval tinted.

Supplier certificates

Number and end date go into the supplier's record. A certificate issued to another company is pointed out, and approving the supplier stays your tick.

A stocktake count filled from a photo of a shelf: two counted quantities tinted, and notes on what the photo could not count.

Shelf photos

Photograph a shelf and Mo counts what it can into an open stocktake. What it cannot count is said, never guessed.

One card with three tank readings read from a single typed line, ready to check and save.

The whole tank round in one line

Type “T3 pH 3,2 brix 6,1; T5 TA 4,5” and check one card. BrauMo's own parser reads it first, and Mo reads only what it leaves. Works without a key.

Mo's chat: a photo attached to a question, Mo's answer, and a card proposing a maintenance task with Confirm and Dismiss buttons.

Photos and PDFs in Mo's chat

Attach a photo or a PDF and ask. A task Mo suggests waits for your Confirm, then is listed under Done for you with an Undo.

Mo writes the first draft. You make it yours.

With your own key. A draft is advice: you copy it, edit it and save it yourself.

A corrective action with Mo's draft: three possible causes to check, and the correction, corrective and preventive action tinted. The root cause is left empty.

Corrective actions

The correction and the actions, with possible causes as things to check. Never “the root cause”: that finding is yours.

A standard operating procedure drafted by Mo: purpose, scope and responsibilities, to copy into your own document.

Procedures (SOPs)

A procedure from your own lines and control limits, to copy into your own document.

A product sell sheet with a description for trade buyers drafted by Mo, tinted for checking.

Sell sheets

A product description for trade buyers, without prices. A word that reads as a health claim is flagged.

The month in review: a table of revenue, cost of goods, margin, supplier bills, litres packaged, losses and yield beside the month before, and a short summary written from those figures.

Month in review

A few sentences on Money, written only from the figures beside them.

A check-in message drafted for a customer due to reorder, with a subject, a message and buttons to copy it or open it in your own e-mail.

Check-in messages

A message to a customer who is due to reorder, from the products and quantities they usually take. Never their name: BrauMo adds it. BrauMo never sends it.

A batch page's not-acidifying notice: pH 4.5 after 5 days against a limit of 4.2, the starter share, starter pH and temperatures beside the recipe's own values, and Mo's suggested things to check.

What to check first

On a ferment that is not acidifying, BrauMo lists the facts beside your own limits. Ask Mo, and it suggests where to start.

Your own AI can read your brewery too

An AI client you already use, such as Claude Desktop or Claude Code, can read your brewery through Agent access. It is read-only, and anything it suggests waits for your approval in BrauMo.

Agent access

A card under Waiting for your approval: a reading proposed by an AI client for a batch, with the values BrauMo worked out, and Approve and Reject buttons.
A suggestion from an AI client waits as a card. Nothing is saved until you approve it.

Your day is prepared before you open BrauMo

Seven routines, each with its own tick under Settings, Alerts and Mo. All are off until you tick them. They start after 06:00, and only the weekly review needs an AI key.

The Morning brief card on the BrauMo dashboard: a short text from Mo on a ferment that has not acidified, a cold-room excursion, readings due and what was prepared overnight, then the counts: 7 done for you, 1 waiting for you, 2 customers due to reorder.
The morning brief on the dashboard, with a count of what Mo made and what waits for you.
  • Morning brief

    What is due, what was prepared and what waits for you, on the dashboard and in your digest. With a key, Mo words it from production facts only.

  • Cleaning tasks

    A task for each tank that needs cleaning.

  • Reading round

    The day's readings as one task, listing the tanks that are due.

  • Restock drafts

    Once a week, a draft order per supplier for what the buy list says. Nothing is sent.

  • Quote follow-ups

    A task for each quote nobody answered for a week.

  • Brew suggestions

    A planned brew when a product will run out before a new batch could be ready, worked out from your own sales and batch times. It always waits for your approval.

  • Weekly review

    Last week's production in a few sentences, written overnight at half the usual price. Needs a key.

The Morning shift card in Settings, Alerts and Mo: seven routines each with a tick, two ticks to apply tasks and restock drafts on their own, and the hour the routines run from.
Settings, Alerts and Mo, Morning shift. One tick per routine, and the hour is yours to set.
Mo's page: a brew suggestion waiting for approval, last week's review in a few sentences, and the Done for you list of tasks and draft orders, each with an Undo.
A brew suggestion waits for approval. Below it, last week's review and what Mo made, each with an Undo. The task somebody has since used says why it stays.

Let Mo make tasks and restock drafts on its own

Tick “apply on their own” and Mo makes tasks and restock drafts without asking. Nothing else is ever made automatically. A brew suggestion always waits for you.

Everything Mo did is listed under Mo, Done for you, each with an Undo. Undo is refused once somebody has changed or used the record.

Automation that uses no AI

These run inside BrauMo, with no key.

A bank statement matched to supplier bills: two payments matched by number and amount and ticked, one matched by amount only, one with no match.

Bank statement

Payments out mark supplier bills paid, by bill number or exact amount. Nothing is marked until you confirm.

A cold room's card with its daily check and its sensor: the last sample, and an alert that it ran above 6 °C for 50 minutes, up to 9.3 °C.

Cold room sensor

A sensor in a cold room or fridge logs its temperature. A run of 30 minutes outside its band raises an alert.

  • What Mo noticed

    Up to three drifts on the dashboard: ferment pace against target, delivery momentum, one product taking most of your sales. Worked out by rules from your own records, with no AI and no network.

  • Stalled ferments

    A batch that is not acidifying lists what to check, each fact beside your own limit.

  • One buy list

    The buy list no longer repeats what a drafted order already covers.

The Needs attention card on the dashboard: today's alerts, among them one that a tank probe read below the recipe's band for about an hour and one that the cold-room sensor read above 6 °C for 50 minutes.
Needs attention on the dashboard: one alert from a tank probe and one from the cold-room sensor.

Sensors on your tanks

An iSpindel or a logging pH probe posts to BrauMo on its own. Give the tank the device's name, and the device the token from Settings, Tanks and devices.

An iSpindel adds a reading to the tank's batch: gravity and temperature, marked as coming from the device. A pH probe's samples are kept as monitoring.

If a probe's temperature stays outside the recipe's band for 30 minutes or more, with the same margin the batch page allows, BrauMo raises an alert. The morning brief says so too. A short dip does not.

A probe's stream is monitoring. It never becomes a reading and never changes your HACCP record: your own reading stays the record.

The rules Mo keeps

The same on every screen above.

Mo prepares, you decide

Nothing an AI proposes applies itself. You check the card or the form, then you save.

Only BrauMo's routines act alone

And only for tasks and restock drafts, only where you ticked it, each with an Undo.

Your key, your limit

AI jobs run on your own Anthropic key, billed by Anthropic, with a daily limit you set. Switch Mo off and it makes no network calls.

BrauMo sends no brewery data to us

BrauMo itself sends no brewery data to us. What Mo sends goes to Anthropic, under your own agreement with them.

Photos go without location

A photo is re-encoded before it leaves, so its GPS position stays behind.

Every job is listed

The privacy notice inside the app names every job Mo does and what each one sends.

Off until you say so

Every part is switched off on a fresh install. Switch on only what you want.

Advice, never certified advice

Mo is not certified food-safety, HACCP, legal or tax advice, and it never calls a batch safe to sell. It can be wrong, so check it.

Mo follows each person's role

A role that sees no prices is not offered Mo's money lookups or the cards that write money, and Mo is told not to quote an amount.

Let Mo prepare tomorrow morning.

Tick the routines you want. The rest stays off.

Email and the business tick at Polar, then the download. Your 21 days start when you first open the app.