$ claude --spawn-crew
→ loading memory … ok
→ waking 3 workers … ok
→ proof level set to L4
→ crew online
✴ visible as f#@k · agent setup

Your own AI
agent crew. Not a chatbot. A team that ships.

For builders who do everything themselves — answering, follow-ups, content, shipping. One setup that works while you build, and proves what it did.

scroll
The problem

You're the bottleneck.

01

Every reply, follow-up and delivery waits for you.

02

Tools forget. Every new session starts from zero.

03

"Done" is a claim, not a proof. You find the gaps later.

Before

  • Messages answered when you find the time.
  • Research and content done by hand, or not at all.
  • Every update eats your own build time.

After

  • One agent per client, answering by clear rules.
  • Research runs every morning, on autopilot.
  • You build. The crew ships and logs the proof.
What the setup does

Six things, proven — not pitched.

01 · routing

One agent per client or role.

Answers incoming WhatsApp messages by clear rules, passes orders on through an inbox, and logs every message with a delivery receipt.

live · our terminal
02 · shipping

Ships real software.

In our own operation, four app updates (0.7.4 → 0.7.7) were built, signature-checked and delivered to users in under two hours — one day.

< 2h
four releases, same day
Nova-Pult web UIlive · our own UI
03 · research

Daily research on autopilot.

A trend run every morning reads YouTube and competitor Instagram reels. Measured cost: roughly 4 to 6 cents per user per day, with a hard daily cap.

4–6¢
per user / day, capped
04 · memory

Memory that carries over.

Every handover is stored, so the next session continues exactly where the last one stopped — no re-explaining, no cold start.

live · canvas, page index
05 · proof

Nothing counts as done without proof.

Four proof levels, from "the file exists" to "it works end to end, where the user actually uses it."

L1→L4
four proof levels
06 · outreach

Outreach flow, built and tested.

Nine stages with three automatic follow-ups. Live sending needs your approval first, by design.

96/96
tests passing
Proof, not slides

Screen recordings. Our own system.

pult status · live, scrolling
pult · live web UINova-Pult web UI
canvas, page index
Inside the crew

One app, built by the crew.

app recording follows separately — six steps, no mockup in its place

01

Pull an idea

from the daily research run
02

Teleprompter, with emphasis

you just talk
03

Record

on your phone
04

Upload

straight to the pipeline
05

Pick a style

cut, captions, pacing
06

Finished episode

ready to review
What this is

You decide. The crew does the legwork.

every recording above is real, from our own running operation — not staged
setup & pricing — ask Lars
draft · demo content only · not for distribution