you-aPlan next week's ticketsFor Velocity members whose team just grew
Mark Thompson · Founder, Codas Labs & Codas MediaBring developers into your AI system without losing control of it.
Your whole team on one system.
On day one, a new developer is doing real work inside your system. Then your whole team lands ten finished changes in an afternoon without breaking the live site, and nothing risky goes out without the right person’s sign-off.
The Teams walkthrough
Video coming soon
Founding price ends Dec 31, 2026
You plus four teammates
$499$249
$499
Save $250 · founding price One-time paymentYou plus up to 14 teammates
$999$499
$999
Save $500 · founding price One-time payment14-day money-back guarantee · Requires Velocity · One payment
You invite your team after checkout · everyone you invite gets Velocity + Teams
Growing past 5? Move up to 15 and pay only the difference.
Bigger than 15? Talk to me. It can include me working with your team in person.
Read this if…
Your team grew.
Your system didn’t.
You built Velocity around one person giving the orders. Then people joined, and inside the first week:
- Your developer works their own way, and you can’t see what’s finished.
- Two people’s agents changed the same thing, and one undid the other.
- A password ended up pasted into a chat for the new hire.
- The live site changed because someone assumed someone else had checked it.
- You have no idea what the AI costs per person.
Every one of those comes from rules written for a team of one. Teams rewrites them for a team.
Mark ThompsonWhere it broke for meIt broke for me in three places.
Memory. My system knew everything we’d done. A new developer’s agents knew nothing, so they redid work or undid it. So we built one shared memory: a new developer’s agents start already knowing what we’re working on and what’s been decided.
Decisions. A developer hits a question only one person can answer, sometimes someone at a client. Multiply that by every developer and either everything stops or people guess. So we built a way to gather every open decision from every developer into one place, sent to the person who can answer it, while the work keeps moving.
Control. Developers bring their own agents. Every one of those agents still has to follow our rules: each person gets only the access they need, our SOPs are enforced, and our choice of which AI model does which job applies, whoever’s agent it is.
Teams is those three systems, and everything else it took to run them.
What changes
Same system. Now built for more than one person.
Everything you installed in Velocity stays. Teams adds the rules for the part Velocity never had to answer: other people.
Velocity, on your ownWith Teams
You give every orderEveryone knows what they own. One owner per area, written where every agent reads it.
Your system remembers your workThe whole team shares one memory. A new developer’s agents start knowing what’s being built and what’s been decided.
Your lanes, your branchesEach developer runs their own lanes. A whole team’s agents at once, without collisions.
A second AI checks your workPlus a human sign-off where it matters. Payments, logins and customer data wait for a person.
You answer your own questionsEvery open decision lands in one inbox. Sent to the person who can answer it, while the work keeps moving.
Your agents follow your rulesSo does every developer’s agent. Your SOPs and your model choices apply, even to agents they bring.
Your vault, your keysEvery person holds only the keys they need. Access removed in one step the day someone leaves.
Your AI billCost per person. One budget owner, spending caps, cheap by default.
You know what you finishedA one-page weekly report of what the whole team finished, pulled from the board.
How it works
One board. One owner per job. Risky work waits for a human.
Every developer runs their own agent lanes. Finished work stops at a review gate: the second AI reviewer checks everything, and the risky areas wait for a person’s sign-off. Then it goes live, and the board shows who did what.
Team board one owner per ticket
YOJRPKSA
4 people · 1 board
Person · owns
Agent lanes working
Review gate
Live
YO
YouConductor · billing
Checkout price change
Payments · your sign-off
Payments · your sign-off
Invoice emails
JR
JRDeveloper · frontend
jr-aMobile menujr-bPricing page layoutHeader redesign
2nd AI reviewer · passed
2nd AI reviewer · passed
Footer links
PK
PKDeveloper · API
pk-aSearch endpointpk-bExport to CSVpk-cFix slow dashboardLogin change
Logins · human sign-off
Logins · human sign-off
Rate limits
SA
SAJoined today · docs
sa-aDay-one ticket: setup checkNothing waiting
First change soon
Each developer runs their own lanes
Risky areas wait for a human
Status lives on the board
The program
Each part ends with something installed and running for the whole team.
Who does what.
An ownership map, a shared team memory, and separate lanes for every developer.
Checking work before it goes live.
One shared board, a decision inbox, and written approval rules.
Safety and onboarding.
A shared vault with per-person access, and a day-one checklist.
Cost and proof.
Cost per person, and a weekly report of finished work.
Part
Who does what
Everyone knows what they own, and nobody's agents trip over anyone else's.
Everyone knows what they ownThe Team Map
Who owns which part of the product, written down where every agent reads it. One owner per area, so an agent working for one developer never quietly rewrites code another developer is responsible for.
A new developer’s agents start already knowing the workShared Team Memory
One memory the whole team’s agents read and write: what we’re working on, what’s been done and what’s been decided. A new developer’s agents start with that context instead of from zero, so nobody redoes or undoes finished work.
Each developer runs their own lanesLanes per Developer
Parallel Lanes from Velocity, stretched from one person to many: each developer's own workspaces, branch names and session names, so a whole team's agents work at once without collisions.
You stop being the one everything waits onThe Conductor Seat
Your job changes when people join. Who writes tickets, who plans, who decides what ships, and what you hand over first so the team stops queuing behind you.
Part
Checking work before it goes live
More people means more changes landing at once. These are the rules that keep the live site safe.
One board the whole team works fromThe Shared Board
People and agents follow the same claim rule: a ticket has one owner, status lives on the board, and nobody starts work that someone else already holds.
Every open question reaches the one person who can answer itThe Decision Inbox
When a developer hits a decision they can’t make, it goes into one inbox with every other open decision from every developer, sent to the person who can answer it, including someone at a client. The work keeps moving while it waits, and the answer goes back to the right developer’s agents.
Nothing goes live on one person's say-soReview and Approval Rules
Who reviews what. The second AI reviewer from Velocity, plus a human sign-off on the risky areas (payments, logins, customer data), and a written list of what can go live without you.
Ten finished changes land on the same afternoon without breaking each otherLanding Work at Team Speed
The order work goes live in, what to do when two changes touch the same file, and how the live version stays working when everyone finishes at once.
Part
Safety and onboarding
The day someone joins and the day someone leaves are the two days teams get hurt.
Every person holds only the keys they needThe Team Vault
Velocity's vault, shared: who gets which passwords and API keys, what agents may never touch, and removing someone's access the day they leave, in one step.
A new developer does real work on day oneOnboarding to the Rulebook
The team rulebook lives in the code itself, so every developer’s agents follow the same rules, including which AI model does which job, even when they bring their own agents. A day-one checklist and a first ticket that proves their setup works.
The rules get better without a fightChanging the Rulebook Together
Who may change a rule, how one person's mistake becomes a rule for everyone, and how to stop ten people's preferences turning the rulebook into mush.
Part
Cost and proof
What the team costs, and what it finished.
You know what each person's AI costsCost per Seat
AI accounts per developer, one budget owner, spending caps, and the habits that keep a team cheap by default.
A one-page answer to "what did the team finish?"The Weekly Proof
Finished, reviewed work per person per week, pulled from the board, in a report the owner can read in two minutes.
Handover files ship inside the program: team rulebook template, ownership map template, review rules template, onboarding checklist, weekly report template, access-removal checklist.
Founding price ends Dec 31, 2026
Team of up to 5$499$249$499
Team of up to 15$999$499$999
14-day money-back guarantee · One payment
The obvious worry
More people means more keys.
So here is exactly who holds what.
Each person holds only the keys they need
Velocity’s vault, shared: who gets which passwords and API keys is written down, and nobody gets the whole ring by default.
Leaving takes one step
The day someone leaves, their access goes with them in one step, from a checklist you already have.
Some things agents never touch
A written list of what no one’s agents may touch, read by every developer’s agents from the same rulebook.
Nothing risky goes live on one say-so
Payments, logins and customer data need a human sign-off on top of the second AI reviewer. Everything else follows rules you wrote.
Fit
Who this is for, and who it isn’t
It’s for you if…
- You’ve hired, or are about to hire, your first developers.
- You run an agency and want every person on the same system.
- You already have a dev team and want them working the way your agents do.
It’s not for you yet if…
- You haven’t installed Velocity’s Starter System. Teams builds on it.
- You work alone and plan to keep it that way. Velocity already covers you.
The offer
Everything you get
- Velocity for every person you invite. They don’t buy anything.
- Who does what. The Team Map, shared team memory, lanes per developer, the conductor seat.
- Checking work before it goes live. The shared board, the decision inbox, review and approval rules, landing work at team speed.
- Safety and onboarding. The team vault, onboarding to the rulebook, changing the rulebook together.
- Cost and proof. Cost per seat, and the weekly proof.
- The handover files. Team rulebook, ownership map, review rules, onboarding checklist, weekly report, access-removal checklist.
14-day money-back guarantee
Change your mind.
If it isn’t for you, email me inside 14 days and you get every cent back.
Founding price ends Dec 31, 2026
Team of up to 5$499$249$499
Team of up to 15$999$499$999
14-day money-back guarantee · One payment
Questions
Before you add Teams.
Do I need Velocity first?
Yes. Teams builds on the system you install in Velocity. If you don't own it yet, the buy button offers Velocity first.
Do my developers need to buy Velocity?
No. Everyone you invite gets Velocity and Teams.
Can I swap people?
Yes. When you remove someone, their place opens again 30 days later.
Does "up to 5" include me?
Yes. You plus four teammates.
What if my team grows past 5?
Move up to the 15-person plan and pay only the difference.
My team is bigger than 15.
Use "Talk to me". Bigger teams usually want me in the room.
Are my developers technical enough?
They're more technical than Velocity assumes, which helps. The parts that are new to them are the rules for working alongside agents, and that is what Teams teaches.
Last thing
You have two choices right now.
Choice 1
Keep running it alone
- Your developers keep working their own way
- Agents keep tripping over each other
- Passwords keep ending up in chats
- You stay the one everything waits on
Choice 2
Add Teams
- From $249 once, at the founding priceFrom $499 once
- Everyone you invite gets Velocity + Teams
- One board, one owner per job, risky work checked by a person
- 14 days to change your mind, with every cent back
Founding price ends Dec 31, 2026
Team of up to 5$499$249$499
Team of up to 15$999$499$999
14-day money-back guarantee · One payment