Coding agentsfor small teams.
Nix Inc sets up Claude Code and Claude Cowork for small businesses, writes the rules the agents work under, and reviews what they produce before it is used. Your team buys its own Claude Team seats. Founder Chris Nixon has spent fifteen years in digital analytics, paid media and SEO, up to director of digital analytics.
What Nix Incdoes for a team.
Your company buys its own Claude Team seats and owns the accounts. Nix Inc does the work below on those seats.
Setup
Claude Code and Claude Cowork, configured on your company's Claude Team seats.
Rules
A written rule set for each agent: what it may do on its own, what it must ask a person about first, and what only a person does. The rules Nix Inc works under are on this page.
Review
What the agents produce is checked against the task and a written standard before your team relies on it. Changes near sign-in, payments or production get a deeper review.
First step
Email chris@nixinc.co. Say what your business does and one job you want an agent to take on.
Nix Inc's own builds.
Nix Inc's own projects, not client work, numbered in the order each one started. Each card says whether it is live, running or still in development. From here on, a build that is stopped stays on this list with the reason.
NameIO
AI visibility scanner for ecommerce brands.
Runs real browser sessions against ChatGPT, Perplexity, Claude and Gemini with a 20-prompt library, scores how often and how strongly a brand gets recommended, and writes the fixes: FAQ content, schema and llms.txt. Free to use.
Hermes Agent
An always-on operations agent.
A self-hosted deployment of Nous Research's open-source Hermes Agent. It runs around the clock, takes instructions over Telegram and runs the scheduled jobs, including a morning research brief. A dashboard shows its sessions, memory search and job history.
TrimIndex
Trim-level reviews of used electric cars.
About 1,100 trim-level pages for used EVs from 2020 to 2026, each scored from NHTSA recall and complaint data, EPA range and battery chemistry. The written buyer briefs are model-generated and only publish if they pass automatic checks against the underlying data.
Maillard
BBQ answers cited to the second.
A native iOS app over a searchable library of 2,995 BBQ videos from 799 creators. Every answer cites the exact moment in the source video and plays it in the app, and a fixed food-safety check runs before anything is shown. Not on the App Store yet.
nixinc.co
This site.
One page, generated from one set of content files. A plain-text copy of the whole page is at /llms.txt for anyone reading through an agent. Live since 2026-10-08.
Next build: not chosen yet.
It goes in the log before work starts.
Chris Nixon.
Fifteen years in digital marketing and analytics. Chris started in paid search at agencies, ran paid search for a Fortune 500 brand, then moved in-house to lead paid media, SEO, ecommerce analytics and site experience, up to director of digital analytics.
Most of that work is measurement and governance: deciding what gets tracked, who is allowed to change it, how a change is tested before it goes live, and how the result is reported. He moved eight brands onto one shared ecommerce and content platform and owned the tagging standards for all of them.
Nix Inc applies that approach to coding agents. Each agent works under written limits on what it may change, and its work is checked before anything ships.
Who does what.
The founder decides and signs off. Claude Code does the build work and Hermes Agent runs the scheduled jobs.
Chris Nixon
Writes the briefs, reads every change before it ships, and owns deploys, customer data and billing outright.
Claude Code
Works each ticket on a feature branch, inside the permission tiers listed under Rules. Nothing it writes ships until a person has read it.
Hermes Agent
Self-hosted and always on. Takes instructions over Telegram and runs the scheduled jobs, including the morning research brief.
Claude Code, review pass
Checks each change against the written standard and marks it must fix, should fix or okay to ship.
Four rules for every piece of work.
They apply whether a person or an agent is doing the work. These are the four rules and three tiers Nix Inc works under.
Brief
Nothing starts without a short written plan: which files will change, the smallest clean way to do it, what could go wrong, how it will be checked, and what is deliberately being left out of the first version.
Plain terms: say what you are going to do, on one page, before you do it.
Ticket
One task, one finish line, one change small enough to read in a diff. “Make it better” is not a ticket. If there is no clear finish line, the work does not start.
Plain terms: cut the work small enough that someone can check all of it.
Eyes
Use the finished thing the way a new customer would. Try the empty state, the error state and the success state. Open the database and check the record is actually there.
Plain terms: click through it yourself before calling it done.
Review
Three readers. The founder reads the change against the ticket. An agent reads it against the written standard and marks it must fix, should fix or okay to ship. Anything near sign-in, payments or production also gets a deeper automated code review before it moves.
Plain terms: every change is read by a person and by an agent before it ships, and risky changes get a deeper check.
What an agent may do on its own
Three tiers, written into the instructions file Claude Code reads before it starts. The riskiest commands are also on a deny list in Claude Code's settings, which still applies when permission prompts are turned off: recursive deletes, force-pushes, opening a secrets file and writes to the payment account.
- Read and inspect code
- Propose a plan
- Run the local tests
- Edit on a feature branch
- Update docs, draft a pull request
Plain terms: work that does not reach customers until a person approves it.
- Install a dependency
- Migrate a database
- Touch sign-in
- Change anything about payments
- Delete files or rename at scale
Plain terms: changes to sign-in, payments, the database or the software the project depends on. A person says yes first.
- Deploy to production
- Decide anything about customer data
- Decide anything about billing
- Change anything security-sensitive
- Open a secrets file
Plain terms: putting anything live, and any decision about customer data, billing or security.
The log.
Decisions and releases, newest first, with the date and who decided. If one of Nix Inc's own builds is stopped, the reason goes here.
- DecisionThe page now opens with what Nix Inc does for a client team and ends with a way to get in touch. It is written for small-business owners as well as developers, which replaces the 3 October decision.Founder
- Shippednixinc.co goes live.Founder
- DecisionEarlier builds go on the site after all: NameIO, Hermes Agent, TrimIndex and Maillard. This reverses the 2 October decision.Founder
- DecisionThe site is written for developers first. Each rule also gets a one-line plain-English version for people who don't write code.Founder
- DecisionFocus: helping small teams run coding agents. Only new builds go on the site; earlier experiments stay off it.Founder
- ShippedResearch brief for this site: 32 comparable practitioners checked against their own pages, 477 sources.Agents, checked by founder
- DecisionName: Nix Inc. Domain: nixinc.co.Founder
- DecisionTwice-daily research scans paused.Founder
- Notenixinc.co registered.Founder
Talk to
Nix Inc.
Write a few lines on what your business does, how many people would use Claude, and the job you want an agent to take on.
Email chris@nixinc.co →