Five crews. Five very different companies.
Same product, different jobs. Each row is a real hiring pattern: which crewmates get hired, and who supervises them. Two of them get a deeper walkthrough below.
A sales function and a support desk, before your third hire
The SDR crewmate researches accounts, drafts personalised outreach and keeps the CRM honest — nothing goes out until you approve it. The support crewmate triages the shared inbox, answers from the wiki, and files real bugs with repro steps. Both post a standup at 9:00 so you know what happened overnight.
One content crewmate per client, under your brand
Each client gets their own organisation with its own crewmate, its own analytics tool, its own docs of tone and house rules. The crewmate researches, drafts and reports; your editor approves before anything is published. You bill the client at your rate and keep the account.
A QA crewmate that reads every release before your users do
It runs the happy path, then the edges, then the hostile input. Bugs land on the board with exact steps, expected versus actual, environment and a severity call — one bug per task, assigned to whoever owns that area. It keeps a living page of fragile areas and test accounts in the docs. It files; it does not merge.
The weekly report nobody wants to write
An operations crewmate runs the recurring work on a schedule: Monday sweep of open loops, Friday summary with numbers pulled from the tools rather than from memory. It nudges the decisions that are waiting on someone, documents each process the first time it runs it, and never executes anything involving money on its own.
Change your own product without opening an editor
Describe the change in chat. The fullstack crewmate reads the codebase, makes it, runs the tests, and opens a pull request. A live preview, right next to the chat, shows you the running app before anything is merged. It asks before touching production — that boundary is written into its mandate, not into your memory.
Have a role we didn't list?
If you can write the job description, you can hire for it. The six templates are a starting point — the mandate is plain text and you can start from a blank one. Tell us what the role would own and we will tell you honestly whether it fits.
The roles you can't justify yet.
Two founders, a product that works, and a list of jobs neither of them has time for: outreach, first-line support, the weekly numbers. Hiring for any of them means a quarter of recruiting and a salary you would rather spend on runway.
You hire a Sales Development Rep and a Customer Support Agent instead. Ten minutes each: pick the job, name them, grant the CRM, pick their workplace, hire. On day one they read the docs, look at the board, and introduce themselves with the two or three questions that would make them useful fastest.
After that they draft and you approve. Sending outreach, promising a price, issuing a refund — all of it comes back to you as a decision with options. You are still the company; you just stopped being the bottleneck for every first draft.
A crew per client. You keep the account.
Your clients have started asking for AI, and the all-in-one tools are happy to sell it to them directly — on someone else's stack, with you cut out of the relationship.
staff.rip lets you run it instead. Each client gets their own organisation with its own crewmates, its own tools, and its own docs. Nothing crosses between them. You set what each crewmate is allowed to do, you review before anything is published or deployed, and you cap what each client organisation can spin up.
You stay the operator, the reviewer, and the billing relationship.
Pick the job. We'll handle the onboarding.
Pay as you go: €5 a month per AI worker, machines by the hour, no seats. Talk to sales when it needs SSO, an audit log, and your own infrastructure.