Modernisation and continuity
Best fit for existing platforms that need to evolve without a risky rewrite. Upgrades, refactoring, migrations and maintenance work best when continuity matters as much as new functionality.
Independent software consultancy
Reflab helps organisations clarify the direction, then builds and maintains web systems, editorial platforms and custom applications with senior ownership, long-term continuity and choices that keep clients in control.
Services
We work best on existing systems that already carry complexity: editorial platforms, intranets, knowledge bases, migrations and technical continuity work where reliability matters as much as new functionality.
Best fit for existing platforms that need to evolve without a risky rewrite. Upgrades, refactoring, migrations and maintenance work best when continuity matters as much as new functionality.
Particularly relevant when a CMS carries permissions, security requirements, workflows and organisational complexity. This is often the case with intranets, knowledge bases and content-heavy platforms.
A good fit for platforms that have to connect systems, support real operations and stay understandable over time. This includes custom web applications, back-office tools and Linux server administration for clients who want us to take care of hosting as well.
Most valuable when AI can improve a real workflow: knowledge access, editorial support, internal assistants, classification, search augmentation and structured automation.
Expertise
Our strongest capabilities come from long-term systems work: Python across Django, Flask and FastAPI for evolving applications, Plone for complex CMS projects, pragmatic interfaces built for maintainability, and LLM integrations treated as engineering work.
We use Python to take existing systems forward, from long-running Django applications to leaner services built with Flask or FastAPI: application logic, APIs, integrations and business workflows designed to evolve cleanly over time.
Plone is a genuine specialist capability for Reflab. We are strongest where permissions, security, workflow and content governance turn a CMS into a technical system, especially in intranets and knowledge bases.
We prefer simple, maintainable front ends over unnecessary framework complexity. In many of our projects, vanilla JavaScript, careful UX decisions and solid integration work are the right tools.
We treat LLM-based features as engineering problems: data boundaries, evaluation, orchestration, failure modes and the product decisions needed to make them useful in production.
A few examples of the kind of platforms, constraints, and long-term responsibilities we have worked with.
These examples are intentionally described with some discretion. In many cases, we worked as a senior technical partner within a broader delivery context. The point is not client-name signalling, but the type of complexity, continuity, and judgement involved.
Consumer brand
We supported the digital evolution of this client for roughly ten years, across multiple connected systems that grew alongside the business itself.
The work began in the mid-2000s, when the company’s web presence was still limited, and first focused on bringing the full product catalogue online for retailers. Over time, this expanded to include a store locator for end customers and a B2B ecommerce platform for wholesale ordering.
One of the most formative phases came with the move from printed sales catalogues to digitally managed catalogues for iPad, built with web technologies and Apache Cordova. The catalogues had to work offline, remain easy to use for sales agents, and support frequent updates to handle corrections, product changes, and newly released lines.
Our role covered analysis, development, maintenance, and coordination. An important part of the work was making the transition practical for the people involved: understanding the needs of the sales network, reducing friction around a new mode of work, and helping the internal design team move from print-first production toward digital delivery without forcing a disruptive change in tools.
International non-profit
For nearly fifteen years, we helped design and evolve an internal platform used by distributed teams across multiple countries to access documents, operational information, and shared knowledge in their daily work.
The project began by moving away from a legacy CMS that had become difficult to use and extend. Plone played a central role in shaping a more sustainable platform, especially around content structure, usability, permissions and long-term governance. Over time, the system grew into a broader knowledge environment, including restricted workspaces for smaller groups, reserved document areas, and additional collaboration and communication features.
In parallel, we also worked on an offline knowledge solution for contexts where internet access could be absent or unstable, while information still needed regular updates. Some of the technical experience built in other offline-first projects carried over, but here it was applied in a very different operational setting.
Our role included analysis, development, maintenance, and coordination in an international environment, with stakeholders across Europe and beyond, and collaboration conducted in English throughout.
Enterprise software company
We have been working with this client since around 2006, supporting the long-term evolution of its digital platform ecosystem as the company grew from a smaller software business into a much larger international organisation.
The relationship began with the corporate website, developed in close collaboration with marketing stakeholders. Across multiple redesigns and platform evolutions, it became a professional multilingual content environment with a large volume of pages, videos, and marketing integrations. A central goal was to make the editorial team increasingly autonomous in creating pages and managing content without routine developer intervention.
A later and particularly important phase was the creation of a dedicated customer and internal community platform. This became a central environment for product knowledge, restricted materials, and content serving different functions such as sales, marketing, product, and legal. Over time, it grew to include complementary tools such as Stack Overflow-style Q&A areas, a customer and project database, and integrations with external services through SAML2-based identity flows and a dedicated identity provider.
The original corporate site was eventually absorbed after acquisition, while the community platform remains actively used today. Throughout the work, Plone remained a key foundation, complemented over time by lighter service-oriented components where they made architectural sense.
Public healthcare organisation
Since around 2016, we have led the technical evolution of a large public-sector healthcare platform, working alongside a partner responsible for the commercial relationship.
The starting point was a legacy site already built on an older Plone stack by previous suppliers. Our work focused on evolving that foundation into a more modern architecture based on multiple services, still using Plone where appropriate but not limited to it, and bringing the experience together through a custom frontend aligned with Italian public-sector standards for accessibility and usability.
The platform supports a wide range of public-facing information and service access patterns, including advanced search and structured discovery for tenders, services, institutional events, and user-oriented information. From the same technical direction, additional satellite platforms were developed for more specialised internal audiences, and the same approach is now being extended to the organisation’s broader staff intranet.
Our role has been fully technical throughout: analysis, development, maintenance, and architectural direction.
The common thread across these engagements is not the sector, but the responsibility involved: long-lived platforms, real operational constraints, and the need to evolve without breaking what already matters.
People
Reflab is led by Francesco Merlo and Riccardo Lemmi.
Clients work directly with the people responsible for the work itself, not through a delivery chain assembled after the contract is signed. That keeps context intact, decisions closer to the platform, and collaboration more accountable over time.
When additional people are involved, the goal is not to add layers for appearance. It is to extend the same standards of responsibility, technical care, and continuity that define the core of the company.
Approach
Reflab works best as a partner: clear in communication, practical in technical judgement, and focused on solutions that stay maintainable and under the client's control.
A defined piece of work should not need constant supervision. We take ownership, communicate clearly and deliver what we commit to.
We prefer working relationships where technical judgement is shared, feedback is direct and decisions are made in the interest of the project, not by rigid role separation.
We favour open-source foundations, vendor-neutral choices and client-controlled hosting when that reduces lock-in and keeps a platform portable, operable and resilient over time.
We prefer incremental work, visible progress and realistic expectations. Micromanagement and inflated scope slow projects down; trust, clarity and room for technical judgement move them forward.
Company
Reflab was founded in 2003. Over more than two decades we have worked on websites, intranets, editorial platforms, digital services and custom Python applications for organisations that needed software to remain useful over time.
That history matters because it reflects the kind of company Reflab is: small, senior, and built for platforms that need continuity, careful judgement, and dependable technical direction over time.
What this experience is for
Some projects need clarity before more code is written. Others need a defined piece of work handled with autonomy, care and consistent communication.
Some relationships have lasted well over a decade. That continuity comes from practical delivery, consistent communication and technical judgement that stays close to the work.
Contact
If you need a technically credible partner for a web platform, a CMS-heavy project, a Python codebase or a careful LLM-enabled feature set, we can help frame the work and take ownership of execution.
General contact
Certified email
Registered office
Via della Pace, 1
56021 Cascina (PI)
Italy
Company details
Reflab s.r.l.
P.IVA 01783920505