Skip to content

Fewer meetings.Same decisions.

Before each recurring meeting, agents settle the agenda from Jira and chat, then you cancel, shorten or keep it.

#payments-squad

Thursday, 22 October

MeetResolveApp08:00

Thursday’s Payments sync: shorten it to 15 minutes?

Recommendedby MeetResolve · from the 6 cards

Shorten to 15 minutes

5 of 6 items settled1 conflict left7 person-hours back

Settled before the meeting

  • Release 2.3 is on track for 7 Nov
  • Postgres for the audit logapproved
  • Webhook retries move to 2.4Inès to approve
  • Sandbox key arrives Fri 24 Oct
  • PAY-150 has acceptance criteria

Still to discuss

Who owns on-call for the reconciliation job?Karim, Thomas

If shortened: 10:00–10:15 with Karim, Thomas and Inès. Everyone else becomes optional.

Only Inès can choose · kept as booked if there’s no choice by 09:45 · undo for 24 h

Gap card · private

Your agent asks: is the 2.3 scope frozen on 30 Oct?

Drafted answer: “Yes, frozen 30 Oct” · from the Jira version 2.3 description

Inès shortened the sync to 15 minutes.

Calendar updated for 8 people: Karim, Thomas and Inès stay; the others are now optional. Items 1–5 are logged.

Example · Nordline is a fictional team

The problem

The hidden cost of recurring meetings.

Most of a weekly sync is reading out what Jira already says. The cost is spread across the team, so nobody sees it.

  • 01

    Status read aloud

    Progress, PRs and blockers are already in Jira and chat.

  • 02

    Decisions wait for the slot

    A two-minute decision waits a week, then takes the time of eight people.

  • 03

    Decisions get lost

    What the room agreed rarely makes it back to the Jira issue.

Person-hours in recurring meetings, per week
  • Daily standup8 people · 15 min · 5 times a week10 h
  • Payments weekly sync8 people · 60 min · weekly8 h
  • Sprint review8 people · 60 min · every 2 weeks4 h
  • Sprint retro8 people · 60 min · every 2 weeks4 h
  • Platform dependency sync5 people · 30 min · weekly2.5 h
A week
28.5 person-hours
A year at $50 an hour
about $65,500

Example: a fictional 8-person squad, as in the sample audit.

How it works

Settled before it starts.

One weekly sync on Thursday at 10:00, from the first signal to the outcome.

  1. Mon–Wed

    Open questions, pending decisions and blockers are spotted in #payments-squad and in Jira.

    Automatic

    • Question#payments-squad

      Who owns on-call for the reconciliation job?

    • BlockerPAY-142

      PAY-142 waits for the sandbox API key

    • DecisionPR #412

      Move webhook retries to 2.4?

  2. Wed 10:00T−24h

    Six items to settle. The lead adds or drops items from one card.

    Lead · one card

    MeetResolveT−24h#payments-squad

    Agenda locked · 6 items

    • Release 2.3 is on track for 7 NovPending
    • Postgres for the audit log, partitioned by monthPending
    • Move webhook retries to release 2.4Pending
    • Sandbox API key arrives Friday; PAY-142 unblocks thenPending
    • Who owns on-call for the reconciliation job?Pending
  3. Wed–Thu

    Owners confirm one missing fact each, with an answer already drafted from their own work.

    Owners · one tap

    Gap card · private

    Your agent asks: is the 2.3 scope frozen on 30 Oct?

    Drafted answer: “Yes, frozen 30 Oct” · from the Jira version 2.3 description

  4. Overnight

    Each involved attendee’s agent states a position, a neutral pass compares them, and agents answer what is addressed to them.

    Agents

    Sam’s agent

    Retries won’t be ready for 2.3.

    Inès’s agent

    2.3 should not slip; retries were never part of its commitment.

    Neutral comparison

    Both agree 2.3 ships on 7 Nov. One open question goes back to Sam's agent.

  5. Thu 07:00T−3h

    One card per item, each with its receipts. Proposals are approved in one tap.

    Owners · one tap

    MeetResolveT−3h#payments-squad

    Needs approvalDecision

    Move webhook retries to release 2.4

    Ship 2.3 on 7 Nov without webhook retries. Retries move to 2.4 as PAY-163, and the pilot runs on manual retry until then.

    Sam approved 07:12Inès waiting

  6. Thu 08:00T−2h

    The lead picks cancel, shorten or keep, with the person-hours at stake.

    Lead · one choice

    MeetResolveT−2h#payments-squad

    Recommended

    Shorten to 15 minutes

    5 of 6 items settled1 conflict left7 person-hours back

    Only Inès can choose · kept as booked if there’s no choice by 09:45 · undo for 24 h

  7. After

    Calendar updated for everyone, decisions written on the Jira issues and in the decision log.

    Automatic

    Decision loggedPAY-148

    Webhook retries move to release 2.4

    Approved by Sam Martin 07:12 and Inès Moreau 07:31

    Why: the retry queue needs 4–5 more days; 2.3 is committed to the pilot for 7 Nov.

    Written back

    • Comment on PAY-148
    • Fix version 2.3 → 2.4
    • Label decision-logged
    • Follow-up PAY-163 drafted

Two hours before: cancel, shorten or keep

  • Cancel

    Everything is settled. The calendar updates and the hour goes back to the team.

  • Shorten to 15 minutes

    Only the open conflict needs people. Everyone else becomes optional.

  • Default

    Keep

    The meeting runs as booked, with a sorted agenda. Keep is the default.

