Use cases
One agent. As many use cases as you need.
SecondBrain 365 is an AI agent with its own company email inside your Microsoft 365: put it in copy and it writes the team's knowledge base on SharePoint. What changes from one use case to the next is not the software — it is the context file, the plain-language page where you write the rules for that job.
Why it fits so many things
Three pieces. The third is the only one you write.
Two of them you already have and never touch again. The third is a page of plain language — and it is what turns the same agent into a project manager, a quality officer or a service desk.
A Teams group
The one the team already works in. The agent joins it like a colleague, with its own company email.
A SharePoint site
Where the knowledge base is written. Your tenant, your permissions, your retention rules.
A context file
A text file in plain language: what matters here, what to watch for, what to flag. The only piece that changes between one use case and the next.
Nothing is configured, nothing is coded. You write the rules the way you would explain them to a new colleague.
Seven, written up in full
Each one is a different job, with its own page: what the day looks like, what the agent actually does about it, and what it does not do.
Project management
Stop chasing people for updates: the agent asks, and the plan stays current
Product management
Why the product is the way it is — written down while you decide it
HR
The answer your team already wrote, found by the next person who asks
IT service desk
Forward the reply you just sent. That is the whole documentation step
ISO audit
Evidence recorded as it happens, not reconstructed the month before
RFP & bids
The tender's deadlines pulled out of the pack, and the chasing done for you
Onboarding & offboarding
What leaves with a person becomes smaller — and it is honest about the rest
Not sure which one is yours?
They divide by the question the team keeps having to answer.
“Where are we?”
Work that runs to a date, with people you do not manage. The agent does the asking and keeps the record current.
“Why is it like this?”
Decisions that get re-opened months later because the reason was never written down.
“Has anyone answered this before?”
The same question arriving again, and the good answer sitting in one person's sent folder.
What is identical in all seven
Different jobs, same mechanism. Nothing in this list changes from one use case to the next.
It joins what you already use
A Teams group and a SharePoint site you have today. The agent gets a company email address, and that is the only new thing in the room.
You choose what it sees
A mail in copy, a meeting invite, a channel it was added to. Nothing is read automatically, and someone outside the workspace cannot put a line into it.
Everything it writes carries a date and a source
Which is what makes a page judgeable a year later — and what turns a knowledge base into evidence rather than folklore.
It asks instead of deciding
When two pieces of content disagree, it flags the pair and leaves the call to you. That is true of a go-live date, a policy and a procedure alike.
It lives in your tenant
Your permissions, your retention rules, your compliance perimeter — because it is not a separate system.
And everything else a team has to agree on
Same agent, same way of working: a Teams group, a SharePoint site, and a context file that says what matters here. The list is a starting point, not a catalogue.
- Department meetings
- Event management
- Procurement
- Tenders
- ERP rollouts
- Rebrands
- Training programmes
- Sales meetings
- Customer care
- Certifications
- Supplier reviews
- Plant commissioning
- Due diligence
- Partner programmes
- Internal communications
- Legal
- Internal support desks
- Board meetings
- Store openings
- Compliance reviews
If it has a Teams group and someone has to remember what was decided, it can have a workspace.