Scoped

Answer the inquiry first, then deliver the night you promised

The CRM for event planners: every inquiry and proposal on one board, the booked event broken down from venue to wrap-up, and the client’s whole history beside it. Your planners, your day-of lead, and your AI assistant work from the same record.

  • Set up in an afternoon
  • Free for 3 people
  • Day-of leads open the event on their phones
A woman stands in a white event tent watching a crew on ladders hang drapes and light fixtures before an event

From the first inquiry to the morning after.

An event is sold months before it happens and delivered in one night, through a dozen vendors. Scoped keeps the inquiry, the proposal, the event, and the client on one record, so nothing is retyped between the first call and the load-out.

Reply to the inquiry before they book someone else

An inquiry lands Saturday night: a 150-guest wedding next October, a rough budget, and a line saying they’re talking to two other planners. Monday morning someone on your team adds it to the board in a minute, with the guest count, what they asked for, and who is calling back. It doesn’t sit in a shared inbox waiting for someone to notice.

Name the stages the way you already talk: Inquiry, Consult, Proposal sent, Booked. The proposal goes out from the tool you already write it in; the amount and the history live on the card. The board shows what you have out and what it adds up to.

The $36,800 product launch party that’s gone quiet for eight days is sitting right there, not three threads down. When you call to follow up, the consult notes are on the card: the rooftop they loved, the CEO who wants a short toast, the guest list that keeps growing.

Next Tuesday. The Saturday-night inquiry got its call back before 10, and the proposal that went quiet has a follow-up on it by lunch.

See the sales pipeline

Try it: drag the $36,800 card to Booked.

Inquiries and proposals on the board, with the stages named the way an event planner says them.

Turn the booked proposal into the event, from venue to wrap-up

When the client says yes, one click turns the card into the project with the client attached. Break it down the way you already run an event: venue and floor plan, vendors, menu tasting and final count, run of show, day-of, wrap-up. Each piece has an owner and a status, so the tasting is never the thing three people each assumed someone else confirmed.

Changes arrive right up to the week of. Twenty-two guests switch to the vegetarian plate, the rooftop replaces the ballroom for the cocktail hour, the DJ needs a second power drop. Each one goes on the phase it touches, as a comment the whole team sees. Your day-of lead reads it on their phone, and when the client calls to ask whether the caterer has the new count, whoever picks up has the answer.

Your Focus view shows only what’s waiting on you: approve the floor plan, confirm the final count, call the florist back about the arch. Your day-of lead opens the same view and sees theirs: confirm the load-in order, send the vendor contact sheet, set the timing of the toasts.

See Projects
Two event staff in dark suits pour champagne into rows of glasses at a white-clothed table by the windows before guests arrive.
A booked launch party broken into phases, from venue to wrap-up, each with an owner and a status, with the client linked at the top.

Wrap up with the whole story, then book them again

Every change, from the first venue walkthrough to the load-out note, is recorded on the event with who made it. Wrap-up is a phase like any other: the vendor thank-yous, the photos to pass along, the note on what you’d do differently. When it’s done, archive the event. The client keeps the history.

Corporate clients often come back for next year’s party, and couples send their siblings and friends. When Fairlight Architects calls about this year’s holiday party, their page already shows last year’s: the venue, the headcount, who ran the day, and the note that the partners want speeches before dinner, not after. You pitch the next one from what you know, not from a blank page.

See Clients
Two staff reset white-clothed tables on an empty seaside terrace under an awning, boats on the water behind them.
An event’s activity: each change recorded with who made it, including an update from a connected assistant under the person who authorized it.

Find the unconfirmed item before the client does.

Connect Claude Code or Codex to your workspace and ask it about the real work: the proposals that went quiet, the open items on next week’s event, the client you’re about to call about this year’s party.

  1. Check the Tallis launch party for anything still unconfirmed and leave a note for whoever owns it.It reads the event’s phases and comments, finds the AV load-in time missing from the run of show, and posts a note for Owen, recorded under your name with the connection it came through.
  2. Which proposals still have no reply, and what did each client love about the plan at the consult?It reads the board and the client pages and lists each unanswered proposal with the event date, the amount, and what the client loved at the consult.
  3. Before I call Fairlight about the holiday party, pull what we did for them last year.It pulls the client’s page and answers with last year’s event, the venue, the headcount, who ran the day, and the notes the team left.

You approve the connection for one workspace, and you can revoke it whenever you like. How assistant updates work.

The assistant’s update is recorded under the person who asked for it, with the connection it came through.

They asked three planners. Be the one who called back first.

Next Tuesday, the weekend’s inquiries have been on the board since Monday morning, each with someone calling back. Every open item on the launch party has an owner, and the day-of lead already knows about the vegetarian plates. Scoped takes an afternoon to set up.

Free for three people. 30 days of Pro on your first workspace, no card.