Follow-through & integrations
A reminder that fails tries again somewhere else.
The ladder runs 90 · 60 · 30 · 7. Delivery is retried, escalated and logged. Actions have owners and clocks. Your calendar, Slack and Jira see the same dates you do.
Reminders · Globex Services · notice by Jan 15 · 30-day rungSweeping
Delivery · Dec 16 · 08:00owner Morgan Lee
Slack · #procurementfailed · channel archived30 days to the Globex notice window · owner Morgan
Retry · Slack DM to Morganfailed · user not in workspaceSame message, direct · 08:02
Fallback · Email to morgan@northwind.exampledelivered · opened 08:41Deep link to the decision · 08:03
Escalation armed · Priya KaurscheduledIf no decision by Dec 23 · in-app + email
Sweep heartbeat · checking the 30-day rung…
Action · Decide renew or exitWaiting on delivery
OWNERMorgan Lee · escalates to Priya Kaur on Dec 23DUEJan 1 · 14 days before the notice window closesBLOCKEDNo · exit cost computed · $182,000 todaySOURCEGlobex Services Agreement §9.2 · p. 11
Mirrored
ICSCalendar · “Globex notice window closes” · alarms at 90/60/30/7live
JIRALEGAL-482 · “Decide Globex renewal” · assignee Morgan · due Jan 1synced
HOOKobligation.reminder.delivered → your endpoint · signed200
Reference contracts never chase anyone · only the Tracked shelf runs the ladderabandoned deliveries are a metric, not a mystery
Ladder · retry · escalate · mirror — every step logged
Meets people where they already work.
Legal · procurement · finance · ops
The vendor owner gets the Slack. Finance gets the invoice date. Legal gets the escalation.
Per-workspace ladder rules: which rungs, which channels, who is copied, when it escalates.
Actions with owners and SLA states live in the action centre — and in Jira if that is where the team lives.
Recurring obligations and “awaiting an event” items check in with the owner instead of guessing.
Lawyers · firms
Client deadlines in your own calendar. Their acknowledgements on the record.
One ICS feed per matter or per workspace, with alarms that match the ladder.
Counterparty digests with signed unsubscribe. The other side sees what they owe and can say “this happened”.
Every notification, retry and escalation is an activity line you can show a client.
02Integrations
Contracts in from where they live. Dates out to where you look.
Intake from email, Drive, Dropbox, SharePoint, Box, DocuSign and Adobe Sign. Follow-through out to calendar, Slack, Teams, email, Jira and signed webhooks.
Integrations · one contract, end to end
Intakecontracts+7f3a@northwind.clauseminds.appTomás forwards the signed Vantage Print PDF from his phone.waiting
Read3 obligations · 1 needs youAuto-renewal with 45-day notice · Net 30 · uncapped price uplift parked.waiting
CalendarICS feed · LegalNotice window closes Mar 17 · alarms at 90/60/30/7.waiting
Slack#procurement“Vantage Print is in. Notice by Mar 17. Owner: Tomás.”waiting
JiraLEGAL-483“Review Vantage price uplift” · assignee Priya · due Oct 1.waiting
09:12:04inbound.email · 1 attachment · 8 pages · workspace token valid
09:12:41extraction.complete · 3 findings · 2 auto-accepted · 1 parked
09:12:42calendar.event.created · ics · Notice window closes Mar 17
09:12:42slack.post · #procurement · ok
09:12:43jira.issue.created · LEGAL-483 · ok
09:12:43webhook.delivered · contract.tracked · 200 · signature verified
Channels are off until you configure them · a webhook is re-validated at delivery · nothing leaves without a person
03What connects
Said plainly, including what is one-way.
Every connector states its direction and what it needs from you. A legal deadline never moves because a calendar event was dragged.
Inbound emailinA private, rotatable address per workspace. Every file acknowledged with a deep link.
Google Drive · Dropbox · SharePoint · BoxinOAuth import of folders; bulk migration with duplicates and families handled.
DocuSign · Adobe SigninImport executed copies; DocuSign Connect auto-imports on completion. On-platform legal-grade signing is not offered yet.
Calendar (ICS)out · one-waySubscribe from any calendar. Alarms match the ladder. A calendar edit never moves a legal deadline.
Slack · Teams · EmailoutReminder channels per workspace. Off until credentials are added and the workspace opts in.
JirasyncActions become issues with owner and due date; status flows back. The only task adapter today.
Signed webhooksoutZapier / Make-compatible events, signed and re-validated at delivery. No turnkey Zapier app yet.
Word add-inin-placeTask pane runs playbook and risk checks in Word and inserts wording as tracked changes. Sideload for now.
04How it works
Compute. Ladder. Deliver. Mirror.
01ComputeDeadlines derived from governing terms across amendments, including recurring occurrences and awaiting-event items.
02LadderPer-workspace rules: which rungs, which channels, who is copied, when it escalates. Default 90 · 60 · 30 · 7.
03DeliverFailed deliveries retry, fall back to another channel and escalate. Abandoned deliveries are a metric.
04MirrorCalendar feed, Slack, Teams, email, Jira and signed webhooks all see the same date you do.
05Before · after
Reminders that used to depend on memory.
The way it wasWith ClauseMinds
A calendar invite someone made in 2024.The deadline recomputes when the amendment lands. The alarms follow.
A reminder to a Slack channel that was archived.Retry, fall back to email, escalate to a second person, log every step.
The owner left. Nobody knows.Ownership is a field. Reassign once; ladder, calendar and Jira follow.
The Jira ticket and the contract disagree.One object. The action is the obligation; status flows back.
06When this happens
When the deadline isn’t simple.
WhenThe counterparty has to do something.ThenThey get a digest and a portal. They can acknowledge, upload the certificate or report the event. Your reminder clears when they do.counterparty digest · “this happened”
WhenThe obligation recurs monthly.ThenOccurrences are generated from the term, each with its own rung and owner. Missing one never hides the next.recurring occurrences
WhenSomeone drags the calendar event.ThenNothing changes here. The feed is one-way; a legal deadline is derived from the contract. Snooze is done in-app and logged.the one asymmetry
07Principle
A deadline is derived from the contract, not from whoever remembers it.
01The ladder retries.A failed delivery is a state, not an end. Fallback channel, then escalation, then a metric.
02The heartbeat proves the sweep ran.A silent scheduler is an alert. Every run leaves a record.
03Nothing leaves without a person.Reminders inform. Notices, letters and writes to other systems are a person’s tap, logged, with Undo.
08Said plainly
What it does not do.
The calendar is one-way.Subscribe-only ICS with alarms matching the ladder. Calendar edits never move a deadline.
Jira is the only task adapter.Everything else goes through signed, Zapier- and Make-compatible webhooks. No turnkey Zapier app yet.
Channels are off until configured.Slack, Teams and email need credentials and a workspace opt-in. Until then delivery is in-app and logged.
Everything in follow-through
What ships with follow-through & integrations
Computed deadlinesFrom governing terms, across amendments. Recurring occurrences and awaiting-event items included.
Reminder ladderDefault 90 / 60 / 30 / 7 with per-workspace rules, channels and escalation.
Delivery retryFailed deliveries retry, fall back to another channel and are counted as a metric.
Sweep heartbeatThe scheduler proves it ran. A silent scheduler is an alert, not a hope.
Action centreOwners, SLA states, blocked and complete. One merged “your turn” queue.
Counterparty digestsThe other side sees what they owe and can report an event. Signed unsubscribe.
ICS calendar feedOne-way subscribe with VALARM matching the ladder.
Slack · Teams · EmailPer-workspace channels; configured, then on.
Jira syncActions as issues, status back. Signed webhooks for everything else.
Intake connectorsEmail address, Drive, Dropbox, SharePoint, Box, DocuSign, Adobe Sign.
Questions people ask
Ownership is a field, not a person's inbox. Reassign in one place and the ladder, calendar entry and Jira issue follow. Escalation to a second person is part of the rule, so a stalled owner never stalls the deadline.
No, deliberately. The ICS feed is subscribe-only. If someone drags an event in their calendar, nothing changes here; a legal deadline is derived from the contract, not from a calendar. Snoozing a reminder is done in ClauseMinds and logged.
Only for the Tracked shelf, and only once a channel is configured. Out of the box, delivery mode is in-app and log until you add Slack, Teams or email credentials and turn them on for the workspace.
Yes, through signed webhooks that Zapier and Make can consume — events like contract.tracked, obligation.reminder.delivered and contract.executed. Each delivery is signed and the endpoint is re-validated at send time.
Never miss the window again.
Upload one contract. Its dates are in your calendar before lunch.
14 days free · no card