Cohort Install Terms

Who this is between

These terms are between WorkGrain, a service of Flow Connect Technologies LLC(the "Provider"), operated by Owen Nordberg, Reno, Nevada, and the person or business buying a seat in a Cohort Install (the "Owner").

1. What this is, in one line

The Provider builds the Owner a Claude Code workspace for their business, installs it with the Owner in a live group session, and coaches the Owner to run it over four weekly group calls. The Owner drives it, and the Owner owns it.

2. What the Owner gets

2.1 The workspace, built before install day.One folder organized around the Owner's business, built from the Owner's written intake: the business's context in the Owner's own words, the Owner's writing rules and voice (from the samples they share), the standard skills, the trade's skills for this cohort (for example, for promotional products distributors: setting up a job from an order, pulling tracking, and building a reorder list), an owner's manual, a getting-in guide for their computer, and the assistant's built-in coaching lessons.

2.2 The group install.One live session over Google Meet, about two and a half to three hours, on the date announced for the cohort and confirmed in the Provider's welcome email. The Owner installs the workspace on their own computer with the Provider and the group, has their first conversation with it, and connects their email and calendar and, where available, the cohort's trade tools, in their own accounts.

2.3 Four weekly group calls,about 90 minutes each, on the dates announced for the cohort and confirmed in the welcome email. Each call aims to teach one skill of running the workspace and to leave time for owners to work through their own real tasks on screen with the Provider's coaching.

2.4 The recordings of the install and the four calls, available to the cohort.

2.5 A group space (a Slack channel or similar) for questions between calls. The Provider answers questions there about once a business day during the four weeks. It is not 1:1 support.

3. What is not included

• The Owner's Claude plan and any other tool subscriptions. The Owner pays these directly. The Provider states any new cost before the Owner signs up for anything.
• 1:1 sessions, custom software, or work beyond Section 2. Those are a different product, quoted separately in writing.
• Changing anything in the Owner's other systems. For promotional products distributors, iSuite is read, not changed.
• Hardware and IT work.
• Business outcomes (Section 9).

4. Fees, dates and seats

4.1 The fee is the one-time amount shown on the payment page, paid in full when the seat is bought. There is no monthly fee from the Provider for the Cohort Install. An optional monthly membership may be offered at the end of the cohort; it is separate and only starts if the Owner chooses it.

4.2 Dates. The install day and the four calls run on the dates announced for the cohort and confirmed in the welcome email. If the Provider has to move a date, it gives as much notice as it can and offers a new date to the whole cohort.

4.3 Missed sessions. Group sessions are not repeated 1:1. If the Owner misses one, the recording is the make-up.

4.4 The intake comes first.The workspace is built from the Owner's intake. If the intake is not in at least five days before install day, the Owner may install with a more basic version of the workspace and fill the rest in with the assistant afterward, or move to a later cohort if one is running.

5. Refunds

5.1 Before install day: a full refund on request.

5.2 After install day: either party may end the arrangement by written notice (email is fine). The Owner keeps everything built so far (Section 6.1), and the Provider refunds the fee pro rata for the group sessions not yet held, counting the install day as one session and the four calls as four.

5.3 If the Provider cancels a cohort, it refunds every Owner in full.

6. Ownership and honest claims

6.1 Owned by the Owner, exportable.The Owner owns the workspace: the files, the knowledge base, the skills and configuration written for it, and their own data and accounts. Claude Code itself is Anthropic's software, used under the Owner's own Claude account. The workspace is plain, readable files in a folder the Owner can keep, copy, back up, or move.

6.2 Where it runs.The workspace runs on the Owner's computer and in the Owner's own accounts, not on the Provider's infrastructure. The Provider builds the workspace from the Owner's intake before install day and does not copy the Owner's project files or AI history onto its own machines or accounts without the Owner's permission. The Provider does not hold the Owner's passwords: the Owner signs in themselves.

