Teamwork.com AI Playbook

Teamwork.com's AI is unusual in this category for a boring reason: it is documented. The vendor publishes which AI features sit on which plan, names the models it connects to, and states plainly that the current price is temporary. Most vendors in this bracket publish an AI marketing page and leave you to discover the metering after you sign.

What it does not publish is what happens next. AI is included "for an introductory period", usage-based credits launch later, and the vendor gives two different dates for that in its own material. So this playbook has two halves: what to use now, and what to write down before the bill changes.

◆Our scorecard

3.8/5

AI 3.4/5

Real and tiered rather than a label: AI Essentials, comment summaries, a project wizard and a task builder from Basics; an AI utilization summary at Accelerate; AI smart assign and profitability forecasting at Optimize; plus an MCP server that names Claude and ChatGPT. Held back by three things the vendor states itself — two features still marked coming soon, an introductory free period with no published credit price, and two different launch dates for billing in its own material.

Value for money 3.5/5

The free tier is unusually generous for this category — Gantt, time tracking and billable flags cost nothing — and Basics at $9.99/seat/mo billed annually is competitive. But seat minimums of three and five raise the real floor above the headline, and the capabilities that justify choosing Teamwork over a cheaper general-purpose tool concentrate in Accelerate and in Optimize, which carries no published price at all.

Capability & depth 4.3/5

118 capabilities documented on the vendor's own pages, and the professional-services layer is deeper than general PM tools reach: billable rates with retrospective changes, personal and company timesheets with approval, expenses against budgets, time and financial and fixed-fee budgets, invoicing from logged time, multi-currency billing, profitability reporting, utilization targets, resource scheduling by skill and capacity placeholders. The ordinary work-management set is complete on every plan, free included.

Ease of use 3.5/5

Scored on structural evidence rather than reviewer testimony, which we do not hold for this product: one-click project import from Wrike, Asana, Basecamp, ClickUp, Trello and monday.com lowers the switching cost, and the full view set plus time tracking on the free plan means the core workflow can be tested before purchase. Against that, the complexity is concentrated where the money is — rates, budgets, retainers and utilization — and the custom-workflow cap of one on Basics and three on Accelerate forces process decisions early.

Integrations 3.9/5

150+ integrations claimed, and the ones that matter are named per tier rather than left vague: Harvest and both calendars on the free plan; HubSpot, OneDrive for Business, SharePoint, Xero, QuickBooks and FreshBooks at Accelerate; Salesforce and NetSuite at Optimize. The MCP server is a current capability rather than a rebrand, and file linking from Drive, Dropbox, Box and OneDrive starts at Basics. API rate limits scale by plan, 150 to 500 requests a minute.

User sentiment 4.0/5

Four sources on file, and the spread is the signal rather than the average: 3.3 out of 5 from 69 reviews at the low end against 4.4 from 1,343 and 4.5 from 941 in the two large pools. Reads as a product that satisfies most buyers and disappoints a minority sharply. The figures come from search results rather than rendered review pages, because the major aggregators block automated reading.

Docs & learning resources 3.0/5

The raw material is better than most vendors publish — a plan comparison matrix with explicit per-tier cells, and a machine-readable pricing file served for AI agents. It is undermined by its own staleness: SAML SSO, the Optimize seat minimum, when quotes unlock and the AI billing date each get two different answers across vendor pages, and a live support article still describes plans named Deliver, Grow and Scale, which no longer exist.

Support & reliability 3.8/5

SOC 2 Type 2 and ISO/IEC 27001:2022 stated, data residency in the US or the EU on AWS, automatic database snapshots every few seconds, an uptime goal above 99.9%, and two-factor authentication plus role-based permissions on every plan. Live chat and email support from Basics; premium support and a dedicated success manager are Enterprise only. One hard limit stated by the vendor: Single Log Out via SAML is not supported.

Weighted across the axes above (weights reflect what actually drives the decision in this category). How we score →

What Exists, and on Which Plan

