InfraStudio Agents Start free

Reference

Ideas

One page for what your customers ask for and what you want built - write a requirement, let the agents find what customers need, set the product's direction, and read the inbox.

Last updated

Open Ideas in the menu. It shows the product picked at the top of the side bar. Everything on it is plain words from you, your team and your customers; nothing on it starts work on your code until someone says yes to a suggestion.

The Customer needs review

Customer needs review is an agent that does Find what customers need for you on a schedule. It is off until you turn it on, on the Agents page, where you can also change how often it runs (every Monday at first). Each time, it reads your connected tools, such as Bagel, groups what is new in the inbox into draft requirements, and sends your news (Telegram, Slack or e-mail) how many it wrote, with a link to this page. It never approves or builds anything: you decide on each draft. A run with nothing new to group does not count toward your plan's runs.

What do you want to do?

Two cards come first, for people who may say yes or no to suggestions. Everyone else reads the rest of the page.

CardWhat it does
Build somethingWrite What do you want? and How will you know it's done?, then press Write it as a requirement. It becomes a requirement, such as R1, and a suggestion at once. It works like require in Chat, and the message shows there too. Nothing is planned or built until you say approve or implement.
Check an ideaWrite What's the idea? and press Check it. One agent run reads the idea against what customers asked for, your requirements and your direction, and says how strongly the evidence supports it. Nothing is built. See Checked ideas. A check counts toward your plan's runs, and one idea is checked at a time. Only people who may start an agent can check an idea.
Suggest ideas"What should we build next?" One agent run reads the inbox, your requirements and your direction, and proposes up to five needs as drafts under Requirements, each with the messages behind it. You approve or reject each draft. Nothing is built. It counts toward your plan's runs, and only people who may start an agent can use it.
Find what customers needGroup signals lets the agents read the inbox and group the messages that ask for the same thing into draft requirements, each with the messages behind it. See Requirements. To do it every week by itself, turn on Customer needs review on the Agents page.

Checked ideas

Each idea you checked, newest first, with its answer:

  • how strong the evidence is: Strong evidence, Some evidence, Little evidence, No evidence yet or The evidence speaks against it;
  • a short summary, then the reasons For it and Against it;
  • how many messages in the inbox it is based on, and the requirements that are the same need.

Build it copies the idea into Build something, so you can say what done looks like and write it as a requirement. The answer is the agents' reading of your evidence, not a promise: check the messages behind it before you build something big.

Product direction

What the product is for, who its customers are, and what comes next, in your words. For example: "For small bakeries. Next: invoices they can send by e-mail. Not now: a mobile app." Every job of the agents on this product reads it, to judge what to do first. It can't change what the agents are allowed to do.

Write it in the box and press Save the direction. It saves at once, without the bar at the bottom of the window. Empty the box and save to clear it.

Who can change the direction: a person who may change the product's settings. Everyone else who sees the product can read it. See Roles.

Requirements

Group signals, under Find what customers need, looks for related chat suggestions and customer feedback. Each run reviews up to 30 ungrouped messages and counts toward your plan's run limit. A message can join an open requirement about the same need. Two or more related messages can become a draft.

Each draft lists the need, what the work covers, how to measure it, and what must be true when it is done. Open the signal count to read the recent messages behind it. People who may say yes or no to suggestions can use Approve requirement or Reject requirement. Approve requirement makes the draft a suggestion a moment later. The suggestion uses the words you approved, not the customers' messages, and the agents check the change against what the draft says must be true when it is done. Like any suggestion, it waits for you to say approve or implement before anything is planned or built. The requirement then shows its suggestion, where it stands, and Open the pull request once there is one. The pull request names the requirement and how many messages it stands on, but not what the customers wrote or who they are. Reject requirement records the no, and nothing more happens.

When a requirement's change is live, the requirement shows Done: it is live, and your news (Telegram, Slack or e-mail) says so, with how many messages in the inbox it stood on, so you can tell the people who asked. This holds for the requirements you write yourself too.

A draft names its measure in words. When your product has a source that can read a number (Google Analytics 4, PostHog, Clarity or Sentry), the draft also names the number to watch, such as "checkout conversion in GA4, higher is better". The suggestion an approved draft becomes takes that number, and the agents read it again 7 and 14 days after the change is live. A draft without a number to watch is not measured. See How we check that a change worked.

You can also write a requirement directly in Chat, for example require invitations by link, done when an admin copies a link and a new person joins with it. It gets a number, such as R1, and creates a suggestion that waits for your approval.

Inbox

What customers and your team ask for: each suggest in Chat, Telegram or Slack, and what customers send with the feedback button or from your product's server. The newest message is first. Receiving a message does not start an agent. See Collect feedback from customers.

ButtonWhat it does
Make a feedback keyMakes the key the feedback button sends. The key and the line to paste into your pages are shown once.
Make a new keyReplaces the key at once. The old key no longer works.
Turn feedback offRemoves the key. The product takes no feedback until you make a new one.
Read nowUnder Connected tools: reads a tool at once (Bagel, FullStory), between its own reads (every few hours for Bagel, once a day for FullStory). Each tool shows when it was last read and what that read found.
Take outTakes one message out of the inbox, for example spam.
Show olderShows the older messages.

Who can take messages out: a person who may say yes or no to suggestions in the product. Who can make or remove the key: a person who may change the product's own keys. Everyone else who sees the product can read the inbox. See Roles.