Tell Paolo what your product needs. He gets it built and shipped.
Start with a change you want, like a new pricing section or a shorter sign-up form.
Paolo is in early access while we tweak his performance. Leave your email and we will come to you when a seat opens.
Early accessThis is what one request looks like.
Someone asks for a change to the site, and a teammate adds to it mid-build. Paolo asks what he needs to know, lists what he will build, folds the addition into the next round, and ships when every item is met. The mark on the request tells everyone where the work is, without opening the thread.
Ask for a change, and he takes it from there.
Ask the way you would ask a colleague. There is no spec to write.
He keeps the backlog
Small coding agents do the building. Paolo decides what goes next.
- Waiting
- New customer logos strip
- In progress
- Shorter sign-up form
- Shipped
- FAQ under the pricing table
He ships safely, and you set the rules.
Paolo keeps sending rounds to his coding agents until every item is met. Then he picks one of three ways to merge:
- Ship
- A small, safe change that does exactly what was asked. He merges it and posts one line.
- Show
- A notable change people should know about. He merges it and posts a short summary of what changed.
- Ask
- A risky change, or a question about direction. He opens a pull request on GitHub, and you review and merge it there.
- Optional: Always ask
- A change to tests, dependencies or CI always gets a pull request, whatever he would have chosen.
Sam Okonkwo10:02Can we add an FAQ under the pricing table? The same five questions keep coming in.
One product associate for your whole workspace.
Paolo takes the changes your team asks for, gets each one built and checked, and ships it.
Paolo
A bar shows how much you have used. It resets every 7 days.
- One price covers everyone in your Slack workspace.
- He picks up work from the channels he is set up in.
- He reviews every change before it ships.
- You choose, per channel, whether a person approves every merge.
- Good for trying Paolo out on small changes.
Paolo 5x
RecommendedThe same week of work fills a fifth as much of the bar.
- One price covers everyone in your Slack workspace.
- He picks up work from the channels he is set up in.
- He reviews every change before it ships.
- You choose, per channel, whether a person approves every merge.
Paolo 10x
The same week of work fills a tenth as much of the bar.
- One price covers everyone in your Slack workspace.
- He picks up work from the channels he is set up in.
- He reviews every change before it ships.
- You choose, per channel, whether a person approves every merge.
Cost is per workspace, billed in USD. One person pays, and the plan covers everyone in your Slack workspace. Your first 27agents bot starts with a 7-day free trial. Cancel anytime.
He only reaches the code you connect
Paolo's coding agents work in your code through our GitHub app, and he only reaches the repositories you connect. Each job runs in its own sandbox. A channel can require a person to approve every merge. Anyone in a channel can steer him, so use a private channel if only some people should. Leaving is clean: uninstall the 27agents app from your GitHub settings and Paolo loses access immediately.
- ✓The repositories you pick on GitHubto read the code, push each job to its own branch, and merge a finished change
- ✓The Slack channels he's inand the repositories you add to each, nothing from a channel he is not in
- ✓What each coding job sends backthe checks, the logs and the screenshots, which he reviews before anything merges
Each job runs in its own sandbox, which is deleted when the job ends.
Paolo is one of the 27agents team
Em, who reads your mail, is live today. Paolo joins your Slack the same way, with one click. Then you connect GitHub and add repositories to his channels. One plan covers everyone in your workspace, so the whole team can ask him for changes.