Web Development

The problem isn't digital, it's operational

If every piece of data passes through three people and four tools, the bottleneck doesn't disappear by itself.

• 01

  Scattered processes

  Excel, email and WhatsApp hold up while volume is low. Then come duplicates, different versions, lost attachments and decisions made on old data. Period.

• 02

  SaaS that don't talk

  You pay multiple platforms to do pieces of the same work. One books, one sends emails, one archives, one measures. The team becomes the human connector between disconnected tools.

• 03

  Customers waiting

  When the customer has to call to know case status, orders or documents, the system is already showing its limits. The information exists, but stays locked in the wrong place.

1. 01

   Custom web app

   Web applications built on the real process, not on a re-themed template. Operational area, data management, internal flows, notifications, roles and permissions: all designed to reduce manual steps and blind spots.

2. 02

   APIs and integrations

   I connect CRM, ERP, management systems, gateways, email providers and external platforms with REST or GraphQL APIs. No copy-paste between different panels: data goes in, goes out, and stays consistent.

3. 03

   Private client areas

   Login, roles, permissions, documents, cases, orders and progress status in a single reserved area. The customer sees what they need to see, the team stops answering the same questions repeatedly.

4. 04

   Live operational dashboards

   Dashboards with metrics, activities, queues, statuses and real-time data where they actually matter: production, sales, support, administration. Not 14 decorative charts, but panels for deciding what to do now.

5. 05

   Automations and AI

   Automations for notifications, follow-ups, document generation, request routing and AI chatbots connected to company data. The goal is to remove repetitive work, not add another toy to maintain.

6. 06

   Scalable architecture

   Modern stack with Next.js, Node, Postgres and services chosen with judgment. Readable code, modular structure, controlled deployment, logs and technical foundations that don't collapse as users and data grow.

1. 01

   Discovery call

   30 free minutes to understand the real need. I listen, ask questions, take notes. No cold quotes: I need to know what you're actually building first.

2. 02

   Quote

   Flat fee with clear scope, timeline and costs. No surprises: if something falls out of scope I tell you upfront, not when the invoice lands.

3. 03

   Design / Strategy

   Wireframes, moodboard or audit with action plan — depends on the service. You see the direction before any code or content gets touched.

4. 04

   Build

   Development, technical work or operational execution. Agreed check-ins along the way, none of that "let's sync end of month".

5. 05

   Launch & follow-up

   Go-live + 30 days of assistance included. Documentation, training if needed, and an open door for the small things later.

• 01

  Web Design

  If the app has real users, the interface has to cut steps, not decorate them.

• 02

  SEO & Visibility

  Public apps have to be readable by Google too, not just by logged-in users.

• 03

  Website maintenance

  After deployment you need logs, backups and ongoing technical responsibility.

• The questions I hear all the time.

• When do I need a custom web app instead of an off-the-shelf SaaS?+

  When real work no longer fits inside generic tools. If you use Calendly, sheets, CRM, email, WhatsApp and a separate management system to complete a single process, the problem isn't a desire for order: it's architecture. A custom web app makes sense when you want a single, controllable flow connected to your data.

  Can we integrate tools we already use?+

  Yes, if they expose APIs, webhooks, reliable exports or a decent technical way to communicate. CRM, ERP, payments, email, calendars, logistics platforms and external databases can be connected. But first we verify what each system actually allows, because many tools promise integrations and then leave only half-doors open.

  Can we build a client area with case status or orders?+

  Yes. It's one of the most sensible cases: the customer logs in, sees documents, progress, deadlines, orders, open requests and notifications. The internal team updates once and the information becomes visible where needed. Fewer calls, fewer duplicate emails, fewer "can you let me know where we stand?".

  What's the difference vs a WordPress site with plugins?+

  A site with plugins can be fine for simple content. But when you need roles, permissions, structured data, automations, APIs and operational dashboards, plugins become a fragile stack. Every update can break something, every extension adds dependencies, every workaround becomes technical debt. Here we build the system, we don't pile up stuff.

  How do you handle security, login and permissions?+

  They get designed before visible code. Roles, permissions, sessions, validations, logs, endpoint protection and data separation have to be in the architecture, not in a check added at the end. A private area isn't just a screen with a password: it's a clear technical boundary between users, data and allowed actions.

  What happens after launch?+

  After launch we look at the system as it works: logs, errors, response times, blocked steps, internal user requests, dirty data. Then we correct by priority. A business web app isn't a showcase to deliver and wave goodbye: it's an operational tool that has to be kept sharp.