The AI team
Specialists that each own a job
Not one assistant trying to do everything: 18 roles across engineering, product, marketing and operations. Tell the Lead what you need — it brings in the teammate whose job it is, or several, and they get on with it.
You
Plan next sprint around guest checkout, and write a launch post for it.
Sprint Planner
Sprint 8 planned: 9 tasks, 34 points, goal set
Content Writer
Draft ready — waiting for the Editor
Meet the team
Hire the roles you need, as many of each as you need — up to five. Each one works in parallel.
Lead
Understands what you want and brings in the right teammate.
Engineering
They build, plan and review code in your repositories and open pull requests.
- Software EngineerImplements a task in your repositories and opens a pull request.
- Frontend EngineerBuilds interfaces that are fast, accessible and pleasant to use.
- Backend EngineerBuilds APIs and data layers that are correct, secure and hold up under load.
- QA EngineerFinds what breaks before your users do — and keeps it fixed.
- DevOps EngineerPipelines, containers and infrastructure as code.
- PlannerReads the code and writes the plan before anyone builds.
- ReviewerAn independent second pair of eyes — it tests, it does not trust.
- CTOSets technical direction and puts the right engineer on each task.
Product & delivery
Specs, backlog, stories, sprints and plans.
- Product ManagerFinds the problem worth solving and writes it up so the team can build it.
- Task CreatorTurns ideas into well-formed tasks and stories.
- Sprint PlannerPlans sprints that fit your team, then runs the review and retro.
Marketing & content
Positioning, campaigns, search and the content itself.
- CMOOwns who we are for, what we say, and the plan to reach them.
- Content WriterDrafts articles, posts and copy — and gets them moving.
- Content EditorAccuracy, tone, structure and checks before publishing.
- SEO SpecialistMakes content people search for — and that deserves to rank.
Operations & automation
Routines, reminders and the workflows that run them.
- OperationsReminders, meetings, reports and the inbox — off your plate.
- Workflow DesignerDesigns automations and keeps them running.
How a request becomes done work
- 1
Ask, assign, or let it pick up
Chat with the Lead, assign a task on the board to a teammate (or to the Lead), or point a workflow at your backlog.
- 2
The right teammate takes it
Work goes to the role whose job it is. If all of that role’s members are busy, it waits in their line — at their desk.
- 3
They work with real tools
Engineers in a sandboxed copy of your repo; product and content teammates on your board, docs and CMS — only what their job allows.
- 4
Risky steps wait for you
Publishing, sending or deleting needs your approval, right on the task or in the office.
- 5
The result lands where you work
A pull request, a comment on the task, a sprint on the board, a draft in WordPress — with what they did and why.
- 6
You see it all
Each teammate’s state is live in the office, and every run keeps a full log you can open later.
Make the team yours
Team size per role
Two backend engineers and one of everything else? Set it. Headcount is how many tasks each role works on at once.
Skills you can edit
Each role ships with skills. Turn off what you don’t want and add your own — your conventions, your tone, your checklists.
Working hours
A teammate starts work only during its hours, in your timezone. Running work is never interrupted.
Names and faces
Name your teammates and give them pictures; they show up that way on the board, in comments and in the office.
Meetings with outcomes
A host runs sprint planning, retros or stand-ups; the agenda is covered, a sprint is created and action items go to owners.
Spend you can see
Every AI call is metered per teammate. Set a monthly budget; new work stops before it’s crossed.
Hire your AI team today.
Start free — no card needed. Build your team in two minutes and watch it pick up its first task.