I love solving problems and creating exciting applications. Here's how I approach building projects I'm passionate about.

Discover
I start by understanding the problem. Who is this for? What are they struggling with? What else exists and why isn't it working for them? I dig into the market, study competitors, and talk to potential users.
This is where I figure out if an idea is worth pursuing. I map out the user journey and identify the real pain points. If the foundation isn't solid, nothing else matters.
What I figure out
- Who it's for
- The core problem
- Competitive landscape
- What makes this different
- User journey
- Validation

Define
Once I understand the problem, I lock in the direction. What's the positioning? What's the vibe? What's in the MVP and what's not? I explore visual directions, nail down the brand voice, and set clear scope boundaries.
By the end of this phase, I have a brand brief and a sitemap. No ambiguity about what I'm building or how it should feel.
What gets locked in
- Positioning
- Visual direction
- Brand voice
- MVP scope
- Out of scope
- Site structure

Design
This is where everything becomes tangible. I design the brand system, write all the copy, and build out every screen. I think about what's going through someone's head at each step—what they need to see, what would confuse them, what makes them take action.
Before moving to code, I make sure the designs actually work. Not just look good—but make sense for real people using them.
What gets made
- Brand system. Logo, colors, fonts, guidelines. The visual foundation.
- Copy. Headlines, buttons, error messages, everything. Words matter.
- Wireframes. Every screen, responsive, ready for development.

Build & Launch
Time to build. I write clean code, test properly, and ship to production. The goal is to get something real out into the world—not perfect, but solid enough to learn from.
Then comes the launch. Product Hunt, social media, communities where the users are. After that, I watch what happens and iterate based on real feedback.
What happens
- Development. Clean architecture, proper testing, modern stack.
- Launch. Product Hunt, socials, relevant communities.
- Iterate. Watch the data, listen to feedback, improve.
How I think - What guides my work
A few principles I keep coming back to.
- Understand before building. I don't start coding until I know the problem is worth solving and the direction is clear.
- Design with intent. Every screen, every word, every interaction should have a reason. If I can't explain why it's there, it probably shouldn't be.
- Scope matters. I decide what's in and what's out early. Then I stick to it.
- Ship, then improve. Done is better than perfect. Real feedback beats assumptions.
- Keep it documented. Decisions, research, assets—everything gets written down. Keeps things organized and makes handoffs clean.
- Think about distribution. A great product nobody knows about is worthless. I think about how people will find it from the start.