Web software

Web tools tailored to what you do.

Software accessible directly from a browser, for you or your clients.
Designed to solve a concrete need.

You already use web software.

Webmail, a client portal, a booking tool, or a tracking dashboard — all of these run directly in a browser.

In a professional context, it’s the same idea : an online tool designed to make a specific task easier.

  • manage data or files,
  • administer a website or service,
  • equip a team with simple screens,
  • test an idea or lay the groundwork for an MVP.

That’s what we call web software. My role is to build useful, clear versions tailored to your real needs — not oversized platforms.

My skills

Functional side

  • forms and simple account management,
  • tables with search, sorting, and filters,
  • content creation / editing via a web interface,
  • restricted access after login (private areas, dashboards),
  • date, schedule, status, or booking management,
  • simple workflows : request → validation → email notification.

Technical side

  • REST APIs to read and write data,
  • authentication with tokens (JWT), sessions, and simple roles,
  • databases : creation, updates, and targeted queries,
  • automatic email sending (forms, confirmations),
  • image management (upload, replacement, deletion),
  • integration of external APIs when needed (auth, data, etc.).

The idea is to rely on well-mastered building blocks that can evolve if the tool is actually used.

Features already implemented

A selection of building blocks I’ve already implemented on real projects, which I can reuse or adapt depending on your needs.

  • authentication via external APIs (e.g. Steam OpenID, adaptable to Google OAuth, etc.),
  • team management, invitations, and simple roles,
  • server-side image upload and replacement,
  • tables with sorting, filters, and pagination,
  • booking or appointment scheduling systems,
  • dated event management (UTC, statuses, validation),
  • private user areas and restricted pages,
  • full CRUD: forms → database → interface,
  • simple dashboards with basic stats or indicators.

This isn’t a closed list : if your needs are close to one of these features, it’s often faster to adapt it rather than start from scratch.

Deployment & hosting

The idea is to keep something simple, reliable, and easy to understand.

  • web interface deployed on Vercel or Netlify (fast, well-suited for modern websites),
  • backend (Spring Boot API) hosted on a VPS (for example OVH) with Nginx,
  • optional setup of an update pipeline (simple CI/CD),
  • backups and basic best practices.

The goal : a tool that runs smoothly over time, without unnecessarily complex infrastructure.

Process & pricing

We always start with a simple version of the software to avoid oversized projects.

  • we define the key screens together,
  • we clarify the main flow (who does what, and in what order),
  • we limit the scope to what is truly useful at the beginning.

Then I work in short cycles (a few days or a week), with regular check-ins to make sure what’s delivered matches your real needs.

Classic model

  • quote based on a scope defined together,
  • 40% upfront,
  • the remainder paid upon delivery of the planned milestone.

Well-suited when the requirements are clear and well-defined.

Short milestone-based work

  • 3 to 7-day cycles, with deliverables at each milestone,
  • payment at the end of each validated milestone,
  • the project can be stopped or adjusted at any time.

Ideal for software projects where you need to build, test, and adapt to real usage.

Pricing

  • €125 / day for software projects,
  • estimated workload before each step,
  • option to start small to limit risks.

Technologies used

For web software, I clearly separate the frontend (interface) and the backend (API / data).
The same building blocks used in many professional web projects, designed to scale.

Frontend (React)

Used to build the interface : screens, dashboards, forms, tables, filters…
I also use Next.js for SEO when relevant.

  • Smooth, responsive app-like interface.
  • Modular components that are easy to evolve.
  • Well-suited for tools with many interactions.
  • Technologies widely used in professional environments.

Goal : a fast, frictionless user interface.

Backend (Spring Boot)

The backend handles the software’s logic : data, user accounts, business rules, emails, and secure access.

  • APIs to read and write data.
  • User accounts, roles, and permissions management.
  • Server-side business logic.
  • Solid foundation for an internal tool or an MVP.

I prefer working with technologies I truly master, rather than promising a “trendy” stack without real experience.