SaaS / Identity / Microsoft 365

HubSigna

From a simple signature to a solution of my own.

An email signature product born from a practical need, now used internally at Gantech.

Original brand · conceptual composition
Context
Personal project · Internal use at Gantech
Authorship and contribution
Individual conception and execution
Current stage
In internal use

01 / HubSigna

The starting point

While using WiseStamp, I found the website complex for editing a simple signature, with licensing costs that felt high for my needs. I decided to develop my own solution.

The challenge was to make editing more manageable while preserving a consistent brand, and connect signature templates to people and the company's email environment.

02 / What I built

From a simple signature to a solution of my own.

I built HubSigna to bring visual creation, people data and signature distribution together. Editing a template connects to its application, instead of requiring each signature to be adjusted manually.

The product is a personal initiative currently used internally at Gantech. The hubsigna.com website is public; subscriptions are not yet open.

03 / Capabilities and deliverables

Capabilities and deliverables

01

Visual signature editor

Compose text, contacts, images, icons, columns and dividers, with styling controls and per-person previews.

02

Reusable templates

A gallery, duplication and template versions support reuse and testing alternatives before broader use.

03

People management

Search, department and Microsoft group filters, individual or bulk selection and signature assignment.

04

Updates from the template

Saving a template in use updates linked signatures while preserving pauses and the settings of different email compositions.

05

Microsoft 365 integration

Directory data connected to people management, with an Outlook add-in applying signatures to email compositions.

06

Organizations and access

Organization separation, administrative roles, invitations, authentication and access controls for management functions.

04 / Decisions that shaped it

Decisions that shaped it

01

Start with a need of my own

Editing complexity and licensing costs motivated the project. Internal use keeps product decisions close to the difficulties encountered in everyday work.

02

Connect creation and maintenance

A template is more than an exported design. It retains links to people and published signatures, allowing changes to reach those using it.

03

Treat email as its own environment

Rendering and APIs vary across Outlook clients. Validation accounts for those differences; a browser preview does not establish universal compatibility.

05 / My contribution

Individual conception and execution

HubSignaBrand and visual identity

Design is part of what I build.

I also created the project's brand and visual language. Identity, interface and communication developed alongside the idea and its implementation.

  • Product conception based on a practical need
  • Editor, interface and management experience
  • Backend, data, security and organization isolation
  • Microsoft 365 and Outlook integration
  • Brand, visual identity, website, infrastructure and operations

Technologies and concepts

  • TypeScript
  • React
  • Node.js
  • PostgreSQL
  • Microsoft Graph
  • Outlook Add-in
  • Railway

06 / Current stage

What the work made possible

HubSigna became the solution I use internally at Gantech for the need that prompted its creation. It continues to evolve through that use before opening subscriptions.

Access and availability

Public website. Subscriptions are not open; current use is internal at Gantech.

Discuss this work