Capture, share, collect, decide. The pie fills as an idea gets round them.
Decision records, roadmap, tasks, timetable, log and procurement, for every idea that makes it to a project.
A feature-request board, a captcha and an AI worklog for your own site, each one script tag, nothing to host.
A six-digit code sent by email signs in founders, reviewers and teams alike.
Four steps to a decision. The pie fills as your idea gets round them.
Write the idea down in a sentence. Add detail when you have it.
Send a private link to people whose opinion you trust. They confirm an email, nothing more.
Everyone answers the same questions, so you can compare what they say.
Proceed, pivot, shelve or park — and keep the reasoning.
Decide to proceed and the idea turns into a project, with the feedback and the reasoning still attached. From there, six pages keep it organised: the decision is where the work starts, not where the record ends.
Numbered records of what you decided and why. Once accepted, a record never changes.
The big pieces of work, each with a state worked out from the tasks under it.
A board with columns you name. Take a task, move it along, mark it done.
Phases and milestones on one timeline, with today drawn across it.
A month calendar that writes itself as the project moves, with room for notes of your own.
The software and services the project pays for, what each costs a month, and the decision that chose it.
A project also puts things in front of its users, on your own site. Each is one script tag; they run here, so there is nothing to host, and what they collect lands in the project. Each tool is $5 a month per project while it is on; see the pricing.
A public board where your users suggest features, vote and comment, as a page with its own address or as a widget on your site. You triage from the project; declined requests leave the board; a board can be kept to your team while anyone still suggests.
A floating button or the board inline. Voters sign in with an emailed code; no accounts to run.
A code in a picture for the forms on your own site. A placeholder in the form and the script once on the page; when the code is right the widget leaves a token in the form, and your server checks it with one call and your secret.
New codeAnswers shaped like the captchas your code already knows, so switching means a new URL.
Your team points at something on your own site and logs the change for your AI to make. It is a task on the board at once, the AI’s, with the page, the element and its HTML; the AI reads its worklog, accepts the task, works through it in the repository, logs its time and finishes it.
button.buy.primary“Buy now”Only the project’s people see the button. The worklog is Markdown at a secret address: the AI’s manual and its tasks, with every call it can make.
Everyone who opens your link gets the same questions in the same order, so their answers line up side by side instead of drifting into opinions you can’t compare.
They confirm an email once and answer once. You see their name and their answers, never their address.
Want to dig into an answer? Open a private conversation with that reviewer from their response, or record a short pitch clip so they hear the idea from you.
Every founder starts with a space of their own. Ideas stay private until you share them, and projects stay yours until you move them.
Make one for your team and invite people with a role, or let anyone with your company’s email domain join the moment they sign in. Ideas and projects made there belong to the team.
Project manager, business analyst, developer, designer: each role is ticked for what it may do, on one table you can change. Who may do what follows the role, everywhere.
Write it down, send one link, decide with the answers side by side, and keep going with the tools a project needs.