# First-client project: Juniper website refresh

Version 1, 29 October 2026. Fictional training scenario, not a customer result. All names, dates and amounts are illustrative. Addresses use the reserved .example domain; do not send email to them. Copy and adapt this kit in any project tool. No sign-in is needed to read it.

## Inquiry and agreement

Inquiry, 28 October: "We need our five service pages refreshed before our December campaign. Casey has the content; Rowan approves the work. Can you keep the existing CMS?"

Confirmed scope, 2 November: refresh Home, Services, About, Work and Contact in the existing CMS. Two consolidated revision rounds. Include a handover guide and one training call. Exclude ecommerce, copywriting and additional pages. Illustrative agreed fee: USD 6,000. Payment and signatures stay in the team's existing billing and signing tools. A won deal is not evidence that a payment was received.

Create one account, two people and a won deal using the three CSVs in this folder. Then create a project named "Juniper website refresh", link the account and deal, and copy this scope into its brief. Importing the deal does not create the project, its tasks, the contacts on the deal or a signed agreement. Check each relationship after setup.

## Kickoff brief

- Delivery owner: Alex, the studio lead (assign a real workspace member).
- Client approver: Rowan Lee. Input and access contact: Casey Morgan.
- Target: a reviewed five-page build by 20 November, subject to receiving content and access by 5 November.
- Acceptance: all five agreed pages checked on mobile and desktop; client-supplied copy applied; contact form delivery tested by a person; two revision rounds recorded; Rowan explicitly accepts the final version.
- Access: ask Casey to invite the named team member with the minimum CMS role. Store the system name and access status here, never a password or recovery code.
- Open question: who maintains the site after the handover? Rowan to confirm by kickoff.

## Six delivery tasks

These are proposed dates, not a scheduling guarantee. Create and assign the tasks deliberately. A project template makes a new copy; it does not send messages or collect approvals by itself.

| Task | Owner | Input / dependency | Target | Done means |
| --- | --- | --- | --- | --- |
| Confirm brief and approver | Alex | Agreed scope and two contacts | 3 Nov | Rowan confirms the five pages, exclusions and review process |
| Confirm content and CMS access | Alex; Casey supplies inputs | Brief | 5 Nov | Named member signs in successfully; five copy documents are accessible |
| Prepare homepage direction | Designer | Brief; brand assets | 9 Nov | A dated draft and open questions are ready for Rowan |
| Record first-round approval | Alex | Homepage direction | 11 Nov | Rowan's actual decision, version and requested changes are saved |
| Build and check five pages | Designer | Access; copy; approved direction | 18 Nov | All five pages and the form have recorded checks; unresolved defects are listed |
| Complete handover | Alex | Build checks; final approval | 20 Nov | Owner, access, files, open issues and support boundary are acknowledged |

## Day-7 checkpoint: 9 November

Expected exercise state: brief confirmed; content and access checked; homepage direction ready for review. Record the actual state, even if it is behind this plan. If CMS access is missing, keep the access task Waiting, name Casey as the next contact, and identify which build work is blocked. Alex contacts Casey outside the assistant connector. Do not mark access received because an invitation was sent.

## A scope change with a decision

On 10 November Rowan asks for a sixth page. Alex records CR-01: requested page, reason, estimated cost and delivery impact. The example decision on 11 November is "defer to a separate quote; retain the original five-page scope." The original deadline remains a target, not a guarantee. Do not add the sixth page to accepted delivery work before an actual decision. In a real engagement, obtain approval through the agreed contractual process.

## Permission and review exercise

1. Create this as a test project and create a second empty test project named "Other client". Use no real client data.
2. Connect an assistant to the Juniper project with read-only access. Ask: "Read Juniper's brief and tasks. List the agreed scope, the next owner and missing evidence. Do not change anything." Check the answer against the records.
3. Ask it to read the Other client project by its known ID. The connection must not return that project's contents. An empty search alone is not a conclusive access test. If unexpected data appears, stop the exercise and revoke the connection.
4. With the read-only connection, ask it to change the test task's due date. The write should be refused. Confirm the task stayed unchanged.
5. If you want to test writes, reconnect with update access limited to Juniper. Ask for a proposed task through Flori's proposal flow, rather than a direct edit: "Propose a task to request the missing logo, with no due date. Do not create an accepted task or modify the brief."
6. Inspect the proposal in Flori. Accept it only if the task, project and owner are right; otherwise reject it. Read the resulting task back.

Proposal review, submitted assistant work and direct authorized updates are different paths. Update access permits some immediate changes; it is not a universal approval queue. Client publication is a separate deliberate action. The MCP connector does not send client email, charge a card or publish a website.

This is a repeatable exercise. The import files are checked by Flori's local importer tests; this document is not a claim that a live Claude session or a competitor trial was completed.

## Weekly update and final packet

Use weekly-client-updates.md for three possible status messages. They are alternatives, not three events that all happened. Use project-handover.md at completion. Link the exact deliverable version, keep unresolved work explicit, and ask the real approver to confirm. A prefilled "approved" example is never approval for your project.