01
Huqui: a product, built end to end.
A complete web platform for customers, quotes and reporting, designed and built by me from the data layer to the interface.
Read the case study
Frontend Engineer · CRM Developer · Consultant
I build the products people useand the systems that power them.
I'm Hugo, a frontend engineer and CRM developer. I design and build web applications, CRM platforms and the connections between them, from the interface people use to the systems behind it.
- since
- 2021 (5+ years on the web)
- scope
- Products and CRM platforms used across Europe
- languages
- Portuguese, English, Spanish
- based in
- Porto, Portugal
// write to me
fig. 1 / system map in sync
01 The bridge
This is the part of the work most people never see: how a business process becomes something people can use. Pick a step.
From how the business works to what its people see.
Everything starts with how the team actually works. In a multi-country rollout every market had its own process, and the system has to follow it, not the other way round.
uses: Requirements · Market-specific rules
// business-processesstep 01 of 06
Business processes
Everything starts with how the team actually works. In a multi-country rollout every market had its own process, and the system has to follow it, not the other way round.
uses: Requirements · Market-specific rules
02 Selected work
Four projects: the problem, what I decided and what came of it. Client names stay private.
02
One CRM, many markets.
Zoho CRM for major global automotive brands, rolled out across international markets that each worked differently.
Read the case study
03
A shared widget library for Zoho.
Reusable Vue and TypeScript components for record views and modal workflows, built once and used across client deployments.
Read the case study
04
Fast by design.
A Next.js marketing site where speed and search ranking were part of the brief from the first day.
Read the case study
03 How I think
Four beliefs that shape how I build, and the work they come from.
01
Good software rarely fails because of code. It usually fails because systems stop communicating.
So I spend as much time on how data moves between systems as on the interface in front of it.
// see One CRM, many markets.
02
Automation only works when the process is understood.
The market-specific rules came after understanding how each market really worked, not before.
// see One CRM, many markets.
03
Complexity should live in systems, not in people.
Typed, shared components and rules kept in one place mean nobody has to remember the exceptions.
04
The goal is not to add tools. It is to reduce friction.
Performance and accessibility belong in the first version, and so does every step someone no longer has to do by hand.
// see Fast by design.
04 Where I can help
When systems start to break:
Customer data is spread across tools
Nobody has the full picture, and every report starts with a reconciliation.
The CRM no longer reflects the business
The process moved on, the system did not, and people work around it.
Teams duplicate work manually
The same data is typed twice in two places, and the two versions drift apart.
The interface is slow, inconsistent or hard to change
Every new feature costs more than the last, and people stop trusting the screen in front of them.
Product and operations are disconnected
What the interface offers and what the business actually does have stopped matching.
That's usually where I come in.