A portal for our clients
Over the coming weeks our client portal starts rolling out. We built it because Distrope wouldn't be Distrope if it didn't hold itself to the same bar it holds the projects it ships.
- portal
- product
- studio
A few months ago we started building a portal for our clients. This month it enters its first tests, and over the coming weeks several of our active clients will be able to log in and review their invoices, manage their subscriptions, and raise support directly from it.
Sounds simple. It's worth saying why we did it.
A portal that, by company size, we shouldn't have
Distrope serves a handful of accounts. At that scale, no "reasonable" consultancy builds a client portal: the cost of maintaining it doesn't justify itself against the volume of invoices or tickets that have to be processed. The logical move would be a shared folder and email.
But building is what we do. We're a development studio, and the first client we have to hold to that bar is ourselves. If we don't apply the same rigor to our operation that we apply to a client's operation, we're not Distrope.
The portal is built on the kind of stack usually associated with platforms serving millions of accounts — modern serverless infrastructure, enterprise-grade authentication, full observability, all running on one of the most recognized compute platforms in the industry. It's intentionally oversized. We want to live inside what we build, at the speed we build it.
What clients will be able to do
In this first release, every active client will be able to:
- Review invoices — past and current, without asking by email.
- Manage their subscription — pause, update, or cancel directly if they prefer.
- Raise support from a channel that arrives to us structured, with context, without having to start a conversation from scratch.
What comes next — documentation of their project, access to change history, a view of the team's pipeline — is already designed and will land in the following weeks.
Personal attention stays put
Saying "portal" sounds like we're pushing clients to talk to a form. That's not the case.
What changes is that the portal opens a second door — designed for the client's internal team that maybe never had direct contact with us. An operator, an accountant, someone from admin: people who need to see an invoice, confirm a charge, or download a receipt, but who don't need to wait for our team to answer. Now they can come in, find what they need, and go back to their day.
For everything else — the product conversation, scope decisions, the fix on the integration that won't quite run — our team is still there, as always. The portal doesn't replace that; it complements it.
Closing
The portal rolls out in the coming weeks, account by account, so nobody runs into surprises. And it remains, as a side benefit, a running example of what we can build when a client asks us for one of their own. That, in the end, is what having Distrope on your side is about.