How do you get tradespeople and subcontractors on board with new construction software?

Why do tradespeople give up on complicated software?

Software becomes difficult to keep using when it adds steps without making the work clearer. A tradesperson wants to know where to go, what has changed and who can help. If they need to enter the same information twice or still call someone to find the agreement, the old channel remains attractive.

Start by assessing what is getting stuck. Ask someone to show the latest situation where they fell back on WhatsApp, paper or calling. Turn ‘they do not use it’ into a specific question: which action failed, what was the consequence, and who can resolve the blockage?

Find the barrier where it arises

Do not use age or job title as evidence of whether someone can manage digitally. Have the person perform the action themselves. You then see whether the problem is access, explanation, setup, device or the office's response.

A customer example of the ‘another app’ objection

In the Woub customer story about Beentjes Hekwerk & Toegangstechniek, Barry Beentjes explains that his team initially dreaded yet more software. They already had Exact Online for invoices and ENK as ERP. The reaction was: ‘Do we really need more software? That's difficult, mate!’ That initial response concerned the complexity they expected, before the team worked with Woub. Barry now describes the team as completely convinced.

Comparing Woub with ERP here is like comparing apples and pears. ERP continues supporting business processes, and invoicing software continues handling invoices. Woub takes the place of WhatsApp groups for daily project communication. At Beentjes, those conversations previously went through WhatsApp, while information from phone calls and emails remained scattered. With Woub, they bring that communication together within the project.

Explain specifically to your team what changes: instead of maintaining both WhatsApp and Woub for work agreements, you communicate by project in Woub from now on. Start with a familiar action, such as posting a message or photo within the right job. The team can experience for themselves how simple that daily communication is, without treating Woub as a new ERP implementation. It is a different place for existing communication, rather than another round of administration.

The case illustrates this switch; it does not prove every team has the same outcome. Agree which project communication moves to Woub so that the old channel does not keep demanding the same work alongside it.

What information does a tradesperson actually need?

A tradesperson needs information that lets them carry out their next action correctly: the location, current working agreement, relevant change, necessary preparation and a reachable contact person. Not every participant needs the whole business file for that.

Focus the first explanation on tomorrow's work

Take an illustrative situation: the installer can only start once another crew releases a room. Show where the confirmed agreement is, who reports a deviation and who assesses the new sequence. Then practise one response: ‘The room is not clear yet; I need confirmation before starting.’

The planner maintains the formal programme. The site manager organises daily coordination. Do not turn a communication message into a second programme with different dates.

A useful starter pack contains the recognisable project name and location, current agreement, place for questions, responsible contact person and an example of the expected feedback. For drawings, refer to the current source. Let DMS, BIM, ERP, estimating and specialist scheduling retain their own functions.

Which construction app do tradespeople like using?

You cannot answer that for all tradespeople with one brand. Assess an app with the people who need to use it. Can they find the right job on their own device, understand the agreement and report back without unnecessary steps? Does the route also work where they do their job? Is it clear what happens during an outage or urgent situation?

Woub focuses on daily project communication. The explanations for a tradesperson and a subcontractor show that project context. That makes Woub an option to test, rather than a proven winner for every site crew. If an existing application already covers the agreed communication well, you do not need to introduce another app.

How do you invite external parties?

Invite the right person to a specific project and explain what you expect. An email with only a product name is not enough. State which job it concerns, which information they will find there, how to ask a question and who will help the first time.

Test internally first, then with a small project group

First have someone in the office and a site manager work through the route: invitation, opening the project, finding a real agreement, responding and finding the response. Fix incorrect access or unclear instructions before asking a subcontractor to practise. The site crew then does not become a test group for a setup that does not yet work.

Then invite a small group involved in the chosen project. Have the external participant open it and respond themselves. Do not take over their phone to finish quickly: you still would not know whether they could do it independently. Ask what was unclear and adjust the instructions.

De Woub guide to external participants describes email invitations. Check the current screens and role selection for your environment; older help texts do not guarantee every button name or permission is unchanged.

Distinguish between external participation and team roles

According to the current Woub pricing page, invited external participants can collaborate free within the participation offered. That does not mean every team role, administrator or setup is free. Before implementation, check the appropriate role, permissions and conditions. Have a supplier explain specifically what the person concerned can see and do.

