AI prototypes · built with Claude Code

    An idea becomes a tool you can try out, within days.

    I build working prototypes and internal tools with Claude Code. You test them with real users and then decide whether to take them further.

    What I buildFlorian Preisenhammer · Munich / Remote
    01What I build

    Three kinds of tools.

    01

    A prototype for your use case

    Clickable and working with real data, so your team and your steering committee can see what the use case actually does. It is the basis for a go/no-go decision.

    02

    An internal tool

    A focused tool for one team, such as an evaluation, a research assistant or a guided form. It takes work off people's hands from the first week.

    03

    A connection to AI assistants

    An MCP server that lets Claude or other assistants use your data and functions, with clear boundaries on what they may read and do.

    02Business units build themselves

    Your teams build small tools themselves, within your governance.

    Many good ideas come from the business units. With Claude Code, people there can build small tools themselves. I help them get started and set the frame, so it stays safe for your organisation.

    Getting started

    A first tool built together, on a real problem from the team.

    Shared rules

    Project guidelines (CLAUDE.md) and building blocks the whole team uses.

    Data protection

    Which data may be used, and where it is processed.

    A clear boundary

    From which point a tool goes to your IT for operation and maintenance.

    03How it runs

    Four steps, then a decision.

    1. 01Clarify the ideaOne conversation about the problem, the users and the data.
    2. 02BuildA few days to a few weeks, depending on scope.
    3. 03Test with real usersWe see what works and what doesn't.
    4. 04DecideDrop it, build it further, or hand it over to your IT.

    Operating a tool in production is your team's job. I hand over with documentation, so your IT can take it from there.

    04Built myself

    Everything here was built with Claude Code.

    Signalwaves

    News intelligence across 500+ sources, as a web app and iOS and Android apps.

    Index-Radar

    A forecast of S&P index inclusions for every US stock, recalculated twice per trading day.

    S&P 500 Additions Monitor

    Detects index additions and places orders automatically.

    This website

    Including the contact form and a public MCP server for AI assistants.

    Do you have an idea you'd like to try out?

    Write to me in two or three sentences what it is about. I will tell you honestly whether a prototype is the right step.

    Get in touch
    05FAQ

    Frequently asked questions

    01What do you mean by a prototype?
    A working tool with real data that people can use and test. It is good enough to learn from and to decide on. It is not a finished production system.
    02How long does it take?
    A few days to a few weeks. The entry offer “Prototype in six weeks” has a fixed price per sprint.
    03What happens after the prototype?
    You decide: drop it, build it further, or hand it over to your IT. I hand over with documentation. Operation in production stays with your team.
    04How do you handle our data?
    NDA on request, clients named only with approval, and I never train models on your data or code.