BAS-02Work
Selected engagements.
Each reflects direct involvement across systems, not isolated deliverables.
Mark Lauren — Platform Architecture and Technical Stewardship
Global fitness brand · Ongoing engagement
CONTEXT
Global fitness brand with fragmented products across books, DVDs, and digital content.
PROBLEM
No unified platform. User experience fragmented. Operational overhead increasing.
INTERVENTION
Designed and built unified subscription platform; established system architecture across content, billing, and delivery; transitioned platform through multiple iterations (PWA → modern stack); assumed ongoing CTO role.
SYSTEMS TOUCHED
Web platform architecture, subscription and billing systems, content delivery pipelines, operational tooling and reporting.
RESULT
Unified user experience. Reduced operational friction. Stable platform supporting ongoing growth. Continued evolution under active stewardship.
View case study
Operational System Repair — Small Business
Anonymized · Local service business
A local service business with disconnected tools and manual workflows. Intake, scheduling, and customer communication were fragmented. High overhead, slow response, lost interactions.
Consolidated toolset. Implemented structured intake and scheduling flow. Simplified the operational surface.
RESULT — Reduced manual work. Faster response time. Clear operational flow.
Westside Shipping — Website Design and Rebuild
westsideship.com · Shipping and logistics
CONTEXT
Established shipping company with an outdated web presence that no longer reflected the scope or professionalism of the operation.
PROBLEM
The existing site understated the business. Service offering was unclear, visual presentation was dated, and prospective customers had no clear path to engage.
INTERVENTION
Full website redesign and rebuild. Clarified the service structure, modernized the visual presentation, and built a site that accurately represents how the business operates today.
RESULT
A clean, direct web presence that reflects the quality of the operation and gives customers a clear way in.
Field Recorder — An Instrument for the Bureau's Own Fieldwork
Internal engagement · 2026 · Systems / Product / AI
CONTEXT
An internal CLI transcription script kept drawing requests for a version without the terminal.
PROBLEM
No transcription product met the practice's three requirements at once: on-device confidentiality, speaker attribution, and output built for machine retrieval.
INTERVENTION
Defined the output artifact as a versioned standard, Record Format Revision 1, then built the standard's reference implementation: a self-contained Windows tray application, specification-driven and executed with Claude Code.
SYSTEMS TOUCHED
On-device transcription and diarization pipeline, application packaging and distribution, published data format.
RESULT
Field Recorder v1.0.0 shipped in one week and six and a half hours of working time, released under Apache 2.0 and in daily use inside the practice.
View case study
Additional engagements are documented as they are released.