When we export, does Projan put the spec and the tasks in the same place?

Yes. Projan writes the agreed spec as a ClickUp Doc and creates the tasks and subtasks beneath it in the same export, so the narrative and the work that delivers it sit together rather than the doc living in one corner and the list in another.

We link tasks that block each other in ClickUp — does Projan preserve that?

It does. ClickUp supports native dependencies, and where the plan establishes that one task waits on another, Projan creates those links as it builds the tasks, so the blocking relationships are visible in ClickUp itself, not just implied in the doc.

Can Projan pull an existing ClickUp item into a planning session?

Yes. Paste the URL of a ClickUp task, doc or list and Projan reads it in as context, so a session can build on work that already exists in your space instead of starting cold.

Does it create subtasks, or just top-level tasks?

Both. The breakdown from a session usually has structure — a feature with the pieces underneath it — and Projan mirrors that as tasks with subtasks, so the hierarchy you agreed is the hierarchy that lands.

Will it touch the tasks and docs we already have in the space?

No. Projan creates new items from the session you just ran. Your existing lists, docs and tasks are left exactly as they are.

Do we have to run the planning session inside ClickUp?

No. The session runs in Slack, Microsoft Teams or Projan's own workspace — wherever the team already talks. ClickUp is where the agreed result is written, not where the conversation has to happen.

Is this trying to replace ClickUp's own docs and tasks?

Not at all. ClickUp stays the one place your work lives. Projan sits above it and decides what should go in, then writes it — the Doc and the tasks — into ClickUp for you.

Everything already lives in ClickUp — so where does an upstream planning layer even fit?

ClickUp's pitch is that everything lives in one place — tasks, docs, lists. The thing it can't hold is the agreement those artefacts are supposed to represent, so a tidy ClickUp space can still be full of work nobody quite signed off on. Projan supplies that missing layer. It facilitates the planning conversation, and when the team agrees, writes a ClickUp Doc for the spec and creates the tasks and subtasks beneath it, with dependencies linked. One session produces both the narrative and the work — already decided, already in ClickUp, already connected.

An agency wins a build for a client portal. The kick-off goes well, everyone’s enthusiastic, and within a day there’s a ClickUp space with a tidy list of tasks and a doc someone started. A fortnight later a developer asks whether the portal needs SSO or just email login, and nobody can say — the task says “auth,” the doc trails off halfway, and the decision was made, if it was made at all, in a call no one minuted. The space looked organised the whole time. It just wasn’t holding the one thing that mattered.

One place for everything, except the decision

ClickUp is genuinely good at being the place everything lives. Tasks, lists, docs, the lot — you don’t have to leave it, and most teams don’t. But “everything in one place” is a claim about storage, not about agreement. A space can be immaculate and still be full of work nobody actually signed off on: tasks written from a half-remembered call, a doc that describes what someone assumed rather than what the team decided. ClickUp will hold all of it faithfully. It just can’t tell you which parts were ever agreed, because agreeing happens before anything gets typed into ClickUp at all.

That earlier step — the working-out — is where Projan sits. It runs the conversation that produces the agreement, then writes the result into ClickUp as both the doc and the tasks, so the thing in your space is something the team genuinely decided rather than something one person drafted at the end of a long day.

A session that fills the Doc and the list

Take the portal. Instead of someone quietly spinning up tasks, the agency runs a Projan session — in the Slack channel the project team already lives in, or in Teams, or in the web app.

Projan facilitates. It asks who the portal is actually for: the client’s end customers, their internal staff, or both? It asks what “done” means for the first release. A developer raises the SSO question early — and instead of it surfacing two weeks in, the team decides then and there that the first phase is email login, with SSO explicitly deferred. Projan holds each of those decisions as they land.

Then it exports, and the agency’s ClickUp space gets two connected things at once:

A ClickUp Doc carrying the spec — the problem, who it’s for, what’s in the first phase and what’s deliberately out, with the reasoning attached.
Tasks and subtasks beneath it, drawn from the breakdown the team agreed: a task for the login flow with subtasks for the screens, a task for the account model, and so on.
Native dependency links where the plan says one piece waits on another — the account model before the login flow, say — so the order is visible on the board.

What was a conversation is now a doc you can hand the client and a list the team can start on, both saying the same thing because they came out of the same session.

Tasks, subtasks and a Doc — from one conversation

That’s the part worth being precise about. Plenty of tools will take a plan and make tasks. Projan exports tasks and subtasks and the ClickUp Doc that explains them — from a single agreed session — and links the dependencies natively where the plan establishes them. The doc isn’t a separate write-up someone does afterwards; it’s generated from the same agreement that produced the tasks, which is why the two don’t drift. And because it’s a real ClickUp Doc and real ClickUp tasks, everything behaves exactly as anything else in your space does.

Plan in Slack or Teams, build in ClickUp

The conversation doesn’t have to move into ClickUp, and it shouldn’t. Projan’s Slack and Microsoft Teams bots run the whole facilitated session in-channel — the questions, the back-and-forth about the portal, the moment the team settles on phasing the auth. A team that lives in Slack never opens anything else to plan; the agreed output is what travels. When the session lands, the Doc and the tasks appear in ClickUp, connected, and the developers pick it up there. The deciding stays where the team already talks. The building stays where the work already lives.

Setting it up

Connect ClickUp once under Integrations → ClickUp (OAuth with your ClickUp account), pick the space or list to export into, run a session, and confirm the export — reviewing the Doc and the task breakdown before anything is created. The same session can target Jira, Linear or Notion just as easily, so leaning on Projan never means leaning away from ClickUp.

Projan is the layer above ClickUp

Keep ClickUp as your one place for everything — that’s exactly what it’s good at. Projan isn’t a second home for your work; it’s the step before it, the bit that decides what belongs in the space and why, then writes that decision in as the Doc and the tasks. ClickUp stays where the work lives. Projan just makes sure what lands there was actually agreed.