Skip to content
Bernhard Götzendorfer
Editorial still-life: open laptop with code, notebook with architecture sketch, espresso and a succulent on a wooden desk

AI-generated

01 /Implementation · Full solution

From prototype to production, in weeks instead of months.

We build what I use myself. Architecture decisions, code, integration into your system, tests, handover. With synthetic data, in weeks. Typically 80–200 fixed-price hours. All documented.

06 /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.

80–200 fixed-price hours

Typical, depending on complexity.

Kick-off → prototype (fast) → validation → handover. Fixed price, confirmed in the intro call.

04 /HOW I WORK

What I use daily

Concrete toolset, no vendor theatre. Six building blocks that appear in every project.

  • Claude Code as daily driver

    Editor and agent in one. Own OSS plugin (session-orchestrator) for structured multi-wave sessions with quality gates.

  • Stack default with clear defaults

    Next.js, TypeScript, Tailwind, Supabase for web. Python with uv for agent pipelines. Swift when mobile is needed.

  • Multi-agent only when needed

    Vercel AI SDK, Anthropic SDK, ConnectRPC are introduced only when pipelines need to run in parallel. No vendor drops for the vendor's sake.

  • Quality gates before every merge

    TypeScript strict, ESLint, Playwright for UI, Pytest for Python. What is not green does not enter the main branch.

  • Version control with audit trail

    GitLab primary, GitHub as mirror, Conventional Commits. Every architecture decision is traceable in the repo.

  • Deployment and monitoring

    Vercel for web, Docker for self-hosting. Sentry for production errors, clear escalation on incidents.

03 /Example

From specification to pilot kick-off in three minutes

Client project onboarding takes four to eight weeks at most companies. With three standard tools, the first productive answers come in minutes. Reproducible, not theoretical.

  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 you'll need for this

The tools themselves are trivial. The difference comes from one person per area who establishes the workflow. Two to six weeks for a pilot project. Start with an area where the recurring task is measurable.

Book an intro call
02 /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 continue developing the solution independently.

07 /Handover & Ownership

Who owns the code? Who maintains it?

Clear answers before you sign.

  • Your code, your repo from day one

    Every sprint commit goes directly into your repository. No vendor lock-in, no withholding.

  • Licences clearly documented

    Open-source dependencies under MIT/Apache 2.0. Proprietary modules listed individually.

  • 30 days handover support included

    Questions after go-live? Included. Beyond that: optional maintenance contract on hourly corridor.

  • Maintainability by design

    ADRs, prompt docs and test coverage so your team can keep building after handover.

05 /REFERENCES

Built & live

BitGN Hackathon: 1st place (2026-04-11, AI Factory Austria)

  • 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: Digital tool for Austrian SMEs (open beta)

  • Next.js
  • Supabase
  • Stripe
  • Vercel AI SDK
  • Gemini OCR

A dashboard that bundles bookkeeping, invoicing, FinanzOnline submissions and time tracking, so SME owners spend less time on administrative overhead and more on the business. Open beta at buchhaltgenie.at. Features: invoices, recurring invoices and delivery notes · create customers, suppliers and products, also directly from chat · bank import with AI-driven categorisation · capture receipts by photo, AI extracts date/amount/VAT · validation against Austrian tax law (UStG/BAO) · FinanzOnline export via XML · Sophie, chat assistant for Austrian accounting · smart insights and cashflow forecast.

03 /Investment

Pricing conversation, not a pricelist.

Concrete pricing discussed in the initial call after scope clarification.

Ready to build your system?

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