The full walk-through

Inside MeetResolve

Every recommendation shows its sources.

See what is settled, what is left and what the meeting costs. Each item links to the issues, PRs and messages behind it.

Payments weekly sync

Thursday 22 Oct · 10:00–11:008 attendees#payments-squad

  1. 1. Agenda locked, Wed 10:00
  2. 2. Agents settled, Thu 06:40
  3. 3. Cards posted, Thu 07:00
  4. 4. Lead’s choice, By 08:00
  5. 5. Outcome, Calendar and Jira

Recommended

Shorten to 15 minutes

5 of 6 items are settled. One conflict is left: who owns on-call for the reconciliation job. Only Karim, Thomas and Inès stay invited; the others become optional. 7 person-hours back.

Agenda · 6 items

  • ResolvedRelease 2.3 is on track for 7 NovResolved · Status · 11 of 13 issues done
  • ApprovedPostgres for the audit log, partitioned by monthApproved · Decision · Karim and Thomas approved at 07:20
  • Needs approvalMove webhook retries to release 2.4Needs approval · Decision · Sam approved · waiting for Inès
  • ResolvedSandbox API key arrives Friday; PAY-142 unblocks thenResolved · Blocker · confirmed by Léa on her gap card
  • ConflictWho owns on-call for the reconciliation job?Conflict · Decision · stays on the agenda

Cost of this meeting

As booked
8 people × 60 min = 8 h
If shortened
3 people × 15 min = 0.75 h
Back to the team
7.25 h · about $360
The meeting page, two hours before

Needs approvalDecision

Move webhook retries to release 2.4

Proposal

Ship 2.3 on 7 Nov without webhook retries. Retries move to 2.4 as PAY-163, and the pilot runs on manual retry until then.

Samapproved 07:12Inèswaiting

Sam’s agentRound 0 · position · 02:14

Retries won’t be ready for 2.3.

  • The retry queue needs 4–5 more days of work.

    From a sourcePAY-148PR #412

  • Sam can pick retries up again on 9 Nov.

    Confirmed by Samgap card · 21 Oct

Written by an agent for Sam

One item, settled between two agents

Decision loggedPAY-148

Webhook retries move to release 2.4

Approved by Sam Martin 07:12 and Inès Moreau 07:31

Why: the retry queue needs 4–5 more days; 2.3 is committed to the pilot for 7 Nov.

Written back

  • Comment on PAY-148
  • Fix version 2.3 → 2.4
  • Label decision-logged
  • Follow-up PAY-163 drafted
The decision, written back to Jira

Example · Nordline is a fictional team

Signals in, decisions out

Every signal ends in one decision.

Threads, issues, pull requests and invites come in. Agents settle what they can, people decide the rest, and MeetResolve keeps the record.

Integrations

Decisions in Jira. Cards in Slack or Microsoft Teams.

Calendar changes land in Outlook or Google Calendar. Nothing new to open.

  • Jira
  • Slack
  • Microsoft Teams
  • Outlook
  • Google Calendar
  • GitHub
  • Confluence

Product names and logos belong to their owners.

Trust and privacy

Built for teams that read the fine print.

MeetResolve reads team conversations, so the limits are built into the product.

  • Encrypted and exportable

    Encrypted in transit and at rest. Admins export the workspace; members export or delete their own data.

  • Mapped channels only

    Only the public channels, Jira projects and repos you map. Never DMs, private channels or email.

  • Raw text gone after 30 days

    We keep signals, decisions and short linked excerpts. Message text is deleted after 30 days.

  • No per-person analytics

    No activity or productivity scores, anywhere. Reports are team-level.

  • Agents are labelled

    Every agent message says “Written by an agent for” the person it acts for.

  • A person always decides

    Agents propose, people approve. Only the lead cancels or shortens, with 24 hours to undo.

Security and privacy in detail

How much do your recurring meetings cost?

Connect Outlook or Google Calendar. In about two minutes, see the person-hours, the yearly cost and which meetings to cancel or shorten.

No Jira or chat needed. Titles, times and attendee counts only.

Frequently asked questions

Does MeetResolve join or record our calls?

No. There is no meeting bot and no recording. MeetResolve works before the meeting, and the meeting itself stays human.

Can it cancel a meeting on its own?

No. Only the meeting’s lead can cancel or shorten it, and keep is the default. Any change can be undone for 24 hours, and if anything fails the meeting happens as booked.

What does it read?

Only the public channels, Jira projects and repositories you map to a meeting. Never direct messages, private channels, group chats or email. Each mapped channel gets a notice, and anyone can opt out.

Will an agent speak for me?

Your agent proposes; you decide. It sees only what you can open, every message it writes is labelled, and anything that needs you arrives as a one-tap card.

Which meetings does it work for?

Recurring team meetings: weekly syncs, standups, dependency syncs, refinement and sprint review prep, and client status meetings. Retros, one-to-ones, brainstorms and hard conversations stay human.

Can it replace our daily standup?

Yes. Agents gather progress and blockers from Jira and pull requests into an async digest, and the lead can cancel the standup when no blocker needs people.

Which tools do we need?

Jira Cloud, Slack or Microsoft Teams, and Outlook or Google Calendar. GitHub and Confluence are optional. The free audit needs only your calendar.

How do we start without risk?

Run the free audit, then a shadow week: agents prepare every card silently while the meeting still happens, and the lead compares them with the room. Nothing is cancelled until you say so.

Do client guests need an account?

No. Guests answer a short intake and approve cards from a magic link. They are never billed.