DesignDigital product design studio vs web agency in Italy: what differs
Italy's ICT sector counts 132,832 companies, so the label proves nothing. Eight axes, four call checks, and where a web agency is the better buy.
A digital product goes out to tender in Italy and two kinds of supplier answer the brief. One calls itself a studio di progettazione prodotti digitali, a digital product design studio. One calls itself a web agency. The quotes look comparable and the scope sections read almost the same. The difference surfaces four months later, when someone has to decide what the third user role sees on a screen nobody drew.
A digital product design studio designs and builds software that people use repeatedly: accounts, roles, permissions, states, a data model, a roadmap that continues after release. A web agency designs and runs a company's digital presence: site, e-commerce, content, campaigns, visibility. Both are real crafts with real specialists. They answer different questions, and the label on the proposal is the least reliable way to tell which one is on the other side of the table.
Which one fits the project?
The test is what the money buys. A product design studio fits when the deliverable has users who come back, roles that see different things, a schema somebody will live with for years, and a version 2 already implied by version 1. A web agency fits when the deliverable has visitors who arrive, read, convert and leave: a marketing site, a catalogue, a content programme, an acquisition budget to spend well.
Mixed briefs are the common case. When a product carries a marketing site alongside it, the product decides the supplier and the site becomes a small piece of the same engagement. When a marketing site carries a form and a login for three internal users, the site decides, and paying product rates for it is waste.
Why the label tells an Italian buyer so little
Italy's digital market reached 84.4 billion euros in 2025, up 3.4 percent year on year, spread across 132,832 companies and 638,150 employees, according to the Anitec-Assinform report Il Digitale in Italia 2026, presented at the Chamber of Deputies on 1 July 2026. Growth ran ahead of national GDP, with ICT services at 18.8 billion euros and software at 9.8 billion (Teleborsa, September 2026).
A sector that fragmented produces every available label: web agency, digital agency, software house, studio, boutique, lab. A forty-person web agency can hold a stronger product team than a three-person firm that calls itself a product studio, and the reverse happens just as often. The word is a hypothesis. The verification happens in the first call.
Listen to the questions. A product team asks who the users are, what they do on day 30, which roles exist, what the data model has to hold, what happens when a payment fails or a subscription lapses mid-cycle. A presence team asks who the audience is, what the message is, which channels carry it, what the conversion target is and what the media budget is worth. Both sets are correct, each for its own craft. The set that arrives says which craft answered.
The axes where the two diverge
- Unit of work. A studio ships a flow with all of its states, an agency a page with its content.
- Success metric. On one side activation, retention, task completion, support tickets avoided. On the other sessions, leads, conversion rate, cost per acquisition.
- What gets handed over. Running software plus the system it is made of: components, tokens, tests, a deploy pipeline. From an agency, the site plus the content and channels around it.
- Team shape. Designers and engineers in one loop, often two or three people in total. An agency carries a wider bench: strategy, design, front-end, SEO, copy, media buying.
- Engagement shape. Sprints or a monthly retainer against a roadmap, against a fixed-scope project followed by hosting and maintenance.
- Life after release. For a product the backlog is the work and release one is the start. For a site the launch is the finish line, and later changes become requests against a maintenance contract.
- Code. A repository the client owns, with tests and repeatable deploys. Or a CMS install with a theme and plugins, which is the right answer for a site and the wrong one for a product.
- Accessibility. Solved once inside the components and inherited by every screen, or solved template by template, page by page.
Where a product design studio earns its price
Roles and permissions, edge cases included
Software with three roles has more than three screens. An admin who suspends an account mid-billing-cycle, an editor who loses a permission with a draft open, a viewer invited to a workspace that has since been deleted: each one is a state that needs a decision and a screen. A studio quotes them. A quote shaped like a site rarely contains them, because a site rarely has them.
A design system that lasts until version 3
A product that grows adds interfaces faster than it adds people. Keeping it coherent takes a small set of components and tokens treated as a company asset, not a style guide in a PDF. That is a build order, and it is cheaper early: our breakdown of the seven categories and the order to build them in holds for a team of two as much as for twenty.
The states nobody puts in a quote
Empty, loading, partial, expired, error, offline, first run. This is where products lose the users they already paid to acquire, and it is the cheapest thing to decide on paper and the most expensive to retrofit. The onboarding patterns that cut first-week churn are made almost entirely of these states.
Compliance that lives in the components
Since 28 June 2025, Italy applies legislative decree 82/2022 in full, the transposition of EU directive 2019/882, the European Accessibility Act. Digital accessibility duties leave the public administration perimeter and reach private operators selling products and services through digital channels, with an exemption for microenterprises under 10 employees and under 2 million euros of turnover. The technical reference is EN 301 549, which points at WCAG 2.1 level AA, and AgID has put its own service guidelines out for consultation. In a product that requirement is solved once inside a component library and every screen inherits it. In a site built template by template it is solved page by page, every time. We wrote the product-side version in accessibility-first design after the EU Accessibility Act.
Design and engineering in the same loop
The separation between the two crafts is closing. In Figma's 2026 AI report, built on 8,403 survey responses and 639 interviews across ten markets, the share of designers taking part in development doubled in a year to 41 percent, and developers doing design work rose from 44 to 60 percent. Ninety percent of respondents building AI-powered products said design matters at least as much as before, and 57 percent said it matters more. A studio organised as one loop absorbs that shift without handoff documents. A chain with one vendor for design and another for development pays for the handoff twice.
Where a web agency is the better buy
Three cases, stated plainly.
- Content and visibility at volume. Editorial calendars, content in several languages, SEO programmes, technical SEO on large catalogues. This is a discipline with its own specialists and its own tooling, and a two-person product studio has no bench for it.
- Platform e-commerce. A catalogue on Shopify, WooCommerce or Prestashop with payments, shipping rules and marketplace feeds is a solved problem with well-paved roads. Building it as custom software spends money on something already solved.
- Paid media and local presence. Search and social buying, creative production at campaign cadence, local listings, landing pages by the dozen. A product studio that claims this alongside product work is claiming a second craft.
There is a fourth: multi-site programmes, where ten sites want the same template and different content. That takes production management, and agencies are built for it.
Four checks that settle it in one call
- Ask for the states of one screen. Take the most important screen in the brief and ask what it shows with no data, while data loads, when a permission is missing, when the request fails. The answer is either a list or an improvisation.
- Ask who owns the repository and how a deploy happens. Product work implies a repository the client owns, reviewed changes, and deploys that can be repeated and rolled back. If the answer is an FTP client, the supplier is built for sites.
- Ask what month one after release looks like. A product answer describes a backlog, a cadence, and what the first usage data will change. A site answer describes a maintenance plan. Both are valid, and they cost differently.
- Ask which part of the accessibility duty is theirs. A supplier quoting an Italian digital service in 2026 who cannot name EN 301 549 or WCAG 2.1 AA has not read the file.
Comparing the two quotes
Quotes from the two categories are rarely comparable, and the gap is structural more than commercial. A site quote prices a finished artefact. A product quote prices a first release plus the machinery to keep changing it, which is why it carries lines a site has no reason to carry: discovery, a component library, test coverage, observability, a retainer. Stripping those lines to get closer to the lower number moves the cost to month six. Our figures for both stages sit in what a discovery phase should cost and what a SaaS build costs by scope.
One more asymmetry is worth naming. A web agency is paid to bring people towards a thing. A product studio is paid for what happens once they arrive. A company that needs both and buys one will feel the missing half within a quarter, and deciding which half is urgent costs less than looking for a supplier who claims the whole surface.
How we work
We are a studio: we design and build SaaS, web apps and the systems around them, with design and engineering in the same loop and a roadmap that continues after the first release. We do not run paid media programmes, and we say so on the first call rather than in month three. When a brief is really a marketing site with a contact form, an agency will do it faster and for less, and that is the right recommendation to give. The procurement side of the same decision is in choosing a SaaS development agency in Italy.
Sources
- Anitec-Assinform, Il Digitale in Italia 2026 (report, PDF)
- Teleborsa, Digitale italiano a 84,4 miliardi, ma resta divario con PMI
- Directive (EU) 2019/882, European Accessibility Act
- Decreto legislativo 27 maggio 2022, n. 82 (Normattiva)
- ETSI EN 301 549 v3.2.1, accessibility requirements for ICT
- W3C, Web Content Accessibility Guidelines 2.1
- AgID, EAA service accessibility guidelines in consultation
- Figma, 2026 AI report
Frequently asked questions
The words overlap and the emphasis differs. In Italian usage, software house usually signals custom development capacity: backend, integrations, a team allocated per project. Studio usually signals design and engineering inside one small team, with product decisions in scope rather than received as a specification. Neither word is regulated, so the check is the same in both cases: ask who designs the screens, who writes the code, and whether the two talk daily or exchange files.
Some can, and the ones that can tend to hold a product team inside them, with its own lead, its own repository practices and its own retainer model. The failure case is a presence-shaped team quoting a product with a site process: fixed scope, launch as the finish line, no line item for the states of a screen. Two questions separate them quickly. Ask for a SaaS they still maintain today, and ask who handles a breaking change in month eight.
Since 28 June 2025, legislative decree 82/2022 applies in full and extends accessibility duties to private operators offering products and services through digital channels, with an exemption for microenterprises under 10 employees and under 2 million euros of turnover. The technical reference is EN 301 549, which points at WCAG 2.1 level AA, and AgID has published its service guidelines for consultation. For a product team the practical consequence is where the work sits: accessibility belongs in the component library, fixed once, rather than in each screen separately.
Normalise the scope before looking at the price. Write down the states of the three most important screens, the roles, the cadence after release and who owns the repository, then ask both suppliers to price that same list. Quotes that differ by half usually differ because one of them carries no line for discovery, tests or the months after launch. The lower number is often the same work with its second half deferred to a date nobody has budgeted yet.
Related services
Related articles
Design
DesignBrand motion design: how one easing curve sets a product's tone
Material 3 eases on cubic-bezier(0.2, 0, 0, 1), Carbon splits productive from expressive. How to pick one signature curve, test it and ship it as tokens.
Design