Plan & track
Lists, boards & tablesTimeline & GanttCalendar
Organize
Spaces, folders & listsCustom fieldsSubtasks, checklists & dependencies
Collaborate
Comments & @mentionsDocs & wikisPublic forms
Automate & connect
AutomationsREST APIBuilt-in MCP server
Solutions
For agenciesFor software teamsFor small business
Resources
Help Documentation Blog Support
More
All features Pricing Roadmap Security ContactSign In Sign Up Free

For agencies

Client work, retainers and approvals — without a seat for every client.

An agency's actual working day isn't one project — it's fifteen, each with its own client, its own retainer hours, and its own version of "is this approved yet." IterDone gives every client a predictable place to live, gives clients a way to see and approve work without a seat you have to pay for, and gives you the reporting to prove where the retainer hours went — without turning account management into a second job on top of the actual work.

How it actually plays out

One structure for thirty clients, not thirty structures.

Six workflows an account team runs every week, mapped onto what the product does today.

Client folders

Give each client a space, with a folder for the ongoing retainer and a separate folder for one-off projects. The structure is identical from client to client, so an account manager can move between six accounts a day without relearning where anything lives — and a new hire understands the whole system in one sentence: space per client, folder per engagement.

Client review & approval statuses

Custom statuses — Brief, In Design, Client Review, Revisions, Approved — replace the "is this ready?" Slack message with a status anyone can see at a glance. Cap work-in-progress on "In Design" so a designer never has eight pieces half-finished at once, and save the set as a template so every new client folder starts with the same review pipeline.

A client guest seat, scoped to one list

Invite the client's marketing contact as a free guest and scope them to their own list. They can see their work move through review and drop a comment on it — and they cannot see your other clients, your internal notes on other accounts, or your rate card. No seat to buy, no risk of cross-client exposure.

Public intake forms for new requests

Replace "can you just email me the brief" with a public form. A client submits a request without logging in, and it lands directly in their list with the fields you asked for already filled in — no forwarding, no re-typing a request out of an email thread.

Campaign briefs as docs

Keep the creative brief next to the work it describes, not in a shared drive three tabs away. Nested doc pages hold the brief, the brand guidelines and the asset checklist, and a public link shares the finished brief with a client who doesn't need — and shouldn't get — a login.

Time against retainer, and monthly reporting

Log time directly on the tasks that used it, add a custom field for hours remaining on the retainer, and build a saved view filtered to this month's closed work. When the client asks "what did we get for the retainer this month," the answer is a view you already have open, not a report you build from memory the night before the call.

Getting an agency live

Onboard the account team in an afternoon, not a sprint.

No implementation project, no per-client setup call with us — just the same three steps for every account.

STEP 1

Bring your work over

Upload a CSV from whatever you're on now — names, statuses, priorities, assignees and due dates come with it. About two minutes.

STEP 2

Invite the team

They log in and see their work. There's nothing to teach them, because there's nothing hidden.

STEP 3

Iterate until done

Adjust statuses, add the two custom fields you actually need, and get on with the work.

Common questions

What agencies usually ask first.

Do our clients need to pay for a seat to review work?

No. Invite them as a guest and scope them to a single list or folder — they can view and comment on their own work without a paid seat and without visibility into any other client's account.

Can each client have a different status pipeline?

Yes. Statuses are set per list, so a design client's Brief → Client Review → Approved pipeline and a dev client's Backlog → In Progress → QA pipeline can coexist in the same workspace. Save either as a template to reuse it on the next client.

What happens if we lose a client and need to hand over their data?

Export that client's list as a CSV, or export the whole workspace as JSON if the handover needs docs, custom fields and comment history too. It's the same export any workspace can run at any time — nothing client-specific to request from us.

Ready for the next account?

Set up the folder structure once, save it as a template, and every new client starts the same way.

Start Free Nothing to install. Productive on day one. Already have an account? Sign in

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.