◆iainbuilds.dev
Available

Systems that make messy work usable.

Software developer. Backend, AI workflows, internal tools.

Software systems, internal tools, and AI-assisted workflows. Built to turn complex ideas into structured, usable products.

View Systems Get in Touch

Status

Availability Open to work
Based in Goleta, California
Open to Remote / Hybrid / Local
Focus Backend, AI workflows, tooling

Core Capabilities

Backend & Systems
PHP · MySQL · Queue / Worker Patterns · Session Management · Modular Architecture · Internal Tools
AI Workflows
Prompt Pipelines · Multi-Stage Generation · Constraint-Based Systems · Structured Outputs · Model Orchestration
Product Thinking
System Design · Maintainability · Iteration Cycles · Workflow Design · Refactoring

Backend, AI workflows, and practical product thinking. The overlap is the point.

Systems 5

SYS / 001 Featured

Modular Content & Narrative System

Branching content, structured as relational data. Expandable without rewriting the app.

Context
Built to support expandable content systems without rewriting application logic each time new content, choices, or rules were added.
What Was Built
  • Relational scene, choice, and effect structure with PDO-based queries
  • Database-driven content management replacing hardcoded arrays
  • Expandable architecture for new content types and conditional rules
  • Admin interface for non-developer content editing
How It Works
Content is stored in related tables and assembled dynamically based on structure, conditions, and user state. Adding new content is a data operation, not a code operation.
Shows
PHP MySQL Data Modeling Backend Systems Admin Tooling
SYS / 002 Featured

Multi-Stage AI Workflow Pipeline

Staged AI pipelines. Each step does one job. Failure is debuggable, not mysterious.

Context
Used to turn messy source material into consistent, formatted outputs across repeated content tasks. Built after the one-giant-prompt approach kept producing inconsistent results.
What Was Built
  • Extraction, transformation, and formatting pipeline with defined stage boundaries
  • Reusable prompt structures versioned as templates
  • Stage-level output validation and fallback handling
  • Multi-model orchestration where each stage uses the right model for the job
How It Works
Instead of asking one prompt to do everything, each stage has a clear job. Output from one step feeds the next. When something fails, you know which stage.
Shows
AI Workflows Prompt Engineering Pipeline Architecture System Design Automation
SYS / 003 System

Content Automation System

One-off creative work, systematized. Consistency at scale through constraints.

Context
Built to scale recurring content work without relying on manual repetition or inconsistent formatting across hundreds of outputs.
What Was Built
  • Template-based generation with strict structural constraints
  • Rule-driven output formatting and validation
  • Anti-repetition logic to prevent duplicate outputs across sessions
  • Reusable patterns that enforce consistency automatically
How It Works
Inputs move through a constrained process with templates, rules, and formatting logic. The constraints guarantee consistency while allowing variation where it matters.
Shows
Automation Process Design Systems Thinking Scalability Constraint-Based Generation
SYS / 004 System

Backend Refactoring for Maintainability

Refactors driven by real friction. Safer change through better boundaries.

Context
Applied when a growing codebase became harder to maintain due to tightly coupled logic, duplicated decisions, and repeated edits across files.
What Was Built
  • Core logic separated into smaller, single-responsibility components
  • Reduced cross-component dependency and shared mutable state
  • Clearer boundaries between data access, business logic, and presentation
  • Improved organization for safer feature additions
How It Works
Core logic was broken into focused components so features could evolve with less risk. Driven by actual friction, not speculative architecture.
Shows
Refactoring Maintainability Architecture Problem Solving Code Organization
SYS / 005 System

Internal Tools for Workflow Efficiency

Small tools that eliminate the ten-minute manual task done fifty times a month.

Context
Used to reduce friction in recurring workflows — the quiet time-sinks that eat the week.
What Was Built
  • Workflow-specific tools with clear inputs, outputs, and validation
  • Reduced manual updates and repeated transcription steps
  • Improved consistency across recurring tasks
  • Lightweight enough to modify as workflows evolve
How It Works
Manual processes became lightweight tools. Each one solves a specific problem. The work becomes repeatable, faster, and less error-prone.
Shows
Internal Tools Efficiency Workflow Design Practical Development Iteration

Method

Start by identifying what should stay manual and what should become repeatable. Break the problem into smaller parts, build the simplest working version, and refine where the friction actually shows up.

When AI tools are involved, treat them like parts of a workflow, not a magic box. Different steps do different jobs. The output is easier to control, improve, and reuse.

The goal isn’t to finish a task once. It’s to build a system that makes the next version easier.

Principles

Break problems into systems
Reusable structure before polish.
Build from real friction
Refactors come from something concrete breaking down.
Use AI as workflow infrastructure
Staged workflows, not one giant prompt.

Available

Status Open to work
Roles Software, backend, systems, AI workflows
Email me

Interested in roles where backend systems, structured workflow design, and practical problem solving matter.