Skip to content

Internal system & operations

CRM Mytrus

An internal CRM built to centralize Mytrus client data, sales operations, and financial workflows.

My role
Product, design, and Full Stack development
Core stack
Next.js / TypeScript / Supabase / PostgreSQL / Stripe
Project
View demo
CRM Mytrus: Internal system & operations

Context

Mytrus needed to organize its day-to-day operations in a tool designed around how the company actually works.

The challenge

Sales, financial, and client information was fragmented. The challenge was to create an integrated view of the journey without forcing the operation into a generic CRM.

My responsibility

I owned the project end to end: problem discovery, product, UX/UI, architecture, frontend, backend, business rules, implementation, and ongoing evolution.

The solution

I turned the company’s real processes into a modular system that connects the sales pipeline, client history, and billing controls in one experience.

Key features

  • Lead and client management
  • Projects and relationship history
  • Payments and subscriptions
  • Referrals and operational indicators

Product and engineering decisions

  • Model the product around the operation rather than a generic CRM template
  • Centralize context without turning every screen into an overly dense dashboard

Outcome and impact

The CRM centralized operations and reduced information fragmentation, creating an integrated view of sales activity and client relationships.

Next case study

IAAHTB

Institutional portal & system

Working through a similar challenge?

Let’s talk about the problem, the context, and what a strong delivery needs to solve.