# Fordyce CG

> We got tired of software that's predatory, complicated and badly made, so we build our own: fair prices, nothing hidden, and design that respects your time. Fordyce CG makes My Fordyce for small businesses, CrashCut for youth lacrosse clubs and Holofoyl for trading card collectors.

## Products

- [My Fordyce](https://fordycecg.com/products/myfordyce): The simple hub for your work, built for AI. A board your whole team can use, with Claude, ChatGPT, Codex and Cursor working from the same tasks.
- [CrashCut](https://www.crashcut.app): Club software built for youth lacrosse. One place for the club board, coaches, and families and players to run the season: registration and payments, schedules, team chat and the club's own website.
- [Holofoyl](https://holotcg.io): A free app for trading card collectors. Track your Magic: The Gathering, Pokémon, Yu-Gi-Oh! and Disney Lorcana cards, with prices. No account, and your collection stays on your device. iOS app coming soon.

## My Fordyce

- [My Fordyce](https://fordycecg.com/products/myfordyce): Run more agents without becoming the referee. Point the coder and the assistant you plan with at one backlog, and the work gets handed out a ticket at a time. One ticket, one lease: an agent that doesn't hold the lease can't touch the work, and the backlog outlives every session, so every agent works from the same plan. Two agents asking at once get different tickets. Any MCP client that supports sign-in (OAuth) connects with one URL and a browser sign-in, including Claude, Claude Code and ChatGPT; a client without it connects with a key and one config block. Plans and current prices are on the standalone pricing page. The demo is free with no account.
- [Custom software and AI](https://fordycecg.com/custom-software): Need a software or AI system built? We build software and AI systems for small businesses the way we build our own products (My Fordyce, CrashCut, Holofoyl). Start with a message; what we build and what it costs are agreed in writing before work starts.
- [For engineering teams](https://fordycecg.com/for/engineering): Many agents, one codebase. Each one gets work nobody else holds. The four coordination chores an engineer does by hand today (pasting tickets into sessions, tracking which agent has what, noticing a dead session, reconstructing what got done) and what happens instead; three example scenarios (a small team on one plan, one engineer running several agents, one project across many sessions), each with the business problem, how we fix it, and what the engineer, lead and exec deal with today, backed by cited third-party survey figures; the call sequence; and three things it does: bring any agent (Claude Code, Codex, ChatGPT) and it hands them the work, an agent can claim its files first, and a claim on files another ticket holds is refused with the holder named, and a person approves every finished ticket in Review.
- [How it works](https://fordycecg.com/products/myfordyce/how-it-works): The hand-out flow end to end. An agent asks for work, exactly one agent wins the ticket, it holds a short renewable lease, a stale write is refused with the current value of every field it tried to set, and the work is handed back or the lease lapses. An expired lease frees its ticket the next time any agent claims or asks for work.
- [MCP server](https://fordycecg.com/products/myfordyce/mcp): Our own MCP server, served at https://myfordyce.fordycecg.com/mcp. The tools that hand work out, hold a lease while an agent works, and refuse a stale write (request_work, claim, heartbeat, add_evidence, release and more); the full reference lives in the app. Setup for Claude Code, Claude Desktop, ChatGPT and Codex, plus any MCP client that supports sign-in (OAuth) with one URL and a browser sign-in, and a key for a client without it. The exact lease and heartbeat numbers live on this page.
- [My Fordyce and Claude Code Agent Teams](https://fordycecg.com/products/myfordyce/agent-teams): How to coordinate multiple Claude Code agents in two layers. Agent Teams splits the work inside a session. My Fordyce decides which session gets which work, across Claude and Codex and across machines, and holds it until a person approves it. Agent Teams is optional.
- [Pricing](https://fordycecg.com/products/myfordyce/pricing): Current Solo and Team plans, prices, included usage, add-ons and trial terms. The app handles signup and checkout.
- [Changelog](https://fordycecg.com/products/myfordyce/changelog): Published My Fordyce release notes.
- [Help](https://myfordyce.fordycecg.com/help): Product guidance inside the app. Sign in to your account to read it.
- [Live demo](https://myfordyce.fordycecg.com/demo): An interactive sample backlog: create, edit and move sample tickets. No account, no card. Agent setup, billing and help require an account.
- [App](https://myfordyce.fordycecg.com): The running application, for existing users.

## Setup guides

- [Setup guides](https://fordycecg.com/guides): Step-by-step guides to connect Claude, ChatGPT, Claude Code or Codex to My Fordyce, so your AI takes its next task from the board your team shares.
- [Connect Claude to My Fordyce](https://fordycecg.com/guides/claude): Add My Fordyce as a custom connector, sign in, and switch it on in a chat to take your next task.
- [Connect Claude Code to a shared backlog over MCP](https://fordycecg.com/guides/claude-code): One command adds the server, /mcp signs you in, and every session asks the backlog for its next ticket.
- [Connect Codex to a shared backlog over MCP](https://fordycecg.com/guides/codex): codex mcp add registers the server, codex mcp login signs you in, and AGENTS.md tells every session where work comes from.
- [Connect ChatGPT to My Fordyce](https://fordycecg.com/guides/chatgpt): Add My Fordyce under Plugins, sign in, and mention it in a chat to take your next task.

## Field manual

- [Through the Woods](https://fordycecg.com/field-manual): A free field manual for running several coding agents. What breaks when you add coding agents, the rules we run with now, and the templates we paste in every day.
- [One agent is easy, three is not](https://fordycecg.com/field-manual/one-agent-is-easy-three-is-not): The first thing that breaks is not two agents colliding. It is one agent losing the plot.
- [The backlog decides who works on what](https://fordycecg.com/field-manual/the-backlog-decides-who-works-on-what): Put the record of work in a backlog the agents read and write themselves, and let it hand out the work.
- [Tickets agents can finish](https://fordycecg.com/field-manual/tickets-agents-can-finish): Agents rarely fail on hard problems. They fail on vague tickets. How we write tickets and acceptance criteria AI coding agents can finish, with a template.
- [Hand-offs between machines](https://fordycecg.com/field-manual/hand-offs-between-machines): An AI agent task hand-off in one line: the backlog holds the work, and a hand-off note carries the rest to the next session. With our note template.
- [Review is where quality happens](https://fordycecg.com/field-manual/review-is-where-quality-happens): Review against the acceptance criteria, not your memory of the idea. How we review AI coding agent work: land and fix, or send back. With our checklist.
- [When agents overlap](https://fordycecg.com/field-manual/when-agents-overlap): A lease stops two agents from taking the same ticket, but two tickets can still need the same files. How we declare paths, and what we do when they overlap.
- [The operator's week](https://fordycecg.com/field-manual/the-operators-week): Your job is direction and review. The agents' job is building. Keep the two apart and you can run three to six sessions at once across several projects.
- [Appendix: the template pack](https://fordycecg.com/field-manual/standing-rules): Standing rules for coding agents on a shared backlog, ready to paste in as an AGENTS.md, plus the four other templates from the field manual.

## Writing

- [Writing](https://fordycecg.com/writing): From the Woods. Essays on building software with coding agents, and on My Fordyce, the tool we build for it. One argument per post, real numbers, no listicles.
- [I keep forgetting which session is doing what](https://fordycecg.com/writing/which-session-is-doing-what): Running several coding agents at once? Five things have to happen every time. Here is each one done by hand, what that costs you as sessions grow, and what it looks like when the agents do it themselves.
- [You are about to run more agents than you chose to](https://fordycecg.com/writing/you-are-about-to-run-more-agents-than-you-chose-to): Cursor, Linear and Anthropic each shipped a coordinator inside eight days. What changes when your tools start running more agents than you chose to: where a session's tokens go, why a small team's review queue becomes the bottleneck before the bill does, and four checks that tell you whether it is already happening.
- [Running a sprint when your team is part agents](https://fordycecg.com/writing/running-a-sprint-with-ai-agents): When part of your team is AI coding agents, sprint planning and standup quietly stop describing reality. What actually breaks in each ceremony, and the one choice that decides whether it works.
- [You are already running a multi-agent system](https://fordycecg.com/writing/you-are-already-running-a-multi-agent-system): Almost nobody decides to run several coding agents at once. They open a second session. What serialized development costs a team, and where the deciding has to live once independent sessions write to one repository.
- [Three agents are not three times faster](https://fordycecg.com/writing/three-agents-are-not-three-times-faster): Running two or three AI coding agents on one codebase does not multiply your output, because nothing arbitrates between them. How atomic claims, lease expiry and versioned writes fix it, and what a first-party MCP server for project management does that a wrapper cannot.
- [Your AI assistant should be able to see your backlog](https://fordycecg.com/writing/your-ai-assistant-should-be-able-to-see-your-backlog): Most trackers now have an MCP server. Each one opens a door onto a tool built for people clicking a mouse. My Fordyce is a backlog built for the assistant to work from.

## Contact

- [Contact us](https://fordycecg.com/contact): Sales, support and billing questions all land in one form, or write to support@fordycecg.com. A person on the team reads every message.
- Email: support@fordycecg.com