Who is over-booked, what it cost, and who signed it off.
Workload shows capacity against assigned work per person across every account, not one project at a time. Timers price the hour per client and export invoice-ready line items. Approvals record who signed the deliverable off and when, against the task the work lives on. The brief arrives as a typed request with a category and a priority rather than as a message; an ask made on a recorded call lands in the register with the sentence the client said it in and one click to the minute; and a delivery plan can start as a paragraph you describe to Hoot and come back as a real timeline you can drag. Choose Agency & Consulting at setup and all of it is already wired.
10 apps queued at setup - untick any of them before you finishDefault project tabs
Backlog replaces Timeline - an out-of-scope ask waits in Backlog until it is quoted or scheduled, and utilisation is read across every client at once on the workspace-wide Timeline rather than one project at a time.
Projects created on day one
- Client Delivery
- New Business
- Studio
How Agency & Consulting actually runs.
Each of these is a project in Noots - its own board, tab strip, meetings, calendar and members. They are not pre-built modules and we will not pretend they are: what the industry gives you is the right defaults around them.
The three that do the heavy lifting.
Choose this industry during setup and its tools are queued for you. Review the list, drop anything you don't want, and the workspace initialises with the rest already working - or install any one of them on its own, later, from the marketplace.
Time Tracking & Billing
A timer inside the task and manual entries after the fact, priced by a rate that resolves per user, per client or per agency - then turned into an invoice.
- Task timers and manual entries
- Rates per user, per client or per agency
- A Billing tab that produces invoices
- CSV export of every line item
Workload
Capacity against assigned work, per person, across every account at once - so an over-committed team member is visible before the deadline is.
- Capacity versus assigned work per person
- Across every client, not one project at a time
- Spot who is overloaded and who is free
- Rebalance before anything burns
Approvals
Sign-off requested on the deliverable itself and routed to the right approver, with a clear record of who approved what and when.
- Request sign-off from the task
- Routed to a named approver
- Who approved what, and when
- The trail sits beside the work, not in email
What changes, in the hours it actually changes.
Three moments from an ordinary week. Every one of them is a thing the product does, not a thing it could be configured to do one day.
09:30 - resourcing, before the week sets
Workload puts capacity against assigned work per person, across every account rather than one project at a time. The designer who is committed to three clients at once shows up on Monday morning instead of on Thursday afternoon.
11:10 - the brief arrives as a request, not as a message
The client's “can you just” lands in Intake with a category, a priority and a description, and the account lead triages it: quoted, scheduled, or parked in the project's Backlog until it is one of those. That is the scope conversation happening at the brief rather than at the invoice. The ask made out loud on Tuesday's call is caught too: it comes back as a decision in the register with the verbatim sentence and one click to the minute it was said, and anything the client asked somebody to do becomes a card with a real start and due date taken from what was actually said rather than from the day the meeting happened. A timer runs from the task, or the entry lands afterwards; rates resolve per user, per client or per agency, and the Billing tab turns the week's unbilled hours into an invoice with every line exportable as CSV.
16:45 - the work is signed off, not emailed about
Approvals routes the deliverable to the named approver - the account lead, or the client contact you have invited into the workspace - and keeps the record of who approved what and when, attached to the task the work lives on. When the scope question comes back in six weeks, the answer is a row rather than a search.
These sit on top of the whole product.
- Intake is where a brief or a change request lands as a typed record with a category and a priority - the single most-cited scope-creep control there is, because a request you can point at later is one you can quote for
- Client Voice keeps what the client actually said on the project they said it about: the verbatim sentence, the date, who said it, and a jump to the minute of the call it came from, sorted so a request, an approval and a scope change do not read as the same thing
- The built-in CRM keeps new business, accounts and opportunities next to the delivery board, and a contact or an opportunity links to the project delivering the work
- Backlog on every project holds the out-of-scope ask until it is quoted or scheduled; Budget tracks spend against the fee; Capacity tracks the load on that one job; the workspace-wide Timeline reads utilisation across every client at once
- Client calls, creative reviews, pitches and status check-ins each get their own steer on the recorder and come back as owned action items, with scope changes logged where the fee lives
- Forms is the brief and the feedback round without another subscription: build it from blocks, attach it to the client's project so the answers sit beside the work, and send a link the client can open without a Noots account. One answer per person if you want it, a thank-you screen you write, and every reply readable individually as well as in the totals
- Offered at setup, one tick each: the Content Calendar for everything you publish for a client, Customer Health to see which accounts are drifting and which retainers end next, the Vendor & Client Register, Competitor Watch for the pitch, and Retrospectives
- Autopilot plans a delivery, assigns from real people and reassigns when someone is over capacity
- Chat channels per project and per team, with calls that survive navigating away
- Describe a delivery to Hoot in a paragraph - the phases, who is on them, what waits on what - and it comes back as a real timeline rather than a picture: change one duration and the whole chain re-flows, with no model in the path. Put it on the board and the phases become tasks and milestones with their dependencies recorded, and from there you drag them like anything else
- A scope question six weeks later is answered from the register rather than from a search: a decision taken on a recorded call keeps the sentence that settled it and the minute it was said, next to the project it changed
- The Corkboard is the concept wall - notes you drag, a pen to scribble with, strings between the ones that connect, and a reply thread on any note
The honest edges.
- Two rates price the same hour, deliberately: the project Budget's blended rate answers “what did this cost us” and the billing rate answers “what do we invoice”. Both are shown; neither is derived from the other.
- Noots produces and exports invoices. Sending, chasing and reconciling them stays in your accounting system.
- There is no Figma integration.
- Approvals record a named sign-off against a task. It is not a frame-accurate proofing tool with annotations over artwork or video, and the approver is a member of your workspace - a client signs off by being invited in, not through a portal of their own.
- The client voice panel reads MEETINGS only. What the client said in a recorded call becomes a client-attributed item with the verbatim sentence, the date and a jump to the minute, and it feeds prioritisation from there. Chat and mail are not sources yet, so an email request still has to be said out loud or typed onto a card.
- A timeline Hoot generates records what waits on what and lets the dates re-flow from it. The chart itself draws no dependency arrows: the sequence is real, and the picture of it is bars and milestones rather than lines between them.
Built for the way your trade actually runs.
The ones buyers ask first.
Can we see utilisation across every client at once?
Why are there two different rates on the same hour?
How does client sign-off work?
Where does scope creep get caught?
Can we get a delivery plan out of a brief without building it by hand?
Does new business live in the same place as delivery?
Open a workspace that already knows Agency & Consulting.
Answer what your organisation does, review what gets installed, and start with the boards, meetings, chat and calendar already in the right shape.
Free to start · No credit card required