Sixty Seconds · Internal systems map · 29 July 2026

How it all fits together

Every arrow on this page is real — traced through the code, not from memory. In one sentence: use60 collects the business, the Brain remembers it, the agents act on it, the Dev Hub tracks the building, and the videos go out to prospects — with the toolkit as the shared toolbox underneath everything.

The big picture

Follow the arrows: data flows in from the outside world on the left, gets collected and remembered in the middle, and goes out to prospects and clients on the right.

Open the map full-screen (wall version) ↗ Brain — remembers use60 — collects Agents — act Dev Hub — tracks building Video — goes out Toolkit — shared tools

The seven pieces, in plain English

What each system is, what goes in, and what comes out.

The Brain

60-Brain · Railway

The company memory — about 1,500 linked pages (people, deals, projects, meetings, ideas) that anything can search. It has a security door (brain-gate) so each person and agent only sees what they're allowed to, and a window (brain-explorer) — the team hub with the graph view, docs, videos, and a client delivery hub.

Goes in

  • use60 — meetings, transcripts, deal signals (nightly)
  • Vault — team notes, merged every morning
  • Slack + GitHub — daily digests of chats and commits
  • Dev Hub — task activity
  • Us + agents over MCP — saved pages and findings

Comes out

  • Agents read it before acting (their shared memory)
  • Team browses it through the Brain window
  • Clients get their deliverables through the client hub

use60

app.use60.com

The sales platform. Joins your meetings with a recording bot, turns them into transcripts and action items, tracks deals and pipeline health, and flags tasks and reminders automatically. Ops tables are its smart spreadsheets — every row can have AI columns that research, enrich, or make a video.

Goes in

  • Calendars → bot joins the call → transcript + summary
  • HubSpot / Attio / Bullhorn — contacts, companies, deals (two-way sync)
  • Enrichment — Apollo, Apify, websets fill Ops rows

Comes out

  • Brain — meetings, emails, deal signals (its "source bus")
  • Wave videos — Ops rows become personalised videos
  • CRM — meeting outcomes pushed back to HubSpot/Attio
  • Dev Hub — its Features page syncs with tickets both ways

Agents platform

agents.sixtyseconds.ai

Where our AI teammates live. It has a task board like a normal team: tasks get auto-routed to the right agent, a worker picks them up, and the agent does the job in its own safe container. Hiring is a real recruitment funnel — post a job, interview generated candidates, run an assessment day, hire the winner, then train it in the Academy with a probation period before it works unsupervised.

Goes in

  • Us over MCP — create tasks, send ideas, chat (Arlo)
  • Brain — agents read company knowledge through the Gate, with a short-lived pass per task

Comes out

  • Brain — findings and lessons written back daily
  • Dev Hub — project and ticket sync
  • Video platform — video orders and wave jobs
  • use60 — agents can use deals/contacts/pipeline tools

AI Dev Hub

sixtyvibes.com

The development tracker. Projects and tickets, GitHub commits and PRs matched to those tickets, and AI usage (token spend and quota, collected hourly from each machine — when set up). Agents use its MCP to claim tickets, update them, fetch secrets, and report back.

Goes in

  • GitHub — commit scans link work to tickets
  • Our machines — hourly AI usage + quota stats
  • use60 + agents platform — ticket/project sync

The process

  • Ticket → agent claims it → works through the /60 pipeline → draft PR → ticket marked "in review" with the PR link
  • Overnight worker drains the backlog while we sleep — it never merges or deploys

Wave videos + landing pages

studio.use60.com · *.use60.com

The personalised outreach machine. Take a prospect (from the CRM, an Ops row, or a LinkedIn URL), research them, write a script, generate a video with a cloned voice and avatar, and put it on a landing page made just for their company. "Wave" is this play at scale — with variants for audits, events, hiring, follow-ups, win-backs, and referrals.

The recipe

  • Prospect data (CRM/Ops/LinkedIn) → research → script
  • ElevenLabs voice + HeyGen avatar → composited video
  • Hosted on media.use60.com, page at company.use60.com

Comes back

  • Watch tracking — a real watch writes back to the CRM contact and pings the Brain
  • Client delivery — finished work lands in the Brain's client hub
  • A human always presses send — never the machine

60-toolkit + Vault

Claude plugin · Obsidian

The shared toolbox — 118 skills and 42 commands that we and the agents both use: the /60 build pipeline, the overnight worker, design and video skills, and the "navigate" skill that teaches any agent how a project is laid out. The Vault is the team notebook (Obsidian) — humans and agents write to it all day, and it merges into the Brain every morning.

Who it serves

  • Us — one command for building, designing, videos, reports
  • Agents — same skills, plus guardrails (they can't deploy)
  • Client work — tracked through these internal tools only: Dev Hub projects, Vault client notes, and the Brain's client hub

Four journeys that show the whole system working

The same map, told as stories.

1

A meeting becomes company memory

You take a sales call. use60's bot joins, records, and transcribes it; AI pulls out action items and flags follow-up tasks and reminders. That night, the Brain's ingest run collects the meeting and its deal signals — so tomorrow, any agent or teammate who asks the Brain about that deal already knows what was said.

Calendaruse60 bot + transcripttasks & remindersBrain (nightly)
2

A CRM contact becomes a personalised video

HubSpot or Attio syncs contacts into a use60 Ops table. A Wave column researches each row, writes a script, and generates the video with your cloned voice and avatar. Each prospect gets their own landing page on their company's name. When they watch it, the view is written back to their CRM record and signalled to the Brain.

HubSpot / AttioOps table rowWave videotheir landing pagewatch stats → CRM + Brain
3

An idea becomes shipped code overnight

A feature idea becomes a Dev Hub ticket (from us, from use60's Features page, or from the agents platform). Overnight, the worker claims it, reads the Brain when it hits a decision, builds through the /60 pipeline with the toolkit's skills, and leaves a draft PR on the ticket by morning. The commit is scanned and linked back to the ticket, and the lesson learned goes into the Brain.

Ticketovernight agent + toolkitasks the Brain at gatesdraft PR by morning
4

A job opening becomes a trained AI teammate

On the agents platform you post a job with a salary band (its monthly budget). The platform generates candidates — each one a genuinely different AI configuration presented as a person — then screens, interviews, and runs an assessment day where their work is compared side by side. The winner is hired, enrolled in the Academy, and works through probation before joining the task board for real, with Brain access granted per-task through the security gate.

Post jobcandidatesassessment dayhireAcademy → probation → work

Actively moving right now

Where the recent commits are, as of today.

Brain window → client hub

brain-explorer is the busiest repo: client delivery hub, video library, and self-serve access passes.

Agent Academy + hiring

Training drills now run against real business evidence; video orders accept rich production briefs.

Meetings & prospecting

Duplicate-meeting detection, browser recordings flowing into the Brain, and the prospecting-video funnel (made → sent → conversation).

Own avatar engine (planned)

A plan to replace HeyGen with self-hosted rendering — removing the ~5 videos/hour cap that blocks big client batches. Spec only; nothing built until quality tests pass.