AB TEAM

19 workstreams, one context each.

AB keeps a team's work moving inside Microsoft Teams, wherever the people are. It is built by workstreams — each one its own session, run by a person, an agent, or both. One moves at a time, the same way we run ReceiptRoller.

Talk to us about AB See the workstreams

19

workstreams this needs

4

kinds of user we build for

8

steps every workstream follows

WHO IT IS FOR

AB is built for four kinds of user

The people doing the work inside Teams, the people watching how it is going, the people who own the tenant, and the people wiring AB into systems of their own. They want different things, so the workstreams divide along those lines.

People doing the work

Anyone with Teams open, getting through their day.

Workstreams serving them9

  • AB Project
  • AB Sales
  • AB Support
  • AB Talent
  • AB IT Desk
  • Copilot experience
  • Product / feature requests
  • CS team
  • Help content

Managers and department leads

The people reading how it is going and deciding what comes next.

Workstreams serving them10

  • AB Project
  • AB Sales
  • AB Support
  • AB Talent
  • AB Finance
  • Product / feature requests
  • CS team
  • PR / SEO / content marketing
  • Direct sales
  • Partner sales

IT administrators

The people who own the tenant, the permissions and the security review.

Workstreams serving them9

  • AB IT Desk
  • Microsoft Teams app store
  • Admin portal watch
  • Product / feature requests
  • CS team
  • Help content
  • Direct sales
  • Partner sales
  • Security / scope management

Developers

The people connecting AB to their own systems through MCP and the API.

Workstreams serving them2

  • MCP / API
  • SDK and developer docs

THE ROSTER

The workstreams behind AB

One workstream, one objective. They fall into three kinds: an app per kind of work, what keeps AB alive inside Teams, and what holds the whole thing up. What follows is the set of workstreams this product needs, not only the ones busy today.

An app per kind of work

6

Each app covers one kind of work, and all of them finish inside Teams.

AB Project

Put every project and task in a state the whole team reads the same way.

Members Managers

AB Sales

Keep a deal and its history followable when the person on it changes.

Members Managers

AB Support

Let nothing drop, and leave each answer where the next person will find it.

Members Managers

AB Talent

Hold hiring progress and people data in one shape the floor and the back office both use.

Members Managers

AB Finance

Keep quotes, invoices and costs from becoming the thing that stalls the work.

Managers

AB IT Desk

Take internal IT requests and assets in one place, and keep them trackable.

Members IT admins

Staying alive inside Microsoft Teams

5

AB runs inside Teams, so some workstreams exist purely to keep up with how Teams itself works and changes.

Copilot experience

Be callable from Copilot, and return something that moves the work on.

Members

Microsoft Teams app store

Meet the review and publishing requirements so any tenant can install it.

IT admins

Admin portal watch

Notice changes to Microsoft's admin surfaces and policies, and follow them early.

IT admins

MCP / API

Let outside tools and AI agents work with AB's features and data.

Developers

SDK and developer docs

Get someone who just found the API as far as their first working integration.

Developers

Deciding what comes next

1

The workstream that runs before anything is built: what people asked for, read against how AB is actually used.

Product / feature requests

Gather what users ask for and what turns out to be missing, and decide what gets built next.

Members Managers IT admins

Getting found, and being looked after

5

What it takes to be installed, and what it takes not to leave anyone stuck afterwards.

CS team

Answer what comes in across all our products, and make sure the same question does not come twice.

Members Managers IT admins

PR / SEO / content marketing

Be findable, and say what AB does before anyone has to ask.

Managers

Help content

Let people solve it themselves instead of waiting for support.

Members IT admins

Direct sales

Take AB straight to the companies that will use it, and show it starting inside Teams.

Managers IT admins

Partner sales

Work through partners so their customers can be brought onto AB.

Managers IT admins

Holding it all up

2

People use this during their working day, so it has to stay up — and stay inside the permissions it was given.

Server log watch / performance

Find errors and slowness first, so nobody meets them mid-task.

Security / scope management

Keep the permissions we hold to what is needed, and re-check on every change.

IT admins

WHAT SHIPPED

What changed inside Teams

What those workstreams actually turn into: the latest releases from AB.

THE LOOP

How one workstream moves

Every workstream turns the same way. A person sets the objective, an agent does the work, and the decision to ship comes back to a person.

See the eight steps

See how a change gets released

  1. 01
    Set the objective

    A member, a manager or an IT admin — whose day gets better, and how. People decide that.

  2. 02
    Open the session

    One session per workstream, started with the code conventions, the past decisions and the current numbers already in hand. A workstream that turns into a long piece of work gets a branch of its own.

  3. 03
    Build it, review it

    Changes go out small, through review and an automated test suite, onto a staging environment — and a person makes the call to put them live.

  4. 04
    Check the number

    Watch whether it is actually used inside Teams, then rewrite the objective. A feature installed and ignored does not stay.

ONE AT A TIME

That is how this much stays covered

The workstreams do not all run at once — one moves at a time. Six apps stay alive while Teams itself keeps changing because one conversation only ever holds one workstream.

Instructions do not mix

Work on AB Sales does not queue behind Copilot support. They are never handed over together, so neither loses the thread.

What is shared, and what is not

Code conventions and the quality bar are the same across the whole project. What stays separate is the mission and the context around it.

Context survives

Decisions accumulate inside each workstream, so picking it up again does not start from zero.

Long ones get their own branch

When a workstream turns into a long piece of work, it moves to a branch of its own. The work is kept apart the same way the context is.

Ship small

Many small changes rather than one large one. People are working in this during their day, so each change stays inside a range we can roll back.

STILL OURS

What people decide

More agents does not move the responsibility. That stays with people.

  • What we will not do

    We can do more than before. That is exactly why the decisions worth our time are the ones to decline.

  • How much access we hold

    How far into a customer's tenant our permissions reach. Keeping that narrow is a human decision.

  • What we promise clients

    Dates, estimates, quality. A company promises those, and a company is people.

  • What goes to production

    Review and merge. A person presses the last button.

LET'S TALK

We can build your Teams workflow the same way.

AB is a working app inside Microsoft Teams. If you want something shaped like it for how your own company works, that is a conversation we are glad to have.

Talk to us