Setup service
The system installed in your repo, with the evidence that it works on your code.
A fixed-scope engagement. Backbrief Business OS installed and configured in your own repository, the two or three rules your team keeps breaking encoded as gates, and one real task run through it so you can see what the verifier does with your own work before you trust it.
$1,500
Fixed fee. Introductory price for the first three engagements.
Two engagements a month, at most.
Read this before you apply
Delivery runs Claude (Anthropic) inside your environment. The source code, configuration, and documents in scope are transmitted to the model provider for processing. You can exclude anything from scope in writing before work begins, and the full terms are shown before you pay.
Setup service termsWhat you get
Four deliverables, fixed.
01
A working install, configured to your stack.
Backbrief Business OS in your repository, set up for the languages and tools you actually run, with the optional enforcement layer installed and its state reported truthfully by /verify-install. One thing stated up front: in interactive bypass-permissions mode the engine-level stops are inert by design, so a team running bypass gets a correct install with an honest NOT FULLY ENFORCED line, not a guarantee of enforcement in a mode they choose later.
02
Your own rules, encoded.
The two or three things your team keeps getting wrong, written as the rules and gates that stop them happening. Not a template. The specific failures you named in the application, turned into files your agents read on every run.
03
A before-and-after evidence pack.
One real task from your backlog run through the system, with what the verifier returned included as an artifact rather than described: the rejection, the caught defect, or the clean pass. You see the gate act on your own work before you decide whether to trust it.
04
One recorded walkthrough, plus a bounded tail.
A recorded walkthrough for your team, and two email exchanges within thirty days of handover. Bounded on purpose, so the tail cannot become open-ended support and the fixed price stays honest.
What it is not.
- Ongoing consulting or a retainer.
- Custom software or features built into your product.
- Prompt writing as a service.
- Open-ended access to your systems after handover.
Those exclusions are what the fixed price buys. Anything outside them is a separate conversation with its own number.
How it runs
Nothing starts before the terms and the payment. Nothing outward happens without your written yes.
01
Apply.
Five questions, answered by email. The second one does the qualifying: if you cannot name a specific incident, you do not have the problem this fixes yet, and the honest reply is the free kit.
02
A written reply, either way.
Either a statement of work naming what the engagement will and will not touch, or a plain no with the reason.
03
Terms, exclusions, and payment.
You read the setup service terms, list anything you want excluded from scope in writing before work begins, and pay the fixed fee. Nothing starts before both.
04
Access, at the minimum.
You create scoped, revocable credentials, never shared passwords. Every change lands on a branch you merge yourself. Nothing is sent, published, spent, or deleted with your access unless the statement of work names it and you approve it in writing at the time.
05
Delivery.
About a day of active work on our side, spread over the window the statement of work sets. You get the four deliverables above and a written note when work is complete, so you can revoke access.
The fine print, in the open
Capacity, and what happens if something is missing.
Two engagements a month, at most.
One person delivers this, so the limit is real. It is published here rather than discovered after payment. If the month is full, the reply says so and offers the next open slot instead of a waiting list nobody updates.
The remedy is a re-run, then a refund of the unearned part.
If a deliverable on the list above is missing at handover, say so inside the thirty-day window and that part is re-run at no charge. If it still cannot be delivered, the unearned portion of the fee is refunded. This is the engagement's own remedy; the all-sales-final policy on the downloadable products does not reach it.
The full terms are four short sections: the AI processing disclosure, credentials and access, ownership, and the liability cap. They are written in plain language and shown before you pay. Read them here.
The application
Five questions. The second one decides it.
Answer them in an email. Short answers are fine; specific ones are better. The reply comes back in writing, either way.
01
What are you building, and what does your team run today? Repo size, language, team size.
02
What has gone wrong that made you look for this? Be specific about the last incident.
03
Are you already running the free kit or the paid bundle?
04
Who signs off on a spend of this size at your company, and is that you?
05
What would you need to see at the end to call this money well spent?
Or write to charles@charlesashe.ai with the five answers.
Questions a careful buyer asks first.
Why is the price on the page?
Because a conversation that ends at the number is a conversation nobody needed. It is a fixed fee, it is the introductory price for the first three engagements, and it will be repriced from what those three show.
Is this how I get the paid bundle?
No. Backbrief Business OS is a $79 one-time download and installs itself in about ten minutes. This engagement is for a team that wants the install done, their own rules encoded, and proof it works on their code before they roll it out. If a download would do, buy the download.
What happens to my code?
Delivery runs Claude Code inside your environment, which means the code and documents in scope are transmitted to Anthropic's servers for processing under Anthropic's own terms. That is stated in the terms before you pay, you can exclude any file, directory, credential, or system from scope in writing before work begins, and those exclusions are honored.
Who owns the rules written for us?
You do, on full payment, for use within your organization. Backbrief's own products and methods stay Backbrief's under their existing licenses, and nothing about the engagement gives Backbrief any claim on your code, data, or business information.