bes@portfolio: ~ — zsh
$ ./intro.sh
> initializing bes.portfolio …
> Hi, I'm Bes.
> I build interactive websites & automations.
> I turn manual, repetitive work into systems that run themselves.
$ 
6builds shipped
100%hand-coded
~40h/wksaved by automations

~/work $ ls -la ./automations

# 4 processes — client builds & automations. select a row to inspect.

STATUSNAMETYPEACTION
● running birria-birria hospitality · ordering & ops inspect →
● running blood-panel health · data & reporting inspect →
● running adobe-emails marketing · email ops inspect →
● running trading-bot fintech · data & signals inspect →

~/personal $ ls ./projects

# things I built for the fun of it.

STATUSNAMETYPEACTION
● running movie-picker personal · web app inspect →
● private birthday-surprise personal · interactive inspect →

~ $ neofetch

   ____
  | __ )  ___  ___
  |  _ \ / _ \/ __|
  | |_) |  __/\__ \
  |____/ \___||___/
bes@portfolio
———————————————
Role Web developer & automation builder
Stack Vanilla JS · n8n · APIs · Webhooks
Focus Interactive UX + workflow automation
Approach Hand-coded, no templates
Builds 6 shipped · ~40h/week saved
Status ● open to work
Contact besforth@icloud.com
# I live in the overlap between interactive front-end and automation.
# One half: sites people actually enjoy moving through.
# The other half: the systems behind them, quietly running the boring work —
# a birria pop-up's order queue, a health dashboard, a self-building email
# pipeline, a trading cockpit. Give me a messy manual process; I'll make it
# run itself.
[ interactive-ux ] [ n8n ] [ apis ] [ webhooks ] [ data-dashboards ] [ email-systems ] [ front-end ]

$ ./contact.sh

> got a site that should feel alive, or a manual process eating your time?

> tell me about it. I'll make it run.

run ./contact.sh — besforth@icloud.com ↵