I run the shop
I build for.

No digital intake path existed. Scanning alone wouldn't have helped — a folder of PDFs isn't searchable, so the records would have stayed just as buried, only backlit.

Built an OCR pipeline that runs scanned invoices through the Claude API, extracts structured fields — customer, vehicle, services, parts, totals — and writes them to MySQL behind a searchable interface the front desk actually uses.

Capture and filing were separate steps, and the second one depended on someone remembering to do it at the end of a shift. It didn't survive a busy day.

A capture tool for the shop's Android and Fire tablets that uploads straight to Google Drive through a service account, filed against the right job automatically. One tap, no filing step to forget.

Service history lives in whatever shop happened to do the work. Nothing follows the vehicle, so nobody — owner or shop — has the full record.

Building the platform that keeps vehicle health continuous across owners and shops rather than resetting at every visit.

The bottleneck isn't writing, it's the absence of a system. Without one, every post starts from zero.

A Notion operating system for content: scripts organized by pillar, funnel stage, and hook type, with board views that make the next thing to film obvious. Shipped as a product, not a service.

Every tool owns a slice and none of them talk. Checking all six is a daily tax nobody pays consistently.

A private dashboard that syncs Notion, Google Sheets, and Apple Watch health data into one operating view, with AI agent panels for the recurring questions. Installed as a PWA, auth behind NextAuth.

Content was hardcoded. Every copy change was a deploy, which meant changes queued up until they stopped happening.

Rebuilt the site against a Supabase CMS so the team edits content directly and the site reflects it immediately.

Every part of the operation was a separate island: an ancient POS, paper for the rest, a brochure website bolted on the side. Nothing connected, so the same order got re-entered by hand as it moved from table to kitchen to bar.

One system wearing a website as its face. Public visitors see a full site rebuild; behind an auth wall, staff run a PWA point of sale that fires tickets to kitchen and bar display systems over a live Socket.IO connection. Guests scan a table QR to view their check and pay by card at the end. Online reservations, menu and closure management, staff scheduling and a timeclock, cash-drawer closeouts, and business reporting all run from an admin dashboard. Everything a restaurant needs, in one place, disguised as a website.

The originals run 1.5 to 24 MB straight out of Adobe, and WordPress's upload caps and media pipeline blocked them at every step. The site was stuck permanently on hardcoded fallback data, which meant every content change was a developer task instead of something Derin could do himself.

Rebuilt on the TaserDesign pattern — static frontend, admin in the browser talking straight to Supabase, WordPress deleted entirely. Derin drags exports straight from his Adobe folder and the pipeline auto-compresses them with sharp so large files upload smoothly. The site carries a museum-style gallery wall, acrylic print checkout at any size, and shoot booking, with a creative admin portal he runs himself.