What actually lands on the board when we export?

Trello cards on the list you choose, each with acceptance criteria written into the card description. They arrive as proper, scoped cards rather than one-line reminders you'll have to puzzle over later.

Will Projan add columns, labels or automations to our board?

No. It adds cards to a list you already have. No new lists, no Power-Up rules to maintain, no change to how your board is set up — the structure stays exactly as you left it.

We capture which work depends on what — does Trello show that?

The dependencies are captured in the plan, but Projan does not create native dependency links in Trello, because Trello doesn't have them as a first-class feature. So you'll see the ordering noted in the planning output rather than as a link between cards on the board.

Can Projan read an existing Trello card as a starting point?

Yes. Paste a Trello card's URL into a session and Projan pulls it in as context, so you can plan around work that's already on the board instead of starting from scratch.

How long does a planning session actually take?

For something small — a landing page, a single feature — it's a few minutes. Projan asks what you're building, who it's for and what done looks like, you answer, and the cards come out the other end.

Does the team have to plan inside Trello?

No. The session runs in Slack, Microsoft Teams or Projan's own workspace. Trello is just where the agreed cards land at the end.

Is this going to make Trello more complicated to use?

No — that's the point of keeping it to cards. Trello stays the simple board you chose on purpose. The only difference is the cards turn up already thought-through.

Trello keeps us deliberately simple — can Projan help us plan properly without complicating it?

Trello's whole appeal is that it's simple, and the last thing a small team wants is a planning tool that drags complexity back in. Projan respects that. It runs a quick facilitated conversation — what are we doing, for whom, what does done look like — and turns the agreement into Trello cards on your list, each with acceptance criteria written into the description. No new columns, no process overhaul, no automation to maintain. The board stays as clean as you keep it; the cards just arrive already thought-through instead of as one-line reminders you'll have to decode later.

A solo founder decides the product needs a waitlist page before launch. It’s a small thing — a headline, an email field, a thank-you. Easy enough to drop a card on the board reading “build waitlist page” and move on. Three days later they’re staring at that card trying to remember whether it needed a double opt-in, what the success message should say, and whether the email even goes anywhere yet. The card was simple. It just wasn’t finished thinking.

Simple is the point — keep it that way

People choose Trello on purpose. A board, some lists, cards you drag across — no fields you’ll never fill in, no process to administer. That simplicity is the feature, and any planning tool that “helps” by bolting on workflows and columns has quietly broken the thing you liked. So the bar here is honest: help us plan a bit more properly without making Trello any heavier to live with.

Projan keeps to that. It does the thinking before the card hits the board, not by adding machinery to the board itself. You get cards that already know what they’re for. The board stays as light as you keep it.

A five-minute plan, properly done

Back to the waitlist page. Instead of writing a one-line card and hoping, the founder runs a quick Projan session — in Slack, in Teams, or in the web app.

It’s short. Projan asks what the page is for and who’s landing on it, what counts as done, and whether there’s anything easy to forget. The founder mentions the confirmation email actually needs to fire, and that they’d rather keep signup to a single field. That’s about it — a few minutes of back-and-forth.

Then it drops cards onto the list, and each one arrives with acceptance criteria already in the description:

Waitlist sign-up form — single email field; validates the address; stores the entry. Done when a valid email is captured and an invalid one is rejected with a clear message.
Confirmation email — fires on successful sign-up. Done when a new sign-up receives the confirmation at the address they entered.
Thank-you state — shown after submit. Done when the page confirms sign-up without a full reload.

Same small board, same simple workflow — but the cards say what “done” means instead of leaving it for a puzzled afternoon next week.

Cards that arrive thought-through

That’s the whole offer: cards onto your list, each carrying the acceptance criteria the session produced. Not a one-line reminder you’ll have to decode, but a card with enough in it that future-you knows exactly what was meant.

One honest caveat, in keeping with Trello staying simple. Where a plan involves ordering — the form before the email, say — Projan captures that dependency in the plan, but it doesn’t create a native dependency link between the Trello cards, because Trello doesn’t really have one. So you’ll see the ordering in the planning output, not as a wired-up link on the board. For a small team that’s usually exactly the right amount: the thinking is recorded, and the board stays uncomplicated.

Plan in Slack or Teams, drop it on the board

You don’t have to plan inside Trello, and you don’t have to plan inside Projan either. Its Slack and Microsoft Teams bots run the short session right where you already chat — the few questions, your answers, done. When you’re happy, the agreed cards land on your Trello list. The conversation stays in the channel; only the cards travel. For a solo founder or a small team, that often means never leaving the one tab you had open anyway.

Setting it up

Connect Trello once under Integrations → Trello (OAuth with your Trello account), pick the board and list the cards should land on, run a quick session, and confirm — you see the cards before they’re created. That’s the whole setup; there’s nothing to configure on the board itself.

It won’t make Trello complicated

Trello stays the simple board you chose on purpose. Projan doesn’t add lists, rules or process to it — it just does the planning beforehand and hands the board cards that already make sense. Trello is still where the work moves. The only thing that changes is that the cards turn up thought-through instead of as reminders you’ll have to decode later.