Onboarding a project worker without a thola account.

2026-05-19 · 9 min read · by the thola team

The most common phrase we hear from project-based founders, in customer interviews, is some variant of this:

"I can't ask my crew to download an app."

Murugan runs a small interiors business out of Chennai. On any given week, he has 30–50 people working on jobs across the city. Some are on his payroll. Most are not. There are masons who come in for the brick-and-cement phase, electricians for the wiring, polishers for the final finish, carpenters for the kitchen modules, and a rotating cast of helpers and labourers who he has worked with for years but does not employ.

When the polisher finishes Phase 3 of the Mylapore project, Murugan needs three things to happen:

1. Someone on site has to record that Phase 3 is done.
2. Photos of the work need to come back.
3. The polisher's payment needs to get approved by Murugan and released.

Today, this happens through WhatsApp. The site supervisor sends Murugan five photos and a voice note. Murugan looks at them between two client calls. He approves payment by sending a UPI to the polisher's number. The polisher, who cannot read English very well and would not download a business app under any circumstances, never touches Murugan's "system."

The cost of this gets paid in two ways. First, the photos and voice notes vanish into WhatsApp, never to be found again when Murugan needs to settle the final invoice with the client. Second — and this is the bigger one — there is no audit trail. When the client comes back six weeks after handover and says the polish on the dining table is uneven, Murugan has nothing to point at except WhatsApp screenshots he no longer has.

The trap most software falls into

The standard answer to this problem, in most PM tools, is "add the worker as a user." Create an account. Give them a login. Train them on the dashboard.

Every founder we've spoken to has tried this. It works for the office team. It fails for the field crew. The reasons are familiar by now — language, low smartphone literacy, the ten-app limit on cheaper Android phones, the resistance to anything that isn't WhatsApp, and the practical problem that a casual worker who shows up for one phase of one project should not need an account that persists across sixty-two other projects he isn't part of.

The right shape of the fix is different. The worker should be able to do their bit without an account, in their language, in under a minute, from a link. The site supervisor or the founder generates a link. The worker opens it. The worker confirms what they did. Done. No download, no signup, no password.

This is what we built. We call it the worker portal, though the worker never sees the word "portal."

A scene from a Tuesday afternoon

Here is what an actual Tuesday afternoon at Murugan's Mylapore site looks like, six weeks into thola.

It is 3:42 PM. The polisher — Karthik, who has worked with Murugan for nine years — finishes the polishing on the dining table. He's done. He packs his cloths and his bottle.

The site supervisor, Reema, opens the project page on her phone. She taps the "Phase 3 — polishing" task and hits Confirm completion. The system asks her to attach 3–5 photos. She takes them. She taps "Send for worker confirmation."

A WhatsApp message lands on Karthik's phone. In Tamil, because that's the language he reads, because the worker portal speaks all six. The message says, in his own language:

"Murugan boss-oda Mylapore project — Phase 3 polishing — Reema says you're done. Confirm here: [link]. After your confirmation, payment of ₹4,800 will go to Murugan boss for approval."

He taps the link. It opens a simple page on his phone — no login, no app. The page shows the photos Reema attached. He confirms they're his work. He taps a big green button: Yes, this is done.

The page asks him a final question, in Tamil: "Did you have any issues on the site that boss should know about?" He doesn't, this time. He taps "No issues." Done.

Karthik's part of the system took 38 seconds. He did not download anything. He did not create an account. He never types a username. He may never use thola again for the rest of his life. But Phase 3 is now confirmed by both the supervisor and the worker, with photos, on the record, in the system.

What happens after that

Murugan, on his end, sees:

• Phase 3 of the Mylapore project marked as complete and worker-confirmed, with photos attached.
• A payment of ₹4,800 sits in his approval queue with the polisher's UPI ID and a one-line description.
• He taps approve. UPI request goes out. He doesn't have to remember to send it later; the system does.

The client, weeks later, can be shown the photos and the timestamps, in a clean summary. The site visit logs are part of the project file. When the dispute arises — "the polishing on the dining table is uneven" — Murugan can point at the photos confirmed on April 22 at 3:42 PM, with the polisher's confirmation, and engage the conversation from a position of evidence.

This is not magic. It is just every single step recorded once, in a place that doesn't disappear into a WhatsApp thread.

The user-side flow, in 4 steps

For Reema (site supervisor):

