# One link for each piece of client work, from the pitch to the handover.

Each client’s proposal, review deck and handover kit gets its own link, shared with only the people who need it. When you revise one, the client’s link shows the new version.

## One client, start to finish

Ostra Studio pitches Saltmarsh Inns with the proposal above, and the client picks a package and approves it in the page. A week later the studio presents two brand directions in the review deck below. The client follows along on their own laptop and makes the choice in the room. At the end, a brand kit page hands everything over, from the PDF guidelines to the launch deck.

| Stage | The artifact | Shared by |
| --- | --- | --- |
| Pitch | Interactive proposal with packages and approval | Secret code, expiring in 30 days |
| Review | Presentation with live comparisons and a decision slide | Email, to the client team |
| Handover | Brand kit page plus the PDF, deck and docs | Email, plus a code for the photographer |

Sample presentation: [Saltmarsh brand review](https://artifact.guru/examples/saltmarsh-design-review). The deck Ostra Studio presented to the client.

## How agencies set it up

1. **A team workspace** Everyone on the team connects their own agent (Claude, ChatGPT, Codex, Gemini CLI or Grok) and publishes to the same place.
2. **One project per client** Keep everything for that client in one project, from the proposal to the reports. Search finds text in all of it, PDFs and decks included.
3. **Each piece on its own terms** Invite the client to the proposal by email, and put a secret code on the draft so the wider client team can open it. Internal notes stay private.
4. **Your own domain** On Individual and Team plans, public and secret-code links move to a subdomain like `work.youragency.com`.

## Know when the client has looked

Open the artifact and switch to **Views**. On an **Email** link you see each person who opened it, when and how often. You also see which invited people haven’t opened it yet, so you know when to call.

**Public** and **Secret code** links show numbers instead of names. You see how many people visited, where they came from and what devices they used. Opens by your own team don’t count while they’re signed in to artifact.guru, so the numbers are the client’s.

Sample brand kit: [Saltmarsh brand kit](https://artifact.guru/examples/saltmarsh-brand-kit). The handoff page shows the new brand’s logo, colors and type. The guidelines PDF and the launch deck sit in the same project.

## Limits

- A team workspace needs the Team plan.
- There’s no client portal and no comment threads, so feedback stays wherever you already talk to the client.
- Pages run in a sandbox with no server, so approvals go out by email or to a form service you use.

## Questions

### Can different clients see different files?

Yes. Access is set per artifact, so each link is shared only with the people you choose.

### Do clients need an account?

Not for secret-code or public links. Invited clients sign in with the address you invited, which puts their names in your Views.

### Can our whole team work in it?

Yes. Create a team workspace and invite people as admins or members. Each person connects their own agent.

Source: https://artifact.guru/use-cases/agencies