Pwas is developed by Pooel Srl.

It's the most useful thing we can offer and the rarest to find in a commercial conversation. There are situations where a mature vertical product costs less and works better than anything built to measure, and others where an organisation's problem isn't software but a process nobody wants to change.

In both cases we say so, even when it means turning down a project. That isn't generosity: a wrong project costs us more than it costs you, because it consumes team time and produces an unhappy client who was right to be unhappy.

The practical consequence is that a demo can end with "in your case, look elsewhere". It happens, and it's a legitimate outcome.

Not out of caution, but because it's the only way to be wrong cheaply. A narrow scope — one process, one department, one service line — goes into service in weeks rather than quarters, and at the end of those weeks you have real data instead of a forecast: whether the method works in your context, whether people use it, whether the estimated timings were realistic.

If the answer is no, you've spent little and you know early. If it's yes, the rest is built on a verified base instead of a bet.

Be wary of anyone proposing to start from everything, including us if we ever did.

The configuration describing your domain is yours, in readable text files versioned wherever you choose. The data sits on a standard relational database queryable with common tools. The system runs where you want, with no dependency on one provider's managed services.

In projects we explicitly train whoever in your organisation will handle ordinary changes — adding a field, changing a permission, introducing a control — because those shouldn't go through a supplier.

It's a position with an obvious commercial cost and a practical reason: a client who stays because it suits them is a better client than one who stays because they can't leave. And in this trade, reputation is built on how relationships end, not on how they start.