Our own product
Our clients don't email change requests. They file them and watch them ship.
Coopen Portal is where every client sees what we are building for them and asks for changes. It is our own product, in production, and we run our own work through it — which is the only honest way to find out whether a tool is any good.
The challenge
Most software projects die in the gap between "here is your delivery" and "actually, could you change…". The request arrives as a message in a thread, next to a photo and a question about the invoice. It gets lost, or it gets done twice, or it gets done wrong.
The client does not know what state their project is in, and asking feels like nagging. So they stop asking, and stop caring.
What we built
What we built
- The state of your project, visible — Each client sees what is being built, what is in progress and what is waiting on them.
- Change requests as tickets — A request has a state, an owner and a history — with screenshots attached where the words run out.
- Processed with AI, then shipped — Each ticket is worked through with AI assistance and applied to the product. What comes back includes the steps to try it yourself.
- An admin board that shows the whole studio — Every client, project and ticket on one board, with drag and drop between states.
- One account for everything — The same sign-in as the rest of our platforms — no separate portal password to lose.
- Notifications by email — Sent through our own account vault, so a new ticket reaches a person instead of waiting to be noticed.
The model: we build the heavy part, you polish it
Nobody knows a business like the person running it, and nobody wants to write a specification. So we build the hard, structural part — the part that is genuinely expensive to get wrong — and then hand over a way to adjust the rest without booking a meeting.
A client who can move a label, reword a section or change how a screen behaves without waiting three days for a developer ends up with software that fits, instead of software they tolerate.
What is not finished yet
The portal is live and we work in it daily. The last step — a client's ticket editing a live preview of their own platform, which they then approve before it goes out — is designed and being built. We would rather tell you where the line is than let you discover it.
The stack
Runs where everything else runs
Static pages plus functions at the edge, data in D1, attachments in R2, sign-in delegated to our own identity service.
The service behind it
Related
Want to work like this?
Every project we take on comes with the portal. You see the state, you ask for changes, you approve what ships. Tell us what you need built.