Autopilot

The project manager that drafts the plan

Write a brief. Autopilot proposes the board, the tasks, the owners, the dates and the meetings, and waits for your approval before any of it is created.

1 · Plans

Autopilot · drafting

Proposed plan · Data migration

4 tasks · drafted from your written brief

1Scope the migration specMaya
2Stand up staging envDev
3Cutover dry-runSam
4Sign-off & launchLead

Drafted in seconds, nothing is live until you approve

2 · Schedules

Placed in working hours

This week

Owners suggested, meetings placed

Maya
Mon–Tue
Dev
Wed
Sam
Thu–Fri

Meetings land inside everyone’s working hours

3 · Runs it, at your autonomy level

Waiting on you

Review before it acts

3 changes proposed

Create 4 tasks on the Migration board
Assign owners and due dates
Place kickoff & review in working hours
Approve & applyEdit

Plans the project

From a written brief to a full plan

Write a brief for the outcome you're after, a launch, a migration, a campaign, and Autopilot proposes the whole project: the board columns, the tasks, the order they happen in, and the estimates against each one.

Proposes board columns and a sequenced task list
Puts an owner, a due date and an estimate on every task
Works from the brief you write, in your own words
Drafted in seconds, edited like any other plan
Autopilot · drafting

Proposed plan · Data migration

4 tasks · drafted from your written brief

1Scope the migration specMaya
2Stand up staging envDev
3Cutover dry-runSam
4Sign-off & launchLead

Drafted in seconds, nothing is live until you approve

Assigns & schedules

The right owner, a realistic date

Autopilot suggests an owner for each task from your actual members, and places the kickoff and review meetings inside everyone's working hours, across time zones, so nobody is asked to dial in at midnight.

Suggests an owner for every task from your real members
Places meetings inside each member's working hours
Handles teams spread across time zones
Every date and estimate is editable before you approve
Placed in working hours

This week

Owners suggested, meetings placed

Maya
Mon–Tue
Dev
Wed
Sam
Thu–Fri

Meetings land inside everyone’s working hours

You set the autonomy level

Draft and propose, by default

Autopilot runs at one of three levels and you pick it per project. On the default, Draft & Propose, every plan, assignment and schedule change arrives as a set of suggested actions to approve, edit or reject — nothing exists until you say go. Move up a level and it applies the safe changes itself; hand it full autonomy and it runs the project as an independent PM.

Draft & Propose — the default; nothing is applied until you approve
Draft and apply safe changes — it acts on the low-risk moves, proposes the rest
Fully Autonomous — it plans, assigns and schedules on its own
Whatever the level, everything it changed comes back as a Keep or Revert list
Waiting on you

Review before it acts

3 changes proposed

Create 4 tasks on the Migration board
Assign owners and due dates
Place kickoff & review in working hours
Approve & applyEdit

Guardrails

The rules it is not allowed to break

Autonomy is only safe if the boundaries are real. Autopilot's guardrails are configured on the project and enforced at runtime: who must never be over-loaded, who has to be kept informed, and the hours it is allowed to reach people in.

A VIP list with a ceiling on the hours anyone can be assigned
Stakeholders who are kept in the loop on what changed
Communication hours evaluated in each recipient's own timezone
Access granted deliberately, per project: calendar, GitHub and chat
Waiting on you

Review before it acts

3 changes proposed

Create 4 tasks on the Migration board
Assign owners and due dates
Place kickoff & review in working hours
Approve & applyEdit
After the plan

Planning is the easy part. Autopilot stays.

A plan that nobody maintains is a document. Autopilot keeps running the project: chasing status, re-dating what slipped, moving what depended on it, and telling the people affected.

Check-ins that understand the answer

Autopilot asks the owner how a task is going and reads the reply in plain language. Answer “already slipped, about a week” and it re-dates the task — you never have to open a form.

Dependency ripple, detected and explained

When something genuinely slips, Autopilot works out what depends on it, moves the successors, and tells the people who own them what changed and why.

A merged pull request closes the task

Connect GitHub and the work closes itself when the code lands, so the board stops being a second place to report the same thing.

Capacity-aware assignment

It assigns across every active project at once, not just the one in front of it, so nobody quietly ends up with three projects' worth of work.

A risk assessor watching the RAID log

Risks raised in meetings and risks it infers from the plan land in the project's RAID log rather than in someone's memory.

Keep or revert, every cycle

Whatever level you run it at, every management cycle ends with a list of what it changed and a one-click way to undo any of it.

Why it works

Faster to start, never on autopilot blindly.

Kickoffs in minutes

Skip the blank page. Autopilot turns a few paragraphs of brief into a structured, assignable plan in seconds.

Owners and dates, already filled in

Every proposed task arrives with a suggested owner, a due date and an estimate, so the plan is reviewable instead of blank.

Always under control

Proposal-first is the default and guardrails apply at every level, so Autopilot takes the busywork while the decisions that matter stay yours.

Business plan

Autopilot ships with the Business plan

Autopilot ships to teams on the Business plan. Start free, then turn it on when you’re ready.

Let your meetings run the project.

Connect Noots once and watch every conversation turn into updated boards, written summaries, and hours handed back to your team.

Free to start · No credit card required