Build

Build apps, and build what customers ask for

Simple apps that run on Supaforce, and the Build Room, which briefs your coding agent from customer feedback.

Build a simple app

Build makes small apps that run on Supaforce: pages, lists, people, automations and emails, put together for one job. A rewards scheme, a partner portal, an order form that emails you. Nobody needs to write or read code.

  1. Open Build in the sidebar, on the Runs on Supaforce tab.

    Describe what you need the way you would explain it to someone joining the team.
  2. Press Get a quote, or Talk it through first.

    Talking it through lets the Builder ask what it needs to know before it plans anything.

You can also ask for it in Slack, or from Claude or ChatGPT once they are connected.

Get a quote, then watch it built

The quote lists every part of the plan. Anything you already have is reused for free; each new list, page or building block shows its price in credits. Nothing is built until you press Approve and build.

Once you approve, the same screen shows each part ticked off as the Builder makes it. You can leave and come back: the screen picks the build up where it is. When it finishes, Open takes you to the app and Share gives you its link.

How the code is checked

When a build needs a new building block, Supaforce writes the code and checks it automatically before it goes live: it looks for things code like this must never do, runs it, and has a reviewer go through it against a fixed list. Code that passes goes live. Code that fails goes back to the Builder with each problem and how to fix it. You are never asked to read or approve code.

Automations are different: each one still waits for your yes before it runs.

Set up the Build Room

The Build Room is for businesses that make their own software. It reads what customers tell you, ranks what to build next, and briefs the coding agent your team already uses, such as Claude Code or Codex. The agent works in your own repository. Supaforce never holds your code.

Open Build, then the In your product tab, then Connect and settings. You need at least one source, the repository and one coding agent.

  1. Connect where customers talk to you.

    Any of Sentry, Granola, Fireflies, Notion, Airtable, Linear, GitHub issues, Slack and Intercom, connected in Tools. Setup shows what each one reads, and Change picks other search words or, for Slack, the channels.
  2. Install the Supaforce GitHub app on your repository.

    It posts an approval check on pull requests and sees merges and deploys. It does not ask to read your code.
  3. Connect your coding agent.

    Add Supaforce to the agent the same way as any AI app, and allow Read RFCs and Write specs and find signals.
  4. Make the check required, under Make approval required.

    Setup reads your repository's rules and gives you the exact steps. Until the check is required it still shows on every pull request, but GitHub will let an unapproved one merge.

In Slack, mention @Supaforce build room in a message's thread to file that message, or add your request after a colon to file it as something you asked for.

Choose what to build next

Requests groups what customers said by meaning, so five people describing the same problem in different words become one request, quoting each of them. Each one says why it ranks where it does, in one of three lanes: Urgent, Roadmap and You asked.

  • Accept → hand to the coding agent turns a request into a brief. This is your first yes: which problem gets solved.
  • Rank it yourself moves it, with a line saying why, which is kept.

Approve your agent’s plan

A brief says what the problem is, who has it and what success looks like, never how to build it. Your coding agent reads it with your code and sends back a plan, section by section. Mark a section Looks right or comment on it; comments go back to the agent as a revision.

Approve and build is your second yes: how it gets solved. The agent builds on a branch and opens a pull request, and the approval check passes only for a pull request tied to the plan you approved. Your own review and deploy process does the rest.

See whether it worked

Supaforce sees the merge and the deploy on GitHub. A week and a month later it reports what changed against what was expected, and marks the customer feedback behind it as resolved. Tell the customers who asked drafts a short note to each of them, sent only when you say yes.

What it costs

  • An app: the price on its quote, in credits. Anything reused is free.
  • The Build Room: 1 credit for each new piece of customer feedback it finds, and 5 for each brief. Feedback it has already read is not charged again.

Build is on every plan.

Still stuck?

Ask any agent “how do I…” in the app — they answer from this help centre. Or email support@supaforce.ai and we'll reply within one business day.