Puelo.xyz
ES / EN
Discuss a case

The method

We analyse. We cut. We act.

The diagnosis decides whether you need a platform, an orchestration, an AI governance frame — or, sometimes, not to build.

Four movements

01

Read the need

The problem stated without tools.

02

Cut and decide

One phase. A written list of what is out.

03

Intervene

The agreed path is executed.

04

Hold in-country

Follow-through in language and time zone.

Five principles

How we decide what not to build

01

Read the need before the catalogue

We start by asking what is broken, for whom, and what can be sustained.

02

One thing per phase

One asset is validated in the field. The rest waits in writing.

03

States, not screens

A process moves from one state to another through a real act.

04

Every dependency is justified

If it cannot be operated or turned off, it is not turned on.

05

Act accordingly

Diagnosis is not décor. The written cut is part of the deliverable.

Possible intervention

Code-less is not a platform.

These paths are chosen by the diagnosis. OutSystems is an option — not a requirement.

  1. Low-code platformWhen the case is a portfolio of business applications.
  2. Digital product or channelWhen the case does not fit a platform.
  3. OrchestrationWhen another application is unnecessary.
  4. A layerAutomate the surface and leave the core alone.
  5. Do not buildWhen analysis does not justify turning anything new on.