AI-Native Workflow Setup
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 have built: Claude Code agents pick up GitHub issues, implement the change, and run the test suite, while GitHub Copilot reviews every pull request as 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.
What you get
- Workflow design matched to your repository, review process, and tooling
- Agent configuration, MCP servers, and subagents using Claude Code, Copilot, or the tools you have
- Cross-model review so one model's blind spots are caught by another, with people making the call
- Model routing and cost reporting so AI spend stays proportional to value
- Team training sessions and a written playbook
Architecture Audit
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.
What you get
- Written assessment covering frontend architecture, API design, data model, typing, testing, and CI/CD
- Prioritized roadmap with effort and risk for each step
- Recommendations on micro frontends, design systems, packaging, and data layers
- Readout session with your engineering leads
Modernization & Build
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.
What you get
- Production features or migrations delivered in reviewable pull requests
- Scoped pieces of a larger project: a feature, a module, or an integration your team hands off
- Legacy-to-modern migrations that keep the old system running until the new one is ready
- API and data-layer work alongside the UI: Node.js services, REST endpoints, and data models in whatever database you run
- Typed contracts, composable data layers, and tests as part of the work
- Documentation and a handoff your team can build on
Node.js Backends & APIs
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.
What you get
- Node.js services with typed REST contracts shared with the frontend
- WebSocket and real-time messaging with reconnection handling
- Schema design and a typed data layer with migrations, in Postgres and Prisma by default or your existing database
- Multi-tenant authentication, organization-level access control, and SSO
- CI/CD and environment configuration for Vercel or your own platform
Design Systems
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.
What you get
- Component library with design tokens, theming, and light and dark support
- WCAG AA accessibility and i18n built into every component
- Packaging and versioning so each app pulls in only what it needs
- Living documentation and contribution guidelines
Desktop & Mobile Apps
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.
What you get
- Electron application architecture on a shared React codebase
- React Native mobile app sharing business logic, state, API clients, and types with your web app
- Real-time messaging over WebSockets with reconnection and offline handling
- System tray, native notifications, and auto-update on desktop
- Signed installers and a CI/CD pipeline for Windows and macOS releases
Terms that fit the work
Short or long
A two-week audit, a three-month build, or an ongoing retainer. Length and terms are negotiated around the work, not the other way around.
Direct, no middle man
You work with me, not an agency or a recruiter. No markup on the rate, and the person on the call is the person doing the work.
1099 or W-2 contract
Fixed-scope proposals, hourly, or a contract through your payroll. Whatever your procurement needs, we can make it work.
Not sure which engagement fits?
Most work starts with a call and a conversation about where things hurt. I will tell you which of these fits, or whether something smaller would do.