Node.js and TypeScript development
I build and fix Node.js and TypeScript backends, APIs and tools. Some of my clients have no developer, others bring me in to help their team.
I'm all in on AI, so the work goes fast. I stay careful with the code and with what goes live.
I usually reply within one working day.
What I do with Node.js
Backends, integrations and tools in Node.js and TypeScript.
APIs and backends
REST APIs with Express or NestJS, user accounts, payments, queues and the database behind them.
Integrations
Connections to payment providers, CRMs, booking systems and other APIs, with webhooks and logs.
Existing Node.js apps
Slow endpoints, memory problems, old packages or code nobody wants to touch. I find the cause and fix it.
TypeScript
Moving JavaScript code to TypeScript step by step. Mistakes then show up before your users see them.
CLI tools and scripts
Command-line tools and scripts in Node.js and TypeScript for your team, your builds or your data.
AI features
Chat, extraction, summaries and assistants with OpenAI, Anthropic or Google models. The output is checked before anything uses it.
How I work
You don't need to have everything figured out before we talk. An idea, access to the repo, a screen recording or a list of problems is enough. I look at what is there, tell you what I would do and what it costs, and then I build it.
I use Claude Code, Codex and my own agent workflows for reading code, planning changes, writing tests, refactoring and debugging. It is not vibe coding. It is senior engineering with a much faster loop.
AI-first, in TypeScript too
Claude Code and Codex work well with TypeScript. I use them for code, tests and refactoring, and I read and test every change before it goes live.
I stay in control
AI writes a lot of my code. I still make every technical decision, read every change before it ships, and test it. Fast, but meticulous: the speed is only worth something if what goes live is right.
The way you want to work
Some clients want to look at every change before it goes live, others want me to deploy. Some want a weekly call, most prefer written updates. I work well asynchronously, and I still ask the important questions when they come up.
I think like an owner
I still run my own online products. So when I build or fix yours, I think about traffic, conversion, revenue and support as much as about the code, and I tell you when something is not worth building.
Ways to work with me
Fixed price, a flat monthly rate, or hourly. It's always me doing the work, not an agency. If you're not sure, describe what you need and I'll suggest one.
Examples of my work
One of these is my own Node.js tool. The other two are Laravel projects with the same kind of backend work.
Writing and image pipeline
A command-line tool that turns briefs and source material into reviewed text, images and product assets. Every step includes a review.
Booking provider integration
A second booking-provider integration for a healthcare SaaS, with OAuth staff login, data sync, appointments, webhooks and tests. The live product kept running the whole time.
Two backends merged into one
A PHP backend and a Ruby on Rails backend moved into one app as a drop-in replacement. Monthly hosting costs fell from four figures to about $150.
What clients say
"He then built exactly what was needed and kept us informed throughout. Communication was clear and proactive at all times."
"Vincent does not just close tickets, he thinks through the product, the edge cases, and the customer impact."
"Vincent was easy to work with and produced high-quality code. Would recommend."
Questions
Do you only work in Laravel?
No. Most of my client backends are Laravel. I also work in Node.js and TypeScript when your product already uses them.
Can you take over an existing Node.js app?
Yes. I read the code, tell you what I would change first, and then fix the most important things.
Express, NestJS or something else?
I keep what you already use. For a new service I suggest the simplest option your team can maintain.
Should we move from Node.js to Laravel?
Usually not. Moving a working backend costs a lot. I only suggest it when it saves money or trouble.
How do you charge?
Fixed price for a job with a clear outcome, a flat monthly rate for ongoing work, or hourly. Describe what you need and I'll suggest one.
Get a quote
What the app does, where it stands today, and what you need. A few sentences are enough. I'll reply with what I would do and what it would cost.
If you would rather talk first, book a 30-minute call or email contact@vincentschmalbach.com.