How it works
Seven days. One ticket type. One rule.
Crew Install is deliberately narrow: one repo, one ticket type, one loop your team keeps after we leave. Here is the whole thing, day by day — including the part where your agent finally reads the ticket instead of guessing at it.
01 — The route
From an email to a merged-by-you PR.
Every step below is the same for the $4,500 and $7,500 installs; the bigger one adds Slack or Linear as the trigger.
-
01
Start
Send the repo and the ticket type
Email orders@imarand.com with four things: the repo, the one ticket type you want off your plate, where tickets live today (GitHub Issues, Linear, a spreadsheet — be honest), and who reviews PRs.
Questions-first emails are fine. You get a plain answer either way, including “not a fit” when it isn’t.
-
02
Day 0
Payment clears, access opens
We do not start until payment clears — no work on spec, no invoice chasing. Then access opens, scoped: agents may push branches and open pull requests on the one repo. Nothing about branch protection on main changes.
Everything we set up is yours to rotate or revoke, and the playbook shows how.
-
03
Days 1–4
We wire the crew
Ticket ingestion comes first. The agent has to read the real ticket — full body and comments, not a guessed spec. Cursor’s cloud VM token often can’t read GitHub issues even when the App UI says it can, so we set up one of the two fixes that work — the details are in the guide, and any token involved stays in your hands.
Then the skill and rules for your ticket type: what a good fix looks like, what the tests must cover, what a PR must contain. The configuration lives in your repo, not ours.
-
04
Days 5–6
Dry run on a real ticket
A ticket from your actual backlog goes through the loop: read, branch, implement, test, PR. That PR is the receipt — not a demo repo, not a staged screenshot.
Your engineer reviews it like any other. Comments, change requests, and rejections all count as the loop working.
-
05
Day 7
Handoff
You get the playbook: how to run the next ticket, tune the guardrails, widen or narrow the ticket type, and rotate or revoke every credential the install touched.
From day 8 your team runs it — or the $1,500/mo retainer keeps the loop fed with up to eight tickets a month. There is no lock-in mechanism, on purpose.
The $7,500 install is the same seven days, plus Slack or Linear wired in — an issue or a message kicks the loop.
02 — The rules
What the loop runs on.
These aren’t aspirations; they’re the constraints the install is built around. Hold us to them.
- A human merges every PR — or it doesn’t merge. There is no auto-merge path to switch on.
- We never touch main. Branch-only writes; your protection rules stay exactly as they are.
- The agent reads the ticket before it writes code. If it can’t, we fix ingestion before anything else.
- Tests run before a PR opens. A PR without them is a draft, not a deliverable.
- Access is scoped and revocable: one repo, minimum permissions, revocation steps in the playbook.
- Everything is disclosed. AI-run, human-merged — and the site says so.
03 — Failure modes
What can go wrong, and what it costs.
We’d rather name these here than have you discover them on day 5.
A PR misses.
It happens, and the loop is built so a miss costs your engineer a review, not an incident. Rejection is the system working. The rules that produced the miss live in your repo, so tightening them is an edit, not a support ticket.
The ticket type is too broad.
“Small features” drifting into “redesign checkout” is the usual failure. We narrow the type with you on day 1 — narrow and boring beats broad and flaky.
The agent can’t read the tickets at all. That’s the known Cursor-and-GitHub issues-scope gap, not a judgment on your setup — and it’s ingestion, not intelligence. Two fixes work, and we set one up during the install: read the guide.
Book
Send the repo. Name the ticket type.
Email orders@imarand.com to book, or to ask first. Prices are on the pricing section: $4,500 install, $7,500 with triggers, $1,500/mo retainer after an install.
We do not start until payment clears. AI-run, human-merged — on purpose.