Bwat

Bwat Enterprise

Bwat for your whole organisation

For companies and public bodies that need more than a checkout page. We agree usage and terms that fit how you buy, answer your security and procurement teams, train your people on their own work, and build agents around your processes.

Terms and features are agreed for each organisation and written into the contract.

  1. 1

    Scope

    Pick the teams, the work, and what success looks like

  2. 2

    Security and procurement review

    Your reviewers sign off before anyone logs in

    Needs a person
  3. 3

    Pilot with one team

    Trained on their own work, compared with how it's done today

  4. 4

    Roll out

    More teams, data and automation, once the pilot has earned it

A rollout that waits for your reviewers

Teams or Enterprise?

Both put a group of people on one Bwat subscription. The question is whether buying online is enough.

Teams: buy it yourself

Pick a per-seat plan, pay online and invite colleagues by email. Everyone gets the plan's standard usage. The quickest way to get a team using Bwat this week.

Enterprise: we plan it with you

Custom usage and pricing, security and procurement paperwork, training, support and custom agents. For when a checkout page can't answer your organisation's questions.

We start with the work, then the seat count

First we find out what your people will use Bwat for, what information is involved, who should see what, where a person has to approve, and what your organisation needs in writing about how data is handled and which AI models see it.

  • Map the roles, tasks, source material and expected results
  • Write down hosting, retention, access and which models are used
  • Keep consequential actions behind a person's approval
  • Agree test cases that look like the real work

Who to bring to the first meeting

They know which parts of the job are slow and what a good result looks like. Without them, a rollout solves the wrong problem.

What an Enterprise agreement can cover

Custom terms

Seats, usage, billing and rollout stages, negotiated when the public plans don't fit.

Security and procurement

We answer your reviewers' questions and put in writing what the deployment will and won't do.

Training by role

People learn on their own approved material, including how to check output and when not to use it.

Custom agents

Bwat agents built around a specific process, with its instructions, tools, approvals and tests.

Support

The support and upkeep your deployment needs, agreed up front.

One owner for the rollout

Clear ownership, staged adoption and shared terms, with room to learn from mistakes before it spreads.

How a rollout goes

  1. 01

    Scope

    Choose the people, the work, the information and the result that make the first step worth it.

  2. 02

    Review

    Settle the commercial, legal, security, procurement and technical questions for that scope.

  3. 03

    Pilot

    Train one group on real tasks and compare the results with how the work is done today.

  4. 04

    Expand

    Add people, data, connections and automation once the pilot's results back it up.

Tell us what a self-serve plan can't do for you

Team size, the work, the information involved, and the questions your reviewers will ask. We'll plan the next conversation around that.