Tests exist but nothing runs them
Claude Code tends to write tests. Without CI they rot within a week. We wire the pipeline so a broken build cannot reach your users.
Claude Code → production
Claude Code writes solid code. Production needs more than code.
You got it to roughly 90% — the idea is visible and it runs. We review what you built with Claude Code, write the missing 10%, and put it live in front of real users. Usually within a week.
You get back the three biggest things standing between your Claude Code build and real users, in writing, within two business days. No call needed. If you want the full version, the fixed-price review is €750 — fixed price, credited back if you continue.
What we usually find in a Claude Code build
Not a criticism of the tool — Claude Code got you further in a weekend than a contractor would in a month. These are just the things it consistently leaves for a human, and they are the things that decide whether your launch holds.
Infrastructure was assumed, not provisioned
The code expects a database, a queue, a bucket. Someone still has to create them, secure them, back them up, and pay for them.
Migrations applied by hand
Schema changes made live during development leave no reproducible path. We get migrations under version control before you have real data to lose.
Nothing is watching it
No error tracking, no uptime checks, no logs you can search. Right now you would learn about an outage from a customer.
The offer
Review at €750. Live from €7,500.
Start with the review: we read your Claude Code build route by route and hand you a written plan with effort and risk on every item. If you continue, the review fee comes off the build. Prices in EUR, excluding VAT. USD invoicing available.
Claude Code to production: common questions
The code is good. What is actually missing?
Usually everything that is not code: provisioned infrastructure, a CI pipeline that runs the tests already written, migrations under version control, secrets separated by environment, error tracking, and a rollback path. An agent writes the application; nobody has yet run the operations.
How do I get migrations under control after applying schema changes by hand?
Snapshot the current schema, make that your baseline migration, and point a fresh empty database at it to prove it reproduces. From then on every change goes through a migration file. Doing this before you have real data is an afternoon; doing it after is a project.
What monitoring is the minimum?
Error tracking with alerts to somewhere you actually read, an external uptime check, and searchable logs with a retention window. Three services, roughly an hour to wire, and it is the difference between finding out from a dashboard and finding out from a customer.
Question not here? Email me — I answer these myself, and I do not need you on a call first.
Built it with something else?
Different tool again, or a mix of several? Tell us what you used — the process is the same.