Hi, I'm Noah Graff.

I build systems that work.

Finance student, founder, and AI builder. I turn loose ideas into operating systems, then use them in my own work.

20 years old Founder & systems builder London, UK

Working proof

The work is easiest to understand while it is running.

I build through Claude Code and keep the useful systems alive. Below are the interfaces, operating layers, and real outputs behind three of those builds.

Role Founder and builder Focus AI systems and operations Method Build, use, improve

Selected systems

Scroll through the evidence.

Each project moves from the foundation to the operating interface and then to a concrete use case.

Running daily

The Hunt

Manual prospecting was too slow. I built a fleet of agents that researches businesses, checks fit, drafts outreach, and surfaces replies inside one live command room. Every external message still waits for a human click.

Problem Manual prospecting Built Agent fleet and approval layer Now Running as an operating system
The Hunt command room with seven AI agents across a live operating interface
Command roomAgent fleet and approval layer01
Belli's map interface with sample markers illustrating how researched leads appear by city and contact channel
Lead mapBelli's real interface with sample lead positions02
A polished prospect website concept generated by the Hunt showcase workflow
Prospect conceptGenerated preview, not client work03

Live in my workflow

The Galaxy

My notes, goals, and projects were scattered. I turned the vault into a navigable 3D system with voice controls, automated journals, and a connected research station. It is the interface I use to run my work.

Problem Scattered operations Built 3D vault and research agents Now My working operating layer
The Obsidian workspace structure behind Noah's second brain, showing folders, working notes, and linked context
Obsidian foundationFiles, projects, and links underneath01
The live Galaxy interface rendering the Obsidian vault as a navigable orbital system
Galaxy interfaceThe same vault rendered spatially02
The V9 research station showing connected research modules and autonomous agents
V9 research stationProblem research and validation03

Live community

Builder Community

The community needed more than another chat server. I built its Discord structure through the API. My partner Eitan built the web platform, and together we are connecting roles, verification, learning, and builder pathways into one system.

Problem Fragmented community setup Built Discord API workflow and roles Now Live Discord and builder pathway
Enter the Discord
The private builder Discord showing channels, an official Hunt launch announcement, bots, and builder roles
Live serverChannels, roles, bots, and verification01
The private builder community learning login connected to Discord
Member accessLearning access through Discord02
The builder community learning pathway explaining how members build projects with support
Learning pathwayStructured build progression03

Building now

The marketplace is the next layer.

The private builder community is moving from a live network and working lead engine toward a vetted marketplace for AI projects.

The community exists. The engine works. The marketplace is in early launch, and that distinction matters.

Open Hunt
The live Hunt AI builder marketplace homepage showing project posting and builder matching
Hunt by KraitosLive marketplace, early launchhunt.kraitos.app ↗
Builder communityLive Lead engineRunning Vetted marketplaceEarly launch

Follow the build

See what ships next.