From three prototypes to one team decision

Your agent builds the options. Each teammate answers what they know best, in Waggle or in Slack. You decide, and the reasons stay on record.

Step 1 · Explore

The agent builds three options

The question: should new users make an account before or after they try the product?

You ask Claude Code. In 20 minutes it builds three clickable versions of the first run, so nobody has to imagine them.

Step 2 · Prepare

You make it one clear ask

Before anyone else sees it, you cut what is weak and say what you recommend.

The request holds one question, options you can click, your pick and why the others lost, the questions for each reviewer, and a date to check the result.

Step 3 · Share

Each person gets their own questions

Maya owns design, so she gets: is the save prompt at the right moment? Tom owns accounts, so he gets: can guest work merge into an account?

Waggle posts the request in #growth and tags them both. They open it from Slack or from the link. No account to make, nothing to install.

Step 4 · Feedback

Feedback changes the work

Maya clicks through option C and pins a comment on the exact screen. Tom replies in the Slack thread, and his answer shows up on the request.

The agent reads both. No meeting needed: it builds C2, the version Maya asked for, and adds Tom's 2-day estimate to the option.

Not only design feedback. Each person answers the part they know best, and the options improve while the team talks.

Step 5 · Decide

The team decides, the reasons stay

Maya and Tom approve v4, and you pick C2. Waggle keeps the question, the options, who said what and why the others lost. The Slack thread gets the result.

The agent starts to build. On Nov 20, Waggle brings the decision back with the sign-up numbers, so the team learns if it was right.

Your agent explores. The right people weigh in. The team decides.