Work · Community report
Find demo meeting slots for your startup
One founder on X says Muse found 2 demo meeting slots in the Bay Area so far, with a goal of 10. The post does not say who the contacts were or whether any meeting happened, so below: a prompt to adapt and the point where it should check with you before reaching out.
What you can get
What it is
Demo meeting slot list
A short list of candidate meeting slots in your target area, each with who it's with, the proposed time, and confirmation that they've agreed before it goes on your calendar.
It came back right when
- Every proposed slot names who it's with and where the contact came from.
- No meeting was confirmed without your review.
- The confirmed count matches what's actually on your calendar, not just what was proposed.
- The demo's purpose is stated for each slot.
The checks are editorial, not from the source.
- Set the targetStops for your approval
Number of demo slots, area, and who counts as a good contact.
- Build the candidate list
From your list or outreach source, not an open search.
- Propose timesStops for your approval
Matched to your calendar; nothing sent without review.
- Track confirmed slotsStops for your approval
Only count a slot once the contact has actually agreed.
Editorial, not from the source
Works when
- You have a list or clear criteria for who should get a demo
- You can review proposed meeting times quickly
- You want a running count of confirmed slots, not just outreach sent
Does not work when
- You want the agent to decide who to contact with no list or criteria
- You need every contact personally vetted before any outreach happens
- You expect a guaranteed number of meetings by a deadline
Find demo meeting slots for your startup: review template
| Item | What it is based on | Status |
|---|---|---|
| [Target] | [Your stated number and area] | [Confirmed by you] |
| [Candidate contacts] | [Your list or criteria] | [Reviewed or rejected] |
| [Confirmed slots] | [Contact's agreement to a specific time] | [Awaiting your review] |
The source case
On X, @sidhdharth, writing as a founder, reports asking Muse to find demo meeting slots in the Bay Area, with the agent locating two so far while aiming for ten. The post gives no detail on who the contacts were, how the slots were found, or whether any meeting has actually taken place; it adds only that the author found this useful and planned to write a longer guide. Checked on 2026-10-09, it is one individual's early report, not evidence of how many slots an agent will find for a given target or area.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
I asked @Muse to find be demo slots in the Bay Area and it found me 2 already, aiming for 10. Pretty useful for founders. writing a guide soon.... https://t.co/mzJFim70xk
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring Target number of demo meetings and the geographic area, A contact or outreach list, or criteria for who counts as a good prospect, Your available times, What the demo should cover. Acts Looks for contacts open to a demo meeting, from a list or outreach source you provide. Proposes times for a demo meeting. Does not confirm a meeting time or send an invite without your review. Source community report, checked 2026-10-09.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- Target number of demo meetings and the geographic area
- A contact or outreach list, or criteria for who counts as a good prospect
- Your available times
- What the demo should cover
Connected
- Calendar access to check your availability and hold slots
- A way to reach contacts (email, messaging, or a CRM)
Approved by you
- Your review of every proposed contact before outreach, if outreach is involved
- Your approval before any meeting time is confirmed
- No authority to represent your startup beyond proposing a meeting
How to try it
Editorial, not from the source
- Give the agent your target: how many demo meetings you want, the geographic area, and the kind of contact you're trying to reach.
- Have it work from a contact list or outreach source you provide, rather than letting it invent who to contact.
- Each time it identifies someone open to a demo, have it propose times that work for both of you rather than booking the first slot it finds.
- Review every proposed meeting before it's confirmed: who it's with, the time, the location or call link, and what the demo is meant to cover.
- Keep a running count against your target so you know how many confirmed slots you actually have, not just how many were proposed.
Start from a list, not a search
An agent chasing demo meetings works best when it isn't deciding who counts as a prospect on its own. Give it a contact list, an outreach source, or at least explicit criteria: the kind of company, role, or situation that makes someone a reasonable fit for a demo, plus the area you're focused on. Without that, 'finding' slots can mean anything from a genuine reply to a cold guess at who might be interested, and the two look identical in a tally that just says how many slots have been found. Set the target number up front too, so progress toward it means something specific rather than an open-ended search that never quite finishes. The clearer the starting list or criteria, the easier it is to tell later whether the agent actually reached the right people.
Separate 'found' from 'confirmed'
The report behind this page counts two slots as found while aiming for ten, without saying what 'found' means: a reply agreeing to a specific time, a calendar hold with nobody confirmed yet, or just a contact who seems open to it. That gap matters, because a count that mixes those stages overstates how many real meetings are actually lined up. Ask the agent to label each item by stage, proposed, pending a reply, or confirmed, so your running total reflects meetings that will actually happen rather than contacts that might take one. A confirmed slot should mean the other person has agreed to a specific time, not that an invite went out and nobody has answered yet. Treat anything short of that as still in progress, not as progress itself.
Keep the demo's purpose attached to the slot
A calendar full of confirmed times isn't useful on its own if nobody remembers why each meeting was booked. Have the agent note, alongside every proposed or confirmed slot, who the contact is, how they came up, and what the demo is meant to cover for that specific person, rather than treating every meeting as interchangeable. This also makes review faster: instead of re-explaining the whole search each time, you can glance at the note and decide whether a meeting is still worth keeping on the calendar as your plans change. If a slot's purpose has gone stale by the time it arrives, that's a cue to reschedule or cancel it rather than show up unprepared.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- One early attributed report. It says two slots were found toward a goal of ten, with no detail on who was contacted, how, or whether any meeting has actually taken place.
- The post does not say what counts as a 'found' slot: a calendar hold, a reply agreeing to a time, or something else. Confirm that meaning before you rely on the count.
- The Bay Area was the stated area; nothing here establishes that an agent can find demo slots in any other location or market.
- Nothing here authorizes the agent to contact anyone or confirm a meeting time without your review.
Stop and check
Editorial, not from the source
- Before outreach: confirm who the agent should be contacting and why.
- Before a time is proposed: your availability is accurate.
- Before anything is confirmed: you've reviewed who it's with, when, and what the demo covers.
If it goes wrong
Editorial, not from the source
- The agent counts a slot as 'found' before anyone has agreed to a time
- Ask for the status of each slot explicitly, proposed, pending reply, or confirmed, and only count confirmed ones toward your target.
- Contacts come from outside your intended list or area
- Give the agent an explicit list or set of criteria rather than an open-ended search, and have it check back before contacting anyone not on it.
- You can't tell why a prospect was considered a good fit for a demo
- Ask the agent to note, for each proposed contact, what made them a candidate, so you can review the reasoning rather than just the result.
Common questions
Can Muse really find demo meeting slots for my startup?
One founder reports asking it to find demo slots in the Bay Area and getting two toward a goal of ten. The post gives no detail on how, and this is one early, individual report that this directory has not reproduced.
Does it decide who to contact on its own?
It shouldn't. Give it a contact list, an outreach source, or explicit criteria for who counts as a good prospect, rather than letting it search without direction.
What does 'finding' a slot actually mean?
The source doesn't say. Ask the agent to label each item as proposed, pending a reply, or confirmed, and only count a slot toward your target once the other person has agreed to a specific time.
Will this work outside the Bay Area?
Unknown. The one report behind this page is specific to that area; nothing here shows it works the same way for a different market.
Does it book the meeting without me seeing it first?
No. Review who it's with, the proposed time, and what the demo covers before anything is confirmed on your calendar.
Next
Related to this task
More in Work
Get recurring task recommendations — ask your own agent to check for relevant updates.