1. Open the project on her phone, tap the active phase.
2. Mark complete, attach 3–5 photos.
3. Pick the worker from a list of known faces (Murugan's "people I work with" registry), or paste in a phone number if it's someone new.
4. Send for confirmation. Worker gets the WhatsApp link. Reema's done.

For Karthik (worker, no account):

1. Receive the WhatsApp message in his language.
2. Tap the link, see the photos and the description.
3. Confirm or flag an issue.
4. Close the page. No further interaction unless he chooses.

For Murugan (founder):

1. See "Phase 3 confirmed" notification.
2. Approve the payment from his approval queue.
3. Get on with his day.

The whole thing, across three people, three roles, two languages, no installed app on one of them, takes less than two minutes of cumulative human time.

The bigger pattern

There is a deeper thing this enables that founders only notice once it's in place.

Project-based businesses — interiors, construction, AV installation, event production, facility maintenance — are structured around temporary teams that assemble for a phase and dissolve. The carpenter on this kitchen is not the carpenter on the next one. The AC technician shows up for half a day. The painter for two days. The freight crew for an hour.

Most software treats these people as either "in the system" (full account, full onboarding, full friction) or "not in the system" (invisible, WhatsApp only, lost to the record). Both are wrong. The right answer is a portable, accountless, lightweight presence — the worker shows up for the link, does the thing, leaves, and the system retains the record.

The result is a project history that is actually complete, for the first time. The mason's confirmation that he closed the brick phase. The electrician's photos of the wiring. The polisher's nod that the surface is done. None of these people are users of your software. All of them are participants in your records.

The audit trail this builds is also, incidentally, what eventually lets you settle a project dispute, defend a final invoice, qualify for a larger client, or — if you ever want to — qualify for working-capital credit from a bank that wants to see a real project history before lending.

A second pattern: the freelance designer who works for three studios

The same flow handles a different shape of "external" worker — the freelance designer who's on a project for six weeks, then leaves, then comes back four months later for a different project.

She doesn't need a permanent account. She needs a project-scoped link that gives her access to the briefs, files, comments, and time-log for her current job, that expires when the project ends, and that picks up cleanly when she rejoins for the next one. The system handles that the same way it handles the polisher — a scoped link, OTP-confirmed, in her language, no app to install.

We've watched a 9-person agency in Mumbai onboard 24 different freelancers across 8 projects in two months, without a single account creation. The freelancers received 24 different links. Each one did their bit. The agency's project records, however, are unified.

A short, important note on safety

When you let people into your records without an account, the obvious question is: how do you keep them out of records that aren't theirs?

Two answers:

1. Every link is scoped. A worker link gives you exactly the task or project phase it was generated for. It cannot navigate to other projects, other workers, other clients, other anything. It is a single-purpose window.
2. Every link is verified by OTP. The first time the worker opens it, they enter the 6-digit code that arrives by SMS or WhatsApp. After that, the session is bound to that phone for the life of the link.

This is not a perfect security model. It is appropriate security. The polisher confirming his own work is a low-risk action. We secure it accordingly without making him jump through hoops he won't survive.

What it looks like a month later

Two real shifts a customer (a 16-person interiors company in Pune) reported six weeks in:

The supervisor stopped doing post-hoc data entry. Before, the supervisor would do the site work all day, then sit in the office at 7 PM and "enter today" into the system. With the flow above, the entry happens at the moment the work happens, by the people doing the work. The supervisor's 7 PM hour disappeared. He went home.

Disputes got shorter. When a client question came back four weeks after handover, the answer was on the project page, with photos, with worker confirmations, with timestamps. The average "how do we settle this" conversation went from three days to one phone call.

Neither of these is a feature. Both are downstream effects of having the field finally inside the record.

What we're not pretending to do

A few honest limits:

• Worker payment release is currently an approval queue, not an integrated payments rail. We tell you "release this ₹4,800 to this UPI ID," you do the UPI from your bank app. Direct payout integrations are on the roadmap.
• The worker portal is for confirming work, not for negotiating it. Quotes, rate disputes, scope changes still happen on the regular conversation channels.
• OCR for handwritten supplier delivery notes at site is best-effort. Some scripts are noticeably better than others. We have customers who use it well; we have customers who don't.
• Local-language voice for workers is not yet in the portal. Voice goes into the POS flow today; the worker portal is tap-based.

Get started

If you want to onboard your first external worker without giving them an account, the worker-portal setup takes about ten minutes. You'll generate your first scoped link in five.

The polisher won't notice anything has changed. That, in a way, is the whole point.