AI capability	Plan
Connect Claude, ChatGPT and other LLMs via the MCP server	Named by the vendor as third-party app connections
AI Essentials — AI summaries, project and task wizard	Basics ($9.99/seat/mo billed annually, 3-seat minimum)
Summarize comment threads	Basics
Spin up a project with the AI project wizard	Basics
Create task cards with the AI task builder	Basics
Log and categorize expenses via AI	Basics
Personal Assistant teammate "Scout"	Basics
Project Management teammate "Flo"	Basics
AI Advanced Operations, utilization insights, "Ask AI"	Accelerate ($24.99/seat/mo billed annually, 5-seat minimum)
Resource Management teammate "Remi"	Accelerate
AI smart resourcing and auto-assign	Optimize (price not published)
Forecast project profitability with AI	Optimize
Financial Management teammate "Kash"	Optimize
Custom teammates, built with "Jack"	Optimize
Ask AI questions across projects in chat	Marked coming soon by the vendor
Service lines	Marked coming soon

Two things to notice in that table. The AI follows the money: the teammates get progressively more financial as the tier climbs, ending with profitability forecasting at the tier that has no published price. And the vendor's own comparison page marks two items as not yet shipped, which is more honest than most and worth respecting. Do not plan around either.

Key takeaway — The AI layer mirrors the product: coordination features low, financial intelligence high, and the most valuable piece behind the quote-only tier.

## Start With the Two That Pay for Themselves at $9.99

Comment thread summaries. The unglamorous one, and the one with the clearest return. A project that has run for three months has comment threads nobody will read, and the person who needs them most is whoever just joined. Summarizing a thread turns twenty minutes of archaeology into a paragraph. This is on Basics.

The AI project wizard and task builder. Both on Basics. The value here is not speed. It is consistency: a project spun up from a described outcome lands with a structure, rather than with whatever the person setting it up remembered to include. Pair it with a template rather than treating it as a replacement for one: the template encodes your standards, the wizard fills in the specifics.

AI expense categorization, also Basics, matters more than it sounds for a team that bills. Uncategorized expenses are the ones that never make it onto an invoice.

The MCP Server Is the Piece Worth Testing First

Teamwork ships an MCP server and names Claude and ChatGPT as supported connections^[1]. That lets an external assistant query your project data directly, rather than through a scraped integration or API code you maintain.

This inverts the usual reporting problem. The standard approach is to build a dashboard, which somebody has to open, and which answers only the questions it was built for. With an assistant connected to live project data you ask the question you actually have: what slipped this week, which client is over budget, who is double-booked. The answer comes from the current state.

Two caveats, both from what the vendor does not say. There is no published limit on query volume, and no statement about what the assistant can write back as opposed to read. Test both in the trial rather than assuming either, and decide deliberately whether you want an assistant that can modify project data.

For a team already using Claude or ChatGPT daily, this is the single highest-leverage thing on this page, and it is available regardless of plan.

What the AI Does Not Do

Worth stating because the marketing in this category rarely does.

There is no AI that writes your project plan from a client brief. The wizard creates structure from a description you provide; it does not read a PDF and produce a scoped engagement.

There is no AI in the approval path. Proofs route to humans, and the custom workflows that do the routing are rule-based, not model-based.

There is nothing that predicts a slip before it happens from historical patterns. Teamwork's forward-looking AI is the profitability forecast at Optimize, which projects financials rather than schedule risk.

And nothing in the AI layer removes the two counters that decide your plan. Custom workflows still cap at three on Accelerate; proofs still cap at 20 on Basics. No amount of AI moves those.

The Expiry, Which Belongs in Your Budget Rather Than This Page

Teamwork states that AI is included in all paid plans for an introductory period, and that usage-based AI credits launch later.

The vendor gives two different dates for that launch. Its pricing page says November 2026. The machine-readable pricing file it publishes for AI agents says September 2026. The credit price appears in neither, and in no other vendor material we hold.

Three consequences, in order of how much they will cost you.

An annual term will outlive the introductory period. If you sign a twelve-month deal now, the AI will stop being free during that term, at a rate you agreed to without seeing. Ask for the credit price in writing before signing, and ask what happens to a committed term when metering starts.

