This article focuses on the no-code movement, which offers the promise of a software creation democratization and more broadly of society. Here we will try to go beyond this deterministic technophile myth by adopting a co-evolutionary perspective to apprehend the recursive relationships between technical objects and organizational forms and specify the opportunities and constraints that carries these technologies in terms of quality of work and quality of life at work. The article is based on an exploratory study conducted in a consulting firm specializing in digital transformations that reflect important organizational changes following the integration of no-code tools: technical and creative professions are hybridizing, promoting intra- and inter-business collaborations. But if these organizational effects manage to be actualized within this company, it is also because the company represents a favorable social ground where organizational silos are voluntarily unstructured, management is barely present, and where the organization promotes the autonomy of employees. The example of this particular structure reveals the profound co-evolution of technical objects and organizational forms, which shape each other more than they are unilaterally determined. On the other hand, these positive organizational effects are also joined by other unwanted and destabilizing effects for the organization and the actors in place. The deployment of no-code platforms may first of all encounter the reluctance of developers that perceive these tools as a threat, compared to the power they traditionally have in the creation of software. The potential of reconfiguration of these tools disrupts business cultures and the games of actors in place. However, no-code tools are not available to everyone : they are primarily used by curious “hackers”, with a strong appetite for digital technology and a minimum of technical skills, with the risk of creating a division between designers and simple users. Moreover, the apparent ease of their use runs the risk of underestimating the complexity of no-code projects and so generating dysfunctional software products, as well as a sense of abandonment in work teams.