Management dashboards, client portals, CRMs, SaaS and B2B configurators. Custom web apps in React, Node.js and PostgreSQL. From Perugia to all of Italy.
From € 850 · React + Node.js
// In short
I develop custom web apps with React and Node.js: management dashboards, client portals, CRMs, B2B configurators and booking systems. An MVP with one or two core features starts at €850 and usually takes 4–6 weeks; an app with several modules and integrations takes 8–14 weeks.
90% of companies don't need custom development — they need to make better use of existing tools. But if you fall into one of these cases, then yes: a custom web app changes the game.
// If you're not sure which case you fall into, the intro call is free — figuring it out together is the first step.
Your team gets requests by email, copies them into a spreadsheet, updates another file and sends a confirmation by hand. Hours wasted every day. An internal web app automates every step — from intake to notification — freeing your team from low-value work and cutting human error almost to zero.
You've spotted a problem that keeps recurring in a specific industry and want to build a tool to solve it — and maybe sell it as a subscription. We build a solid, working MVP: enough to validate, enough to gather your first users, enough to see whether it's worth scaling before investing more.
Your clients write to ask where their order is, to download an invoice, to send a document. A custom private area solves it all automatically: each client logs into their space, sees exactly what they need and you stop answering the same email ten times a day.
You're paying an expensive licence for software you use 70% of and curse the other 30%. Or you use a system so old nobody knows how to update it anymore. A custom application built on your real processes — not the ones imagined by whoever wrote the software in 2008 — completely changes your team's productivity.
Every web app I deliver is production-ready from day one: secure authentication, persistent data, a usable interface, maintainable code.
First I design the flows and validate them with you, then I build. No developer writes useful code without understanding who will use it and in what context. Clear dashboards, smart forms, zero cognitive overhead.
Secure login with JWT or sessions, granular roles and permissions (admin, operator, client), social OAuth if needed, optional 2FA. Every user sees only what they should.
PostgreSQL, MySQL or MongoDB depending on the needs. A schema designed to last: correct relations, indexes for frequent queries, automatic backups. Your data is safe and accessible in milliseconds.
A structured backend with clear, documented and tested endpoints. You can connect the app to any existing system — management software, CRM, payment gateways, third-party services — via webhooks or dedicated APIs.
Server-side rendering with Next.js where needed, lazy loading, strategic caching, optimised queries. The app is fast with 10 users and stays fast with 10,000. An architecture built to grow with you.
Transactional emails, web push notifications, webhooks for automatic triggers. When an order changes status, a document is uploaded or a deadline approaches — the app alerts the right people at the right time.
Mandatory HTTPS, sanitised input, XSS and CSRF protection, rate limiting on sensitive endpoints, server-side validation. Security isn't an add-on — it's part of the architecture from the first commit.
The app works on desktop, tablet and mobile. Tested on Chrome, Firefox, Safari and Edge. No "desktop only" — your team and your clients use every device.
I write code as if another developer had to read it tomorrow — because they probably will. Reusable components, clear naming, logic separated from presentation. I don't hand you an opaque monolith.
// TYPICAL ARCHITECTURE — FULL-STACK WEB APP
The stack is chosen for the specific project — I don't always use the same tools, I use the right ones. TypeScript almost always, because runtime bugs are no fun.
A custom web app makes sense in almost every industry — what changes is the problem to solve. Here are some areas where I've worked the most.
Before writing a line of code, I take time to understand your real process. Who uses it, in what context, where it breaks, what it must produce. Too many apps are built on an imagined solution — good ones are built on the real problem.
I design the user flows and wireframes of the main screens before touching code. I define the database schema and API architecture. I show you everything and we gather feedback — changing a wireframe costs hours, changing badly written code costs weeks.
I don't vanish for three months and reappear with a finished app. I work in iterations: every week you have a working version on staging to test. Problems surface early — when they're still easy to fix — not at the last second before launch.
Full functional tests, load tests on critical endpoints, a security review. Deployment on scalable infrastructure with automatic CI/CD. Then training for your team and technical documentation — the app is yours, you need to understand how it works.
Project scenarios: realistic examples built on the work I do most often. They don't name clients or report results — they show how I work.
Attendance, leave, reviews and reports in one place, with role-based permissions and fewer spreadsheets to chase.
Customers and sales reps configure the product, see the price on their price list and download the quote as a PDF, with no email back-and-forth.
Several specialists’ schedules online, automatic reminders and a patient area, with health data handled with great care.
Web apps vary a lot by nature — complexity depends on the number of modules, users and integrations. These are indicative ranges: after the call I send you a precise estimate.
Single-purpose app or MVP to validate an idea. Ideal for early-stage startups.
Complete app with multiple modules, roles, notifications and external integrations.
Complex multi-tenant platform, SaaS or replacement of articulated management software.
A website presents information — who you are, what you do, how to contact you. A web app is a tool: it does things, processes data, reacts to user actions, stores information over time. In practice: your company's site is a website. The system your employees use to log hours, or your clients use to access their orders, is a web app. The difference isn't aesthetic — it's functional. If you need someone to do something (not just read), you probably need a web app.
It depends on complexity. An MVP with 1–2 core features: 4–6 weeks. An app with authentication, several modules and external integrations: 8–14 weeks. An articulated platform with complex business logic: 4–6 months. The discovery and design phase (the first 1–2 weeks) is what most determines whether the project runs smoothly. Apps that "slip" almost always slip because the requirements weren't clear at the start — not because writing code is slow.
The data is yours. We host it on European servers (Vercel, Railway, Hetzner or AWS EU depending on the project), with automatic daily backups. The database is protected from unauthorised access, communications are encrypted via HTTPS and sensitive data is always hashed. If you have specific GDPR obligations (almost everyone does), I build the app to be compliant from the start: consents, right to be forgotten, access logs. I also hand over the documentation your DPO needs.
Yes, and that's the right way to work. We build the essential version (MVP), use it in the real world, see what works and what's missing, and add. I always architect apps modularly for exactly this reason: adding a new module doesn't mean rewriting everything. Usually we work with a monthly evolutionary maintenance contract or periodic development sprints — we decide together which formula suits your organisation best.
Almost always, yes. Most modern software (CRMs, management systems, accounting platforms, communication tools) exposes an API or webhook for exchanging data. HubSpot, Salesforce, Fattura24, TeamSystem, Slack, Google Workspace, Microsoft 365, Stripe, Twilio for SMS — if they have an API, I can integrate them. For very old or proprietary software without an API, we assess case by case: sometimes we work through automated CSV/Excel, sometimes we build a custom adapter.
The first month of post-launch support is included in every package: bug fixing, adjustments, questions about the code. After the first month, I offer a monthly maintenance contract that includes infrastructure monitoring, dependency security updates, verified backups and a number of development hours for small changes. If the project grows, we can move to an ongoing collaboration — many clients prefer a stable technical point of reference rather than changing developer every time.
I'm based in Perugia but develop web apps for businesses and professionals across Umbria: Perugia, Terni, Foligno, Spoleto, Assisi, Gubbio, Città di Castello, Umbertide, Orvieto, Narni, Amelia, Bastia Umbra, Corciano, Marsciano, Deruta, Castiglione del Lago, Norcia and every other town in the region.
90% of the work happens remotely — which means I work with clients all over Italy with no geographical limits. Discovery sessions, interim feedback and demos happen on calls: distance changes nothing about the quality of the final product.
Requests today
First call is free. You describe the process, I tell you whether it makes sense to build an app on it, how long it takes and how much it costs.
Your data stays between us. No newsletter, no spam.
I'll reply personally within 24h. In the meantime… I'll start making the coffee.
