Count the tools your signups asked you to connect to, and build the one most people wait for. Everyone who asked hears when it ships.

What you get

1count of signups per requested tool, most asked firstCollection
1list of who asked, per tool, to tell when it shipsLead
1waitlist per tool, once you open oneWaitlist

Your agent does

Collection.query

You, to your agent

Which integrations do people want?

Should Teams come before Slack?

How many people asked for Outlook?

# Collection.query
curl -X POST https://api.sb/leaseline.app/collections/query \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"Waitlist signups grouped by the integration they asked for, most requested first."}'

import { $ } from 'startup-builder'

await $.Collection.query({ query: 'Waitlist signups grouped by the integration they asked for, most requested first.' })

npx startup-builder do Collection.query --json '{"query":"Waitlist signups grouped by the integration they asked for, most requested first."}'

{
  "name": "do",
  "arguments": {
    "code": "return await $.Collection.query({ query: 'Waitlist signups grouped by the integration they asked for, most requested first.' })"
  }
}

The same sentence does more as the business grows:

State	Calls	Asks first
Idea	`Collection.query`
Live	`Collection.query`, `Waitlist.create`	Open a waitlist for the top one?

Change it

Open a waitlist for Outlook.
Tell everyone who asked for Slack that it shipped.
Break it down by company size.

Under the hood

Systems: Waitlists, Product planning
Nouns: Integration, Waitlist, Lead, Collection
Events: Collection.queried, Waitlist.joined

The signup interview asks which tools people use today. Collection.query groups those answers by tool across every Lead, and a Waitlist per tool keeps the people who asked.

What you getCopy Anchor Link

Your agent doesCopy Anchor Link

Change itCopy Anchor Link

Under the hoodCopy Anchor Link

What you get

Your agent does

Change it

Under the hood