One portal, instead of five half-used tools
We built this because running client work across email, spreadsheets, a chat app and an invoicing tool loses things — and the client is the one who notices.
Why it exists
Most businesses that serve clients end up running the relationship across four or five tools that were never meant to work together. The task board does not know about the invoice. The chat app has no memory once someone leaves. The client cannot see any of it, so they email to ask, and someone rebuilds a status update by hand.
This portal puts the parts that touch a client into one place: a workspace per customer holding their tasks, their documents, their conversation, their support requests and their invoices. Your team gets an internal side the client never sees. The client gets one login and can answer their own questions.
It is self-hosted. It runs on ordinary PHP and MySQL hosting, and the data lives on your server and your database rather than with a third party. For a lot of the businesses we built this for — legal, accounting, healthcare administration — that is not a preference, it is the whole reason they can consider it.
The problem we kept living
We run a marketing agency. For years, the same thing happened every week: a client would email to ask where something stood, and one of us would stop what we were doing, open three tools, and reconstruct an answer by hand. Files lived in email and a shared drive and a chat app, and the newest version was never where you expected. Approvals happened in replies and got re-litigated a month later. And at the end of the month, an invoice went out that the client could not connect to anything they had actually seen us do.
We tried the obvious fixes. We added a project management tool — but it was built for our team, not our clients, so the client still could not see anything and still emailed to ask. We added a client-portal add-on — but it did not know about the invoice, or the support request, or the conversation. Every tool solved one slice and created another seam. What we actually needed did not exist as one product: a single place, per client, that held the work, the files, the conversation, the support and the bill, that the client could open themselves, and that we controlled.
So we built it, for our own agency first. The version you can sign up for today is the tool we use to run our own client work.
What we believe about client software
The client is the user, not an afterthought. Most “client portals” are an internal tool with a read-only guest view bolted on. We started from the other side: what does the client need to see to stop having to ask? Everything else is built around that.
One system beats five integrations. Tools that were designed separately and wired together later always leak at the joins. Tasks, files, messaging, support, retention scoring and invoicing here were designed as one product, so the invoice knows about the work and the health score knows about the invoice.
Your data should be yours. Self-hosting is not a technical footnote — it is the point. Your client data sits in your database, on your server, with a full export whenever you want it. Nothing switches off if you stop paying or we stop building.
Honesty is a feature. A new platform has limits, and we would rather name them than let you discover them after you have moved real client data across. Where the software does not do something, our pages say so.
Where we are now
The platform launched in 2026 and is being built with its first customers. We would rather tell you that than imply a history we do not have.
Newly launched
Built as one system rather than assembled from separate tools over a decade.
Shaped by early users
What early customers ask for is what gets built next. That is a genuine advantage of arriving now.
Self-hosted
Your server, your database, your backups.
What it does not do
It is not a CRM, a clinical records system, an accounts production package, an issue tracker for engineers, or an EPOS. It sits alongside those and handles the client-facing layer.
On security: files are stored on your own server and are not encrypted at rest, there is no two-factor authentication, and we hold no compliance certification. We say so on the pages where it matters rather than leaving you to discover it. If your regulator requires more than that, this is not the right tool for the records in question — though it may still be right for the work around them.
Who we build for
We build for the businesses that live and die by their client relationships: marketing and SEO agencies, contractors and home-service firms, law and accounting practices, IT and managed-service providers, consultancies, and the many service businesses in between. The specifics differ — a law firm cares about a confidential case workspace, a contractor cares about the emergency desk, an agency cares about approvals and content — but the shape of the problem is identical: a book of clients, work that needs to be visible to both sides, and a stack of tools that makes that harder than it should be.
Because we run an agency ourselves, we are opinionated about the things that actually matter day to day: that a client can answer their own questions, that sign-off is on the record, that the bill connects to the work, and that you can see which relationship is at risk before it is gone. Those are the things the product is best at, and they are the things we use it for.
How this is different from what you are using now
If you already run clients through a project tool, a shared drive, a chat app and an invoicing package, you have a stack — not a system. Each piece is good at its job and blind to the others, so you spend your time being the integration: copying a status into an email, re-sending a file, reconciling what was delivered against what was billed. A client operations portal replaces that human glue with one place where the pieces already know about each other. The invoice sits next to the work it bills. The retention score reads the invoices, the tasks and the support requests. The client sees a single workspace instead of being cc’d on fragments.
And unlike most of the client portals you can buy, this one runs on your own hosting. That means no per-seat pricing creeping up as you hire, no vendor holding your data, and no anxiety about what happens if a supplier changes direction. It is a different trade than the usual SaaS bargain, and for a lot of service businesses it is a better one.
Questions about the company
Who owns and runs it?
Get Us Listed LLC, a small team that runs a marketing agency and built this for its own client work first. When you email us, a real person replies.
How do you make money?
Through simple monthly subscriptions for the paid plans, with optional add-ons. There is no venture pressure to monetise your data, no ads, and no reselling of anything. The self-hosted model means we are paid for the software, not for holding your information hostage.
Is it safe to build on a new platform?
That is a fair question, and the honest answer is: judge it on one client first, and lean on the fact that it is self-hosted. Because the application and database run on your own hosting with a full export available, you are never locked in and nothing depends on our servers staying up. Start small, and expand only when it has earned it.
How do I influence the roadmap?
Tell us what you need. At this stage, what early customers ask for genuinely decides what gets built next — that is one of the real advantages of arriving early rather than late.
Try it on one client
Start free, set up a single workspace, and see whether it removes more email than it creates.
Create your workspace