Skip to content
Open to projects & collaborationDominican Republic · Working remotely

Building digital solutions that solve real business problems.

I design and develop websites, applications, automation tools and AI-driven systems — focused on improving how businesses actually work.

5

Tools designed, built and shipped

6

Certifications across CS, IT and AI

140+

University credits in engineering

What I build

Four things, done properly.

A narrow set of capabilities that reinforce each other — enough range to take a problem from workflow to working software, without pretending to do everything.

Web applications

Interfaces and tools people use to get real work done — designed to be understood on first use, not after training.

Workflow automation

Finding the repeated manual step inside a business process and replacing it with something reliable.

Applied AI

Agents, extraction and local models used where they measurably beat conventional code — and skipped where they do not.

Technical foundation

Systems, networking and infrastructure knowledge, so what gets built can actually be deployed and supported.

Selected work

Products, not portfolio pieces.

Each of these came out of a real constraint — a team that could not install software, audio that could not leave the building, a drawing that had to become data, a laptop that had to stop behaving like a laptop.

clean-taggyPROJECTSLine 4 — Rev CLine 2 — Rev ABay 7 retrofitArchive 2024Synced · 4 devicesLine 4 — Rev CVALIDATEDExportTAGWIREFROMTOSTATUSTAG-0142W-2210RACK-ADSP-01OKTAG-0143W-2211RACK-AAMP-02OKTAG-0144W-2212RACK-BSPK-07CHECKTAG-0145W-2213RACK-BSPK-08OKTAG-0146W-2214PATCH-1CTRL-03OK
AutomationIn production2025

Clean Taggy

A label and wire-tag workspace for a manufacturing quality team — built as one file so it could be deployed inside a locked-down corporate environment.

JavaScriptFirebaseFirestoreSingle-file app
View project

How I work

Technology is only valuable when it removes a real problem.

Most software fails long before the code does — it fails at the point where someone decided what to build. So the work starts in the workflow, not in the editor.

  1. 01

    Understand the problem

    Sit with the process as it actually runs, not as it is described in a document.

  2. 02

    Analyse the workflow

    Find where the time goes, where errors enter, and which constraints are non-negotiable.

  3. 03

    Design the right solution

    Choose the smallest thing that removes the problem — including deciding not to build.

  4. 04

    Build and test

    Ship something real quickly, then put it in front of the people who have to live with it.

  5. 05

    Improve on results

    Watch how it is actually used and refine. The first version is a hypothesis.

Foundation

An engineering background, formal computer science, and the IT layer underneath both.

View education & certifications
  • HHarvard UniversityCS50
  • fCfreeCodeCampWeb development
  • A+CompTIAA+ certified
  • GGoogleIT Support
  • GGoogleAI courses
  • AAnthropicMCP & agents

Have a problem worth solving?

Tell me what the process looks like today and where it breaks. If technology is the right answer, I will tell you what I would build — and if it is not, I will tell you that too.