Clients see the work, not your system.
One link, and the whole engagement is behind it: what you have shared, what is waiting for a signature, how the work is going, the invoices if you bill through us, and a way to send you files or raise a problem. You choose who gets in, one person at a time. Closing the portal takes all of it away at once.
Nobody writes the client a status report
Your team works in Studio. Your client opens the portal. Both are drawn from the same record the work already lands on, so there is no second version of the truth to keep current and nothing to assemble on a Thursday night. What your client sees is the work, filtered to what you have shared with them.
Invite their team, each with a role
Invite your client's team the way you would invite a colleague. They sign in with the email you invited them by and a code sent to it, so nobody creates a separate account and nobody has a password to lose. Each person is invited with a role that says what they can do, and what they can see is set per person, so two people on the same team do not have to see the same things.
- Managing their own connected tools is one of the things a role can allow, which is why they can switch that access off without asking you
- Remove someone and their access ends at their next sign-in
The statement of work, and everything that follows it
The engagement's own papers live here: the statement of work, the requirements the delivery is measured against, and the documentation your team writes as the work goes. One place, searchable, with the tickets your client raises sitting beside the work they are about.
- They can comment next to the exact line they mean, and get an answer from someone on your team, by name
- Give them editing access and they are in the live document with you, not a copy somebody emailed last week
Instead of asking where things stand, they look
The project page carries what is moving now and who is on it, the latest update, how much is open, and a versioned list of what the software is built from. None of it is written for them. It is the record, shown.
- If you bill through us, invoices sit on the same page with what is still owed and a link to pay. If you do not, none of that appears
- An update can be a short video or a spoken briefing instead of a paragraph, which is often the faster way to say it
They can ask, out loud if they like
A client who does not want to read four pages can type the question or say it, and get an answer. It is an agent like any other here: it has an owner on your side, it is capped by what the person asking is allowed to see, and it cannot tell them something their role does not cover. What it tells them lands on the record with everything else.
They connect their own tools, and they can pull the plug
Your client connects their own account for the tools their team already works in. TEKIMAX never holds their password or their keys. The connection is theirs, so they set what we can reach for the whole engagement, and they can switch it off whenever they like. It stops immediately, and the record of what was done through it stays.
Raising a problem takes three answers
What kind of thing it is, one line about it, and the details, with a screenshot if that helps. The kinds are: a question, something is broken, please change something, and I cannot get in.
- Each one gets a reference your client can quote back at you
- A ticket can be withdrawn. It cannot be deleted, which is the same rule the rest of the record follows
- It sits with the work it is about, not in a separate inbox somebody has to remember to check
See a portal set up for one of your clients.