Skip to content
Bernhard Götzendorfer

Implementation · Full solution

From prototype to production — at record speed.

I build the complete solution: architecture decisions, code, integration into your system, tests and handover. Typically 80–200 h. All documented.

OUTCOME

What I deliver

Production-ready code with tests. Multi-agent setup when needed. Full integration into your systems (APIs, databases, third-party tools). Live deployment incl. monitoring. Handover training for your team. Documentation that stays maintainable.

Typical, depending on complexity.

Kick-off → prototype (fast) → validation → handover. Fixed or time-and-material — your call.

HOW I WORK

How I build

I use Claude Code with multi-agent setups to build prototypes in days rather than weeks. The LLM agent handles boilerplate, tests, and documentation — I decide on architecture, review the diff, and roll out. Every commit is readable, every test runs, every decision is traceable in the repo.

Example

From specification to pilot kick-off in three minutes

Client project onboarding typically takes four to eight weeks to get off the ground. With a simple tool chain, the first productive exchange happens in minutes — not in theory, but reproducibly.

  1. 45 s

    Create the project container

    Claude Project: set name, system prompt ("Reply only using sources from the uploaded documents."), and team access.

  2. 30 s

    Pull in the specifications

    Three PDF documents (tender, technical specification, framework agreement) via drag-and-drop. Summary appears automatically.

  3. 30 s

    Load the pricing table

    CSV with line items and market prices. First calculation as a bar chart with variance commentary.

  4. ongoing

    Container grows with the project

    Every new document, request, and meeting record lands in the container and is linked with context. After one week: a fully searchable project history with sources.

What changes afterwards

  • Every answer in client interactions has a source reference — no statements without evidence.

  • Project onboarding time: from weeks to days, because the container carries the learning curve, not the individual.

  • Handover during leave or role changes without knowledge loss — the container is the documentation.

  • Scalable to all knowledge-intensive processes: tenders, supplier evaluations, HR onboarding, compliance reviews.

What this requires in your organisation

The tool chain itself is trivial — the lever is the champion who establishes it for their area. Implementation takes two to six weeks with a pilot project. Start with an area where the recurring task is measurable.

Book a 30-min call

PROCESS

How your project runs

  1. 01

    Kick-off & tech-stack planning

    Which tech? Database? Hosting? Auth? LLM provider? We settle these decisions before the first commit lands.

  2. 02

    Prototype build (1–2 weeks)

    Fast iterations: build MVP features, validate with test data, incorporate feedback. You see progress every 2–3 days.

  3. 03

    Validation & production

    Write tests, cover edge cases, remove performance bottlenecks. Real data, real load. All green.

  4. 04

    Live & handover + documentation

    Deployment into your production. Monitoring set up. All levers explained. Your team can turn them themselves.

REFERENCES

Built & live

BitGN Hackathon — 1st place (2026-04-11)

  • Vercel AI SDK
  • Anthropic SDK
  • TypeScript
  • ConnectRPC

Autonomous agent with prompt-injection defence (Soft-SGR + 5-layer hardening). Scoring based on observable side effects. 3-h build window, eval against 104 tasks.

BuchhaltGenie — OCR pipeline (+71% accuracy)

  • Next.js
  • Supabase
  • Stripe
  • OpenAI

AI-assisted accounting for Austrian companies. Multi-agent architecture (read/validate/post). Customer saves 15+ h/month of data-entry work.

Ready to build your system?

30-minute intro call. Afterwards you know whether it fits.