Founders and software development in Rome.

Why the name Lovy

Lovy joins the initials of Leonardo Oliva and Volha Yakubouskaya: L and V. The signature of the people who take the brief and write the code.

How we work

We start from the operational problem, not a template. We map real workflows, design the interface and build on Next.js and TypeScript. We measure Core Web Vitals, technical SEO and structured data from day one; we keep real products in production: every case study on this site is still in use. For multi-tenant management systems we use Hubia, our SaaS platform for salons and barbershops, as the base and adapt it to the client's process.

What we do not do

Saying it upfront saves both sides a pointless quote. Some work we turn down, because someone else does it better or cheaper than we would.

• WordPress or off-the-shelf theme builds: if that is the budget, a well-chosen template beats a custom project done in a hurry.
• Ongoing ad campaigns and social media management: we build the technical foundation, we do not run media buying.
• Projects with no single decision-maker: when every choice has to clear four people who do not talk to each other, timelines triple, and we say so first.
• Work on someone else's codebase without an audit first: we find out what is there before deciding whether to continue it or start over.

Why we work remotely, even with clients in Rome

The base is Rome and some clients are a few kilometres away, but the work happens almost entirely over video calls and shared tools. It is the mode that has produced better results.

An hour in a meeting room produces notes nobody rereads. Forty minutes on a shared screen produces a map, an updated prototype or a written decision. When meeting in person is the right call, for a site visit or a presentation to a board, we meet.

• Every decision stays written in a shared document, not in the memory of whoever was in the room
• You watch the project grow on a link, not through screenshots over email
• No travel costs loaded onto the quote

Why Next.js and TypeScript, and not something else

Next.js lets us ship fast pages without hand-tuning every one, and lets the same project grow from site to product without a rewrite. TypeScript catches at compile time a class of bugs the client would otherwise find in production.

The concrete consequence is that the products in our case studies are still online and still maintainable months later, on the stack they were born on. It is also why we can quote a fixed price: we know what each piece costs because we have built it several times.