Announcement

IntroducingBAS, the BizBMS Agentic System

BizBMS announces BAS, the BizBMS Agentic System: the system behind agentic delivery, our main offering, and the way BMS, our business management system, is built.

Plan. Execute. Review.

Book a DemoRead how it works
Plan3

BAS-12

Browser journeys recorded as video from the chat

recorderworkspace

BAS-5

Per-stage model policy in the loop

two modelsbudgets

BAS-2

Founder chat: the runner that answers from the record

questions first
Execute2

BAS-1

Founder chat: the data layer, permissions and API

slot 90tests 100%

BAS-4

A worker for the scheduled runs on the testing site

preview building
Review2

BAS-7

BAS launch on bizbms.com: hero, section and page

preview readyawaiting the word

BAS-10

Server-side fetches carry the forwarded protocol

gate green

Plan. Execute. Review. Every card on every BAS board moves through the same three lanes.

A whole system, not a chatbot
Each client gets their own deployment: code, board, documentation, previews, ledger and audit trail.
Honest by construction
Every change passes a quality gate of conventions, types, full test coverage and a reviewed commit. Status is read from the record, not from a report.
Two models, two roles
A reasoning model plans, reviews and talks to people. An execution model writes code and runs tools, under supervision.
Built for business users
Ask BAS Agent anything about your project, at any hour, and get an answer grounded in the code, the board and the tests.
Read the explainer →

For business users

A business user signs in and asks BAS Agent anything about their project: what shipped this week, what the tests say, where a card stands, what a page does. Documents, PDFs and recordings land in their workspace. The answer comes from the record, at any hour, with the cost of every question on the ledger.

BAS Agent
You

What shipped this week?

BAS Agent

Three landings since Monday: the client sign-in with the viewer role, the nine guides at /docs, and inbox-first delivery with the ledger and audit pages. Each passed the gate at full coverage. The testing site runs the latest.

You

Put that in a one-page PDF I can share with the board.

BAS Agent

Done. weekly-update.pdf is in your workspace: what shipped, what the tests say, what is next on the board. Open it or share the link.

You

Record a walkthrough of the new inbox for the sales team.

BAS Agent

Recorded the inbox journey against the testing site. inbox-walkthrough.mp4 (48 s) and a one-page summary are in your workspace.

You

Add a weekly digest email to the founders.

BAS Agent

That is a behaviour change, so it goes through the board. I drafted the card "Weekly digest email to founders" with the acceptance checks and one open question on recipients. It is in Open, waiting for your go.

thinking · 0 questions ahead

Today: 4 questions · 52k tokens · $0.61 of the daily budget

Try it

Ask BAS Agent about BAS. Answers come from this site's own pages.

Ask BAS

0/400

Answers come from the public BAS pages. Six questions per visitor.

Watch BAS work

A recorded walk through bizbms.com, which BAS built and shipped.

Every change is signed

Each commit names the agent and the model that made it, says what changed and why, and records the gate it passed. The history reads as one record.

Agent named
Every commit carries the agent that made it.
Model named
And the model it ran on, in its trailer.
Gate recorded
With the checks it passed before it landed.
author BAS Agentmodel namedgate recorded
commit 222e86f1
Author: BAS Agent <bas.agent@bizbms.com>
feat(bas): lead the bas page with the chat and widen the conversation
The chat section moves directly under the hero and the window is
titled BAS Agent, with You and BAS Agent labels on every message.
The conversation gains a PDF ask and a recording ask. Business
owners become business users across the page.
Gate: typecheck clean · lint clean · tests 7/7 · build green
Preview: website-s90 · Landed on: bas · Promoted to: main
Agent: BAS (BizBMS Agentic System)
Model: claude-opus-5-5

What you get

Delivery

Work goes on a board. Software comes off it, reviewed and gated.

Architecture
Every build follows one framework design: conventions, base classes, one way to lay out an app. A requirement binds behaviour, never design.
Software development
A work item becomes code on an isolated slot with its own database and preview. The plan comes first, and the questions before the plan.
Quality gate
Conventions, types, migrations, docstrings and full test coverage, enforced by hooks and a push gate. Under-tested work cannot leave the machine.
Delivery
Landing under a merge lock, promotion to the main branch, deployment to the testing site, previews per work item, all on one gated path.

Assurance

Everything is tested, recorded and scored, and the record is what you read.

Testing
Unit and integration suites at full coverage on every change, a dedicated test database per slot, browser journeys through the real pages.
Browser recording
Journeys recorded as video against a preview or the live site, delivered with a write-up.
Evaluation and audit
Each delivery scored for recall and groundedness with charts the client sees, and an audit trail of runs, reads and sign-ins.
Reviews and governance
Two commits per change, code then tests, so a reviewer reads exactly what ships. Protected branches move by pull request. Every commit names its agent and model.

People

Business users ask, read and decide. Nobody waits on a status meeting.

Chat and workspace
A business user asks anything at any hour and the answer comes from the record. Documents, reports and recordings land in their own workspace. Code changes go through the board.
Documentation
Guides written alongside the code and served to the client behind their sign-in. A change to a documented path ships its guide.
Access and isolation
Roles from the backend, client users see their own project only, and each client runs in its own deployment with its own keys.

Money

Every run and every question has a cost, and you see it.

Budgets and ledger
A budget per project and per person, every run and every question costed, a ledger page the client reads.

How it works

  1. 01Plan

    Work arrives as cards

    A work item on the board is the unit of delivery. BAS plans it, asks its questions first, then builds it on an isolated slot with its own database and preview.

  2. 02Execute

    Every change is gated

    Conventions, types, migrations, tests at full coverage and a reviewed commit, enforced by hooks and a push gate. Under-tested work can be committed but cannot leave the machine.

  3. 03Review

    People stay in the loop

    A person reviews on the preview and says the word. Code changes travel through tickets, reviews and gates. Documents, reports and recordings come straight from the chat.

Where it comes from

BAS is the productised form of the delivery system BizBMS runs on its own products.

See BAS on your own board

Book a DemoHow agentic delivery works