Development engineer who thinks like a product owner

Start with an idea. Leave with a plan worth building.

I work with founders and small teams who have something worth building but aren't sure where to start. I help make sense of the idea, define what matters first, and figure out what it actually takes to get it in front of real users. When you're ready to build, Threls — the product tech partners I lead as CTO — is where we take it from there.

Expertise

A decade of building products that matter

I sit at the intersection of engineering and product thinking — which means I care as much about what we build as how we build it.

01

Web & mobile product builds

I design and ship React and React Native apps that feel smooth for both users and admins, from first MVP to live, dependable products.

  • React & React Native builds
  • Web and mobile from one vision
  • UX‑driven flows, not just screens
  • Production‑ready launch support
02

MVPs & product shaping

I help founders and teams move from vague ideas to something real, then keep improving it with real feedback.

  • Clarify scope with stakeholders
  • Define MVP, not endless v1
  • Turn ideas into actionable tasks
  • Iterate based on real usage
03

Architecture & DevOps for small teams

I design practical architectures and CI/CD pipelines so your team can ship often without fearing deployments.

  • React/Next.js and API design
  • Monorepos where they make sense
  • CI/CD with GitHub Actions
  • AWS / DigitalOcean, Vapor / Forge
04

Mentoring & team support

I unblock developers, help split work effectively, and keep everyone aligned on what a “good” solution looks like.

  • Code reviews with clear guidance
  • Help juniors grow into confidence
  • Kick‑offs to align stakeholders
  • Available for questions, still hands‑on

Process

How I Work

I care about the entire lifecycle of a product: from the first rough idea to the version your team depends on every day.

1
Clarify and frame the MVPI work with you to define a realistic MVP: what must exist for real users to get value in the first release, and what can safely wait. This turns vague ideas into a focused scope we can actually ship.
2
Break work into buildable piecesI translate the MVP into concrete, buildable tasks that developers can own. This includes clarifying edge cases, dependencies, and success criteria so the team knows exactly what “done” looks like.
3
Build for the whole experienceI design and implement flows that work for everyone involved: end users, admin teams, and the developers who will maintain the system. That means clear UX, sensible data structures, and code that’s not painful to revisit.
4
Ship and ObserveI set up simple, reliable deployments and basic monitoring so we can ship confidently and watch how the product behaves in the real world. We pay attention to usage, errors, and user feedback instead of guessing what’s working.
5
Iterate with intentUsing what we learn from real usage, we decide what to improve next and how to do it without breaking what's working. Small, deliberate changes that reduce friction and keep the product moving. When you're ready to scale with a dedicated team, that's when I bring you into Threls.

My Toolkit

Frontend

Next.jsReactReact NativeExpoVueNuxt.jsElectronFlutterTailwind CSSTypeScriptJavaScript

Backend

NodeJSLaravelMySQLSanity.ioRust

DevOps

DockerAWSDigitalOceanHetznerGithub ActionsVercelHerokuLaravel ForgeLaravel Vapor
New to this technology, but excited to use it in a real project.

Away from the IDE

I’m the CTO of Threls, a small product studio on a Mediterranean island. Day to day I still work like a senior engineer: designing systems, writing code, and helping ideas become real products. I’m also a husband and father of two, which is a big part of why I care about building things that make people’s lives simpler, not more complicated.

Who I work best with

I’m the right person to talk to if you have an idea and need help making sense of it before you commit to building anything.

  • Founders with a fresh idea who want to understand what to build before spending money on it.
  • Products that already exist but feel slow, clunky, or frustrating for real users.
  • Small teams who need someone who can own front‑end, mobile, and deployment without a committee.
  • Anyone who wants a direct conversation about what to build, why, and what to leave for later.

Have a project worth exploring?

Tell me about it. We’ll work out what it actually needs to become something real — and when you’re ready to build, Threls is where we take it from there.