OLIVA_JS / Services

Services — Full-stack web development, MVPs and consulting

Okay Matteo Peroni aka oliva_js, so what services do you actually offer?

I’d say the simplest way to put it is this: I help companies and startups turn an idea or a need into a working web application.

In practice I take care of the entire technical side of the project: from architecture design to actual development, both frontend and backend, all the way to deploying the app online.

Depending on the situation I can step in in different ways.

Sometimes I build the application almost from scratch, other times I join existing projects to provide technical support, advise on the architecture or help the team make the right technical decisions.

Tell me, what kind of applications do you usually build?

I’ve pretty much done a bit of everything:

  • management tools, internal dashboards, web platforms
  • MVPs for startups
  • SaaS products
  • integrations between systems
  • marketing / presentation websites

In terms of size I usually work on small to medium-sized applications, which is also my favourite target because that’s where I can bring the most value by handling all (or most) of the technical work.

So do you handle the whole development process or just parts of it?

The whole thing <3.

My goal has always been to work as a full‑stack developer so I can understand and build in both worlds, frontend and backend.

Over time my skills have extended to the architectural and technical decision-making side which, to be honest, is the part that currently gives me the most satisfaction.

For these reasons, if I had to define my role, it would be Full‑stack engineer: a technical profile that, beyond full‑stack development, is also able to design the whole architecture of the application.

In what kind of situations should a company reach out to you?

Usually people call me when they need someone to take care of the technical side without having to build a whole team of developers, or when they want to keep the team lean without redundant roles.

For example:

  • when a startup wants to build an MVP to validate a product idea
  • when a company wants to create a web app or an internal tool to digitalise a process
  • when an existing project needs a clearer technical direction
  • or when a team needs a full‑stack developer who can work on both the frontend and the backend

In general I step in when you need someone who doesn’t just write code, but can also design the technical solution and move development forward quite autonomously.

How does a typical collaboration with you work?

When there are the right conditions for a good collaboration, my ideal workflow is roughly split into these phases:

  1. Analysis

    We analyse the development request or the problem to be solved, talking openly and clearly.
    If there are limitations or critical issues, I prefer to put them on the table right away so we can discuss them and avoid unpleasant surprises later.

  2. Design

    We design the database, the architecture and the technologies that will be used for development, also defining the cost of any additional services or subscriptions.
    I like to produce documents that summarise all of this so we can share them with the rest of the team and with the client, making sure everyone is clear on what we’re going to work on.

  3. Development

    I develop the solution on both the backend and the frontend using the technologies chosen earlier.
    In this phase I find it (personal opinion) counterproductive to give 100 status updates a day, because it just eats into the time needed to actually ship.
    I’ve found it much more effective to give feedback whenever a feature is completed: this way development stays fast and the meetings/calls we have are meaningful and not a waste of time.
    Obviously, to make this work you need a solid design phase beforehand.

  4. Release

    Release of the application (this is the moment where everyone says “Yeeeeeeeee”).
    Also here, based on the needs discussed during the design phase, we decide where it’s best to host the application.

Last thing: why should a company choose you?

I’d say because I’m used to managing a web project in a pretty complete way, not only from a development point of view but also on the planning and architecture side.

I’ve noticed that for many companies it’s convenient because instead of coordinating multiple technical roles, they can have a single person taking care of the architecture, development and the main technical decisions.

Of course, when needed I’m happy to collaborate with other developers or with the internal team, but I’m also able to carry a project forward independently without creating too much organisational overhead.

And finally because I enjoy building things, as long as they’re technically solid.