Our company

A technical company, not a generic agency.

Nordev is a development company based in Treviso, Italy. We exist to put different skills in the same room — web, systems, engineering, electronics, and finance — and use them for businesses that need their digital systems to actually work.

We mainly work with SMEs, especially manufacturers in North-Eastern Italy, and we stay open to clients elsewhere. We are not freelancers and not a generalist agency. We are a small technical team that would rather understand the problem before proposing a tool.

Why we exist

Four people, one concrete reason.

Nordev was not founded to sell software. It was founded to make the skills of its members available to small and medium-sized businesses that need to build, connect, or improve their digital systems.

In too many companies, digital still means spreadsheets, disconnected tools, and work done in fragments. We already had different crafts. We chose to practice them together, so a client can talk to people who understand both the technical side and the business constraint.

How we work

A practical path, not a script.

01

Understand

We start with the business: processes, systems already in place, constraints, and what is actually needed. Problem first, technology second.

02

Design

We look for the simplest solution that holds. Few parts, clear ones, extendable later if needed.

03

Build

We develop with quality, performance, security, and maintainability in mind. The code should still be readable after handover.

04

Integrate

We connect the new work to the tools, data, and processes the company already uses. No unused islands.

05

Evolve

We stay when the business changes. A useful system is one that can grow.

Principles

Four things we will not drop.

  • Understand

    We start from the problem, not from the technology. If we have not understood the need, we are not ready to build.

  • Simplify

    We follow KISS: Keep It Simple, Stupid. We prefer modular, configurable solutions over systems stuffed with unused features.

  • Build well

    Performance, clean architecture, security, testing, scalability, and maintainability. Technical quality has to create value for the client, not complexity for us.

  • Grow together

    We look for long relationships. A technical partner stays. They do not vanish after go-live.

Technical quality

Technical quality first.

Good technology should remain useful after the project is delivered.

Quality is not only writing code. It is making the system fast, orderly, secure, and sustainable — including when we are no longer in the room.

  • Fast, efficient systems
  • Clean, structured architecture
  • Security
  • Scalability
  • Automated and manual testing where it matters
  • Maintainability
  • Reliable integrations
  • Precise delivery
  • Long-term sustainability

The team

Four perspectives, one company.

Nordev combines different views: systems, interface, back-end, and finance. A project gets read from the technical side and the business side.

  • Matteo

    CTO / Systems & technical architecture

    Infrastructure, integrations, long-term choices

    Designs how the pieces hold together: servers, networks, architecture, and the constraints a system must respect so it does not become fragile.

  • Federico

    Web developer / Front-end

    Interfaces, perceived performance, usability

    Builds what people use every day. A site or an app has to be clear, fast, and sustainable to maintain.

  • Enrico

    Web developer / Back-end

    Data, APIs, system integrations

    Works on the engine: logic, databases, and the links between tools a company already runs. The point is that data arrives where it is needed.

  • Luca

    Finance / Business operations

    Costs, priorities, economic sustainability

    Brings a financial and operational reading into the project. A solution has to stand up in the numbers, not only in the repository.

What we build

Systems that improve the work, not just the storefront.

This is not a second services catalogue. We build these systems because a company has to sell, produce, keep data aligned, and stop wasting time on manual steps.

  • Web applications

    Internal tools and digital products the company works in every day.

  • Mobile applications

    When the work happens away from a desk, not only on desktop.

  • CMS and management platforms

    Systems to update, organise, and govern content and processes.

  • ERP and business software

    Built around real processes, not a generic package.

  • Integrations

    Getting software that currently ignores each other to talk.

  • Automation

    Removing repetitive steps where a rule is more reliable than a tired person.

  • SEO and web performance

    Fast sites that search engines can read: engineering, not campaign talk.

Technical philosophy

Open where it helps. Modular always.

Open source

We gladly work on open, extensible ecosystems when the project justifies it. It is not a dogma: the right choice is the one that holds for the client, the constraint, and the timeline.

Modular solutions

We prefer systems that adapt through configuration and extensions, not monoliths packed with features nobody will use. Build what is needed. Keep what is useful. Avoid what is not.

Who we work with

Close to businesses, without drawing a fence.

Nordev is built first for SMEs: manufacturers and companies with systems already in place that need integration, modernisation, or automation.

North-Eastern Italy — Veneto, Friuli Venezia Giulia, and nearby — is where we work most and where we can stay close. That is a starting point, not a geographic limit.

Direction

Grow without losing what makes us useful.

We are small on purpose today. We want to grow: skills, capacity, the team, client relationships, and the size of the projects we can take on.

We do not want to grow into a distant agency. Direct relationships, technical quality, simplicity, trust, speed, and attention to the real need stay the measure. If we lose those, we grew the wrong way.

Have a system that needs putting in order?

Tell us the constraint, not the buzzword. You will hear back from us.