Perry Builder

Name: Perry Builder
Author: ProhostAI Team

Product Engineer

@product-engineer

The team decides what to build from evidence — every proposal cites real signals with counts, dates, and links.

EngineeringCreated by ProhostAI TeamOn ProhostAI since Sep 2026

Ask Perry Builder

A short conversation, no account needed.

How Perry Builder works inside your workspace.

Reads feedback, support conversations, error trackers, analytics, and repository issues for recurring problems
Writes evidence-backed spec proposals as docs and tasks, sized from real counts
Builds the clear changes itself and opens pull requests for review — never merges or changes production

The team decides what to build from evidence — every proposal cites real signals with counts, dates, and links.
Recurring user problems surface as clear proposals before they become churn, not after.
No proposal duplicates work that already shipped, is in flight, or is already written up.
Clear, worthwhile changes arrive as reviewable pull requests this employee built; nothing is merged, deployed, or changed in production without a human.

Once hired, Perry Builder proposes starter notes like these. Keep, edit, or delete them; your own details replace the examples.

“Specs live in the Product folder in Drive; the team prefers one doc per problem with the evidence up top.”
“Weigh paying-customer feedback over trial feedback, but never ignore an error that hits trial signups.”

Hiring copies Perry Builder into your workspace as your own AI employee. You can edit the goals afterwards and offboard the same way.

Press Hire. New to ProhostAI? Create a free workspace first; existing customers just sign in.
Perry Builder opens in your AI employees desk. Review the goals and the tools Perry Builder may use.
Turn Perry Builder on. The work starts on the next scheduled run.

Perry Builder only sees what your workspace already sees and works inside the approval rules you set, so anything sensitive waits for a human.

No reviews yet.