What Can I Do For You? (And Why That's the Wrong Question)

I get this question at least once a week: "Gabriel, what can you do for me?"

Usually it comes from a startup founder with an idea, a business owner who needs to "go digital," or a company that wants to add AI to something (because, you know, AI is hot right now).

Here's the thing: I can build almost anything. Twelve years as a full-stack engineer will do that. I've shipped features at Snapchat used by hundreds of millions of people. I've built fintech platforms at Backbase. I've architected conversational AI systems. I've wired up Next.js apps that feel instant and Supabase backends that scale.

But "what I can build" is the wrong lens.

The Real Question: What Problem Are You Solving?

The projects that succeed — the ones that actually move the needle for a business — start with a clear problem, not a technology wishlist.

I worked with a client last year who came to me wanting "an AI chatbot." Everyone wants AI right now. But when I dug in, their real problem was that customer support was drowning in repetitive questions about order status. They didn't need cutting-edge GPT-4 magic. They needed a simple interface that connected to their order database and could answer "where's my stuff?"

We built it in three weeks. TypeScript, Next.js, a straightforward OpenAI integration, and a Supabase backend to log conversations. It handled 60% of their support volume within a month.

The win wasn't the tech stack. It was understanding the actual problem.

Here's What I Actually Do

Instead of listing technologies (though yes, I work with Next.js, TypeScript, Angular, Node.js, Supabase, OpenAI, and more), here's how I think about projects:

1. I Turn Business Problems Into Technical Solutions

You tell me customers are dropping off during checkout. I look at the flow, identify friction points, and build a faster, smoother experience. Maybe that's optimizing API calls. Maybe it's rethinking the UI. Maybe it's adding better error handling so people don't rage-quit when something breaks.

2. I Build Systems That Scale With You

I've seen too many startups paint themselves into a corner with duct-tape architecture. When I build something, I'm thinking about what happens when you 10x your users, add new features, or need to onboard another engineer.

That means clean code, proper documentation, and infrastructure that doesn't fall over when you hit Product Hunt's front page.

3. I Ship Fast, Then Iterate

Perfection is the enemy of done. I'd rather get a working MVP in your hands in two weeks than spend three months building the "perfect" system that may or may not solve your problem.

At 84.51°, we operated in two-week sprints. You learn what works by putting it in front of real users, not by theorizing in Figma.

4. I Integrate AI Where It Actually Adds Value

Look, I love working with OpenAI's APIs. Conversational AI is genuinely powerful. But I won't slap a chatbot on your site just because it's trendy.

AI makes sense when:

• You need to process or generate natural language at scale
• You want to personalize experiences based on user input
• You're automating something that requires understanding context

It doesn't make sense when a simple form or filter would do the job.

5. I Work Like a Senior Engineer, Not a Code Monkey

You're not hiring me to translate Jira tickets into React components. You're hiring me to think through the problem, propose solutions, challenge assumptions, and build something that works.

That might mean saying, "Actually, we shouldn't build that feature at all." I've done that. Sometimes the best code is the code you don't write.

The Types of Projects I Take On

To make this concrete, here are the kinds of things I actually build:

• Full-stack web applications: Customer portals, internal tools, dashboards, SaaS platforms
• Conversational AI systems: Chatbots, virtual assistants, AI-powered support tools
• Fintech integrations: Payment flows, banking APIs, transaction processing
• Rapid prototyping: MVPs for startups that need to validate ideas quickly
• Architecture consulting: When you need someone to audit your codebase or plan a major refactor

What I Don't Do

I'm not a designer. I can implement a design beautifully, but don't ask me to make it pretty from scratch.

I'm not a data scientist. I can integrate ML models, but I'm not training them.

I'm not cheap. I charge what I'm worth because I deliver results.

So, What Can I Do For You?

Here's my actual answer: I don't know yet.

Tell me what's keeping you up at night. Tell me what's slowing your business down. Tell me what opportunity you're missing because your tech can't keep up.

Then I'll tell you exactly what I can do — and whether I'm the right person to do it.

Because after 12 years, I've learned that the best projects don't start with "what can you build?" They start with "what should we build, and why?"

That's the conversation I actually want to have.