Fix one recurring meeting, on paper you can send
For the owner of a recurring meeting who suspects it should change but has nothing concrete to send. Answer nine questions, get a recommendation with real numbers, and a document written in your voice with a six-week trial and revert criteria built in.
Free for your first 3 meetings. No card, no calendar access.
Meet half as often
Rarely decides anything new, but it is the only route people have to raise blocks, so a live session stays at half the frequency.
What changes
Ruled out
Detail
Nine questions, one recommendation
Three screens, nine required answers, and a deterministic engine that returns exactly one outcome on a seven-step scale. Every question changes the routing, none of them exists to pad the wording, and the language model writes prose inside a decision it did not make.
The question that earns its place: what else does the meeting do, beyond the agenda? Meetings survive because they are quietly the deadline, the escalation route, or the only time a senior person looks at the work. The engine will not cut a function it cannot replace.
- 1Cut the invite list
- 2Make it shorter
- 3Meet half as often
- 4Split into two sessions
- 5Move status to a pre-read
- 6Replace the meeting with writing
- 7Cancel with no replacement
The shallowest fix that addresses the problem wins. Depths 6 and 7 are the rarest correct answers, and the ones most often blocked.
Does it need people responding to each other live?
How often does something get decided that was not already decided?
What else does it do, beyond the agenda? Select all that apply.
The written-disagreement gate
Before recommending that a decision meeting become writing, Meetless asks whether anyone has ever disagreed in that channel in writing. Objections to a proposal, not general comments.
If the answer is never, conversion is blocked and the block is named on the result. Converting anyway produces agreement that is not real: the calendar improves and the decision quality degrades. This is the primary way a tool like this could do harm, so it is the highest-weight input in the product.
A blank advanced answer never unlocks a deeper cut. Unknowns make the recommendation coarser, not more aggressive.
written_disagreement never
decisions_findable sometimes (default: not answered)
everyone_can_reach yes
channel_ready false
Replace the meeting with writing
blocked: No one disagrees in writing in Notion.
# Converting a decision meeting into writing, in an org where
# nobody has ever objected in writing, produces agreement that
# is not real. The engine falls back to a shallower outcome
# and states the reason on the result.
Two documents, two audiences
The diagnosis says the thing you will not say to yourself, and no one else ever sees it. The change spec is written in your first person as a decision you made, and nothing in it reads as generated.
12 people · 60 min · weekly
The agenda says status. The meeting is actually the deadline that gets the status written, and the only route anyone has to raise a block to you. The replacement has to cover both, not the agenda.
Ruled out
Replacing the meeting with writing, and cancelling it: no other escalation route exists.
Cost
43 hours a month come out of the room. The written update costs you 30 minutes a fortnight, and each reader 5.
Most likely failure
The off-week update stops within a month because nothing forces it. Name the update as the deadline, and check the first two for replies before assuming agreement.
What is changing
From 3 March, this meeting runs fortnightly for 30 minutes with 5 required attendees. On off weeks I post a written update in Confluence by Tuesday 10:00.
Still gets a meeting
Anything blocked for more than two days, any decision that affects another team, and anything you would rather raise live. Message me and I will book it within a day.
Trial
3 March to 14 April. Then we review.
We go back if
Two consecutive updates get no replies, or a block goes unraised for a week. We return to weekly on the old invite list.
Not changing
Raising blocks. If you are stuck, come to me directly, same as now.
External participants see a separate rendering of the same record with cost figures, internal channel names, and internal escalation routes suppressed. One document, one suppression layer, so the two can never drift apart. Distribution is manual: permalink, PDF, or a 600-character plaintext calendar block. Meetless never posts or sends anything on your behalf.
One check on your read, and a verdict at week six
An optional anonymous poll is the only correction to owner self-report in a product with no integrations. Skip it and the result is flagged as owner-only evidence. Then the follow-up loop finds out whether the change held, which is the part a one-shot generator never does.
Results appear after 6 of 12 responses.
Could you get what you need from a written summary?
If this meeting were cancelled, what would be your first concern?
Free-text responses reach the owner verbatim, shuffled and unattributed. Individual responses are never displayed.
Going back is a documented outcome, not a failure state. The revert criteria were committed before anyone agreed to anything.
How it works
Describe the meeting
Title, headcount, duration, cadence, whether it needs live back-and-forth, how often it actually decides something, and what else it does beyond the agenda. Meetings about someone's performance, pay, or job are refused outright.
Name where the writing would go
Pick the destination, then answer the highest-weight question in the product: does anyone ever disagree there in writing? Optionally send the anonymous poll to attendees before generating anything.
Get the recommendation
One outcome, one sentence of reasoning, a table of concrete changes with before-and-after numbers, and a struck-through list of deeper options that were blocked, each with its reason.
Send the spec, run the trial
Distribute the change spec by permalink, PDF, or a 600-character calendar description block. Meetless emails you at day 14, 28, and 42, and records whether the change held, reverted, or was extended.
One price. Cheaper than one minute of the meeting.
A weekly 60-minute meeting of 12 people costs roughly 52 person-hours a month. Meetless costs $4.99.
$0
your first 3 meetings
Analyse up to 3 meetings with the full engine, poll, both documents, and the follow-up loop. Sharing is by permalink and PDF only; no org, no team membership, no shared visibility.
- 3 meeting records with full analysis
- Anonymous attendee poll
- Permalink and PDF distribution
- Day 14, 28, 42, and 90 follow-ups
$4.99
per month
Everything in Solo, plus an org with invited members, domain verification, per-record org visibility, and external participant approval. Up to 25 meeting records per month.
- 25 meeting records per month
- Org creation, invites, and admin roles
- External participant approval and external view
- Org channel inventory that prefills the flow
$38.99
per year, about $3.25 a month
The same plan billed once a year. Fits the product: trials run six weeks and reinstatement checks land at day 90, so most records outlive a monthly cycle.
- 25 meeting records per month
- All org, domain, and sharing features
- 35% less than monthly billing
- Follow-up loop across the full trial and 90-day check
Prices in USD. Cancel any time; your existing permalinks stay live through their expiry date.
Objections, answered
Does Meetless connect to my calendar or Slack?
No. Meetless has no integrations of any kind in v1: no calendar read or write, no chat tools, no document systems, and it never posts or sends anything on your behalf. You answer nine questions, and you distribute the output yourself by link, PDF, or a plaintext calendar block.
Will attendees know I used a tool?
Not from the document. The change spec is written in your first person as a decision you made. It contains no scores, no engagement percentages, no diagnostic language, and no mention of Meetless or AI. You can edit it before sharing.
What if the meeting is doing something the agenda doesn't say?
That is the core of the product. One required question asks what else the meeting does: it is the deadline, the escalation route, the ratification step, the only contact between certain people, or the only time a senior person engages. The engine blocks cancellation and conversion when those functions have no replacement, and names the block.
Can my admin or my team see my private diagnosis?
No one can. The private diagnosis is visible only to you, is never exportable, never appears in any email, and has no public URL. Org admins can see shareable change specs for records owned by the org, but never the diagnosis or your intake answers.
What can external people, like clients or vendors, see?
Only an external view of the change spec, and only after two approvals: your org admin approves the external share, and the external person explicitly accepts being named. The external view suppresses cost figures, internal channel names, and internal escalation routes. Their company gains no visibility into your org.
What happens if the change doesn't work?
The spec pre-commits revert criteria before anyone agrees to anything, and the trial defaults to six weeks. At day 42 you record held, reverted, or extended against those criteria, and at day 90 Meetless asks whether the meeting was reinstated. Going back is a documented outcome, not a failure state.
One recurring meeting in. A defensible change spec out.
Pick the meeting you already suspect. Nine questions later you have a recommendation with real numbers, a document your attendees can hold you to, and a check-in at day 14, 28, and 42 to see whether it held.
Free for your first 3 meetings. No card, no calendar access.