🐾 Private beta · invite-only · free during the beta
Contracts. Herded.
Pishik routes every contract through the review flow you design — sequential stages, parallel reviewers, per-document assignments. Reviewers never log in: each gets an emailed link, opens the document in your own storage, and confirms approve or reject. Nothing is recorded until they confirm.
🗂️Documents stay in your own storage — SharePoint, OneDrive, or Google Drive. Pishik keeps share links and workflow state, never your files.
MSA — Northwind × BigCoIn review
⚖️
Legal review
Dana Okafor · Counsel
✓
💳
Finance sign-off
Marcus Reyes · CFO
✓
✍️
Final approval
Sam Whitfield · VP Ops
✓
Illustration — sample data. Approvals advance the flow automatically; a rejection pauses it and notifies the team.
The short version🗂️ Docs stay in your storage✉️ Reviewers never log in📮 Email sends itself🧾 Everything tracked
How it works
Three steps. Zero herding.
Build the flow once — Pishik does the emailing, the chasing, and the record-keeping.
1
Build the flow
Paste share links from SharePoint, OneDrive, or Google Drive, then arrange reviewers into stages — sequential, parallel within a stage, or per-document for multi-part contracts. Save the layout as a reusable path.
→
2
Pishik emails your reviewers
The moment a stage starts, every reviewer in it gets a personal review link by email. Automatic reminders nudge anyone still pending — on the schedule you set.
→
3
Decisions advance the contract
Approvals move it to the next stage automatically. A rejection halts the flow and notifies the team, so you can fix the issue and resend. You watch it all on the Board.
Capabilities
One tidy home for the whole review
Design the flow once. Pishik handles the emails, the reminders, the discussion, and the paper trail.
Review flow · stage 2 of 3
DO
Dana Okafor
Legal review · whole contract
Approved
MR
Marcus Reyes
Finance · Schedule B
Reviewing
PS
Priya Shah
Finance · Schedule C
Reviewing
Both Finance reviewers must approve before the stage completes — then Pishik emails the final approver. Illustration — sample data. How flows advance →
What a reviewer receives
To: dana@northwind.example · via Pishik, for Northwind Trading
Your review is requested
MSA — Northwind × BigCo
W
Open the document →
Your share link · comment & redline with the rights the link grants
@Dana — did the indemnity cap survive the latest redline?
@mention
DO
Dana Okafor
Confirmed — cap held at 12 months.
Resolved
🔔
Automatic reviewer reminders
Pishik nudges pending reviewers on the schedule you set
Auto
Every @mention lands in a Tagged items inbox — seen, resolved, or escalated, never lost. Illustration — sample data. Comments & @mentions →
Sent · outbound email log
✉️
Review request — Dana Okafor
Sent the moment the stage started
Delivered
🔔
Reminder — Marcus Reyes
Automatic · on the schedule you set
Delivered
📣
Status update — counterparty
You choose exactly what it reveals
One click
Honest delivery statuses, a pixel-faithful preview of every send, one-click resend — and replies go to your team's reply-to address. Illustration — sample data. See the full tour →
See it in action
Your whole pipeline, at a glance
A Board that moves cards itself, a Dashboard that surfaces what needs you, and a searchable Repository of everything you've signed.
Pishik — sample workspace
Draft1
NDA
Vendor Co — Mutual NDA
2 stages · not started
In Review2
MSA
BigCo — Master Agreement
Finance sign-offMRPS
SOW
Acme — Statement of Work
Legal reviewDO
Approved1
Reseller
Contoso — Reseller Terms
Pending signature
Signed1
Lease
Suite 400 — Office Lease
✓ Fully executed
Illustration — sample data. Cards move themselves as reviewers decide — watch the Acme SOW go. 🐾
Active
5
1 draft · 2 in review
In review
2
2 reviewers pending
Signing
1
1 fully executed
Overdue
1
review sent 6d ago
Awaiting reviewer action
MR
MSA — BigCo
with Marcus · sent 6d ago
Overdue
DO
SOW — Acme
with Dana · sent 6h ago
Pending
Status distribution
Draft
Review
Approved
Signed
Illustration — sample data. The Dashboard surfaces what's waiting on you; admins also get workload, deadlines, and approval-queue views.
🔍 Search signed agreements…
📄
Contoso — Reseller Terms
Reseller · executed Mar 2026
Fully signed
📄
Suite 400 — Office Lease
Lease · executed Feb 2026
Fully signed
📄
Northwind — Renewal 2026
Renewal · executed Jan 2026
Fully signed
Illustration — sample data. Archive signed agreements into collections and search them in seconds.
Your contracts stay yours
Pishik adds the workflow — not another copy of your files. The architecture, in three lines:
🗂️ Your storage, not ours
Documents live in your own SharePoint, OneDrive, or Google Drive. Pishik stores share links and review state — never the files.
🏢 Isolated workspaces
Every organization gets its own isolated workspace. Your contracts, reviewers, and team are separate from everyone else's.
🧾 A true audit trail
Every decision, reminder, and change is recorded and attributed to the person who actually did it — even on-behalf actions.
No — and they never log in. Reviewers get an emailed link, open the document in your own storage, and approve or reject on a decision page. Nothing is recorded until they confirm. Only the people who build and manage flows need an account. How reviewing works →
In your own storage — SharePoint, OneDrive, or Google Drive. Pishik stores the share links and the workflow state, never the files. Any linkable document works: Word, Google Docs, Sheets, an Excel exhibit, a PDF. The share-link model →
Pishik is in private, invite-only beta. Request an invite — we review requests and email you a single-use invite code. Beta workspaces are free, with 10 seats per workspace during the beta and no card required. From invite to workspace →
Pishik sends every review request and reminder itself — there's nothing to configure and nothing to send by hand. Every send lands on the Sent page with an honest delivery status, and reviewer replies go to your team's reply-to address — yours, or a company-wide one your admin sets. Email that sends itself →