Connection
Sign inStart a pilot

Nothing asked on site gets lost again.

Channels, drawings and asks for each project. Every ask stays open until its task is done.

Start a pilot Walk through a day
Mehul’s Home in the app: an ask from Nirav Shah to approve the revised shuttering rate, with Done and Not yet, and Mehul’s own tasks that are due.
  1. An ask from Nirav, open until the task behind it is done.
  2. Mehul’s own tasks that are due, before anyone has to ask.

A day on Shilaj Tower B

Mehul Trivedi runs the site. Here is one day, as the app keeps it.

  1. The day arrives in order.

    One digest at eight says what is due, what is overdue and what is asked of Mehul. Then the phone stays quiet until something needs an answer.

    EN
    Your day 1 due today · 1 overdue · 1 asked of you
    GU
    તમારો દિવસ 1 આજે છેલ્લી તારીખ · 1 મોડું · 1 તમને કહેલું
    HI
    आपका दिन 1 की आज अंतिम तिथि · 1 में देर · 1 आपसे कहे गए
    The digest word for word, in whichever of the three Mehul reads.

  2. The pour sequence goes out.

    It is issued to Rakesh Parmar, the foreman who builds from it. Rakesh acknowledges it with a tap, and the time is kept with the drawing.

    The Pour sequence drawing in the app: revision 1 current, added at 9:10 am, issued to Rakesh Parmar at 9:12 am and acknowledged.
    The current revision, who it went to, and when they acknowledged it.

  3. A message becomes an ask.

    Mehul wants the pour started by three. The message is turned into an ask of Rakesh, and the ask stays open until the pour is done.

    The Structural works channel: the pour sequence drawing, issued and acknowledged, then Mehul’s message asking for the pour by 3 pm, now showing Rakesh Parmar, Waiting. A note at the foot says Rakesh Parmar, an external, can read this channel.
    Externals read only the channels opened to them, and the app says who is reading.

  4. An honest not yet.

    The cube test samples can’t go today. Rakesh says why, and when to be asked again, in two taps. Mehul sees both.

    The Not yet sheet: why not yet, with Ask me again set to Tomorrow morning, and four reasons to choose from.
    Tomorrow morning unless they pick another time, so one tap still answers.

  5. Asked again, as they said.

    The ask comes back to Rakesh at nine, the time Rakesh chose. Had Rakesh gone quiet twice instead, Mehul would have been told to call.

    The cube test task as Mehul sees it: Rakesh Parmar, Not yet, waiting on someone else, asked again at 9:00 am the next day.
    What Mehul sees: the reason, and when the ask comes back.

  6. The day, on record.

    An edited message keeps its earlier words. A deleted one leaves who removed it and when. Staff can open the project’s record pack at any time.

    • Every document, and each revision with who added it
    • Photos, with the time the camera took them
    • Drawings issued, and when each was acknowledged
    • Tasks, with every close and reopen
    • What was deleted, by whom, and when
    • A chain of hashes that breaks if a line is altered
    What the record pack holds, from the project’s first day.

What holds on every project

Staff-only stays staff-only.
Subcontractors see the channels, drawings and tasks opened to them, and nothing else.
Nothing to install for subcontractors.
An access link, sent on WhatsApp, opens what they may see and takes their one reply or photo.
Quiet by default.
A phone buzzes when something is asked of that person or issued to them. Reminders wait for the morning.
In their own language.
Gujarati, Hindi or English, chosen by each person, from the buttons to the digest.
Built for bad signal.
What is written without signal goes by itself when signal comes back.
An assistant, if they want one.
It answers from what they can already see. Each person switches it on for themselves.

Start with one project.

We set up your firm and its first admin. You add your projects and your people, and they sign in with their phone numbers.

Start a pilot
Project
Yours
Issued to
Your firm
Revision
Pilot