Also test whether the external participant can access only the intended project information. Do not make everyone an administrator for convenience. If a subcontractor sends another employee or someone leaves the project, agree who updates participation and access. That check is part of collaboration, rather than a one-off installation task.

Which project agreements support adoption?

Adoption becomes practical when everyone uses the same route and management follows it too. An office employee sending important changes only through private messages teaches the site crew that the project overview is incomplete.

Record five working agreements

These agreements do not require five extra administrative actions. Use Woub as the regular place for project communication: messages stay within the project, and Wouby AI automatically records supported conversations. Here is how Woub helps with each agreement:

1. Ask within the right project. Ask your question in the project chat or call from within the project. Communication is then immediately within the right job. For a conversation through Woub, Wouby AI automatically creates a subject and summary so that colleagues can find the question discussed. The team makes sure the question is sufficiently clear and answered.

2. Make the change recognisable. Discuss what changes and what still needs confirmation. Wouby AI includes the status, feedback and implications discussed in the summary. Points still needing confirmation appear under a separate heading. The audio recording remains available to listen back to. The team checks whether the authorised person has actually confirmed the change.

3. Get the action to the right person. Wouby AI automatically turns recognised commitments into tasks and assigns the right person responsible. Without an agreed deadline, Woub dates the task today. If a conversation covers several projects, Wouby AI links the specific tasks to the right project. The employee checks the output and picks up the task.

4. Discuss urgent matters and retain the outcome. Call the person responsible through Woub. Afterwards, the recording automatically produces the summary and tasks; you do not need to retype the outcome in a WhatsApp group. Agree as a team who takes over an urgent question if someone cannot be reached. This automatic recording applies to supported calling through Woub and recorded live meetings, rather than automatically to a regular phone call outside Woub.

5. Keep using the right source. Woub keeps the conversation source and the resulting summary and tasks within the project context. Your specialist systems remain the primary reference for the current drawing, formal programme and administration. Refer to them clearly and agree who processes a change; this does not promise automatic updates in ERP, BIM, DMS or scheduling.

Also agree who answers during absence. A quick installation helps little if the first three questions go unanswered. The subcontractor needs to see that the agreed route actually works.

Choose which old project channel stops

For the trial project, agree where confirmed daily agreements will be kept from now on. Decide which WhatsApp project group or separate action list will be closed or no longer updated for that purpose. Transfer relevant open agreements carefully and tell those involved where to continue.

This does not mean the whole business may no longer use email or the phone. Invoices, formal correspondence and urgent contact have their own functions. The issue is duplicate routes for the same project agreement. Have someone help with the transition, but do not make permanent copying between two channels the new standard.

Adapt guidance to the organisation

With 1–10 employees, the owner can guide the first actions personally. Arrange someone to cover too: the approach needs to keep working when the owner cannot be reached.

With 10–100 employees, a contact person for each team or project helps. Have office and site teams explain the same agreements. A subcontractor working on two projects should not receive two different instructions for the same type of feedback.

With 100+ employees, expansion also needs attention to role management, training new colleagues, changing external parties and ownership of the approach. Test those requirements with IT and process owners. Size is no reason to activate every function at once.

Guidance is also evident outside Woub. In the AFAS case about Wagemakers Bouw, departmental representatives, champions and training are described during ERP implementation. The case also shows enthusiastic carpenters. It is a supplier story about a different application; it does not support a universal adoption score or a Woub result, but makes the role of guidance concrete.

How do you measure daily use and follow-up?

Measure whether people can carry out the agreed action and whether the outcome is picked up. Accounts, downloads or lots of messages do not prove that. Combine a small, regular check with participants' experiences.

Use a simple measurement sheet

Choose beforehand which relevant situations you check and over which period. The sheet below is a proposed team check, rather than an automatic Woub adoption dashboard.

Record the counts and selection. Three well-handled messages say little if dozens of other questions were not examined. Compare the same type of work at the next check. Do not use a general success percentage without explaining who and what you checked.

Only expand once the first route works

Hold back expansion when necessary participants cannot get in, questions remain unanswered, current agreements cannot be found or duplicate work increases. Resolve the cause and test again with the same action. Adding more users does not automatically improve an unclear approach.

If the route works, add another project or team and guide the first action again. Retain one owner for working agreements and use site feedback to improve the setup.

Want to develop daily communication between roles further? Read how office, site and subcontractors coordinate. Want to test it with your own project group? Try free for 14 days and view the pricing and conditions.