Notes on design, engineering, and building products.

About

Learn

  • Case studies
  • Newsroom
  • Our products

Support

Legal

Scan to leave a Google review
Give us your feedback

© 2026 Azarr Technologies Ltd. Trademarks and brands are the property of their respective owners.

Why We Built a Client Portal Instead of Sending More Status Emails

Why We Built a Client Portal Instead of Sending More Status Emails

A company can hire us for more than one thing at a time, and mixing them is how things get lost.

Azarr Team
Jason Ball

Azarr Team, Jason Ball

Sat, October 24, 2026 · 2 min read

Why We Built a Client Portal Instead of Sending More Status Emails

Every agency has the same Friday. A client emails to ask where things stand. Someone digs through chat, a tracker and last week's invoice to piece together an answer. It is accurate, and it is already out of date by the time it is sent.

We decided the fix was not a better status email. It was removing the need to ask.

Start with the question, not the feature

Before building Azarr Console, we wrote down the questions clients ask us most:

  1. What are you working on right now?
  2. What has been finished?
  3. What do I owe, and for what?
  4. Who do I talk to about this?

Every screen in the Console answers one of those. If a feature did not, it waited.

One project, one home

The biggest design decision was making the project the centre of everything. A company can hire us for more than one thing at a time, and mixing them is how things get lost. So chat, requests, invoices and the changelog all belong to a project, and people are added to projects individually. A new team member at the client sees only what they were invited into.

Visibility is a feature, and so is hiding things

Transparency does not mean showing everyone everything. A designer on the client side may need the changelog and chat but have no business seeing invoices. So owners can hide entire areas from a member. Hidden is stronger than disabled: the screen is simply not there.

Proof of work, written by the people doing it

The changelog and README for each project are written by the team building it, in the tools they already use. That keeps the record honest, because nobody is translating it afterwards.

What we would tell another team

  • Write the client's questions first, and build to answer them.
  • Scope everything to the unit the client thinks in (for us, the project).
  • Give owners control of who sees what, with hidden as the default for sensitive areas.
  • Let the record be written by those closest to the work.

We will keep refining the Console as clients use it. If your team is wrestling with the same Friday, we would like to hear how you handle it.

Azarr Team
Jason Ball

Azarr Team +1

Editor

As a technology incubator with a focus on sustainable growth, Azarr Technologies identifies market opportunities and develops solutions that address real-world challenges in the mobility and accommodation sectors.

#product design#client experience#Azarr Console#transparency

You May Also Like

From Idea to Launch: How Long Does Building an App Actually Take?
Product Development

From Idea to Launch: How Long Does Building an App Actually Take?

August 28, 2026 • 4 min read
Pay by Phase: Why We Bill Projects in Stages
Business & Strategy

Pay by Phase: Why We Bill Projects in Stages

October 24, 2026 • 2 min read
Designing a Token That Can Only Do Three Things
Software Development

Designing a Token That Can Only Do Three Things

October 24, 2026 • 3 min read

Notes on design, engineering, and building products.

About

Learn

  • Case studies
  • Newsroom
  • Our products

Support

Legal

Scan to leave a Google review
Give us your feedback

© 2026 Azarr Technologies Ltd. Trademarks and brands are the property of their respective owners.