Your customer’s tasks, statuses and documents in one place, not in a chat thread

A task written down in the customer’s own words

They describe what the result should be and attach the files. From then on it is one record, not five messages in different places.

An estimate before the start, and the customer’s word

The work begins only after their "yes". Agreement becomes a record rather than a recollection.

Clear statuses instead of "in progress"

Running · waiting on you · done, please check · accepted. There is a "needs changes" button and a field for what exactly — an argument turns into a task.

Documents and invoices in the same place

The contract, the invoices and the files for the job sit in the portal rather than in four chat threads, and can be downloaded at any time.

The work runs for weeks

A renovation, a build, a production run, a project, a legal matter. The longer the work, the more often people ask about it — and the more each retelling costs.

Files travel through the chat

Measurements, photographs, the contract, the latest version of a layout. The only way to find the current one is to scroll, and every time somebody sends the wrong file.

"I thought we agreed that"

The agreement lives in a spoken conversation and three consecutive messages. A month later each side remembers it differently, and that is expensive.

The client is not one person

One decides, another pays, a third signs it off. Each of them has to be told the whole story again.

1 · A conversation

Half an hour about who asks you what, and how often: customers, dealers, partners, staff. No access to your systems is needed at this step.

2 · A map of the questions, and the first screen

We show which questions eat your people’s time and pick what the portal closes first — usually the status of the work and a place to put files. The map stays with you either way.

3 · We take it into service

We build the portal, connect it to your systems, open it to the first users and stay around: we watch what they actually use and tell you what changed and why.

We do this ourselves

A portal like this runs for us: it lives on this very site. Sign-in is by a code sent to email or phone — no password to invent; the task is described in plain words with files attached; the status, the estimate and the sign-off are exactly what is described above. We show a working portal, not pictures.

It opens on a phone: no separate app to install, and it is not a cut-down mobile version — the screens are the same.

We build this out for you

Exactly what the customer sees in the status, and which roles we set up (who decides, who pays, who signs off) depends on your work. We settle that before the work starts, not along the way.

Medical and other sensitive data does not go into the portal: where the law requires it, the portal keeps the booking and the correspondence, and health information stays in your own system.