Contact

Yes. The board works on any phone in the browser, no app to install. Moving a card or adding a photo takes seconds, and the office sees it the moment it happens.

The board runs the daily flow of work, not the months-ahead schedule. Most teams keep their planning tool and stop using mail, spreadsheets and status calls for day-to-day coordination.

It gets its own card, typed as additional work, the moment the scope grows. The card carries when it was added, the conversation about it and who agreed, so at the invoice there is a record to point at instead of a memory to argue about. Dropped work is recorded the same way, which keeps the record fair in both directions.

Yes. The backlog imports cards from a spreadsheet, so the list you keep today becomes cards in one batch. From there you move them onto the board whenever the work is ready to start.

No. Every project starts with columns that fit building work: To do, In progress, Inspection and Completed. Add labels, epics and roles when you want more structure; the board is useful from the first minute.

Both. Typing @ offers the people on the project and the files in it, so a question can name the sheet it is about as easily as the person who should answer. A mentioned drawing points at the file rather than at one version of it, so the link still opens the current revision after a new one arrives. If a mentioned file later leaves the project, the mention is shown struck through rather than quietly repointed at something else.

An edited comment says so, with the time it changed. A deleted one leaves its place in the thread with a note that it was deleted, so a conversation cannot be quietly rewritten after the fact. That is deliberate. A record people can edit away is not a record, and on a building project the thread is often the only account of why something was done.

Yes, and most teams do. Phone calls and quick messages are not going anywhere, and Wyroo does not try to replace every channel. The claim is narrower: the conversation about the work belongs with the work. Decide it wherever you like, then put the answer on the card or the drawing it concerns, so the next person who asks does not have to find the person who knows.

It stays. Comments belong to the work, not to the person who wrote them, so removing someone from a project does not remove what was asked and answered. Their name stays on what they wrote, which is what makes the record worth keeping. What does change is access: they stop seeing the project from the next click onwards.

No. Notifications follow the conversation, not the project. The people already involved in a thread hear about a new reply, and mentioning someone reaches exactly the person you named. Editing a comment does not re-notify everyone in it either: only someone you added while editing is told. Mentions are also bundled into a digest email rather than sent one by one.

No. Reading and replying to a conversation needs an account, and access to the project it belongs to. Someone who opens a link to a card without one is asked to sign in or create an account and then request access from a project admin. What they can get without an account is the work itself: a role can be sent a short email listing the open cards that concern it, and a drawing can be shared as a link that needs no account. Both inform without opening the project. If you need a subcontractor in the discussion, invite them to the project.

Marking up happens on PDF, which is what drawing sets are issued as, and it happens in the browser with no plugin. Everything else the trade sends is stored, versioned, previewed where the browser can show it and shared like any other file: photos from site as JPG or PNG, office documents, and the native formats such as DWG and DXF from 2D CAD, IFC and RVT from BIM, SKP, OBJ and STL from 3D. So the model stays with the project and the drawing set is what people write on.

In private storage in the European Union, in Amazon's Frankfurt region, never in a public bucket. A drawing is served through a link that is signed for you and expires after five minutes, so a link cannot be forwarded and reused later. When you do want to share a file outside the project you create a share link deliberately, and you decide how long it lasts.

No. A drawing opens in the browser on any phone, and a mark is a tap on the spot plus a line of text. There is no plugin and no desktop application to install.

Most teams keep their drive for the company archive and move the drawings the project actually works from into Wyroo. The difference is the conversation: in a drive a drawing is a file, in Wyroo it carries its versions, its marks and the work that came out of them.

Wyroo offers to carry the open marks forward onto the new version, replies included, each one flagged to verify. The drawing may have moved, so you check every carried mark against the new sheet and confirm it or drag it to the right spot. Marks that were already resolved stay with the version they belong to, as the record of what was raised.

Yes, through a share link that you can protect with a password and let expire after a set time, or revoke whenever you want. Every open and download is logged, so you can see the link was used. For a supplier who only needs the marks, the drawing also downloads with every note stamped on it.

Yes. Drag a whole set onto the project at once, or drop them straight into a folder. Nothing needs converting first: the formats the trade uses are recognised as they are.

It goes to the project's trash, where anyone can put it back for 90 days. Only a project manager can remove it for good before then, and the activity log of who uploaded, changed and deleted it survives either way.

Up to 150 MB per file, which covers drawing sets, photo batches and most documents comfortably. A full BIM model is often larger than that: keep the heavy source where it is authored and put the exported drawings and the IFC you actually share into the project, which is the set the rest of the team needs anyway.

No. Same agenda, same round table, same chair. Wyroo carries the agenda, the clock and the minutes while you run the meeting the way you always have. The only new habit is one tap when the room agrees on something.

You mark an agreement with one tap while the room decides. After the close you review the marked points, and each one you accept becomes a card on the board: owned, typed and traceable to the meeting it came from. Nothing reaches the board until you accept it.

No. The invitation lands in every calendar as a normal calendar invite, and the meeting itself happens wherever you hold it: the site cabin, the office or a call. Wyroo runs the agenda, the clock and the minutes, not the conversation.

No. Closing the meeting locks it: the minutes are frozen exactly as the room approved them, and stay that way. Six months later, in a discussion about additional work, that is precisely what you want.

Not on its own. When a conclusion is left empty, AI can draft one from the notes of that point, clearly marked as an AI draft, and it can point out agreements in the notes you may have missed. A person reviews and approves every conclusion in the closing step before the minutes lock, and nothing reaches the board without someone accepting it.

Yes. Prepare your first Wyroo meeting by putting the open points from your last set of minutes on the agenda, and queue the cards that need discussing from the board. From that meeting on, open points carry forward by themselves.

No. A guest is on the attendance list with a name and an email address, reads the agenda through a link, and receives the minutes by email like everyone else. An account is only needed to pick up work on the board.

No. The update is a web page behind a share link: your client opens it in the browser, no account, no login. You can see whether and when it was viewed, and revoke the link at any moment. There is also a PDF with your logo on it, for the file or for print.

Mostly no. The cards were marked during the week, the numbers and the chart come from the board, and AI can suggest the per-card context lines and the note. Everything it suggests lands in a field you can edit, and nothing goes out until you generate.

Only the attachment does. You still write to your client from your own mailbox; you just paste the share link instead of assembling a document, or attach the generated PDF. The difference is what is behind it: a report that took minutes, not an evening.

No. The link shows one page: the cards you selected, the board totals, the chart, your photos and your note. Nothing else in the project is reachable through it, and marking a card never changes who can see the project itself.

Nothing happens to the report. An update is frozen the moment you generate it: the numbers, the chart and the cards stay exactly as they were. The next update shows the new state. Six weeks of updates read as a fair history of the project.

Marking cards is open to everyone on the board, invited partners included: collecting is teamwork. Generating the report and managing the share link is reserved for team members of the company that owns the project, so nothing reaches your client without your team behind it.

Not on the update itself: it is a report, not a discussion. Questions come back through whatever channel you already use. If you want your client actively in the project, with their own view of the board, invite them as a collaborator instead; that is a separate choice.

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.

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.

Yes. Assign them to a role, and they receive a short email digest of the cards that concern them, without creating an account and without seeing the project itself. Informing someone never means letting them in.

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.

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.

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.

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.

If you added a payment method, your subscription continues per active seat. If not, the workspace simply pauses: your data stays safe and read-only until you subscribe.

Anytime, from the billing page, effective at the end of the billing period. No phone calls, no retention flow.

A team member who signed in during the last four weeks. Someone who does not use Wyroo for a while stops counting automatically, and counts again the moment they return. You never pay for dormant accounts.

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.