Setup brief · source-backed board planning

Send a better setup request before buying anything.

IdeasDiamond works best when the first board starts from real repeated requests, not a blank suggestion box. Use this brief to collect the minimum context for a credible public board, widget placement, and first roadmap/changelog response.

Email this brief View €149 setup pilot Read seeding guide Invite first voters Contact IdeasDiamond

The email button opens your mail client with this brief prefilled. Nothing is stored by this public page; do not send passwords, API keys, payment details, or sensitive private data.

Brief builder

Fill it once, then copy or email the same brief.

This is still client-side only. The fields below update the mailto body and preview without sending or storing anything.

Email filled brief
IdeasDiamond public board setup brief

Organization / project: 
Website: 
Best contact: 

1. Board promise
What one public idea board should we launch, and what decision should it clarify?


2. Audience
Who should submit or vote first?


3. Existing source evidence
Where do repeated ideas already show up? Please paste links or describe sources.


4. Starter ideas
List 3–7 recurring requests that could become voteable public ideas.


5. Website placement
Where should the board, embed, or widget appear on your website?


6. First response loop
What first roadmap/changelog response would prove this board is alive?


Please tell me whether this fits the €149 founding setup pilot.

What to prepare

Six answers make the setup useful.

1. Board promise

Name one narrow public board and the decision it should clarify.

Example: “Collect restock and product-line requests for Northstar Coffee Gear customers.”

2. Audience

Who should submit or vote on ideas first?

Customers, members, residents, open-source users, workshop participants, website visitors, fans, or local regulars.

3. Existing source evidence

List where repeated ideas already appear so the first board is not fake or empty.

Reviews, GitHub issues, support tickets, emails, social comments, app-store feedback, in-person notes, forum threads.

4. Starter ideas

Pick 3–7 recurring requests that can become voteable public ideas.

Keep each one specific enough to vote on: “Add decaf single-origin beans” beats “More products.”

5. Website placement

Choose where the board, iframe, or one-script widget should live.

High-intent pages work best: product pages, menu pages, docs, changelog, support, pricing, events, reservation/contact pages.

6. First response loop

Decide what kind of first roadmap or changelog receipt would prove the board is alive.

Move one idea to under review/planned/shipped and publish the short reason publicly.