How to Build an AI Project Manager That Keeps Your Team on Track
Project managers spend roughly 60% of their time on status chasing — pinging people for updates, copying numbers between tools, reformatting the same information into three different reports for three different audiences. The actual work of project management — removing blockers, sequencing dependencies, making tradeoffs — gets squeezed into whatever time is left.
An AI agent can absorb the status-chasing half entirely. It pulls from your project boards, aggregates progress, writes the summaries, sends the reminders, preps the meetings, and follows up on action items — all through email. You focus on the decisions only a human can make.
AI Project Manager vs. Project Management Software
Asana, Linear, Monday, and ClickUp are databases. They store tasks, track deadlines, and display boards. They don’t do anything unless a human clicks buttons.
An AI project manager sits on top of those tools and operates them. You email it “standup update” and it reads your boards, interprets what’s behind schedule, writes a summary, posts it to Slack, and emails stakeholders. You forward it meeting notes and it extracts action items, creates tasks, and sends follow-up emails. One email from you triggers a multi-step workflow across every connected tool.
The difference: project management software is a filing cabinet. An AI project manager is the person who opens the cabinet, reads the files, and takes action.
Building Your AI Project Manager in Carly (Step-by-Step)
The whole setup takes under ten minutes. You’re writing plain-English instructions that tell the agent what to do, when, and with which tools.
Step 1: Create the Agent
Fastest method: Email your main Carly agent at agent@usecarly.com and describe what you need:
Create a project management agent connected to Asana, Slack, Google Calendar,
Google Docs, and Gmail. It should track project progress, send status updates,
prep meetings, and check deadlines when I ask.Your agent builds the new agent for you — name, email, tools, instructions, everything.
Dashboard method: Go to dashboard.carlyassistant.com/agents and click “Add Email Agent.” If you’re new, the getting started guide walks through account setup.
Step 2: Name and Email
Give it a name that matches its function — “Project Ops,” “PM Agent,” “Sprint Tracker.” Each agent gets its own email address. Pick something your team will recognize: pm@yourdomain.com, project-ops@yourdomain.com, or use the default @usecarly.com address.
For naming strategy, see our guide on giving your AI agent a name, email, and personality.
Step 3: Write Instructions
Your instructions are the agent’s playbook. Be specific, sequential, and explicit about escalation rules. Here’s a starter template:
You are the Project Management agent for [Company Name].
Standup digest:
When I email you "standup" or "project status":
1. Pull task statuses from Asana for all active projects. Identify tasks
that are overdue, due today, or blocked.
2. Post a digest to Slack #project-updates with: overdue tasks (with owners),
tasks due today, blockers flagged in the last 24 hours.
3. Email me a summary with the same information plus a risk assessment —
which projects are on track, at risk, or behind.
Meeting prep:
When I email you "prep for [meeting name]" or forward a calendar invite:
4. Create a prep doc in Google Docs with: agenda, attendee list, open action
items per attendee, and key decisions needed.
5. When I forward you meeting notes afterward, extract action items,
create tasks in Asana assigned to the right people, and email attendees
a summary of decisions and next steps.
Deadline checks (when I email you "check deadlines"):
6. If a task is within 2 days of its deadline with no recent activity, send a
Slack DM to the owner with a reminder.
7. If a task is overdue by more than 1 day, escalate: Slack the owner
and their manager, and email me with [OVERDUE] in the subject line.
Escalation rules:
- Never move a deadline without my approval
- If a blocker affects more than one project, flag it immediately via email
- If you're unsure about priority or scope, ask me before actingThe key: instructions should cover recurring workflows, triggers for action, and clear escalation boundaries. You’ll refine these after testing.
Step 4: Connect Tools
Grant only the integrations this agent needs. Carly connects to 70+ integrations across 25 categories. For a project management agent, start with:
| Category | Integrations |
|---|---|
| Project Management | Asana, Linear, ClickUp, Monday, Basecamp, Wrike |
| Messaging | Slack, Discord |
| Documents | Google Docs, Google Slides, SharePoint |
| Productivity | Google Sheets, Airtable, Notion |
| Video Conferencing | Zoom, Google Meet, Microsoft Teams, Webex |
| Gmail, Outlook | |
| File Management | Google Drive, Dropbox, Box |
| Native | Google Calendar, Outlook Calendar, Web Search |
Start with your project board tool, messaging, calendar, docs, and email. Add the rest after your core workflows are running.
Step 5: Test It
Send the agent 5-10 test scenarios: “What’s the status of Project X?” “Prep for my 2pm meeting.” “Which tasks are overdue this week?” Review every response in the dashboard. Refine instructions where the output misses the mark.
5 PM Workflows with Detailed Instructions
These are copy-and-paste-ready instruction blocks. Add them to your agent’s instructions or email them to agent@usecarly.com to build a dedicated agent for each.
1. Daily Standup Summaries
Pull task updates from your project board, compile a team-wide digest, and distribute it — no 15-minute standup meeting required.
Tools: Asana or Linear, Slack, Gmail
When I email you "standup update" or "standup":
1. Pull all tasks updated in the last 24 hours from Asana across
active projects
2. Group by project, then by status: completed, in progress, blocked
3. For blocked tasks, include the blocker description and owner
4. Post the full digest to Slack #standup in this format:
- [Project Name]: X tasks completed, Y in progress, Z blocked
- Blockers: [task name] — [blocker] — [owner]
5. Email me a version with additional context: which projects had
no movement (flag as stale), which have tasks due this week,
and any patterns (e.g., same person blocked on multiple items)
6. If any project has had zero task movement for 3+ days, flag it
in the email subject as [STALE PROJECT]This replaces the daily standup for async teams. You email the agent, everyone gets the same information, and stale projects surface automatically.
2. Meeting Prep and Follow-Up
Automate the cycle of research, agenda creation, and action-item tracking that eats hours every week.
Tools: Google Calendar, Google Docs, Web Search, Asana or Linear, Gmail
For every calendar event tagged "project" or containing "sprint,"
"kickoff," "review," or "retro":
Before the meeting (2 hours prior):
1. Create a Google Doc titled "[Meeting Name] — [Date] Prep"
2. Add: attendee list with roles, open action items per attendee
from Asana, agenda topics from the calendar event description,
and 3 suggested discussion points based on recent project activity
3. For external attendees, research their company and role via
web search and add a one-line context note
4. Share the doc with all attendees via email with subject
"Prep doc for [Meeting Name]"
After the meeting (when I forward you the notes or update the doc):
5. Extract every action item with owner and deadline
6. Create tasks in Asana under the correct project, assigned to
the right person, with the deadline from the notes
7. Email all attendees a summary: decisions made, action items
with owners and deadlines, next meeting date if mentioned
8. If any action item has no clear owner, flag it in the email
and assign it to me as a placeholder3. Sprint and Project Status Reports
Aggregate data from project tools into a stakeholder-ready report — weekly, biweekly, or on demand.
Tools: Asana or Linear, Google Docs, Google Sheets, Gmail, Slack
When I email you "status report" or "weekly project update":
1. Pull task data from Asana for all active projects: total tasks,
completed this week, added this week, overdue, blocked
2. Calculate completion rate and velocity (tasks completed vs. planned)
3. Create a Google Doc titled "Project Status Report — Week of [Date]"
with sections per project:
- Status: On Track / At Risk / Behind
- Completed this week (bullet list)
- Planned for next week
- Blockers and risks
- Key metrics: completion rate, velocity, overdue count
4. Add a summary table at the top with all projects and their status
5. Email the report to [stakeholder list] with subject
"Weekly Project Status — [Date]"
6. Post a condensed version to Slack #leadership with just the
summary table and any projects flagged At Risk or Behind
7. If any project's completion rate drops below 60% two weeks in
a row, add a [NEEDS ATTENTION] flag in the report4. Deadline Monitoring and Escalation
Catch slipping deadlines before they cascade into missed milestones.
Tools: Asana or Linear, Slack, Gmail
When I email you "check deadlines" or forward a task list:
1. Check all active tasks in Asana for deadline issues
2. For tasks due within 48 hours with no activity in the last 3 days:
- Send a Slack DM to the task owner: "Heads up — [task name] in
[project] is due [date]. Let me know if you need anything
unblocked."
3. For tasks overdue by 1 day:
- Send a Slack DM to the owner: "[task name] is now overdue.
Can you update the status or let me know the new ETA?"
- Add a comment on the Asana task noting the reminder was sent
4. For tasks overdue by 3+ days:
- Slack the owner AND their manager (use the team directory
I've provided in my instructions)
- Email me with subject "[ESCALATION] [task name] overdue by
[X] days in [project name]"
- Include: task description, owner, original deadline, last
activity date, and any blocker notes
5. Never move deadlines or reassign tasks without my explicit approval5. Cross-Team Coordination
When multiple teams or projects share dependencies, surface conflicts and route information to the right people.
Tools: Asana or Linear, Slack, Gmail, Google Docs
When I email you "dependency check" or "cross-team status":
1. Scan all active projects in Asana for cross-project dependencies
(tasks tagged "dependency" or "blocked-by-[other project]")
2. For each dependency: check if the upstream task is on track.
If it's behind or blocked, flag it.
3. Post a dependency status update to Slack #cross-team:
- Which dependencies are clear (upstream on track)
- Which are at risk (upstream behind schedule)
- Which are blocked (upstream task is blocked)
4. For at-risk or blocked dependencies, Slack DM both the upstream
task owner and the downstream team lead with context
5. Email me a dependency report with recommended actions:
"Consider descoping [feature] to unblock [team]" or
"Suggest [owner] prioritize [task] — it's blocking 3
downstream items"
When I email you "dependency map" or "cross-team map":
6. Create a Google Doc "Cross-Team Dependency Map — Week of [Date]"
showing all active dependencies, their status, and risk level
7. Share with all project leads via emailAdvanced: Agents Per Project or Per Client
For agencies, consultancies, and multi-project teams, the real power is running separate agents per project or per client.
Each agent gets its own email, instructions, and tool access scoped to a specific project board, client folder, and Slack channel. A client emails their dedicated agent at project-alpha@yourdomain.com, and it handles status requests, meeting scheduling, and progress updates — all within the context of that specific engagement.
To set this up, email agent@usecarly.com:
Create a project agent for Project Alpha connected to the "Project Alpha"
board in Asana, the #project-alpha Slack channel, and the "Project Alpha"
folder in Google Drive. It should handle status requests from the client,
send weekly updates, and prep our Thursday review meetings.Agents can also spawn sub-agents for specific workstreams. Your main PM agent handles overall coordination while sub-agents manage individual tracks — engineering, design, QA — each with their own tool access and reporting cadence. For more on this pattern, see how to build AI employees.
Mistakes to Avoid
Letting the agent reassign tasks or move deadlines without your approval. An agent that shifts a deadline by three days because a task looks “behind” can cascade into missed milestones across dependent workstreams. Hard rule in your instructions: the agent surfaces overdue tasks and recommends actions, but never changes assignments, deadlines, or scope on its own.
Not defining what “blocked” means. Without a clear definition, team members flag everything as blocked — waiting on feedback, waiting on a decision, waiting on a Figma file. Tell the agent which blocker types require escalation (cross-team dependency, missing access, executive decision needed) and which are just normal back-and-forth that doesn’t need your attention.
Sending too many Slack reminders. If you email the agent to check deadlines multiple times a day, task owners get piled with notifications and start ignoring them — including the ones that matter. Set reasonable escalation rules: one reminder when a task is approaching its deadline, one when it’s overdue, escalation to their manager at 3 days overdue. Less frequent, higher signal.
No distinction between internal status updates and client-facing reports. Internal updates can include blockers, risks, velocity dips, and team names. Client-facing reports should show progress, milestones hit, and next steps — no internal drama. If your agent generates both, write separate formatting instructions for each audience or you’ll accidentally send a client a report that says “engineering is behind and blocked on design.”
Covering too many projects before the agent is calibrated. Start with one project. Dial in the reporting format, escalation thresholds, and reminder cadence until they match how your team actually works. Then clone those instructions to a second project. An agent pulling from 10 boards on day one produces a wall of noise that nobody reads.
Not specifying the team directory so the agent knows who to escalate to. When a task is overdue, the agent needs to know who owns it and who their manager is. Without a team directory or org chart in the instructions, escalation breaks down — the agent either guesses wrong or just emails you about everything. Add a simple list: name, role, manager, Slack handle.
Pick the PM workflow that burns the most of your time — standup summaries, meeting prep, status reports, deadline chasing — and email agent@usecarly.com to build an agent for it. Or set one up at dashboard.carlyassistant.com/agents.
Related: What Are AI Agents · How to Build AI Employees · Best AI Agent Platforms · Best AI Agents for Productivity · What Carly Can Do
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
Get Carly Today →Or try our Free Group Scheduling Tool
