01 / Recovery
Protect before you troubleshoot.
A staged drive assessment that separates inspection, imaging, recovery, and handoff.
Start with thisPortfolio index / six verified builds
Built for actual work.
Live websites, installed software, repair operations, creator systems, and hardware experiments—each solving a different kind of problem.
Selected work / verified builds
Real systems.
Real use.
Websites, desktop software, repair operations, creator tools, and hardware experiments built around actual jobs.
Live ClawzPokeShipz
A live-status hub and storefront for a TikTok creator, backed by one Cloudflare Worker.
- React
- Cloudflare Worker
- KV + R2
- Discord
View live site↗
02 / Storefront prototypePrototype
Affinity for Gaming
A custom storefront direction for a local tabletop and gaming business.
- HTML + CSS
- JavaScript
- Cart system
Website capability↗
03 / Windows desktop appReleased
YTD Media Downloader
A packaged Windows application for permitted audio and video downloads.
- Tauri
- Rust
- Windows installer
View source↗
04 / Creator systemLocal system
RTCO Overlay
A standalone local control system for live-sale overlays and OBS production.
- FastAPI
- OBS WebSocket
- Live chat
Creator capability↗
05 / Repair operationsLive / gated
TPS Report
A secure barcode-driven repair and inventory tracker for slot-machine parts.
- Cloudflare
- D1 + R2
- Barcode scanning
View secure site↗
06 / Hardware labLab build
240USB
RP2040 Round Display Lab
Native firmware and a desktop controller for a 240×240 round LCD.
- RP2040
- C++ firmware
- Python GUI
Device capability↗
06 VERIFIED PROJECTSWEBDESKTOPREPAIRCREATORHARDWAREOpen portfolio index →
The workbench
Six systems. Six kinds of friction.
Open each demonstration as a clue to what RTCO Labs can inspect, configure, build, or explain.
02 / Web
A front door with a purpose.
A fast, focused site that explains the work and gives visitors a clear next action.
Start with this yourbusiness.com
Start here
03 / Automation
Make the repeated step disappear.
Small scripts, searchable systems, dashboards, and alerts shaped around a real workflow.
Start with this1 # RTCO Labs — end-of-day sales report
2 import csv, schedule
3
4 def daily_report():
5 sales = read_pos_export("sales.csv")
6 total = sum(row.amount for row in sales)
7 notify(f"Today: ${total:,.2f} across {len(sales)} sales")
8
9 schedule.every().day.at("18:00").do(daily_report)
✓ Report sent to Discord #daily — $1,284.50 across 37 sales
04 / Signal
A creator system you can run live.
Scenes, capture, audio routing, overlays, and controls arranged around the operator.
Start with this ON AIR PROGRAM / 01
INPUT A SYNC LOCKED 60 Hz
05 / Systems
Keep the counter moving.
Hardware, menus, displays, and back-office basics organized around daily use.
Start with this Latte
$4.50 Muffin
$3.25 Bagel
$2.75 Cold Brew
$5.00 Tea
$3.00 Charge
$4.50 Muffin
$3.25 Bagel
$2.75 Cold Brew
$5.00 Tea
$3.00 Charge
YOUR SHOP
Latte$4.50
Muffin ×2$6.50
Cold Brew$5.00
TOTAL$16.00
Thank you!
Printer ✓ Card reader ✓ Cash drawer ✓
06 / Community
Keep the room in motion.
Roles, intake, reminders, moderation helpers, and useful notifications.
Start with this M
mia.k
!order 1042
R
RTCO Bot BOT
J
jorge
!hours
R
RTCO Bot BOT
Swipe through the capability console
Capability demonstrations—not invented client case studies.
How RTCO works
Start with the friction. End with a system you can use.
Good technical work should not become a mystery after the handoff. RTCO Labs starts with what is getting in the way, chooses the right level of technology, and keeps the next step understandable.
Bring the goal- 01
Describe the outcome
Share the problem, device, project, or repeated task and what a successful result would look like.
- 02
Inspect first
RTCO Labs checks the situation and explains the options, risks, likely effort, and what should be backed up.
- 03
Approve the work
No device, account, or project changes happen until the useful scope is clear and you approve it.
- 04
Receive the handoff
You receive a plain-English summary, practical next steps, and training or documentation when it helps.
Build only what earns its place.
Use a page, repair, station, script, bot, or workflow when it makes the work clearer, safer, or easier to operate.
Keep the technology in service of the work.
The goal is a useful next step, not extra complexity for its own sake.
Leave people in control.
The handoff should make sense to the people using it—not leave them afraid to touch the system.
Field notes
Better decisions start before the build.
Plain-language guides for protecting data, planning a useful system, and knowing what to do before a technical problem becomes a bigger one.
Read the guides 01
Web + Presence
What a service-business website needs before it goes live
A practical launch checklist for turning a homepage into a clear next step for the people you want to reach.
Read guide ↗ 02Repair + Setup
What to bring to a computer repair or device-migration intake
A plain-language checklist for getting useful help without sharing passwords, recovery codes, or more personal data than a technician needs.
Read guide ↗ 03Automation + Systems
When a small business should automate a task—and when it should not
How to spot a repeatable process worth simplifying, choose a small first step, and avoid turning a simple task into an expensive system.
Read guide ↗