Piscis — More backend capacity without putting the product at risk

The challenge: move faster without lowering the technical standard

Piscis develops software for hospitals. In that context, a backend cannot merely work.

It has to be stable, well designed, and treat security as part of the product, not as something reviewed at the end when everything has already been built.

Their team needed to accelerate development, but did not want to do it by adding people who would require months of supervision or leave behind decisions that were difficult to maintain.

They needed people able to join and contribute from day one.

For several months, we joined their team to strengthen backend development and work on system security.

We did not arrive to build a parallel architecture, change everything because we would do it differently, or fill the project with unnecessary layers. We understood what they had already built, adapted to their way of working, and brought experience exactly where it was needed.

Our team has spent years developing backends that handle sensitive information. We know that in these products, delivering features quickly is not enough. Decisions about access, data handling, architecture, and maintenance have to be made properly from the start.

Piscis did not simply need more developers.

It needed to move faster without putting its product in just anyone’s hands.

That is where we came in.