Selectively Available

Interesting Problems
at the Edge

I like work that uses my skills but stretches what I know. Systems architecture, automation, AI integration—generalist thinking for challenges that don't fit neatly into one specialty.

Not a specialist. A generalist who sees the whole system.

15 hrs/week saved
one integration
12→82% inbox placement
six weeks
20+ years building
on the internet
01

The Toolkit

Broad and deep. The tools I reach for depend on what the problem needs.

Systems & Architecture

  • AWS infrastructure design
  • Database architecture
  • API design & integration
  • Email deliverability systems
  • Automation workflows

AI & Automation

  • LLM integration (Claude, GPT)
  • AI-first workflow design
  • Headless agent systems
  • Prompt engineering
  • Cost optimization

Development

  • JavaScript / TypeScript
  • Node.js / Lambda
  • Python
  • Static site generators
  • Google Apps Script

Strategy

  • Technical architecture review
  • Build vs. buy decisions
  • Vendor evaluation
  • Process optimization
  • Systems thinking
02

What I Build

The kinds of problems I solve best.

System Integration

One client saved 15 hours/week by connecting their CRM to their email platform properly. That's what happens when you stop copying data manually and make your tools talk to each other instead.

APIs Webhooks Data sync

AI Implementation

AI that actually does something useful. Custom agents that handle repetitive work. Workflow integration that cuts costs, not corners. Zero hype, all utility.

LLMs Agents Automation

Email Infrastructure

12% inbox placement to 82% in six weeks. That's what proper warm-up, reputation management, and infrastructure work delivers. The unsexy foundation that makes every campaign succeed.

Deliverability DMARC Warmup

Automation

Manual processes that run automatically with minimal oversight. The kind of reliability where you forget the automation exists—until you realize you haven't thought about that task in weeks.

Workflows Triggers Scheduling

Technical Architecture

Systems that scale without drama. Maintain themselves without begging for attention. The boring, bulletproof foundation that lets everything else work.

AWS Infrastructure Scaling

Technical Audits

Evaluating existing systems. Finding the bottlenecks, the risks, the opportunities. Actionable recommendations you can actually implement.

Review Analysis Roadmap
03

The Process

How projects move from problem to solution.

1

Understand

Deep dive into your problem, constraints, and goals. What does success actually look like? What have you already tried that didn't work?

2

Design

Architect a solution that fits your context. Trade-offs made explicit. No hidden complexity.

3

Build

Implement with attention to maintainability. Code that works now and can be understood later.

4

Transfer

Hand off cleanly with documentation. You own it completely. No lock-in.

04

Engagement Models

How we can work together.

What I Don't Do

I'm selective about the work I take on. Clarity helps everyone.

× Routine maintenance—I build systems that don't need babysitting
× Projects without clear ownership—someone needs to care about the outcome
× "Build it and we'll figure it out later"—that's how tech debt starts
× Unrealistic timelines—rushing creates problems that take longer to fix
× Quality compromises—I'd rather lose the project than ship something broken

Fewer projects done right beats more projects done poorly. Every time.

Good Fit

Projects I take on tend to share these qualities:

✓
At the edge Uses my skills, stretches my knowledge
✓
Well-defined Clear goals and success criteria
✓
Resourced right Budget matches scope
✓
Good people I enjoy working with you

Have an Interesting Project?

Tell me what you're trying to build. If it's a good fit, we'll talk.