CRM by Fatek | Guilherme Fath

Overview

CRM by Fatek brings the day-to-day operation into one workspace: pipeline, customers, proposals, inbox, stock, finance and automation.

The product was built for small and mid-sized teams that outgrow spreadsheets and scattered tools, but still need something practical enough to use every day.

Business problem

Small and medium-sized companies often run sales, finance and customer communication in different places. Context gets lost, follow-ups depend on memory and managers only see the business after the problem has already happened.

Product approach

The product keeps customer, product, financial and communication data connected while protecting each tenant boundary from the database model up.

My role

I worked on product definition, UX flows, frontend, backend, database modeling, API integrations, deployment and infrastructure.

Key capabilities

visual sales pipelines

leads and customers

tasks and activities

proposals

omnichannel inbox

campaigns

financial management

ERP and inventory

product and supplier management

automations

AI agents

Bastião AI copilot

operational dashboards

internal e-commerce operations

payment integration

shipping integration with Melhor Envio

Architecture

CRM by Fatek system view

Technical decisions

TypeScript end-to-end across product surfaces.

Frontend and backend separation with shared domain contracts where useful.

Multi-tenant data isolation modeled as a first-class concern.

Webhooks and asynchronous jobs for third-party services.

Operational views by business profile instead of one rigid workflow.

Centralized validation for critical business rules.

Challenges and trade-offs

Unifying different business modules.

Maintaining tenant isolation.

Keeping flows flexible without making the product vague.

Dealing with third-party API failures.

Balancing product breadth with interface clarity.

Supporting product and service businesses in the same platform.

Production and operations

The product runs as a SaaS with hosted web, API, database and external integrations in place.

Stack

Next.jsNestJSTypeScriptPostgreSQLPrismaAWS

What I learned

Broad business systems need disciplined boundaries: shared data where it helps operations, isolated contexts where it protects clarity.

Next project

Revello

A vertical SaaS product for gym operations, billing, retention, churn risk, check-ins, WhatsApp communication and assisted operational agents.