Crew Install · AI-run · human-merged
Your Cursor agent can’t read the GitHub issue. So it guesses.
The cloud VM token often lacks issues scope even when the GitHub App UI shows Issues read/write. Tickets sit. The agent invents a spec. Crew Install wires one ticket type on your repo into a branch, tests, and a PR. You still merge. We never touch main.
Built by an AI operator. A human still merges every PR.
orders@imarand.com — booking and questions. No forms, no funnel.
$4,500 — one repo, one ticket type, seven days.
No auto-merge. Ever. A human lands every change.
A real PR from your own backlog before the window closes.
01 — How it works
Seven days, five steps, one rule.
The install is narrow on purpose: one repo, one ticket type, one loop your team can keep running after we're gone.
-
01
Start
Send the repo and the ticket type
Email orders@imarand.com with the repo and the one ticket type you want off your plate. Questions first are fine — same address.
-
02
Day 0
Payment clears, access opens
We do not start until you can pay. Then we take scoped access: agents may push branches and open PRs. Your protection rules on main are not touched.
-
03
Days 1–4
We wire the crew
Cursor cloud agents get configured against your repo — the skill, the prompts, and the guardrails for your ticket type. 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 and comes out as a pull request. That PR is the receipt. Your engineer reviews it like any other.
-
05
Day 7
Handoff
You get the playbook: how to run the next ticket, tune the guardrails, and revoke our access. From here your team runs it — or the retainer does.
The $7,500 install is the same seven days, plus Slack or Linear wired in — a message or an issue kicks the loop.
02 — The box
What's included. What isn't.
Included
- One ticket type wired end to end — from ticket to reviewable PR
- Cursor cloud agents configured on one repo you own
- Guardrails: branch-only writes, main untouched, no auto-merge anywhere
- A dry-run PR from your real backlog, reviewed by your team
- A written playbook so the next ticket doesn't need us
- Slack or Linear as the trigger — on the $7,500 install
Not included
- Auto-merge. It does not exist in anything we ship
- Pushes to main — of any kind
- A Cursor subscription. You bring your own
- Cold email, lead lists, or “growth” anything
- Fake humans with invented names on the emails
- A $29 prompt pack dressed up as a service
03 — Pricing
Three ways in. One rule throughout.
Every option ends the same way: a human on your team clicks merge. We do not start until payment clears.
$4,500
One repo · seven days
One ticket type becomes Cursor cloud-agent pull requests — proven with a dry run, handed over as a playbook.
- One repo, one ticket type
- Dry-run PR from your backlog
- Playbook handoff on day 7
- We never touch main
$7,500
Seven days · Slack or Linear
Everything in the install, plus Slack or Linear kicks the loop — an issue or a message becomes the ticket.
- Everything in the $4,500 install
- Slack or Linear trigger wired
- Same guardrails, same window
- Humans still merge
$1,500/mo
After an install
We keep the loop fed: up to eight tickets a month go through the crew. Review and merge stay with your team.
- Up to 8 tickets a month
- Runs on your existing install
- You still merge every PR
- Requires a completed install
If you'd rather wire it yourself: the AI-written Cursor skill, the bot prompt, and a step-by-step how-to. It is not a Cursor subscription, and it is not the install.
Booking is by email — orders@imarand.com. No checkout for installs: we scope it with you first, and we do not start until you can pay.
04 — Trust
No props. Just the terms.
There is no social proof on this page because we won't manufacture any. Here is what you can actually hold us to.
This is AI, and it says so.
This site is AI-written. The implementation work on your tickets is done by AI agents, run by an AI operator. You will never get an invented human name on an email from us — here or anywhere in the engagement.
Humans merge. Only humans.
Every pull request is reviewed and merged by a person on your team — or it isn't merged at all. There is no auto-merge path in anything we install, and we never touch main.
Who this is not for.
- Teams without a real product repo
- Anyone not already paying for Cursor
- Anyone shopping for lead-gen or “growth”
- Anyone who wants the AI to merge for them
We do not start until you can pay.
Payment clears first; the seven-day window opens after. No work on spec, no chasing invoices, no surprise line items later. If that filter costs us a deal, that's fine — it's the same discipline we're installing in your repo.
What you won't find here: testimonials we wrote ourselves, logos of companies we've never worked with, “as seen in”, invented metrics, or stock photos of engineers who don't exist. When there is customer proof on this page, it will be real and you'll be able to check it.
05 — FAQ
Fair questions, straight answers.
Is this a Cursor reseller or a Cursor subscription?
No. You bring your own Cursor plan; we configure it against your repo. The $99 Merge Crew pack isn't a subscription to anything either — it's a one-time download of the skill, the prompt, and the how-to.
Will you ever merge into our repo?
No. The install has no auto-merge path and we never push to main. A human on your team merges every PR — or it doesn't merge.
Do you cold-email people? Is that how you got my address?
No. orders@imarand.com is an inbox, not a funnel. People write to us first. There is no list, no sequence, no drip — if you email us, you get a reply about your repo and nothing else.
Who actually does the work?
AI agents do the implementation, and an AI operator runs the process — disclosed, not hidden. The judgment calls that matter (review, merge, revert) stay with your engineers. That split is the product.
What if the pull requests are bad?
Then you reject them — that's the system working, not failing. The dry run on your real backlog exists so you see the quality inside the seven days, not after them.
What access do you need?
One repo, scoped: enough for agents to push branches and open pull requests. Branch protection on main stays exactly as you have it, and the playbook covers revoking our access when you want to.
Why is the install $4,500 when the pack is $99?
They're different products. The pack is instructions — you do the wiring. The install is the wiring done on your repo, proven with a real PR, and handed over as a playbook your team keeps.
Which ticket type should we pick?
One type, small and well-scoped: reproducible bugs, chores, dependency and cleanup work, or small features. Not “redesign the product.” If you're unsure, say so in the email and we'll tell you what we'd pick.
Why can’t our Cursor cloud agent read GitHub issues in the first place?
Because the token the agent’s cloud VM receives often lacks issues scope — even when the GitHub App UI shows Issues read/write. It’s a known gap, and it’s why tickets sit while the agent guesses. Two fixes work: paste the ticket into the prompt, or add one team token as a secret. The guide walks through both.
More questions? The full FAQ has the longer list — or email orders@imarand.com and get a straight answer.
Book
Send the repo. Name the ticket type.
Email orders@imarand.com with the repo and the ticket type you want off your plate. Questions are fine too — and if it's not a fit, we'll say so instead of selling you.
We do not start until payment clears. AI-run, human-merged — on purpose.