You will get an honest assessment of your codebase, and a plan to make it shippable
Project details
You inherited a codebase, or generated one fast, and now nobody can tell you whether it is fine or a liability. The developer who wrote it is gone, or it was an agency, or it came out of an AI tool in a weekend and worked until it did not.
I read it and tell you the truth.
What you get:
• A written assessment: what the code does, how it hangs together, and where the bodies are
• Findings ranked by real risk, not by style. Data loss, auth holes, silent failures and scaling walls first. Formatting opinions last, clearly labelled as such
• A keep, fix, or rewrite call per area, each with a rough cost in developer days
• A straight answer on the question you actually have: can we build on this, or are we starting over
On the paid tiers I do the work as well: fix the dangerous items, add the tests that were missing, get CI running so the next change is safe to make.
I will not pad the report. If the code is decent, I say so and you have paid for peace of mind rather than a rescue.
Background: twenty years building and maintaining production systems, in TypeScript, Python, Clojure and more languages than I want to list.
I read it and tell you the truth.
What you get:
• A written assessment: what the code does, how it hangs together, and where the bodies are
• Findings ranked by real risk, not by style. Data loss, auth holes, silent failures and scaling walls first. Formatting opinions last, clearly labelled as such
• A keep, fix, or rewrite call per area, each with a rough cost in developer days
• A straight answer on the question you actually have: can we build on this, or are we starting over
On the paid tiers I do the work as well: fix the dangerous items, add the tests that were missing, get CI running so the next change is safe to make.
I will not pad the report. If the code is decent, I say so and you have paid for peace of mind rather than a rescue.
Background: twenty years building and maintaining production systems, in TypeScript, Python, Clojure and more languages than I want to list.
Programming Languages
JavaScript, Python, TypeScriptCoding Expertise
Performance Optimization, SecurityWhat's included
| Service Tiers |
Starter
$600
|
Standard
$1,400
|
Advanced
$3,000
|
|---|---|---|---|
| Delivery Time | 5 days | 10 days | 21 days |
Number of Revisions | 1 | 2 | 3 |
Number of Pages | 1 | 1 | 1 |
Design Customization | - | - | - |
Content Upload | - | - | - |
Responsive Design | - | - | - |
Source Code | - |
Frequently asked questions
About Jan Hein
AI Agent and LLM Architect - RAG, MCP, TypeScript, Python
Rotterdam, Netherlands - 1:32 am local time
Behind that: 20+ years as a software architect (PhD) and founder/CTO of several startups. I have been shipping LLM-based workflows since 2019, well before the current wave, and I take ownership of the outcome, not just the tickets.
What I do:
- AI agents and LLM integration - multi-agent architectures, tool and function calling, MCP servers, agent orchestration
- RAG and knowledge infrastructure - retrieval pipelines, embeddings, organisational memory that stays accurate
- Architecture and technical review - is your approach going to survive production? Build-vs-buy, scaling, cost
- Rescue and take-over - inheriting a half-finished codebase and making it stable and shippable
- Full-stack and DevOps - polyglot: TypeScript/Node/Bun, Python, Elixir, Clojure; containers, IaC, CI/CD, self-hosted deployment
How I work:
I am senior enough to work unsupervised. I have been the CTO, so I can own a system end to end or drop into an existing team and stabilise it. I will tell you when the thing you asked for is not the thing you need.
Based in Taipei (UTC+8) - full working-day overlap with Asia-Pacific, and mornings overlap with Europe. Contracted through my Dutch company: proper invoicing, contracts and IP assignment.
Available 15-20 hrs/week, starting immediately.
Steps for completing your project
After purchasing the project, send requirements so Jan Hein can start the project.
Delivery time starts when Jan Hein receives requirements from you.
Jan Hein works on your project following the steps below.
Revisions may occur after the delivery date.
Read the code the way the next developer would
I go through the repo start to finish: structure, data model, auth, error handling, tests, dependencies and deploy path. No tooling verdicts, no lint report dressed up as an audit. I read it.
Separate the dangerous from the merely ugly
Most code that looks bad is survivable. I rank findings by what can actually hurt you: data loss, security holes, silent failures, things that will not scale. Style opinions go at the bottom, clearly marked.