Kickoff Ariel — decisions
Go-live confirmed for 15 September. We need the ACME data by August or the date slips.
Native Microsoft 365
An agent with its own company email inside your Microsoft 365: put it in copy, and the project knowledge base writes itself — staying coherent over time.
Kickoff Ariel — decisions
Go-live confirmed for 15 September. We need the ACME data by August or the date slips.
We need a second run on production before go-live.
Agreed. Before the 15th?
Yes — week of the 8th.
Documents / Tender /
Tender pack — Annex C
4.2 The clarification window closes 11 days after publication.
Modified
3 Mar
By
M. Rossi
ACME data — first extract
Partial export attached. Missing the cost centres.
Rollback window: 4 hours from cutover.
Modified
22 Feb
Re: go-live checklist
Two items still open on the ACME side.
All critical paths passed. Two minor defects logged.
Modified
4 Mar
Timeline — revised
Proposing we slip to the following week.
Projects / Ariel /
Go-live 15 September. ACME data by August.
A second production run is required before go-live.
Clarification window: 11 days from publication.
Rollback window: 4 hours from cutover.
Migration plan signed off. Staging green, production booked.
Built by Dev4Side, makers of intranet.ai
SecondBrain 365 lives where your company already works: the agent has an identity in your tenant, reads what you share with it in Outlook and Teams, and writes to SharePoint. If you run Microsoft 365, there is nothing to integrate.
Solutions Partner across the whole stack
The software house that builds SecondBrain 365. Microsoft-only since 2010, from Milan and Pesaro.
Our SharePoint intranet, used by 200+ enterprises across 10 languages.
The problem
A company that moves fast makes its own information obsolete. Decisions get taken in a meeting, corrected in a chat, confirmed in an email — and the page that was supposed to hold them was written months ago. Keeping it current is a real job, and it is nobody's.
Information travels on more channels than anyone can follow. Each one is right when it is written — none of them goes back to correct the page that is now wrong.
How it works
No new tool to adopt, no migration. The only new thing is an email address.
Kickoff Ariel — decisions and next steps
From Anna Bianchi
To Marco Realli, Giulia Ferri
Ccagent@yourcompany
Thanks everyone. To recap what we agreed: go-live is 15 September. Marco is fine on infrastructure but flags that we need the ACME data by August, otherwise the migration slips…
Marco Realli 09:14
Migration test passed, but only on staging.
Giulia Ferri 09:21
Then we need a second run on production before go-live.
Tender pack — Annex C
3.4 The contracting authority shall publish clarifications on the portal.
3.5 The clarification window closes 11 days after publication of this notice.
Decisions /
Project timeline
Go-live set for 15 September, agreed at kickoff. Dependency: ACME data by August.
A second migration run on production is required before go-live.
Clarification window: 11 days from publication.
CC it on an email, invite it to a meeting, add it to the Teams group, or share documents with it.
It turns those conversations into structured knowledge base pages on SharePoint, linked to each other.
It posts on Teams when two pieces of content contradict each other, so you decide which one holds.
Keeping what you know is the easy half. The agent also compares what comes in against what is already written, and raises a hand when the two disagree.
It is not a tool your team has to adopt. The kickoff minutes are already in Outlook, the message about the permit is already in Teams, the knowledge base is already SharePoint.
You do not query it to find the contradiction — it posts in Teams the day it appears, and asks the team which version holds.
Use cases
What changes from one use case to the next is not the software. It is the context file — a page of plain language where you write the rules that apply here.
Explore where SecondBrain 365 fits in your company — and what it would keep straight for the teams you run.
A workspace is three things — and you already have two of them.
The one the team already works in. The agent joins it like a colleague, with its own company email.
Where the knowledge base is written. Your tenant, your permissions, your retention rules.
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.
No new app for your team to learn. People keep working in Teams and Outlook exactly as they do today — the agent is one more address in the Cc field, and the knowledge base is a SharePoint site they already know how to open.
Coming from Viva Topics
Topic pages went back to being ordinary SharePoint pages, and the knowledge they were holding together went back to being scattered across Teams and Outlook. If you had it, you already know the gap it left.
What a Viva Topics alternative has to doThe difference in one line
Found what was already written down.
Writes it — and tells you when two pages stop agreeing.
Security and governance
They process your meetings on their infrastructure, under their retention rules. SecondBrain 365 has nowhere to put your content: the agent lives in your tenant, and everything it writes stays in a SharePoint site you own.
And the agent proposes, it does not decide. Turn on the approval step and nothing enters the knowledge base until a person says yes.
The five questions your IT department asks →What it replaces
Keeping a project's knowledge written down and current is work, and somebody is doing it — or nobody is, which costs more. There are three ways it goes.
Brought in from a consultancy when the documentation is contractually required and nobody internal has the time. You know the day rate — it is on the last invoice.
Senior enough to know what matters, spending a day a week writing up what everyone else said. It works, and it is the most expensive hour in the company spent on transcription.
Decisions taken twice because the first one could not be found. Handovers that lose half the context. A go-live that slips because the date nobody updated was the wrong one.
What clients say
SecondBrain 365 is new. Dev4Side is not — these are reviews of the company that builds it, on Google.
“It's not easy to find professionals as competent and passionate as I found at this company. Congratulations.”
“I recommend Dev4Side 100%! I needed their support and they were absolutely exceptional — not only very kind, but also fast and effective. A special thanks to the whole team!”
“I have been working with this company for several years and can confirm their great competence, reliability and availability. Always ready to support us with effective and tailored solutions — a solid and trustworthy long-term partner.”
“Very competent company in the Microsoft 365 space, with professional and skilled technicians. Thanks to their help we were able to implement new technologies and solve difficult problems.”
“I confirm the excellent collaboration with Dev4Side. Engaged for a fairly critical project in cloud Azure software development, they proved extremely competent.”
“Since 2022 we have been working with Dev4Side for national and international internal communications. The team is always present and ready to handle our requests, always offering solutions, ideas and interesting insights. We highly recommend Dev4Side to anyone looking for a reliable and innovative partner.”
FAQ
No. SecondBrain 365 runs inside your Microsoft 365 tenant. The only new thing your team sees is an email address to put in copy — there is no client to deploy and no tool to adopt.
In your tenant, where it already is. The knowledge base is a SharePoint site you own and the agent has an identity in your Entra ID. There is no server of ours that your conversations pass through.
Yes. The pages the agent writes live in SharePoint, so Microsoft 365 Copilot reads them like any other content in your tenant. You are making Copilot better at answering about your projects.
The workspace decides. Whoever manages it chooses who joins, and only those people talk to the agent. The agent sees what is shared with it — it does not go looking around your tenant.
You correct it, like any other SharePoint page. You can also turn on an approval step, so a person validates what the agent proposes before it enters the knowledge base.