Announcement

IntroducingBAS, the BizBMS Agentic System

BAS runs agentic delivery, our main offering, and builds BMS, our business management system.

Agents execute. Humans review.

The method

  1. Plan.

    You and BAS

    You write the card. BAS asks its questions before it builds.

    • questions first
    • scope agreed
  2. Execute.

    BAS

    BAS builds, tests and lands it on its own slot.

    • own slot
    • tests at 100%
    • signed commit
  3. Review.

    Your people

    Your people read the live preview and say the word.

    • live preview
    • your word

Works with the board you already have. The method is BAS, the BizBMS Agentic System.

Plan. Execute. Review. The same three moves for every card, on the board you already have.

A whole system, not a chatbot
Each client gets their own deployment: code, board, previews, ledger.
Honest by construction
Status is read from the record, never from a report.
Two models, two roles
A reasoning model plans and talks; an execution model writes code.
Built for business users
Ask Biz anything about your project.
Read the explainer →

For business users

A business user asks Biz what shipped or what the tests say. Answers come from the record; documents and recordings land in their workspace.

Biz
You

What shipped this week?

Biz

Three landings since Monday: the client sign-in with the viewer role, the nine guides at /docs, and inbox-first delivery. Each passed the gate at full coverage.

You

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

Biz

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.

Biz

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.

Biz

That is a behaviour change, so it goes through the board. I drafted "Weekly digest email to founders" with one open question on recipients. It is in Open.

thinking · 0 questions ahead

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

Try it

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

Ask Biz

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 its agent and model, and says what changed and why. Read together, the history is 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
One framework design for every build. A requirement binds behaviour, never design.
Software development
Questions first, then the plan, then code on an isolated slot.
Quality gate
Conventions and full coverage, enforced before anything leaves the machine.
Delivery
Merge-locked landings, a preview per item, one gated path to live.

Assurance

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

Testing
Full-coverage suites, a test database per slot, browser journeys on real pages.
Browser recording
Journeys recorded as video on a preview or live, with a write-up.
Evaluation and audit
Each delivery scored for recall and groundedness; every run and sign-in audited.
Reviews and governance
Code, then tests: two commits per change. Branches move by pull request.

People

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

Chat and workspace
Answers from the record; documents and recordings land in your workspace.
Documentation
Guides ship with the code, served behind the client sign-in.
Access and isolation
Roles from the backend; each client sees only their own deployment.

Money

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

Budgets and ledger
A budget per project and person; every run costed on the ledger.

How it works

  1. 01Plan

    Work arrives as cards

    A work item on the board is the unit of delivery. BAS asks its questions first, then builds it on an isolated slot.

  2. 02Execute

    Every change is gated

    Hooks and a push gate enforce the conventions and full test coverage. Under-tested work cannot leave the machine.

  3. 03Review

    People stay in the loop

    A person reviews the preview and says the word. Code changes go through the board; documents come straight from the chat.

Where it comes from

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