Mobile · Web · Full-stack · AI · Real-time · Geospatial

Engineered software systems for products that have to ship and stay running.

MFB Services, Inc. builds AI-augmented platforms, real-time and geospatial dashboards, B2B SaaS, and mobile apps. A decade of TypeScript across the energy industry and a growing roster of outside clients — production-grade work, end-to-end ownership, no agency layers.

iOS React React Native Next.js TypeScript Node.js NestJS GraphQL PostgreSQL Mapbox OpenAI Claude Supabase Firebase Docker Kubernetes
Dark office desk with a computer monitor, keyboard, and premium minimalist workspace lighting.
Built for software that has to look sharp, move fast, and survive real use.
Production-grade scale Codebases owned and maintained across years of feature growth — including ones with 10K+ commits and live production load.
Direct collaboration Senior engineering, architecture, and product judgment handled directly. No agency layers, no junior handoffs.
TypeScript-first, observable Typed, tested, instrumented (logs, traces, error tracking) so the system stays maintainable from day one through year three.

Capabilities

Focused expertise across the digital stack.

The work stays concentrated on products and systems that require strong architecture, product-grade interfaces, and serious implementation discipline.

AI & LLM Products

LLM-powered chat platforms, document Q&A, voice-first data capture, IDE assistants, and agent workflows. OpenAI, Azure OpenAI, Anthropic Claude, LangChain, and the Model Context Protocol — shipped to production, not stuck in demo.

Full-Stack Web Apps & SaaS

React + TypeScript on the front, Node / NestJS / Apollo GraphQL on the back, PostgreSQL + Redis underneath. Monorepo-organized (Nx, Turborepo) so teams can ship in parallel without stepping on each other.

Real-time & Geospatial Dashboards

Live equipment status, well analytics, type-curve forecasting, fleet and asset tracking — built on Mapbox GL, Deck.gl, Turf.js, AG Grid, amCharts, and battle-tested WebSocket and PubSub stacks.

Mobile Apps — iOS and Android

One Expo + React Native codebase, native-feeling on both stores. NativeWind styling, Reanimated motion, Expo Router navigation, Supabase or Firebase backends, and a Next.js admin portal where it earns its keep.

Identity & Access Platforms

Multi-tenant OIDC authorization, role / scope / organization rules engines, real-time security event streams, and the published libraries to drop them into every app in your fleet.

Component Libraries & Design Systems

If your team rebuilds the same drawer, modal, or grid in every app, that’s a problem worth fixing. Author and maintainer of internal React libraries; open-source contributor on dnd-kit and react-use-audio-player.

Selected Work

Real systems. Real production load.

A mix of long-running enterprise platforms and outside-of-day-job client work. Each one shipped, each one used by people who depend on it.

Enterprise · Energy

AI-augmented document & conversation platform

Apollo Federation GraphQL backend with Anthropic Claude integration; multi-app frontend with embedded chat, document viewers, edge-synced document storage; OneDrive integration; and an IntelliJ IDEA plugin streaming Claude / GPT / custom-model responses inside the IDE.

TypeScript · React · NestJS · Apollo · Prisma · Postgres · Anthropic · Azure OpenAI · PDFTron · Kotlin
Enterprise · Energy

Multi-tenant identity & access platform

An OIDC-based authorization platform with a rules engine, admin UI, and a real-time WebSocket event stream that pushes authorization changes without polling. A four-app proof-of-concept matrix demonstrated authorization parity across user contexts and domain models.

TypeScript · React · Express · OpenID Connect · resilient WebSockets · Nx · Kubernetes
Enterprise · Energy

Well analytics & type-curve forecasting

Long-running React rewrite of a legacy well-productivity analytics tool. Type-curve generation and forecasting, Mapbox + Deck.gl visualizations, Cypress E2E integrated with the team’s workflow tracker, and PR-preview release pipelines.

TypeScript · React · Mapbox GL · Deck.gl · Recharts · Express · Cypress · Nx
Client · B2B SaaS

JustLockIt — document & transaction locking

Full-stack SaaS for document and transaction locking. Built the SPA, auth flows, profile and subscription UI, and the Node/TypeScript backend. Stripe payments, Sentry-monitored, deployed on Heroku.

React 18 · Vite · Redux Toolkit · Firebase Auth · MUI · Stripe · Vitest · Sentry · Heroku
Client · Nonprofit

Tiny Paws Rescue — mobile app + admin portal

Browse adoptable dogs, submit applications, receive donations, and let staff manage the back office. Built end-to-end: cross-platform mobile app, Next.js admin portal, and Supabase data layer with edge functions.

Expo SDK 54 · React Native · NativeWind · Reanimated · Next.js 15 · Supabase · Firebase Analytics · Sentry
Open Source

dnd-kit & react-use-audio-player

Contributor on dnd-kit, the modern accessible React drag-and-drop toolkit (hooks-based API, multiple collision-detection algorithms, keyboard navigation, zero external dependencies). Author and maintainer of react-use-audio-player on npm — an idiomatic React hook for audio playback built on howler.js.

React · TypeScript · Cypress · Storybook · Lerna · Changesets · howler.js

Approach

Simple process. High bar. No wasted motion.

The engagement model is intentionally direct: understand the problem, prove the riskiest part first, and ship something considered from architecture to interface.

Spike the hardest thing first If there’s a load-bearing technical risk — a third-party integration, an LLM cost question, a real-time concurrency assumption — prove it works before everything else lands on top of it.
Thin vertical slices over half-finished layers End-to-end working features over horizontal half-built layers. You see something usable each week. The codebase stays deployable from day one.
TypeScript-first. Tested. Instrumented. Everything ships typed, tested where it matters, instrumented with logs, traces, and error tracking, and structured so a second engineer can pick it up cleanly.
Knowledge transfer is part of the deliverable You get a README that explains the why, an architecture diagram, and a walkthrough — not a black box only the original author can maintain.

Why MFB

Serious engineering without the usual agency drag.

The work stays direct, technical, and production-minded from first conversation through launch — and through year three.

01

10+ years inside the energy industry — systems that have to work, all the time, for engineers who don’t tolerate hand-waving.

02

Owns code at scale. Codebases with 5K, 10K, even 35K+ commits kept alive across years of feature growth — treated as products, not projects.

03

Author of published React libraries adopted across an entire enterprise. Open-source contributor on dnd-kit and react-use-audio-player.

04

Build quality that hits design, performance, and business pressure at the same time — with a finished product that feels materially better than the usual agency output.

About

One senior engineer. End-to-end ownership.

MFB Services, Inc. is the company side of Rudy Sanchez — a senior full-stack engineer with a decade of production work inside the energy industry and a growing roster of outside clients. Most engagements come in as “we have a hard problem, we don’t want to staff three vendors to solve it.” That’s the comparative advantage: one person who can take a brief through GraphQL schema, frontend UX, observability, and deploy — and stay through year three.

Based in Texas Working with US clients across time zones; long-form async by default, calls when they pull weight.
What I take on AI-assisted products, B2B SaaS, real-time and geospatial apps, mobile, and the architecture audits that tell you whether to keep building or restart.
What I don’t Greenfield .NET, Java/Spring, Rails, or PHP. I’ll work alongside them when there’s an existing system — I won’t lead one.
How engagements work Discovery is fixed-fee. After that, fixed-fee per phase if the scope is well-defined; hourly retainer if it’s exploratory or ongoing.

Contact

Start the next build.

Use the intake page if you want a structured start, or send a direct email if you already know what needs to be built. Reply window is one to two business days — with a one-page brief back if it’s a fit.

Open Contact hello@mfbservices.inc Response window: 1 to 2 business days