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.
About
Two founders, one project followed from start to finish.
Leonardo Oliva and Volha Yakubouskaya lead architecture, development and UX. We are remote-first with an operating base in Rome and work across Italy and Europe.
Studio
Who works on your project.
Two founders, one workflow: strategy, UX and code with no handoffs between departments. Clear ownership from brief to go-live.
RomeOperating base
7Documented case studies
6Available languages
2Founders on the project
The portfolio includes H501 Barber, Il Panzerotto Chic, Di Nezza Moto, Amministrazione Capalbo and S.C. Gioielli.
Leonardo Oliva
Founder & lead developerArchitecture, development and product logic: Next.js, TypeScript, backend, databases and infrastructure, with a focus on performance, security and technical SEO. He built the management tools, PWAs and websites in our published case studies.
A product works when it makes a previously scattered flow feel simple.
Volha Yakubouskaya
Founder & UX leadFlows, prototypes and interfaces: user research, design systems and B2B UX. She turns operational processes into clear screens for teams that use them every day.
Every screen should make clear what matters and what to do next.
What this means for the client
- You talk to who designs and builds, not an account relaying tickets.
- Fast decisions on architecture, design and priorities; fixed quote and dates in the contract.
- Same team from workshop to go-live; maintenance and support stay available when agreed.
- Code, repository, access and design-system delivery are defined in the contract; third-party services retain their own terms.
How we work
We start from the operational problem, map workflows, design the interface and use Next.js and TypeScript when they fit the product. We verify performance, technical SEO and structured data before launch. Each portfolio entry states what is public, reserved or supported by documented evidence.
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 clear decision-maker: before starting, we agree who approves content, functions and revisions.
- 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
Our operating base is Rome, with no public-facing office. Work runs remotely through video calls and shared documents so decisions, revisions and responsibilities remain traceable.
When a site visit or in-person presentation is useful to the project, it can be arranged in Rome by appointment.
- 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
- Any in-person meeting or travel is agreed before it is added to the scope
Why Next.js and TypeScript, and not something else
We use Next.js and TypeScript where the project benefits from server rendering, reusable components and a shared foundation between website and application. TypeScript helps catch some errors during development, but does not replace tests or monitoring.
The technical choice is explained in the quote and depends on functions, content, integrations, maintenance and the skills that will support the project over time.