6.3 Honest claims.The Provider does not claim this is a "private AI" or that the Owner's data "never touches the cloud." When the Owner asks Claude to work on a file, that file's content goes to Anthropic (the maker of Claude) to be processed, the same as any cloud AI. At install the Provider helps the Owner set their Claude account so their chats are not used to train Anthropic's models, where the plan offers that setting. Anthropic sets and can change its own terms; the Provider does not control them.

6.4 The Provider's own methods. The Provider keeps ownership of its reusable methods, templates, and the general WorkGrainbuild system, including the trade skills, which are shared across the cohort. The Owner owns their specific workspace, files and data. The Provider does not reuse the Owner's business data, customer information, or knowledge base for anyone else.

7. The group: confidentiality and recordings

7.1 What you show, the group sees.On the calls, owners may share their screens. Share only what you are comfortable showing the group. Every Owner agrees to keep what they see or hear about another owner's business confidential and to use it only to learn in the cohort.

7.2 Recordings.The install and the four calls are recorded. Recordings are shared with the Owner's cohort. Any use of a recording beyond the cohort (for example, a later cohort's library or the Provider's marketing) leaves out other owners' screens and business details unless that owner gives written permission. The Provider may use clips of its own teaching.

7.3 Case studies are opt-in.The Provider will only use an Owner's name, business, words or results publicly with that Owner's written permission.

8. Guardrails, and nothing leaves without the Owner

8.1 Guardrails.The workspace is opened in its own folder and runs in Claude Code's Manual mode, where file edits and most commands ask the Owner first; a built-in set of read-only commands runs without asking. The modes that skip the Owner's approvals are switched off in the workspace's settings. These are guardrails, not a wall: a command the Owner approves runs with the Owner's own computer permissions.

8.2 Nothing leaves without the Owner.The workspace is set up so the assistant does not send email, publish anything, or contact the Owner's customers, suppliers, or anyone else on its own. What it writes for someone else stops as a draft for the Owner to review. A job only graduates to acting on its own if the Owner decides that later, themselves.

9. What the Provider stands behind, and what it does not promise

9.1The Provider will build the workspace described in Section 2.1 from the Owner's intake, run the install and the four calls, and make the recordings available.

9.2 No specific business results. The goals the Owner writes in the intake are what the workspace is built toward. They are the aim of the work, not a warranted result. The Owner puts in the reps.

9.3 The assistant is AI and can make mistakes, including misreading orders, dates, quantities, tracking numbers, and the Owner's own documents. The Owner reviews its work before relying on it or sending it.

9.4 Third-party tools.The workspace relies on Claude Code and Claude (Anthropic) and the Owner's other tools. The Provider does not control those services, their features, pricing, uptime, or changes to their screens and terms, and is not liable for changes those providers make.

9.5 Limit of liability.Each party's total liability under these terms is limited to the fee the Owner paid. Neither party is liable for indirect or consequential losses.

9.6 Use after handoff.The workspace is the Owner's, and with ownership comes responsibility for its use: reviewing AI-generated content before acting on it or sending it, and using the workspace in line with the law and with the terms of the tools it connects to. The Provider is not liable for claims arising from the Owner's use, misuse, or modification of the workspace, and the Owner will indemnify the Provider against third-party claims arising from that use. Nothing here limits 9.1 for the workspace as delivered.

10. Owner responsibilities

To get the most from the cohort, the Owner agrees to: send the intake at least five days before install day; complete the setup page before install day; have a Mac or Windows computer they can install software on and a Claude plan; join the sessions or watch the recordings; and use the workspace in line with their own policies and the terms of the services they connect.

11. General

The Provider is an independent contractor, not an employee or partner of the Owner. These terms are governed by the laws of the State of Nevada, and disputes belong in the courts of Washoe County, Nevada. These terms, the payment page and the welcome email are the whole agreement for the Cohort Install; changes must be in writing. If any part is found unenforceable, the rest stays in effect. Our Privacy Policy also applies. Questions go to owen@workgrain.com.