Fixed-scope engagements, and one that runs every week.

I design and install an AI-assisted development workflow that fits how your team already works, then train the team to run it. The shape depends on your needs: which models and tools you have access to, how strict your review process is, and where the mechanical work is piling up. One configuration I run daily: eight Claude Code agents pick up GitHub issues, design, build, and test the change, a reviewer agent checks every pull request, and OpenAI Codex gives high-risk changes an independent second opinion. Whatever the tools, the principle holds: agents do the mechanical work, a second model challenges it, and nothing merges without a person signing off.

Senior technical direction one to three days a week, without a full-time hire.

A standing engagement for teams that need an architect's judgment on a steady cadence. As your fractional software architect, I own architecture decisions, set engineering standards, review the risky changes, and bring in AI-assisted development workflows with human review built in, while your team keeps shipping.

Engagement shape: One to three days a week on a monthly retainer. Month to month by default, cancel with two weeks' notice; a fixed term is available when you want a committed engagement.

A structured review of an existing codebase, delivered as a roadmap you can act on. I look at how the code is organized, typed, tested, and shipped, from the React components down to the Node.js services, API contracts, and data model, then tell you what to change, in what order, and why. Where micro frontends, atomic design systems, packaging, or a better data layer would pay off, I say so; where they would not, I say that too. Many audits continue as a Fractional Architect engagement; the audit fee is credited toward the first month.

Hands-on implementation across the stack: React and Next.js on the front, Node.js services, REST APIs, and the database behind it, all in TypeScript. I work inside your process, ship production code in reviewable pull requests, and leave behind patterns your engineers can keep extending after I am gone. It does not have to be a whole system: I also take on a scoped piece of a larger project, a feature, a module, an integration, and deliver it to the same standard.

Backend services in TypeScript on Node.js, for teams that want one language and one set of patterns across the stack. REST APIs with typed contracts the frontend can rely on, real-time messaging over WebSockets, data models in SQL or document databases, and multi-tenant authentication with organization-level access control and SSO. Postgres with Prisma is my default pairing, not a requirement; I work with what you already run.

A hand-built component library using atomic design: atoms through organisms to full page templates. Accessible and internationalized from day one, so a UI change lands in one place instead of fifty and every product looks like it came from the same team.

Your product, extended to the desktop and to phones. Electron desktop applications run your React code as-is, with real-time messaging, system-tray presence, and a release pipeline that ships signed, certified builds for Windows and macOS. React Native mobile apps share what can be shared with the web app, business logic, state, API clients, and types, while the UI stays native to the platform.