A 30-person AI agency in Philadelphia ran a time audit and discovered that their senior engineers were spending an average of 18 hours per week in meetings — standups, project syncs, client calls, all-hands, one-on-ones, sprint planning, sprint retros, architecture reviews, and ad-hoc discussions that turned into calendar invites. With a 40-hour work week and 18 hours in meetings, engineers had 22 hours for actual engineering. After accounting for context switching, email, and Slack, productive engineering time was closer to 14 hours per week. These were senior ML engineers costing the agency $180,000-220,000 per year, spending 45% of their time sitting in meetings and only 35% building things.
The agency restructured their meeting cadence and recovered an average of 7 hours per week per engineer — the equivalent of adding 5 full-time engineers to their capacity without hiring anyone.
Meeting cadence design is not about having fewer meetings. It is about having the right meetings at the right frequency with the right people. A well-designed cadence creates alignment and information flow with minimum time investment. A poorly designed one creates the illusion of alignment while destroying the deep work time your team needs to deliver excellent work.
The Principles of Good Meeting Design
Principle 1: Every Meeting Has a Clear Purpose
Every recurring meeting must serve one of four purposes:
- Information sharing — distributing knowledge that people need to do their jobs (all-hands, status updates)
- Coordination — aligning work across people or teams to prevent conflicts and gaps (standups, resource planning)
- Decision-making — reaching decisions that require input from multiple people (architecture reviews, project approvals)
- Relationship building — strengthening connections that improve collaboration (one-on-ones, team socials)
If a meeting does not clearly serve one of these purposes, it should not exist. If it serves a purpose that could be accomplished asynchronously (many information-sharing meetings), convert it to an async format.
Principle 2: Minimum Viable Attendees
Every additional person in a meeting increases coordination cost and decreases individual engagement. Invite the minimum number of people who can accomplish the meeting's purpose.
Decision-making meetings: 3-5 people. More than 5 and decisions stall. Coordination meetings: 5-8 people. Larger groups should break into sub-teams. Information sharing: As many as needed, but consider whether a written update would be more efficient. Relationship building: 2-6 people. Larger groups dilute genuine connection.
Principle 3: Protected Deep Work Time
Block out sections of the calendar where meetings cannot be scheduled. Engineers need uninterrupted time to think deeply, write code, and solve complex problems. Context switching — jumping between a meeting and technical work — destroys productivity.
Common approaches:
- No-meeting mornings: No meetings before noon, giving everyone a guaranteed 4-hour block for deep work
- No-meeting days: One or two days per week (often Tuesday and Thursday) are meeting-free
- Meeting windows: All meetings are scheduled within defined windows (1-5pm, for example), leaving mornings free
The specific approach matters less than the commitment. Pick one and enforce it.
Principle 4: Time Boxes Are Non-Negotiable
Every meeting has a defined duration. It starts on time and ends on time. If the agenda is not complete, items carry over to the next meeting or are handled offline — the meeting does not extend.
Standard time boxes:
- Daily standup: 15 minutes
- One-on-one: 30 minutes
- Team sync: 30-45 minutes
- Project status meeting: 45-60 minutes
- Strategic planning: 90 minutes-2 hours
- All-hands: 30-45 minutes
Running overtime signals that the meeting is either poorly structured, has too many attendees, or is covering too many topics. Fix the structure rather than extending the time.
Principle 5: Default to Shorter and Less Frequent
When unsure about duration or frequency, start shorter and less frequent. A 30-minute weekly meeting that consistently ends early can be shortened to biweekly. A 60-minute meeting that always runs over might need a better agenda rather than more time.
The AI Agency Meeting Template
Here is a meeting cadence designed for a 20-40 person AI agency with 4-8 active projects.
Daily: Team Standups (15 minutes)
Purpose: Coordination Frequency: Daily, same time Attendees: Each delivery team (engineers, data scientists on a specific project), plus PM Format: Each person answers three questions:
- What did I complete yesterday?
- What am I working on today?
- Is anything blocking me?
Rules:
- No problem-solving during standup. If someone is blocked, note it and handle it after the meeting with only the relevant people
- Stand up physically (or keep cameras on for remote) — this naturally keeps it short
- Start on time even if someone is missing. Latecomers catch up from notes
- Rotate who speaks first to prevent the same person always dominating
Alternative for async teams: Replace the daily standup with a written check-in (in Slack, Geekbot, or similar) where each person posts their three answers by 10am. The PM reviews and flags blockers.
Weekly: Leadership Team Meeting (60-90 minutes)
Purpose: Coordination and decision-making Frequency: Weekly, same day and time (Monday or Tuesday works best) Attendees: CEO/founder, COO/operations, sales lead, delivery lead, finance lead (5-7 people)
Standard Agenda:
- Good news (5 minutes) — one positive item from each person to set a constructive tone
- Scorecard review (10 minutes) — review the weekly metrics dashboard. Discuss any metrics outside target range
- Client and project health (15 minutes) — traffic light status of all active projects. Discuss any yellow or red projects
- Revenue and pipeline (10 minutes) — closed deals, pipeline changes, forecast updates
- People (10 minutes) — hiring updates, retention issues, performance concerns
- Issues (20-30 minutes) — identify the top 1-3 issues facing the business this week. Discuss, decide, and assign
- Action items (5 minutes) — recap decisions made and tasks assigned
The most important part is the issues discussion. Do not just report status — solve problems. If a project is red, decide what to do about it in this meeting. If a hire is stalled, decide the next step now.
Weekly: Client Status Meetings (30-45 minutes per project)
Purpose: Information sharing and coordination Frequency: Weekly Attendees: PM, technical lead from your side; project lead and key stakeholders from the client side
Standard Agenda:
- Accomplishments since last meeting
- Upcoming work and timeline
- Decisions needed from the client
- Risks and issues
- Action items
Tips for effective client status meetings:
- Send a written status update before the meeting so the meeting focuses on discussion, not presentation
- Use the meeting for items that require conversation — decisions, risk discussions, relationship building
- If there is nothing substantive to discuss, cancel the meeting for that week rather than holding a perfunctory check-in
Weekly: Resource Planning Meeting (30 minutes)
Purpose: Coordination Frequency: Weekly (Tuesday, after leadership meeting) Attendees: Delivery lead, project managers (4-6 people)
Agenda:
- Current allocation status — who is overcommitted, who has capacity
- Upcoming staffing needs — projects starting in the next 2-4 weeks
- Conflicts — where do allocation conflicts exist, how do we resolve them
- Decisions — staffing decisions that need to be made this week
This meeting prevents the ad-hoc Slack conversations about "who's available to help with X" that fragment everyone's attention throughout the week.
Biweekly: One-on-Ones (30 minutes)
Purpose: Relationship building and coordination Frequency: Every two weeks (weekly for new hires in their first three months) Attendees: Manager and direct report (2 people only)
Structure:
- 10 minutes: Direct report's agenda (their updates, concerns, questions)
- 10 minutes: Manager's agenda (feedback, context, expectations)
- 10 minutes: Career and development (what they want to learn, where they want to grow)
One-on-ones are the direct report's meeting, not the manager's. The primary purpose is to create a private space for the individual to raise concerns, ask questions, and discuss topics they would not bring up in group settings. Managers who use one-on-ones primarily for status updates are wasting the opportunity.
Never cancel one-on-ones. Canceling signals that the individual is not important enough to warrant 30 minutes of your time. Reschedule if necessary, but never cancel.
Biweekly: Sprint Planning and Retrospective
Purpose: Coordination (planning) and decision-making (retro) Frequency: Every two weeks at sprint boundaries Attendees: Delivery team for the specific project
Sprint Planning (60 minutes):
- Review previous sprint completion rate
- Present upcoming sprint backlog
- Estimate and commit to sprint scope
- Identify dependencies and risks
Sprint Retrospective (45 minutes):
- What went well?
- What did not go well?
- What will we change next sprint?
- Action items with owners
These can be combined into a single session at sprint boundaries, keeping the total under 2 hours.
Monthly: All-Hands (30-45 minutes)
Purpose: Information sharing Frequency: Monthly Attendees: Entire team
Agenda:
- Business update — revenue, wins, pipeline (high-level, not detailed financials)
- Project highlights — showcase interesting work being done
- Team updates — new hires, promotions, departures, milestones
- Culture — upcoming events, policy changes, open discussion
- Q&A — open floor for questions to leadership
All-hands meetings serve a cultural purpose as much as an informational one. They remind the team that they are part of something larger than their individual project. Keep them positive, transparent, and engaging. If all-hands become rote status reports, attendance and engagement will decline.
Monthly: Technical Architecture Review (60-90 minutes)
Purpose: Decision-making and coordination Frequency: Monthly (or as needed) Attendees: Technical leads, senior engineers, CTO (6-10 people)
Agenda:
- Review significant architecture decisions made in the past month
- Discuss upcoming technical challenges that need input
- Review technical debt and prioritize remediation
- Share learnings from recent projects (what worked, what did not)
This meeting ensures technical consistency across projects and prevents teams from making decisions in isolation that create problems later.
Quarterly: Strategic Planning (Half-day to full day)
Purpose: Decision-making Frequency: Quarterly Attendees: Leadership team
Agenda:
- Review quarterly performance against goals
- Assess market conditions and competitive landscape
- Set priorities and goals for the next quarter
- Review and adjust resource allocation
- Identify strategic risks and mitigation plans
This is the longest meeting in your cadence and the most consequential. Dedicate real time to it — do not try to squeeze strategic planning into a 2-hour slot between client calls.
Calculating Your Meeting Load
After designing your cadence, calculate the total meeting hours per role to ensure you have not overloaded anyone.
Example for a senior engineer on one project:
| Meeting | Duration | Frequency | Weekly Hours | |---------|----------|-----------|--------------| | Standup | 15 min | Daily (5x) | 1.25 | | Client status | 45 min | Weekly | 0.75 | | One-on-one | 30 min | Biweekly | 0.25 | | Sprint planning/retro | 2 hrs | Biweekly | 1.0 | | Architecture review | 90 min | Monthly | 0.375 | | All-hands | 30 min | Monthly | 0.125 | | Total | | | 3.75 hrs/week |
That is under 10% of a 40-hour week — reasonable and sustainable. Compare this to the 18 hours the Philadelphia agency discovered. The difference is eliminating redundant meetings, reducing attendee lists, and enforcing time boxes.
For project managers, the load will be higher (they attend more client meetings and coordination meetings), but should still stay under 40% of their time.
If any role exceeds 25% of their time in meetings, restructure. Either reduce meeting frequency, reduce attendee lists, or convert some meetings to async formats.
Async Alternatives
Not every coordination need requires a synchronous meeting. Consider async alternatives for:
Status updates: Written updates in Slack, your project management tool, or a shared document replace many status meetings. People can read updates on their own schedule.
FYI announcements: Email or Slack posts for information that does not require discussion.
Decision-making with clear options: A Loom video presenting the decision, options, and recommendation, with a comment thread for input, can replace a 30-minute meeting.
Feedback on documents or designs: Commenting on shared documents allows thoughtful feedback without scheduling overhead.
The test: Before scheduling a meeting, ask "could this be an email?" If the answer is yes, make it an email. If the topic requires real-time discussion, negotiation, or relationship building, schedule the meeting.
Auditing and Evolving Your Cadence
The Quarterly Meeting Audit
Every quarter, audit your meeting cadence:
- List every recurring meeting on the team's calendars
- For each meeting, ask: Is this still necessary? Is the frequency right? Are the right people attending? Is the duration appropriate?
- Survey the team: Which meetings do they find valuable? Which feel like a waste of time?
- Calculate total meeting load by role and compare to your targets
Cancel, consolidate, or restructure meetings that fail the audit. Add meetings only when there is a clear gap that cannot be addressed asynchronously.
Evolving with Growth
Your meeting cadence should evolve as your agency grows:
10-15 people: Minimal formal meetings. Daily standups, weekly team sync, monthly all-hands. 15-30 people: Add leadership meetings, one-on-ones, and resource planning. 30-50 people: Add department-level meetings, cross-functional syncs, and formalize sprint ceremonies. 50+: Consider communication layers (team leads attend cross-functional meetings so individual engineers do not need to).
Your Next Step
Audit your team's calendars this week. For each recurring meeting, write down its purpose, frequency, duration, and attendee count. Calculate the total meeting hours per week for your most heavily-loaded roles. If anyone exceeds 25% of their time in meetings, identify which meetings to eliminate, shorten, or convert to async. Then implement the changes next week. The hours you recover are hours your team can spend doing the work your clients are actually paying for. That single change will do more for your delivery capacity and team satisfaction than any tool purchase or process improvement you could make this quarter.