TOBYToby, creative technologist
CREATIVE TECHNOLOGIST
DIGITAL SYSTEMS
AUTOMATION & TOOLING
Creative technologist building the machinery a business runs on.
I work close to the ground, inside the actual workflow of a food and beverage business, not from a spec document. The tools I build get judged the same way the kitchen does: does it work today, under pressure, without anyone babysitting it.
The problems I take on are the ones nobody writes a ticket for. A recap typed out by hand every night. A price that lives in four places and disagrees with itself. The same adjustment applied two hundred times by someone who stopped concentrating an hour ago. None of that is interesting work for a person, and all of it is load-bearing.
So I start by watching the manual version of the job rather than asking what it should do. Then I build the smallest thing that removes the step, and I keep it running. Design, code and the automation behind it are the same job here, which is the reason these tools stay small: nobody has to hand a specification to anyone else, so nothing gets built to cover a misunderstanding.
WHAT I BUILD
- 01 /Internal tools
- 02 /Operational dashboards
- 03 /Automation scripts
- 04 /Reporting systems
- 05 /API integrations
- 06 /Workflow utilities
- 07 /Interactive web experiences
07
Projects shipped
07
Systems in use
13
Technologies in use
2026
Active
- OngoingOperations & AutomationCreative Technologist
Embedded in the day-to-day running of a food and beverage operation, building the internal tools the team works with: dashboards, reporting jobs, order automation and the references the floor reads during service.
- PracticeHow the work happensDesign, build, maintain
Each tool is specified by watching the manual version of the job, built end to end, and then kept working as the operation changes. No handover between designing it and running it, which is why the tools tend to stay small.
- 01AutomationRemoving repetitive manual steps from operational workflows
- 02Web DevelopmentBuilding interfaces used directly inside day-to-day operations
- 03Backend & APIsConnecting services, data and internal workflows
- 04Data & ReportingTurning recurring operational data into usable reports
- 05BotsAutomating repetitive order and operational tasks
- 06UI / UXInterfaces designed around how people actually work
- 07Creative DevelopmentInteractive web experiences, motion and experimental interfaces
- 08AIApplied selectively, where deterministic rules are not enough
BUILT WITH
- 01 /Astro
- 02 /TypeScript
- 03 /JavaScript
- 04 /Python
- 05 /HTML / CSS
- 06 /Git
- 07 /REST APIs
- 08 /Google Sheets API
INTERACTIVE & 3D
- 01 /Three.js
- 02 /WebGL
- 03 /GSAP
- 04 /Shaders
- 05 /Scroll-driven motion
CAPABILITIES
- 01 /Automation
- 02 /Bots
- 03 /Data processing
- 04 /Internal tooling
- 05 /Operational systems
- 06 /Reporting
- 07 /Workflow automation
- 08 /Interactive experiences
/ CONTACT
Open to technical projects, operational systems, automation work and creative technology. If you have a process that only works because somebody is holding it together by hand, that is the kind of problem I find interesting.
LOCATION
Indonesia
SEEING THE REAL THING
The case studies describe these systems rather than show them. The working interfaces sit inside a live operation, so they are not published here. If you want to see how any of them actually looks and runs, ask and I will walk you through it.