Since 2009 we've built software on solid foundations, so it can grow and evolve for years.
We're a small digital studio that sees every project from the first idea through its evolution.
Every stage is incremental and ends with something concrete you can see and use right away.
We believe the best software is the kind designed to still be growing ten years from now.
Our work with the Corpo Nazionale dei Vigili del Fuoco, Italy's national fire and rescue service, began in 2021, getting its portal ready for production. Over the years it has extended to the Corps' local branches: today the local Commands and the sports activities office each run their own minisite, with independent editorial teams we trained.
Flexform is a furniture company founded in Brianza in 1959, now in the third generation of the founding family. We've worked together since 2016 and have built two generations of their portal: the first stayed online until 2023, the second is the one we work on today.
You can even start with an idea that still needs refining. Before writing any code, we’ll work with you to understand what you and the software’s users need, and if we’re not convinced by a particular choice, we’ll let you know – to protect your investment.
Work is split into milestones, planned on a roadmap that is kept up to date as the project evolves. With every delivery you receive a snapshot of it, with the next milestones, and you can ask for it at any time. During development you have your own test environments, where you can check each increment as it arrives.
Every project runs through a Continuous Integration and Delivery pipeline. The pace depends on the project: on a live platform, we usually release new features every three weeks, often with no downtime.
When the software goes into production, the work carries on. Maintenance and ongoing development are part of the project, and they're what keep software useful for years.
We wanted a company where the people who make decisions about a project actually work on it. Instead of layers of management, we have clear, shared responsibilities.
There are twelve of us, working as one team. On every project the Client Manager is responsible for your priorities, the Delivery Manager for the roadmap and deliveries, and the Tech Lead for the technical choices. You can talk directly to all of them.
Claudia Astazi and Daniele Piaggesi founded bmeme in 2009. Today Claudia is our CEO and Daniele our System Architect.
Five of us joined between 2011 and 2015 and are still here. We built the method we use today together, one retrospective at a time.
Drupal, Monolitich, Operations, Continuous Integration
In 2022 we started with an assessment, the analysis we use to check whether a portal can keep growing on its current foundations. It gave a red light, so we rebuilt the portal, keeping the previously approved design. It has been live since 2024.
Drupal, Next.js, Decoupled, Continuous Integration
In 2022 digital was becoming central to Flexform's work, and the portal needed new tools. The choice: content on Drupal, with the frontend rebuilt in Next.js. Since 2023 the portal has grown every year, with new features for users and retailers.
Strapi, Next.js, Decoupled, Continuous Integration, UX & UI
We're Drupal specialists, and for Vivo Concerti we advised against it: their editorial team needed a lighter CMS that suited its work. Strapi manages the content, while Next.js, running separately, renders the pages and handles the high traffic.
Between 2011 and 2017 we helped organise five editions of the Italian Drupal Day, and since 2025 we've been among the organisers of DrupalCamp Italy.
In 2025 we showed how to use Schema.org to make content understandable to generative AI engines. In 2026 we're giving two talks: one on incremental migration, the other on building accessibility into development work.
On drupal.org we maintain or support twelve modules, including Breadcrumb Manager and HTTP Client Manager, and we've contributed to two security advisories.
Page Delivery grew out of our incremental migration projects, and we're releasing it as open source at DrupalCamp Italy 2026.
We've worked with Drupal since 2010. We build new projects, take existing ones further and handle version upgrades. When a portal isn't working as it should, we start with an assessment to understand where to step in.
Separating content from the frontend pays off when the frontend is slowing your work down, and the first thing we check is whether that's your case. If it is, content stays in Drupal or another CMS and the frontend moves to Next.js, even one section at a time with the Strangler Fig Pattern. From then on, a frontend-only change can be released without touching the rest.
If you don't need it, we'll be the first to tell you.
We help you understand what your users need, through research and clickable prototypes. Then we build a Design System integrated into the frontend, which keeps your applications consistent as they grow over the years.
We describe infrastructure as code and automate builds, tests and releases, with development and staging environments as close as possible to production.
We design cloud native platforms and size them for production, so they can be scaled up when needed and restored quickly after an error. With Blue/Green deployments, a new version only receives traffic once it has been checked, without interrupting the service.
Tell us what you have in mind, even if it’s only an idea