File
SMF·MICROSOFT-TEAMS-ESSENTIALS
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·MICROSOFT-TEAMS-ESSENTIALS

Can a prompt replace Microsoft Teams Essentials?

Video meetings & webinars — team chat and meetings

Not yet Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
$4/moSource: www.microsoft.com · Checked on July 31, 2026
Per year
$48
Build time
One sitting
Votes
0 votes
YesAlmostNot yet (checked)

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: bundle economics and identity
Exhibit Q Questions

Verdict

At four dollars a user this is priced to be cheaper than thinking about it, and it bundles chat, storage, and meetings that hold up. The meeting half is media infrastructure and the identity half is a directory other software expects to find — neither is a personal build. The chat half genuinely is, and it is worth building well, because the thing most small teams actually need from Teams is a conversation they can find again six months later.

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build team chat organised by topic, not by time.

Stack: your choice with websockets, Postgres, Docker Compose, a domain with TLS.

The structural decision: a message belongs to a **topic** inside a channel, and a topic is created by whoever starts the conversation, with a name. Reading a channel means reading a list of topics with unread counts, not scrolling a merged river of messages. This is the one design choice that makes chat searchable a year later, and it should be enforced — there is no way to post to a channel without naming a topic, though picking an existing one is one keystroke.

Messages: Markdown, edit and delete with an edit marker, reactions, @mentions writing to a notifications table, and file attachments to local disk with a content-hash filename and a type allowlist.

Search has to be genuinely good or the design is pointless: full-text over message bodies with Postgres, filterable by channel, topic, sender and date range, with the matching term highlighted and three messages of surrounding context. Search must include topic names, since a well-named topic is often the whole answer.

Retention: a per-channel policy in days, defaulting to unlimited but easy to set, deleting messages and their attachments from disk. Show the policy in the channel header so nobody is surprised. A channel marked as a decision log can be exempted explicitly.

Read state per user per topic, so an unread badge means something. Mark-all-read at the channel level.

Export: a whole channel as JSON, and as readable Markdown with one file per topic — that second format is what makes an archive useful after you stop running the server.

Write tests for read-state correctness with concurrent posts, for retention deleting attachments from disk and not just rows, and for search returning correct context at message boundaries.

Do not build voice or video calling, screen sharing, or a mobile app.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 meetings, calls and screen sharing
  • B.2 the identity directory that other business software expects
  • B.3 the mobile and desktop apps with reliable notifications
  • B.4 file storage and co-authoring in Office documents
  • B.5 guest access for people outside your organisation

Prior art

Exhibit C — Why people still pay: bundle economics and identity

Because four dollars buys chat, meetings and storage that a small business would otherwise assemble from three vendors, and because it is already installed on everyone's laptop.

Questions

Why force every message into a named topic?

Because untopiced chat is unsearchable within weeks — the decision is in there somewhere, in a river of messages, without a handle. Naming the topic costs one keystroke and is the difference between a chat log and a record.

Is chat without meetings really useful?

For a small team, yes: the meeting can happen anywhere, and the thing you cannot outsource is the written record. This build deliberately does the durable half and leaves the ephemeral half to whichever conferencing tool you already have.

Why export to Markdown as well as JSON?

Because JSON is for importing somewhere and Markdown is for reading in five years with no software at all. An archive you cannot open without running a server is not an archive.

What does Teams Essentials actually include?

Chat, calls and video meetings with recordings and transcripts, plus 10 GB of storage per user, on an annual auto-renewing subscription. It does not include the Office desktop applications — that is the Business Basic tier and above.

Receipt

Already built this yourself?