AI project assistant · on WhatsApp

Your project record
finally talks back.

Ask it anything — status, history, who owes what, what's stuck. It answers like your best engineer: with insight, and with the evidence attached. And it watches everything that moves, so you hear about the letter that matters before anyone has to ask.

Connects to the platform your project already runs on. Nothing leaves your project.

YOUR PROJECT PLATFORM · CDE AISTMA YOUR TEAM'S WHATSAPP

The part nobody budgets for

Your CDE has the answer. Getting it out is the job.

The common data environment does its part — everything is filed, revisioned, and auditable. These three things still happen every week.

A hundred transmittals land at once

Somewhere in them is the letter with a five-day response deadline. The platform emailed you about it, along with everything else. The notification that mattered looked exactly like the ninety-nine that didn't.

Someone asks for a status

A count means opening the register, filtering, scrolling, and hoping the search caught the ones with a typo in the title. Twenty minutes later you have a number you would rather not be quoted on.

You are not at your desk

You are on site, in a meeting, or in a car. The document exists. The login does not fit the moment, and the question waits until it is no longer useful.

Onboarding

Three steps, then it is just a phone number.

Aistma is a channel into the platform you already pay for. It reads through your own account, with permissions your team sets.

STEP 01

Your IT team creates the access

An API client on your own platform, scoped to the projects you choose. The credentials stay yours and can be revoked at any time. Aistma never asks anyone for a password.

STEP 02

Your team saves one number

No app to install, no account to create, no training session. They already know how to send a WhatsApp message. Access is granted per person, per project.

STEP 03

They ask. It answers.

In plain language, in the words they actually use. Every answer carries the document number and, where the file can travel, the file.

Plain language, typos and all

What people actually type.

Not commands, not a menu, no syntax to learn. Questions like these, typed the way a busy person types them on a phone.

"Fine me the rfis about backfill"ANSWERED · 9s
"Give me pdfs of them"4 FILES SENT
"Who is sitting on our overdue RFIs?"ANSWERED · INSIGHT
"What the status of the master schedule submitted by contractors?"ANSWERED · 47s
"Notify me when new letters or rfi comes in"WATCH ARMED

The spelling matters: register titles contain typos too, so Aistma searches for what people meant, not only what they typed. Response times are from our own test project.

The part that surprises people

It reads the record like a senior engineer.

Lists are easy. What your best people add is the connection — who is sitting on what, which questions are really the same question, what is about to bite. Aistma adds it too, and only from what the record actually says.

"which RFIs are overdue?"

  • Four overdue — listed with numbers, senders, and days late, oldest first.
  • "Three of the four sit with one subcontractor. Two are the same paint-system query on adjacent zones — worth chasing together."
  • Every claim traceable: the numbers are on the message, the documents one tap away.

A real answer from our demonstration project, unedited. It connects what is in the record — it does not speculate, predict, or give contractual opinions.

For the people who run the job

Alarms early enough to matter.

Trouble hides in aggregates: rejections creeping up, overdue RFIs stacking against one party, response dates clustering into the same week. Aistma keeps those signals one question away — and behind every number, the trail to the root cause. Early response is a management act; Aistma's job is to make sure it can still be early.

Rejections climbing

"why are structural rejections up?"

The rejected documents, the reviewers' verbatim comments, and the pattern named — root cause on the screen, not in a meeting next week.

Overdue stacking

"who is sitting on our overdue RFIs?"

Three of four with one firm — chase together. The bottleneck identified in one message, while chasing it still changes the outcome.

Deadlines clustering

"tell me before any response date passes"

Watches on respond-by dates put the warning in the responsible person's chat before the date passes — not in the monthly report after it did.

A dashboard waits for you to look. Aistma speaks up.

The half no chatbot has

It tells you before you have to ask.

Ask it to watch a document, a package, an inbox, or a person's name on the distribution — and it checks continuously, then messages you the moment something moves. With the file attached, not a link telling you to go and look.

It sweeps completely rather than sampling the newest page. A hundred transmittals landing at once cannot bury the one letter you were waiting for.

What it watches for

  • A review workflow reaches its final step
  • A document's status becomes Approved — or Approved with comments
  • A new revision is issued against a drawing you named
  • A response-by date passes without a reply
  • New correspondence lands in an inbox, filtered to the types you care about

Before you ask

What Aistma does not do.

  • It does not replace your platform. Your CDE stays the system of record and the only place anything is approved. Aistma is a way in and a way to be told.
  • It does not approve, submit, or reply on anyone's behalf. It reads and it reports. Every action stays with the person who owns it.
  • It does not ask you to trust it. Every answer carries the document number and the file, so the source is one tap away and any answer can be checked.
  • It does not see what your account cannot see. Permissions are your project's, per person and per project, enforced before any query runs.
  • It is not a contract adviser. It retrieves, reports, and connects what the documents say. Judgment stays yours.

The arithmetic

What document chasing costs you now.

Move the numbers to match your team. Conservative by default — it counts only time spent looking things up, not the cost of finding out late.

Document controllers, design managers, engineers, planners.
Searching the register, chasing status, re-sending files, checking deadlines.
Salary plus overhead, not take-home pay.
Set it low if you would rather be sceptical. The case holds at 20%.

Start here

A paid pilot, on one project, for 90 days.

Long enough to cross a real submission cycle, short enough that nobody has to defend a big decision. If it has not earned its place by day 90, it stops and the pilot fee is all you spent.

We deploy it, we run it, we fix it. There is nothing for your IT department to host and nothing for your team to learn.

90-day pilot

$5,000 one project

  • Up to 5 named people on WhatsApp
  • One project, connected to your own platform
  • Questions, insight, documents, and standing alerts
  • Setup, hosting, and support included
  • Credited in full against an annual agreement
Talk about a pilot

Questions we are always asked

The awkward ones first.

Which platforms does it connect to?

Aistma works with the cloud-based project management and collaboration platforms — the common data environments — that large construction projects already run on, through their documented APIs. Tell us what your project uses and we will confirm the fit on the call, on a live demonstration.

Where does our project data go?

Aistma queries your platform through your own API credentials and passes the answer to the person who asked. Documents are fetched when someone asks for them and are not kept as a copy of your register. For a pilot we will put the arrangement in writing, including where anything is processed, before you sign.

What if it gives someone a wrong answer?

Every answer carries the document number and the file, so it can be checked in seconds rather than taken on trust. Counts come from the register rather than from a guess, and where a list is cut short it says so and gives the true total. It reports and connects what the documents say; it does not give contractual opinions.

Can people see documents they should not?

No. Access is granted per person and per project, and it is enforced before a query runs rather than left to the assistant's discretion. Someone with access to one project cannot ask about another, and anyone not on the list gets nothing.

What do you need from us to start?

An API client on your platform scoped to the pilot project, the phone numbers of the people who should have access, and about an hour of someone's time. We handle everything else, including the WhatsApp side.

Does it work in Arabic?

It reads and answers questions written in either language, and the documents keep whatever language they were issued in. Tell us on the call which mix your team works in and we will show you that case specifically.

Next step

See it answer your kind of question.

Twenty minutes, on a demonstration project. Bring the question you asked someone this week and watch it come back with the answer, the insight, and the document attached.

Or write to [email protected].