Skip to content
Services Blog Changelog About Sign in Talk To The Founder
Trigger-Based Workflows

Set the playbook. The system runs it.

Trigger-based workflows for relationship-led work. Multi-step sequences with wait timers, conditional branches, and signal detection. 20+ pre-built Playbooks cover the patterns that compound revenue: lost-deal recapture, renewal reactivation, referral nurture, dormant-network revival, signal-driven outreach. Plus a builder for the custom ones.

Talk To The Founder

30 minutes with the founder. On your actual data. Not generic slides.

Automation that pulls weight

Activity targets set, behaviour tracked, recommended actions surfaced. The system handles the follow-up bookkeeping so your week runs on commitments, not memory.

Nynch Today > Actions view with the Say-Do Ratio canvas tracking weekly activity targets and the Recommended versus Say Do columns

Trigger. Condition. Action. Done.

Every Automation follows the same shape: something happens, the system checks a condition, and an action runs (or queues for your review). The shape is simple. The leverage compounds because Nynch is reading dozens of signal types, job changes, engagement spikes, deal stalls, missed commitments, that you couldn’t monitor manually.

Triggers

12+ signal types

Job changes, engagement spikes or drops, deal stage transitions, missed commitments, anniversary milestones, news mentions, mutual-connection events, methodology checkpoint changes, and more. The trigger menu maps directly to the signals Nynch is already detecting via Relationship Intelligence.

Conditions

Multi-conditional logic

If contact is in a Strategic group, AND it’s been more than 30 days since contact, AND the contact’s engagement trend is down, only then run the action. The conditional layer keeps Automations from firing inappropriately.

Actions

Draft, queue, or send

Most actions involve drafting an email or LinkedIn DM and queuing it in your morning briefing for one-click approval. Internal-only actions (logging events, creating reminders, updating fields) run silently. You choose per-Automation what runs autonomously vs. what awaits review.

Automation flow: Trigger (Job change detected) -> Condition (in Strategic group) -> Action (draft reconnect email) -> Queue (in tomorrow morning briefing)

20+ Playbooks ready to install.

Most relationship-led firms run the same handful of patterns. Pre-built Playbooks make those one-click installable, then customisable.

Playbook 01

Lost-deal recapture

Triggers 90 days after a deal closes-lost. Checks whether the original blocker (timing, budget, scope) might have changed. Drafts a context-aware reconnect note for review.

Playbook 02

Renewal reactivation

Triggers 120 days before a contract end-date. Surfaces the Client Cockpit for the account, drafts the renewal-conversation opener, and queues the meeting request.

Playbook 03

Referral nurture

Triggers 30 days after a successful engagement. Drafts a referral ask to the project champion, calibrated to the relationship strength and the specific work that just succeeded.

Playbook 04

Dormant-network revival

Quarterly trigger. Identifies the 30 highest-value contacts in your Sleeping Network and queues a personalised reconnect campaign via Personalised Communication.

Playbook 05

Signal-driven outreach

Triggers when one of 12 signal types fires on any contact (job change, funding, hiring, role expansion, content engagement spike). Drafts a context-specific note referencing the actual signal.

Plus 15 more

Industry & motion-specific

Whale-Hunting follow-up sequence. Multi-stakeholder mapping completion. Champion-departure response. New-buyer-introduction protocol. Quarterly business review prep. Each one targeted at a recognisable pattern.

For relationship-led businesses.

For Consultants

The patterns you keep meaning to systematise

You know you should follow up 90 days after a closed-lost deal. You don’t. You know you should ask for referrals after a successful project. You forget. Automations turn the patterns you intend to run into ones the system runs for you.

For Fractionals

One playbook stack per portfolio

Your fractional CRO motion has different patterns than your fractional CFO motion. Each portfolio gets its own enabled Playbook stack. Switching between contexts means the right Automations are active automatically.

For Agencies

Firm-wide playbook standardisation

The renewal protocol that works for one account lead becomes a Playbook the whole agency runs. Onboarding new account leads becomes “here are the eight Playbooks every account runs”, not a 47-page playbook PDF.

See Playbooks running on real data.

Book a 30-minute walkthrough. We’ll install three Playbooks on a sample of your network and show you what the morning briefing looks like a week from now.

Talk To The Founder

30 minutes with the founder. On your actual data. Not generic slides.