Your fragile business processes become robust systems your whole team can rely on.

You end up with software that works the way it should and holds up over time.

Custom, AI-enabled websites and apps, built and cared for after launch.

Start a conversation

How I think about systems

Most business software is built to prove a concept or chase a deadline. It works until it doesn't. Then someone calls it "technical debt" and moves on.

I build software that's meant to run for years. That means different choices:

  • Owned infrastructure over rented platforms. You control the system. You're not locked into someone else's roadmap or pricing.
  • Simplicity over clever abstractions. Straightforward code is easier to understand, fix, and extend.
  • Documentation that reflects reality. If the runbook says "do this," it works. If monitoring fires, you know why.
  • Graceful handling of edge cases. Systems fail. Good systems fail predictably and recover cleanly.
  • Stewardship, not just delivery. Launching the system is the beginning, not the end.
Most software is built to work once. I build software that's meant to work repeatedly, reliably, for years.
Keith Pelchat

What working together usually looks like

Engagements vary based on scope, risk, and responsibility. Most work falls into one of these patterns.

Fast Build

Small, bounded work. A data migration. A one-time integration. A proof-of-concept to test an assumption. Fixed scope, delivered quickly.

Fixed scope • Delivered quickly

Production System

A real system. One primary workflow. Authentication, admin panel, the infrastructure to support it. Usually AWS. Usually 8–12 weeks from kickoff to launch.

This is where most engagements start.

8–12 weeks • Auth & admin • AWS infrastructure • One workflow

System Program

Multiple workflows. Hardened infrastructure. Continuity planning. Governance. Long-term stewardship. This is what it looks like when software becomes a pillar of the business.

14–18+ weeks • Multi-workflow • Hardened infrastructure • Stewardship

Clear boundaries

What this is

  • Custom software for specific business processes
  • Infrastructure you own (AWS-first, no platform lock-in)
  • Systems built to last years, not months
  • Clear scope and realistic expectations
  • Direct relationship, no intermediaries
  • Web apps that install on phones and desktops (PWAs)
  • AI-enabled: every site includes Visibility, built to be found by AI search tools, with AI chat, search, voice or automation added as needed

What this isn't

  • Consumer SaaS products
  • Native App Store apps
  • Hourly consulting or staff augmentation
  • "We do everything" consulting

The goal is reliability, not velocity at all costs.

How engagements usually work

1

Figure out if we're a fit

Initial conversation. What's the problem? What's been tried? Does this match the work I do? These questions help us both see quickly whether I'm the right fit.

2

Define scope and timeline

Document what gets built, what doesn't, who owns what, and when it happens. Written agreement before any work starts.

3

Build the system

Regular check-ins. You see progress. Decisions get documented. If scope changes, we re-scope explicitly.

4

Launch to production

Deploy with monitoring. Full handoff: documentation, credentials, runbook. You own it.

5

Ongoing care

Every build includes a monthly care plan: maintenance, monitoring, and updates. You can opt out.

Start a conversation

These questions help us both see quickly whether I'm the right fit.

Current availability: Accepting inquiries. Response within 1-2 business days.

I don't use your contact information for anything except responding to your inquiry. No mailing lists, no follow-up campaigns.