Use cases
Pick the page that sounds like you.
Narcove works the same way for every team. The plan keeps itself honest. Clients can see what they need to see. We give time guesses you can trust. But the parts that matter most depend on what you do. Pick the page that fits, and we'll show you the parts that fit too.
Freelancers
One person. Many clients. One link each.
A free public link per project means clients can see their own work without seeing anyone else's. The plan updates itself when work moves, so you stop sending Friday emails.
Free or Pro · £15/seat + VAT
Marketing teams
Campaigns where every part feeds the next.
Copy waits on research. Design waits on copy. Launch waits on design. When one piece moves, the rest moves with it — and the client sees the new launch date the same day.
Pro or Team · £15–£29/seat + VAT
SaaS teams
Public roadmaps and bug intake without GitHub.
Customers submit bugs straight from your app. The portal becomes a public roadmap by accident. Support tickets drop because people self-serve their own status.
Pro or Team · £15–£29/seat + VAT
Agencies
One studio. Many clients. Branded portals.
Each client gets their own workspace and their own portal — at portal.your-domain.com if you want. Public viewers are always free, so paying for clients never makes sense again.
Team · £29/seat or £99 flat-5 + VAT
Not sure which fits?
Start free for one project. You can pick a tier when you grow.
Same for every team
Three things that don't change with the use case
A schedule that maintains itself. The Tide cascade is in every plan, on every tier. Move a card. The rest of the chain moves with it. Pull-forwards apply on their own. Push-backs over a threshold wait for you to review them. Forward-pull fires on the assignee's queue when something finishes. Whether you're one freelancer or a ten-person studio, the cascade works the same way.
Public viewers always free. Most PM tools count every guest as a billable user. We don't. A freelancer's clients, a marketing team's stakeholders, a SaaS team's customers, an agency's clients — they all read the public portal without a seat. You only pay for editors. That decision shapes how every feature is built: the portal is the same data, with private fields hidden.
UK bank holidays and working hours. The scheduler skips bank holidays. Working hours are 09:00 to 17:30 Mon–Fri unless configured otherwise. Per-person hours on Team. A launch never gets scheduled for Christmas Day, on any tier, for any team.
Different per team
What changes with the kind of work you do
Freelancers care most about the public portal — five clients, five bookmarks, no status emails. And honest time guesses, because guessing high to be safe and low to win the work is how freelancers eat their margin.
Marketing teams care most about the cascade replan when briefs slip. Campaigns are chains: research feeds copy, copy feeds design, design feeds launch. When the brief moves, the launch should move automatically — and stakeholders should see the new date the same hour.
SaaS teams care most about the public portal as a roadmap and bug intake. One tool, three jobs: team plan, public roadmap, bug tracker. Customers self-serve their own status and support volume drops.
Agencies care about multi-workspace and branded portals. One studio, many clients, one portal each — each on its own domain with the client's logo. The Team tier adds studio-wide capacity view so you spot designers double-booked across clients before Friday hits.