A screenshot is not proof of work
Clients do not want last week's status PDF. They want a live board they can open, without seeing your vault, your keys, or anyone else's account.
Sep 6, 2026 · 8 min · Jimmy Harika
Your client wants to know if the work is happening.
So you send a screenshot. Or a status PDF. Or a loom of you scrolling a dashboard they cannot click.
That is theater. It is also stale the second you hit send.
A live board, read-only, is the adult version. They see what is in Backlog, what is sitting in Needs you, what is In flight, and what is Done. They do not see your vault. They do not see your keys. They do not see the other client.
What a shared board is actually for
Proof. Not vibes.
A client who can open a link and see Clerk chasing invoices, Mail drafting the Hartley reply, Maker sitting on the October calendar, does not need a weekly "update" meeting. The board is the update. You still take the calls that need a human. You just stop performing the work.
This is why agencies invent status decks. The work is real. The client cannot see it. So you invent a second job: explaining the first job. That second job is unpaid, and it is the one that makes you hate Fridays.
A read-only board kills the second job.
Four columns, and that is the whole story
Octopus keeps the board boring on purpose.
Backlog. Created. A teammate will pick it up. The client can see the pile. They cannot pretend they never asked for the winter pricing page.
Needs you. Paused. Waiting on a call from you. This is the honest column. If a refund is sitting here, the client knows you have not vanished. They also know it is not sent until you tap.
In flight. Work a teammate has picked up. Mail on overnight replies. Clerk on payroll prep. Watch on vendor quotes. Motion, not a progress bar you typed.
Done. Finished today. The only column anyone actually believes.
If a vendor cannot show you those four, they are showing you a chat log with a coat of paint.
What stays private
Sharing a board is not sharing a company.
Keep the vault off. Keys never belong in a thread, and they definitely do not belong on a client link.
Keep other clients off. Northwind does not get to see Bell & Rowe. That is not a setting you "remember." That is the default.
Keep scopes tight. A client link is read-only. They do not approve sends. They do not open Stripe. They do not chat Clerk into doing a side quest.
Keep the run guts off if you want. Receipts are for you. "Listed 7 overdue invoices at 9:04" is useful internally. The client needs the card, not the pipe.
Dedicated workspace, never train. That is the floor. A share link does not change it.
When to keep the share off
Three times, at least.
The board is a mess. If Backlog is a junk drawer and Done is empty because nobody moved cards, you are showing them your laundry. Clean it, then share. Or do not share.
Legal said no. Some contracts do not want a live view of work product. Some clients are in a fight. Some industries treat a card title as a document. Listen. A PDF can be redacted. A live board cannot pretend it was never there.
There is nothing to show yet. Day one of a teammate is a first week. You would not CC a client on an intern's first login. Hire Clerk. Let Chief write the process. Let a Tuesday happen. Then send the link.
A share that is empty is worse than no share. It looks like you hired nobody.
How you send it without looking sloppy
Name the workspace like a studio, not like a debug dump. Northwind Studio. Not "jimmy-test-3."
Write card titles the client could read out loud. "Refund request from the Hartley account" is a sentence. "fix stripe thing" is a note to yourself.
Put the human column where they will see it. Needs you is the trust column. If everything is In flight forever, they will assume you are hiding.
Tell them what they are looking at in one line. "This is the board. Done is finished. The dark column is waiting on me." Then stop talking.
If they want a weekly PDF anyway, generate it from the board. Do not maintain two sources of truth. You will lie in one of them by accident.
The test I actually use
Would I let this client sit behind me for ten minutes while I work?
If yes, send the read-only board.
If no, because the vault is in the same view, because another client's name is on a card, because the titles are jokes: fix that. Then send it.
If no, because the work is a mess or the contract is a wall: keep it off. Take the meeting. Send the PDF. Do not pretend a live link is always the grown-up move.
Octopus is built so the desk can be shown. Four columns. Named teammates. A share that does not drag the vault with it. $99 gets you the board and the computer. The 7-day money-back is there so you can try this on a real client week, not a demo.
Straight answers
- What does a client actually see?
- The four columns: Backlog, Needs you, In flight, Done. Named teammates and card titles. Not the vault, not keys, not another client's work, and not a send button.
- Can a client approve work from the shared board?
- No. The share is read-only. Approvals stay on your desk. Needs you is there so they can see that something is waiting on you, not so they can tap it.
- When should I not send the link?
- When the board is a junk drawer, when the contract treats live work product as a problem, or when the teammate has not finished a real Tuesday yet. An empty board looks like you hired nobody.
Hire your first AI teammate
Ten minutes to set up, on the AI plan already sitting in your browser — or on ours.
Sign up