Services
Production web apps, from database to interface.
Senior full stack engineer. 20 years in production. 200+ client sites shipped. I write the code, own the architecture, and hand you something that works in production, not just in a demo.
Let's talk about your buildSolo senior engineer means one person who knows the whole system. No handoff between a frontend team and a backend team. No "that's not my part."
What I build
Web applications
Full-stack apps from scratch. Next.js on the frontend, Node.js or FastAPI on the backend, Postgres or Supabase underneath. Built to be extended, not rebuilt in 18 months.
Internal tools and dashboards
If your team is living in spreadsheets or waiting on a developer to pull a report, that's a fixable problem. I've built BI dashboards sitting on millions of rows that return in under 200ms.
APIs and integrations
Third-party APIs, webhooks, OAuth flows, data sync between systems. If two tools in your stack don't talk to each other, I've probably already wired that connection somewhere.
Legacy rescues and migrations
Old codebase, no documentation, last developer gone. I've started from a SQL dump and a zip file more than once. It's not glamorous work, but I know how to do it without breaking things further.
Some of what I've shipped
Built a BI dashboard for a 3PL fulfillment operator: 2.26M+ transactions, $7.79M in revenue tracked across 56 clients. Next.js frontend, Flask API layer, BigQuery underneath — 19 endpoints over 18 SQL views, sub-200ms on the heavy queries.
9 FastAPI microservices handling live EDI X12, AS2, and SFTP retailer onboarding — QVC/Rithum, Tractor Supply, Cin7, ShipStation. Durable workflows via Temporal.io, so a failed step retries itself instead of taking down the platform.
citadevisa.com — Next.js 15, Strapi v5, Stripe billing, multi-role auth. Live in production with paying customers since 2024. I own the whole lifecycle: I built it, and I still run it.
Stack
Frontend
- React
- Next.js
- TypeScript
- Tailwind CSS
- Radix UI
- shadcn/ui
Backend
- Node.js
- Python
- FastAPI
- tRPC
- REST
- WebSockets
Databases
- PostgreSQL
- MySQL
- Supabase
- BigQuery
- Redis
- Prisma
- Drizzle
Infrastructure
- GCP (Cloud Run, GKE, Pub/Sub, BigQuery)
- Docker
- Terraform
- Vercel
Testing and observability
- Vitest
- Playwright
- Sentry
Payments and auth
- Stripe
- Chargebee
- OAuth 2.0
CMS and e-commerce
WordPress (custom themes, plugins, WooCommerce), BigCommerce (Stencil, Handlebars, Storefront and Catalog APIs), Shopify (Liquid, headless), and HubSpot CMS. Six-plus years on BigCommerce. 100+ WordPress builds shipped, building on WordPress since version 1.5.
How it works
You explain the problem, not the solution.
Tell me what's broken, slow, or missing. I'll figure out the right build. If a simpler approach exists, I'll tell you before we write a line of code.
I scope it clearly.
Fixed-scope or milestone-based, depending on what's defined. You get a plain-English breakdown before anything starts. No surprise invoices.
I build it and you can see it moving.
Staging environment from day one. You're never waiting weeks for a first look. I ship incrementally and I explain what I'm doing.
A few things worth knowing
20 years shipping production software — 200+ client sites, 100+ WordPress builds among them. Microsoft Certified: Azure AI Engineer Associate. B.Eng. Computer Systems Engineering & MIS, Universidad Tecmilenio. Based in Tamaulipas, Mexico, working US business hours. Bilingual English and Spanish.
I've been the sole engineer on systems handling millions of records, and the only developer maintaining a 13-year agency's entire client base. I work well without hand-holding, but I stay communicative.
FAQ
Do you build the frontend and the backend, or just one side?
Both. I'm equally comfortable in a Next.js interface and the FastAPI or Node.js layer behind it — one engineer owns the whole stack, so nothing gets lost between a frontend team and a backend team.
Can you take over a project someone else started?
Regularly. I audit the existing codebase and data model first, in writing, then tell you honestly what's worth keeping and what needs to be rebuilt — not a blanket rewrite by default.
Do you build custom integrations with our existing tools?
Yes — EDI X12/AS2, Cin7, ShipStation, QuickBooks Online, Stripe, and general REST/webhook APIs. If it has an API or a spec document, I can build against it.
Do you handle the database design, or just the interface?
The database design is usually where a system succeeds or fails long-term. I model it first — Postgres, MySQL, or BigQuery — then build the API and interface on top of it.
Do you do fixed-price work or hourly?
Fixed-scope or milestone-based, depending on how well-defined the project is. You get a plain-English breakdown before anything starts — no surprise invoices.
What if I need AI added to this later?
That's a separate discipline I also work in — see AI Consulting & Development. Most of the platforms I build integrate cleanly with an AI layer later, because the data model was designed to support it.
Who maintains it after launch?
I do, under retainer if you want ongoing support. The platforms above run in production today — infrastructure included.
Is there a minimum project size?
Full-stack work generally starts around $5,000 — smaller builds are usually better served by a template, and I'll say so if that's the case. Send it anyway; the budget-range question on the contact form helps me answer honestly and fast.
Need the AI layer on top of this? That's the AI Consulting & Development side.
Ready to build something?
Tell me what you're working on. I'll tell you honestly whether I can help, how long it'll take, and what it'll cost.
I reply within one business day.