tdTanguy Dessoly
Contact me
Product · Full-stack development

Evolve an internal tool into a structured product

Design of a customer relationship management tool organised around company workflows and prepared to evolve progressively into a SaaS service.

Context
Company project
Role
Full-stack design and development
Status
In development
CRM interface showing the account, employees, branches and external connections
An organisation view bringing together the profile, business modules and integrations.
  1. Organisation, employees and branches
  2. Microsoft and LinkedIn connections
  3. Architecture designed to evolve
The starting point

Build around real work, not a generic model.

Challenge

An internal CRM must bring very different information and actions together without becoming a pile of screens. The challenge was to create a shared structure for accounts, employees, branches and sales views while preserving a credible path for future development.

Mission

Contribute to the product’s design and development, connect the interface to business needs and prepare a technical foundation for new modules and a future SaaS offering.

The process

A business product takes shape layer by layer.

  1. 01

    Start with internal workflows

    Organise the product around the entities and actions teams already use instead of imposing an abstract CRM model.

  2. 02

    Structure the interface

    Separate accounts, employees, branches and sales views to make navigation predictable and enable module-by-module development.

  3. 03

    Connect the ecosystem

    Plan connections to existing tools, including Microsoft and LinkedIn, through an understandable configuration space.

  4. 04

    Prepare for what comes next

    Maintain a clear separation between React, the Node.js API and MySQL data so the planned SaaS evolution does not require a full rewrite.

What the project demonstrates

A clear foundation to keep building on.

This project illustrates the shift from an isolated feature to product thinking. The challenge is not just building screens: it lies in naming the business concepts, separating responsibilities and leaving room for future needs without over-engineering too early.

  • Business navigation organised around identifiable modules.
  • An interface connecting account information, organisation and integrations.
  • A full-stack foundation with a clear separation between presentation, services and data.
  • A product path designed beyond the immediate need.
ReactMaterial UINode.jsExpressMySQL
Does an internal product need to move forward?

Let’s turn its workflows into a sustainable architecture.

Get in touch