Can Projan actually read what was said in a Teams meeting?

Yes. Projan can import a Microsoft Teams meeting transcript as planning context, so the points raised in the meeting feed directly into the follow-up conversation instead of relying on whoever happened to be taking notes.

Does Projan create the tickets inside Teams itself?

No, because Teams has no tickets. What happens in Teams is the facilitated conversation — messages, Adaptive Cards and the agreement. The work items are created in whichever tracker you've connected.

Who has to approve this before our team can use it?

A team or tenant admin grants tenant-wide consent. That single approval lets Projan operate across the tenant, which is how most enterprise IT prefers to vet and authorise a tool rather than chasing per-user installs.

How does a piece of work get its own space in Teams?

Projan can create a dedicated channel for a piece of work, run a short welcome flow when it joins, and post a share link so the right people can pick it up. Planning then happens in that channel.

Are the buttons in Projan's messages just for show?

No. Projan posts interactive Adaptive Cards, and the buttons and inputs on them drive the session — moving the conversation forward, capturing choices and triggering the export when the team is ready.

Is the Teams integration available on every Projan plan?

It's a Team-plan feature. It's built for group decision-making and runs on tenant admin consent, so it lives on the plans designed for teams rather than individual use.

Our decisions get made in Teams meetings and then vanish — can Projan turn them into tracked work?

Q: Will I have to retype the meeting outcome into Jira or Linear afterwards?

No. Once the team agrees the plan in the Teams channel, Projan exports it to your connected tracker — Jira, Linear, Notion or ClickUp — as structured work. The hand-off is the whole point; nobody copies anything across by hand.

In a lot of organisations the real decisions happen in a Microsoft Teams meeting, get half-captured in someone's notes, and then quietly fail to become anything. Projan works inside Teams to close that gap. It facilitates planning in channels, can pull a meeting transcript in as context so nothing said in the room is lost, and turns the agreement into structured work in your tracker. It runs on tenant-wide admin consent, so it fits how enterprise IT actually approves tools. The conversation stays in Teams; the decision finally goes somewhere.

A compliance lead calls a thirty-minute Teams meeting because a regulator has changed what counts as acceptable data handling. Seven people join. The discussion is genuinely good — someone flags a downstream system nobody had thought about, the legal stance gets nailed down, an owner is named for the risky bit. The meeting ends, everyone agrees “we know what to do now,” and the recording sits in the chat. Two weeks later the change still hasn’t started, because knowing what to do and having it written down as work are not the same thing.

Where enterprise decisions evaporate

The meeting is where the deciding happens, and the meeting is also where it’s lost. A transcript gets generated, but a transcript is not a plan — it’s an hour of talking with the conclusions buried somewhere inside it. The action items live in one person’s head, or in a recap nobody opens again. By the time anyone tries to turn the decision into tracked work, the nuance that made it a good decision — the exception that was carved out, the dependency that was spotted — has already gone. The bigger the organisation, the wider this gap, because the people who decide and the people who deliver are rarely the same people, and the only bridge between them was a meeting that has now finished.

From a meeting to a plan that exists

Take the compliance-change meeting. Afterwards, in the Teams channel for that work, someone brings Projan in and hands it the meeting transcript. Projan reads the transcript as context — so the downstream system that got flagged, the legal position that was agreed and the named owner are all already in the room with it.

Then it facilitates. It doesn’t ask the team to start from a blank page; it works from what the meeting established and pushes on what the meeting left loose. It asks which systems actually touch the affected data, whether the carve-out the team mentioned needs its own task, and what “done” looks like for an auditor. The answers come back in the channel — as messages, and through the buttons on the Adaptive Cards Projan posts. What was an hour of conversation with no edges becomes an agreed, scoped plan, and crucially one that still carries the reasoning the meeting produced rather than a flattened summary of it.

What Projan does inside Teams

Projan’s Teams bot is a participant in the channel, not a dashboard hanging off the side of it:

Inside Teams	What Projan does
Channel messages	Processes them and facilitates the planning conversation in-channel
Interactive Adaptive Cards	Posts cards whose buttons and inputs drive the session and capture decisions
A new piece of work	Creates a dedicated channel for it, with a welcome flow and a share link
A Teams meeting	Imports the meeting transcript as planning context so nothing said is lost

It’s a Team-plan feature, and it runs on admin (tenant) consent — one tenant-wide approval rather than a scramble of individual installs.

Then it becomes work

The conversation stays in Teams; the output doesn’t. When the team agrees the plan, Projan exports it to your connected tracker — Jira, Linear, Notion or ClickUp — as structured work the delivery team can actually pick up. The compliance change that was a finished meeting and an idle recording becomes a set of tracked items with owners, in the tool your engineers already work in. No one has to sit down afterwards and “write it up”, which is the step that, left to humans, simply never happens.

Setting it up (and who approves it)

Projan installs against your Microsoft 365 tenant on admin consent: a team or tenant administrator grants tenant-wide permission once, and from then on Projan can operate across the tenant. This is deliberately the model enterprise IT already trusts — a single, reviewable authorisation by an admin, not a per-person scramble that security teams dislike and can’t easily audit. After consent, point Projan at the tracker you export to, and start planning in any channel.

It lives inside Teams, it doesn’t replace it

Projan isn’t trying to be your meetings tool or your tracker. Teams stays where your organisation talks and decides; your tracker stays where work gets delivered. Projan occupies the gap between them — the bit where a good decision in a meeting is supposed to become real work and, far too often, simply doesn’t. It keeps the conversation exactly where it already is, and makes sure the conclusion finally leaves the room.