Working together

Three firms, one client, one project

Collaboration is not handing out accounts. It is everyone seeing the same picture, and each person exactly their part: your team in full, partners on their projects, and the people who never log in still in the loop.

Free to try. No credit card needed.

See it live

Meet a project team before you build one.

Project team

Everyone working on this project.

Sanne de Vries

Site manager

De Vries Bouw
Owner
Main contractor
sanne@devriesbouw.example
+31 6 12 34 56 78
Lena Fischer
External

Architect

Atelier Fischer
Editor
Architect
lena@atelierfischer.example
Marco Bianchi
External

Client

Viewer
Client
marco.bianchi@mail.example
Roles
Main contractor
2 people
Architect
1 person
Electrician
1 person
Client
1 person
Plumber
No people

Sanne owns the project, Lena and Marco joined from outside with their own access, and the plumber role is still waiting for a plumber. This is the real component your team would use.

The short version

2

Access levels for outside partners

An editor works, a viewer follows; both see only their project.

0

Accounts needed to stay informed

Role digests, minutes, updates and share links travel by email.

1

Visibility rule, everywhere

Boards, lists and search all answer to the same access check.

From your team to the whole team

The circle grows as the project does

  1. 01

    Invite your own team

    Your company works together on every project you give them.

  2. 02

    Add the other firms

    Architect, engineer or subcontractor join as editor or viewer, on exactly that project.

  3. 03

    Wire in the outer ring

    Roles for the trades, digests for people without accounts, links for the client.

That's it. The project decides who sees it, not the org chart.

Ready when you are: the first project is free.

Start for free

Everyone in, nobody wandering

Invite the people, keep the boundaries

The architect brings their own account and their own firm, and lands on your project as an editor: they draw, comment and move their cards. The client joins as a viewer and watches the same board without changing a thing.

What they see ends at the project's edge. A partner on one renovation sees that renovation: not your other projects, not your team pages, not your numbers. One access rule decides it, and every list, board and search answers to that same rule.

Their firm, your project Partners collaborate under their own name and company.
Exactly their slice A collaborator sees the projects they are on, nothing beside them.
Access lives in settings Granted and removed per project, in one place, by your team.

Talk where the work is

The conversation stays on the card

A question about the drain lives on the drain's card, next to the drawing it is about, where the plumber and the architect both find it. Mention someone by name and it reaches exactly that person: on their phone, in the app, and in a tidy email digest instead of a message per mention.

Notifications know the difference between "this needs you" and "this happened": what is addressed to you stands out, the rest stays ambient. Nobody is CC'd into a project they can already see.

On the work itself The discussion sits on the card, the file or the meeting point.
A mention reaches one person By name, with the context attached, not a group blast.
Email only when it helps Mentions bundle into one digest instead of a mail per ping.

No account, still on board

Reach the people who never log in

Every project has an outer ring: the inspector, the client's partner, the supplier quoting on one drawing. They do not want another tool, and they do not need one.

Meeting minutes arrive in their inbox, and the agenda opens from a link. A drawing travels as a share link that always shows the current version. The client's weekly update is a web page behind a link. All of it lands in the mailbox they already read.

Share links Drawings and documents open in the browser, always current.
Minutes and updates Meetings and client reports travel by email, ready to read.
No tool to adopt Ordinary email, in the mailbox they already have.

Work by role, not by inbox

The whole team takes part, account or no account

On a building project the trade is certain before the name is: there will be an electrician long before you know which one. So in Wyroo the role exists before the person, real from day one. Cards belong to the electrician while the quotes are still coming in, and the moment someone fills the role, the work that waited is theirs.

And a role is not a permission. Put someone in a role to keep them informed, without opening the project to them; invite them the day they need to work in it. Two decisions, taken separately, which is exactly how site life works.

How roles work
Plan before the hire The whole project takes shape while the team is still forming.
Reach non-users Role members without accounts get their cards by digest.
Not a permission Informing someone never means letting them into the project.

Why collaboration, not accounts

Collaboration is not handing out accounts. It is everyone seeing the same picture, and each person exactly their part.

Projects do not stall because people cannot log in somewhere. They stall because five parties work from five pictures of the same building.

So the picture is what gets shared: the board, the current drawing, the decisions, each at the level that fits. Full access for the team, a project for the partner, a digest for the trade, a link for the client. Email keeps doing what email is good at: delivering. The work itself stays in one place, whole.

Less noise. More progress.

Questions about working together

Can work belong to a trade before I know the person?
Yes, and it should. Assign the electrician role to a card while you are still comparing quotes; the whole project takes shape before the team is complete. When the person is known, they join the role and every card that was waiting for them is theirs, digest included.
Does my subcontractor have to learn a new tool?
Not to stay in the loop. A role digest lands in their mailbox with the open cards for their trade, minutes and updates arrive by email, and a share link opens a drawing in the browser. The account comes later, if and when they want to work on the board themselves.
What is the difference between an editor and a viewer?
An editor works: moves cards, uploads drawings, joins the conversation. A viewer follows: sees the same project, changes nothing. A client who wants to watch progress is usually a viewer; the architect drawing your details is an editor.
Should I invite my client, or send them updates?
Both exist for a reason. A client who wants to be close to the work joins as a viewer and watches the board live. A client who wants the summary gets the weekly client update: a frozen report behind a link, no account at all. Many projects start with updates and invite the client later.
Who sees which board?
You decide per project. Your team sees the projects they work on, a subcontractor sees only theirs, and a client can follow progress without the internal back and forth.
Do clients and partners I invite cost a seat?
Only people in your own team are seats, so clients, architects and contractors never add to your bill. The free plan includes a small number of outside collaborators, counted across your whole workspace rather than per project.
What happens when a collaborator leaves the project?
You remove them in the project settings and their access ends there and then. What they contributed stays: cards, comments and uploads remain part of the project history, with their name on them, so the record keeps making sense.

Dig deeper

The full guides behind this page, in plain language.

Bring the whole building team onto one project

Free to try, no credit card needed. Partners and clients never cost a seat.

Create your account