Starting point
Collaboration on software projects fragments quickly. The status lives in email threads, deliverables arrive as attachments and vanish in the inbox, approvals are agreed in a call and recorded nowhere. And the documents we deliver with every project, that is the data processing agreement, the entry for the record of processing activities, the technical and organisational measures and the EU AI Act classification, are sent once and can no longer be found when the client's data protection officer or an auditor asks for them.
Our clients should always have an answer to three questions without writing to us: Where does my project stand? What do you need from me? Where is the evidence? We built a portal of our own for that.
Solution
After signing in, the client first sees what is waiting for them: "Your feedback is needed" gathers every deliverable awaiting approval across all of the company's projects and jumps straight to the item. Below it, each project has a card with its status, the latest update and the next milestone.
Every deliverable, whether a PDF, a Figma file, a document, a ZIP archive or a link, carries the buttons "Approve" and "Request changes". Only the client's users can decide, and the person and time are stored. An approval is final; requested changes can still be approved later. The discussion sits next to the deliverable as a comment thread, as it does on every update and under "Questions & notes" for anything that belongs to no single deliverable. Under "Exchange", the client sends us files in the portal instead of by email.
Plan and execution are kept apart. Milestones are what has been promised for which date; a completed milestone gets a timestamp, and a missed date is flagged as overdue. Work packages show progress at the level of epics, and only the packages we release to the client. Individual tickets stay internal. "Demo & preview" holds staging and prototype links with version and date.
Under "Documents", every project has a "Compliance & data protection" section: the data processing agreement under Art. 28 GDPR, the entry for the record of processing activities under Art. 30 and the TOMs under Art. 32, each with a status (pending, draft, final), a version and a PDF or link. Added to that are the risk class under the EU AI Act with its rationale and a table of sub-processors with purpose and location. Each item can be hidden until it is ready. When a project is duplicated as the template for a new one, every document starts again at "pending", so no "final" is ever carried over to another client. Manuals are shown by role: to everyone, to admins only or to users only.
Sign-in uses a login link by email by default, single use and valid for 24 hours; the first sign-in asks for consent to the privacy policy. Anyone who wants to can also set a password, with a reset by email. A client's admin invites colleagues and assigns individual projects to users, for example to an external consultant for exactly one project. Every view and every email exists in German and English, and the weekly summary arrives on Mondays, and only when something has happened. The portal uses no tracking.
- "Your feedback is needed": every open approval across all projects, with a jump to the deliverable
- Approve or request changes, with person, time and a comment thread on the deliverable
- Milestones with dates, kept apart from work packages; individual tickets stay internal
- Compliance per project: DPA, RoPA entry and TOMs with status and version, EU AI Act risk class, sub-processors
- Drafts stay hidden until they are ready; a duplicated project starts at "pending"
- Two roles on the client side, team management in the client's own hands, projects assigned one by one
- Login link by email as the default, optional password; German and English down to every email
A look inside the product
Recreated view with sample data.
Result
The project portal has been live since August 2026 and is in a pilot phase with its first client projects. The application grew out of a clickable prototype in just over two weeks: from the first commit on 20 July to today's feature set with milestones, client uploads and password reset on 4 August.
An approval is now a record with a person and a date rather than the memory of a phone call. And the compliance documents we deliver with every project no longer sit in an inbox but with the project, together with their status: when the client's data protection officer asks for the DPA or the EU AI Act classification, the answer is one sign-in away.
- Live since August 2026, in a pilot phase with its first client projects
- From the first commit to today's feature set in just over two weeks
- Approvals recorded with person and time instead of verbal agreements
- Compliance documents per project in one place, with status and version