Any total-cost model that includes the AI is wrong by an unknown amount. Put it in as a line item with a question mark rather than as zero. A zero reads as settled and this is not settled.

Habits formed now become costs later. If your team comes to rely on comment summaries and the project wizard, those become per-use charges at an unpublished rate. That is not an argument against using them. It is an argument for knowing which ones you would keep paying for.

## The Teammates Framing, and Whether It Helps

Teamwork names its agents rather than offering one chatbot: Scout for personal assistance and Flo for project management at Basics, Remi for resource management at Accelerate, Kash for financial management at Optimize, and Jack for building custom teammates, also Optimize.

The framing is more useful than it first appears, for one practical reason. A single assistant that claims to do everything has to be prompted into the right mode, and the person prompting it has to know what modes exist. A named agent per function makes the scope legible before you ask. You know what Kash is for without reading documentation, and you know not to ask Scout about margins.

The risk in the same framing is that it suggests more autonomy than is published. Nothing in the vendor's material states what any teammate can change without approval, or whether its actions appear in an audit trail. Teamwork does log activity, and for AI agent delivery status the vendor states it is saved in the activity log. But that is one specific case rather than a general guarantee. If an agent assigning work or adjusting a budget would need review in your organisation, establish that before you let one loose on live projects.

Worth noting what the tiering implies about intent. The teammates get more financial as the price climbs, and the one that builds other teammates sits at the top. That is a product betting that the valuable automation is in the money layer rather than the task layer, which matches where the rest of Teamwork concentrates its value.

Where the AI Meets the Counters

One section, because it is the question people ask after the demo: does the AI make the plan limits less binding?

Automation actions. AI-driven automations draw on the same account-level allowance as rule-based ones: 100 a month on Free, 5,000 on Basics, 20,000 on Accelerate, 100,000 above. An AI that assigns work is spending from the same budget as a rule that sends a notification, so a team planning heavy AI automation on Basics is planning against 5,000 shared actions.

Custom workflows. Capped at one on Basics and three on Accelerate regardless of how the routing decision gets made. The AI does not add a fourth path.

API rate limits. The MCP server queries your data, and the vendor publishes no separate allowance for it. Only the plan's 150 requests a minute below Optimize. Whether assistant queries count against that is not stated, which is worth asking if you plan to connect it to a whole team rather than one person.

A Four-Week Plan

Week one: connect the MCP server. Point Claude or ChatGPT at your Teamwork data and ask three real questions you currently answer by opening reports. Note which answers were useful and which were wrong. This costs nothing and it is the capability with the least marketing around it.

Week two: summaries and the wizard. Run comment summaries on your three longest-running projects and have whoever joined most recently read them. Spin up one project with the wizard from a template, and one without, and compare what each is missing.

Week three: measure the utilization summary, if you are on Accelerate. It is the first AI output in the product that touches money. Check it against what you already believe about utilization; if it tells you something you did not know, that is the business case for the tier.

Week four: write down the expiry. Three lines in whatever document holds your software budget: AI is free until an introductory period ends, the vendor gives two different dates for that, and the credit price is unpublished. Then list which AI features your team would pay for and which it would drop. That list is what you need when the pricing arrives, and it is much harder to write honestly after you are already paying.

The Honest Summary

Teamwork's AI is better documented than most and more tightly tied to the product's actual purpose, billing and resourcing, than the generic assistants bolted onto competitors. The teammates are a reasonable framing: a named agent per function rather than one chatbot pretending to do everything.

What nobody outside Teamwork has published is a measured result. There is no independent figure for what any of this saves a team, and the vendor's own customer stories speak in the language of "hours every week" rather than numbers you could model. So use the AI where the mechanism is obvious: summaries, structure, categorization. Treat the rest as a trial rather than a plan.

And remember which half of this is settled. The capabilities and their tiers are published and verifiable. The price is not, the launch date contradicts itself, and two features are still marked coming soon. Build on the first half.