Minns
    Your day · Gets it done online

    The website jobs, done in a browser you can watch.

    Renewing an account, filling in a supplier's form, comparing fares, downloading last month's statement. Your assistant works through the site in a real browser of its own, keeps you able to watch every step, and puts anything that sends or books to you before it is pressed. Paying is always yours.

    Join the waiting listTalk to us

    A cloud browser kept for you, or the browser pane in the Minns desktop app on your own computer.

    A submit as you see it: the page, the button it will press and what it sends. If the page has changed when you approve, it is not pressed. Example names.

    01 · A real browser of your own

    Kept signed in, and you can watch every step.

    Your assistant has its own browser in the cloud, kept for you between jobs, so a site you have signed in to stays signed in. It reads and uses pages the way you would, from the page itself, and waits for each page to settle before the next step rather than clicking blind.

    Open the live view from your phone or computer to watch it work, and take over at a tap when you would rather do a step yourself. Every step that acts is kept with a picture of the page afterwards, under the reply it led to, so you can see later exactly what was done.

    • Pictures of steps are kept 30 days; password and card fields are masked in them.
    • Save a login from the live view and it is filled for you, on that site only, without the assistant seeing it.
    • A browser unused for 14 days is packed away encrypted and brought back when next needed.

    Cookie banners are answered with their least tracking button. Any other popup stops the step for your assistant to decide.

    02 · Forms and bookings

    Filled from your details, put to you before it is sent.

    Forms are filled field by field from what you have given your assistant, and every field is read back to check it took. Filling a form never sends it: sending is a step of its own, which your assistant puts to you first, saying exactly what it will do.

    Personal details come from your details, kept encrypted for you. A sensitive one, such as a passport or National Insurance number, is asked for before it is used, and the first time it would go to a new site you are asked about that site by name. The assistant types it without ever seeing it.

    • An approved submit is pressed in the same tab, once, and only if the page still matches what you saw.
    • A job application is sent only after you have reviewed every page of it.
    • Comparing suppliers or prices can run across up to 40 sites, several at a time, in tabs that cannot submit anything.
    03 · Paying stays with you

    It gets everything ready, then hands you the payment.

    Your assistant never pays and never types card details. When something has to be paid for, a ticket, a deposit, a booking fee, it finds the exact option, tells you what it buys and the total the site shows, and sends you a card with a button that opens the page on your own phone.

    You pay there, in the site's own checkout, and tell your assistant when it is done. It then finds the confirmation in your mail, keeps the booking in your details and puts it in your diary. A button that pays is refused in its browser, even one you approved before.

    • A button is treated as paying if its words, the page or a payment provider's frame say so: a wrong guess costs you one tap, not money.
    • Card numbers are hidden wherever the assistant reads a page.
    • A booking is kept with its reference, so a change or a refund can start from it.
    04 · When a site says no

    Never forced, never fooled, and you are told why.

    When a site refuses a plain read, your assistant opens the page in a real tab and reads it there, as you would see it. If a site asks to check that a person is there, it does not try to solve or get round the check: it sends you a notification that opens the live browser, and waits for you.

    A site that has refused the browser is left alone for a while rather than retried, since retrying is how an address gets blocked for a day, and you are told another way to get it done. Some places it never goes: HMRC's online services are closed to it, because HMRC does not allow software to use them, so tax goes through HMRC's own API.

    • Signing in, codes sent to your phone and checks are handed to you in the live browser.
    • A booking service that does not allow automated booking is left for you, or phoned instead.
    • GOV.UK guidance pages are read like any other.
    The use case: a day out to see a supplier

    From "get me to Leeds" to the ticket in your diary, in the order it happens.

    One journey. Your assistant finds and prepares; you choose and pay.

    1. MON 8:10

      You ask

      You need to be at Northgate Build's Leeds office by 10:30 on Tuesday and back by the afternoon. Your railcard and home station are already known.

    2. MON 8:11

      Trains and fares found

      The journey planner gives three trains that arrive in time. Fares are read on the operator's site in the browser: an Off-Peak Day Return beats two singles.

    3. MON 8:14

      You choose

      You pick the 09:41 and say yes to the fare and its rules. Your assistant finds that exact option, ready to buy.

    4. MON 8:15

      You pay on your phone

      A card opens the operator's page on your phone. You pay £18.40 there. The assistant never sees your card.

    5. MON 8:20

      Kept and in the diary

      It finds the confirmation in your mail, keeps the booking with its reference, and adds the trains to your diary with time to get to the station.

    6. TUE 8:40

      Checked on the day

      An hour before, it checks the train is running and tells you the platform.

    Who decides

    It does the work. You make the calls.

    What the assistant may do on its own, and what only you, or someone you choose, may do.

    The assistant may

    • Use its own browser to read sites, fill forms and compare options.
    • Fill a form from your details, asking before a sensitive one.
    • Keep a picture of every step for you to look back on.
    • Hand you a payment with exactly what it buys and the total.

    Only you may

    • Send, book or confirm. Each submit is put to you first, saying what it will do.
    • Pay. Always on your own phone, never by your assistant.
    • Sign in, pass a site's check or enter a code sent to your phone.
    • Let it use the browser on your own computer, and stop it at once.
    Questions owners ask first

    Straight answers.

    Can I watch what it is doing?
    Yes. Open the live view from the Minns app on your phone or computer. You can take over at a tap, and every step that acts is kept with a picture of the page for 30 days.
    Can it use my own browser?
    With the Minns desktop app, it can use a browser pane in the app on your computer while you watch, if you allow it: never, ask each time, or always, per assistant. It is a browser of its own, not your everyday one, and it never reaches your files. Press Stop and it stops at once.
    Will it pay for things?
    No. It never types card details and a button that pays is refused in its browser. It gets the payment ready and hands it to you on your phone.
    What happens with a captcha or a robot check?
    It does not solve it or try to slip past it. It asks you to do that step in the live browser, then carries on. A site that refuses it is left alone, not retried.
    Can it file my VAT return on HMRC's website?
    No. HMRC does not allow software to use its online services, so your assistant never opens them. VAT goes to HMRC through its own Making Tax Digital API, with your accountant.

    Give your business an assistant.

    Connect your mail, calendar and books in a few minutes. It works the way you do, and asks before it acts in your name.

    Join the waiting listTalk to us