We waited for so long. That"s the old way.
Remember when a designer"s job wrapped up with a Figma file and a careful hand-off? I sure do. For nearly a decade at Performics.Convonix, part of Publicis, my world was all detailed wireframes, prototypes, and specs.
We"d pass them to development teams — often massive ones — and then… we"d wait. Sometimes, what came back wasn"t quite the vision. Or it took so long the market had already moved on.
That"s the trap. Most businesses, especially the agile SMEs I work with now, simply can"t afford that kind of lag. They need to move. Quick changes. Value delivered yesterday.
And that"s why "full-stack designer," a term that honestly felt like corporate jargon a few years back, has become genuinely meaningful. It"s not some theoretical ideal anymore.
It"s not about shiny mockups anymore. It"s about code that actually runs.
For me, the jump from a lead design role in a big agency to CPO at a startup like Swimwell, and now running Hamzio as a freelance builder, was a huge shift. I quickly realised: a beautiful design, if you can"t actually build it efficiently or tie it into existing systems, is just a pretty picture. It won"t move the needle for a business. No users. Zero revenue.
Being a full-stack designer means I don"t just design the solution. I ship it. I"m not just making mockups; I"m making working software. Whether it"s a new feature for an analogue schematic tooling web app, an e-commerce storefront for HomeGlazer, or a bespoke lead generation system using Enqode QR codes, my goal is always to deliver something that actually works, directly impacting their bottom line.
This isn"t about being a unicorn who knows every single framework and database inside out, by the way. It"s about understanding the entire process. From that first user interview right up to the final deployment.
My background in UX (UT Austin post-grad) and Psychology (BA) helps me understand why people actually behave the way they do. My 13+ years of implementation experience then helps me figure out how to build for that behaviour, effectively. It"s the bridge between empathy and execution. I"ve seen too many brilliant designs crumble because technical feasibility wasn"t considered early enough.
SMEs just can"t afford to wait.
For big enterprises, separating design and development can sometimes fly. They"ve got the resources, the internal processes, and the sheer number of people to wrangle complex hand-offs.
But for SMEs? That"s usually a luxury they can"t afford. Budgets are tighter, teams are leaner. Every single hour counts.
When I work with an SME, they often don"t have a dedicated design team and a separate development team. They need someone who can grasp their business problem, sketch an intuitive solution, and then turn that design into a functioning product with minimal friction.
This means I can sit down with a client, outline an idea on a virtual whiteboard, and then — sometimes even during the same call — start writing the React components or setting up the Supabase tables that will bring it to life. We just cut out layers of communication, misinterpretations, and delays.
I remember a late evening. I was working on a custom dashboard for an SME client. We"d gone back and forth on the Figma prototype all day, trying to nail a tricky data visualization.
Around 10 PM, the client pinged, "Hamza, if we could just add this one filter here, it would make a huge difference." In the old setup, that meant: update Figma, export assets, write a detailed spec, hand it off, wait for a sprint, then deal with potential back-and-forths.
But I had my VS Code open right next to Figma. I knew the Next.js component structure, the Supabase query, and exactly how it all connected. A few lines of TypeScript, a quick npm run dev, and within 20 minutes, I sent a screenshot of the live, working filter. "Like this?" I asked. The response: "Perfect!" That"s the direct value I"m talking about.
The tools we have today? They let me do this.
This isn"t just about skill. It"s also about the incredible ecosystem of tools we have today. Next.js gives me the power of React with a fantastic developer experience.
Supabase handles my database and authentication with ease. n8n lets me automate complex workflows and integrate services without writing a backend from scratch. Telegram bots? A quick way to build direct user interactions or internal alerts. These aren"t just technologies; they"re enablers that let a single builder achieve what used to require entire teams.
The beauty of this stack is it lets me stay focused on the user problem while simultaneously building a robust, scalable solution. I"m thinking about the UI/UX, the data model, the API integrations, and the deployment strategy all at once. Fewer surprises down the line. A much smoother path from idea to production.
I"m still figuring things out, but I know this much.
I"m still figuring out the best ways to streamline my own processes, always. But what has consistently worked for me is this integrated approach. It"s not about trying to be a master of all trades and a master of none. It"s about having enough proficiency across the stack to connect the dots, understand the real-world implications of design choices on implementation, and, most importantly, own the delivery of a working product.
For anyone in product design today, especially those aiming to make a real impact on lean teams or startups, I don"t think "full-stack designer" is an option anymore. It"s becoming the standard. We"re not just designing experiences; we"re building them. This makes the difference.
