Senva
DE Book an intro call

Services · 01

Enterprise portals and platforms

Self-service, customer and partner portals that connect to your existing systems and don't surprise your operations team on go-live day.

Book an intro call See our work

The problem

Portal projects stall at the interfaces, rarely at the screens

The screens are usually agreed within a few weeks. Then the real questions arrive: a legacy system with no documented API, an identity service that three departments are responsible for, an operations team that learns shortly before go-live what it is supposed to run.

So we start with the interfaces. Before we design the first screen, we know which systems the portal has to read from and write to, who owns them and how they behave under load.

What you get

Deliverables

  • Architecture and interface design, agreed with your IT architects and your operations team
  • UI/UX design in Figma, with clickable prototypes that your business teams test before development starts
  • Frontend and backend, built and tested, connected to your sign-in and permission systems
  • Automated tests and a CI pipeline
  • Architecture and operations documentation for the handover
  • If you want, operations by us; see Operations & SLA

Technologies from our portal projects

Backend
Java, Node.js
Frontend
Next.js, React, Angular
Cloud
AWS in an EU region
Design
Figma

We choose the stack to fit what you already run and the team that will run it, not our own preferences. A portal your team cannot develop further is a dependency risk.

Approach

How a portal project runs with us

  1. Discovery: we map user groups, workflows and interfaces. The result is an architecture sketch with the open risks listed.
  2. Prototype: the most important workflows as a clickable draft, tested with future users.
  3. Build in sprints, with a demo at the end of every sprint.
  4. Acceptance and go-live, planned together with your operations team.
  5. Handover to your team, or operations by Senva.

Architecture, core development and project management are based in Berlin. The partner team in Hanoi develops alongside them, but works only with synthetic or anonymised test data.

More on the two-zone model

Work

Portal and platform projects

Typical first step

Discovery sprint or architecture review

If you are planning a new portal, we start with a discovery sprint that produces a prototype, an architecture sketch and an effort estimate. If the platform already exists, we look at it in an architecture review before we change a single line.

See the first steps

FAQ

Questions from procurement and IT

Do you work with our existing technology stack?

In most cases, yes. In our portal projects that has meant Java, Node.js, Next.js, React and Angular. If your stack is different, we'll tell you in the intro call whether we know it well enough to stand behind the work.

Who at Senva has access to our production systems?

Only the Berlin team, only when the project requires it, and only to the extent set out in the contract. The partner team in Hanoi has no access to production systems and never sees personal data.

Can you work with our operations team or another service provider?

Yes. We plan the handover from the start: deployment pipeline, operations manual and a joint phase in which your team already rolls out changes on its own while we are still alongside.

Who owns the code?

Usage and ownership rights to the code are set out in the contract before the first line is written. If you wish, the repositories sit in your environment from day one.

Intro call

Let's talk about your portal

30 minutes with Kim Pham or Holger Spickmann. We reply within one working day, and sign an NDA beforehand if you wish.

Book an intro call
Kim PhamManaging Director, Senva GmbH
Holger SpickmannSenior Project Manager, Senva GmbH
Email
info@senva.de
Phone
+49 30 5268 7541
Address
Bundesallee 32, 10717 Berlin, Germany