LinkedIn → CRM enrichment sync

Live Sales Correlation key: lead_id · 96.8%

Live Automated since Feb 2026 — 7 h/week reclaimed across everyone who runs it, 162 h to date. 0 h/week of hands-on work is left, and that is the figure quoted everywhere on this page.

Case footprint: median 1.6 h elapsed, 16m 25s of it hands-on, across 1 work session and 0.1 calendar days. 7 of the 10 happy-path waits exceed the 150 s idle-gap threshold, but a gap only ends a work session when it outlasts one (59 min, the fleet's mean). None here do: the case is put down and picked up inside the same sitting, while the person works other cases.

Cases: 176
Activities: 13
Variants: 38
Median throughput: 1.6 h
p95 throughput: 6.7 h
Working time / Waiting time: 16m 25s / 78m 48s
Rework: 14%
Fitness: 0.91
Precision: 0.77

No filters — showing every case

176 of 176 cases (100%)

Directly-follows map

Discovered from the event log. The editable automation design is the last tab.

showing 13 of 13 activities · 100% of activity instances covered

Geometry is computed at build time, so nothing reflows when you filter. 48 of 88 directly-follows relations sit below the 0.20 noise threshold and are hidden; together they carry 4.2% of transitions.

Node fill 0–20%20–40%40–60%60–80%80–100% Happy path Loop back Self-loop

Five discrete steps. Edge thickness is a square-root scale on frequency, so the busiest edge is 8 px and the quietest 1 px.

Where the hours go

Edges ranked by total recoverable waiting time, not mean.

9% working 91% waiting · mean 10m 29s · p95 35m 39s · 156 cases affected · 10.6% of total cycle time
8.8% working 91.2% waiting · mean 10m 49s · p95 36m 47s · 161 cases affected · 10.5% of total cycle time
8.5% working 91.5% waiting · mean 10m 15s · p95 34m 51s · 153 cases affected · 10.3% of total cycle time
9.1% working 90.9% waiting · mean 9m 28s · p95 32m 11s · 126 cases affected · 7.1% of total cycle time
10.3% working 89.7% waiting · mean 5m 42s · p95 19m 23s · 144 cases affected · 5.5% of total cycle time
6.9% working 93.1% waiting · mean 4m 58s · p95 16m 53s · 175 cases affected · 5.2% of total cycle time

Variant explorer

One row per distinct end-to-end activity sequence, ranked by case count. Row 1 is the happy path and every other row is column-aligned to it, so deviations read as vertical discontinuities.

Top 12 variants cover 83% of cases.

Select exactly two variants to compare.

#	Variant	Sequence	Cases	% of cases	Cumulative	Median	p95	Steps	Δ vs happy path	Conformance	Compare
1	V-01 Happy path	SNOPQLERDDCLANORCV	57	32.4%	32.4%	65m 30s	5.4 h	9	—	Conforming	Compare V-01
2	V-02	SNOPERQL^×2ERDDCLANCLORCV	17	9.7%	42.1%	1.9 h	11.7 h	11	+2 · 47m 35s	Deviating	Compare V-02
3	V-03	SNMDOPQLERDDCLANPVORCV	16	9.1%	51.2%	85m 12s	10.1 h	11	+2 · 19m 42s	Deviating	Compare V-03
4	V-04	SNQLOP^×2QLERDDCLSWANORCV	13	7.4%	58.6%	1.7 h	11.5 h	11	+2 · 38m 23s	Deviating	Compare V-04
5	V-05	OPSN^×2OPQLERDDCLANORCV	10	5.7%	64.3%	84m 10s	5.3 h	9	—	Deviating	Compare V-05
6	V-06	SWSNOPSWQLERDDCLANORCV	8	4.5%	68.8%	1.8 h	11.1 h	11	+2 · 42m 08s	Deviating	Compare V-06
7	V-07	SNOPQLERDDCLANORCV	7	4%	72.8%	61m 01s	7.1 h	8	-1 · -4m 29s	Deviating	Compare V-07
8	V-08	SNOPQLERCLDD^×2CLANORCV^×3	5	2.8%	75.6%	2 h	14.3 h	13	+4 · 56m 46s	Conforming	Compare V-08
9	V-09	SNPVULOPQLERDDCLSWANORCV	4	2.3%	77.9%	1.9 h	14.7 h	12	+3 · 48m 27s	Deviating	Compare V-09
10	V-10	SNOPQLULERDDCLSWPVANORCV	4	2.3%	80.2%	2.1 h	11.7 h	12	+3 · 60m 58s	Deviating	Compare V-10
11	V-11	OPSN^×2OPQLERDDCLANORCV	3	1.7%	81.9%	73m 56s	6.8 h	10	+1 · 8m 26s	Deviating	Compare V-11
12	V-12	SN^×4OPQLERDDCLANORCV	2	1.1%	83%	2.1 h	8.1 h	13	+4 · 61m 35s	Deviating	Compare V-12
—	Other variants (14) · 8% of cases	Activity sequence —	14	8%	100%	—	—	—	—	—

22 variants (57.9% of all variants) occur exactly once, together 12.5% of cases.

Variant distribution

Rank on a log scale against cases on a log scale, with cumulative coverage on the right axis.

Cases (log scale) Cumulative coverage (%) Variant rank (log scale) 10 variants cover 80% of cases

Variant comparison

Two variants on the same alignment columns. Colour says which side; hatching repeats it, so the diff survives greyscale.

Variant A

Variant B

A · V-01

Merged activity set

B · V-02

Merged activity set

Every alignment column, coloured by which side uses it.

In both Only in A Only in B In neither

List of changes

Side by side
Side by side	A	B	Δ

Attributes associated with each branch

These are associations measured on the log, not causes. Every rule prints the number of cases it was measured on.

Lead source `lead_source`

171 of 176 cases · 2.7% missing

Inbound form58 · 33%
Sales Navigator42 · 23.9%
Event list31 · 17.6%
Partner referral23 · 13.1%
Cold list17 · 9.7%

Rule statements

Ranked by lift × support. Each rule is a sentence you can read aloud.

When region = DACH → the case takes “Merge a duplicate record” in 40.4% of cases (baseline 10.2%, lift 3.96×, n = 43).
40.4% confidence 10.2% baseline 3.96× lift n = 43
When deal_band = > €100k → the case takes “Merge a duplicate record” in 41.6% of cases (baseline 10.2%, lift 4.08×, n = 22).
41.6% confidence 10.2% baseline 4.08× lift n = 22
When product_line = Plus AND resource_count > 3 → the case takes “Update the existing lead” in 11.7% of cases (baseline 5.7%, lift 2.05×, n = 27).
11.7% confidence 5.7% baseline 2.05× lift n = 27
When rep_tenure > 58 AND lead_source = Sales Navigator → the case takes “Update the existing lead” in 15.8% of cases (baseline 5.7%, lift 2.77×, n = 8).
15.8% confidence 5.7% baseline 2.77× lift n = 8
When lead_source = Sales Navigator AND deal_band = > €100k → the case takes “Update the existing lead” in 11.7% of cases (baseline 5.7%, lift 2.05×, n = 8).
11.7% confidence 5.7% baseline 2.05× lift n = 8

Decision point

Pick an exclusive choice in the map to see its branch shares and the attributes that discriminate between them.

Decision point

Branch

Qualify the prospect156 · 89.7%
Open Sales Navigator15 · 8.6%
Switch application9 · 5.2%
Enrich the record9 · 5.2%

Pick an exclusive choice in the map to see its branch shares and the attributes that discriminate between them.

Conformance against the reference model

Reference model v3, 28 Jun 2026

Fitness0.91

Precision0.77

Fitness and precision trade off; we report both rather than a single model-quality score.

Conforming cases — 67 (38.1%) Non-conforming — 109 (61.9%)

Deviations by type

A deviation is not necessarily an error — it is behaviour the reference model does not allow.

					Breaks conformance
Invalid activity	76	43.2%	4m 03s	5.1 h	Breaks conformance
Skip	70	39.8%	3m 01s	3.5 h	Breaks conformance
Loop back	55	31.3%	2m 46s	2.5 h	—
Activity retry	33	18.8%	4m 24s	2.4 h	—
Exclusive-choice violation	17	9.7%	1m 39s	28m 03s	Breaks conformance
Invalid start/end	9	5.1%	0s	0s	Breaks conformance

Conforming cases over the window

Conforming cases (%) · 16 Jun – 13 Jul 2026

Conforming cases (%)16 Jun – 13 Jul 2026

Rework and loops

Self-loops and loop-backs, with loop inflow, outflow and net gain.

Activity	Kind	Self-loops	Cases affected	Mean repeats	Loop in	Loop out	Net gain	Total waiting
Assign the record owner	Loop back	0	18	2×	18	14	+4	7.3 h
Create the lead record	Self-loop	17	17	2×	17	16	+1	17m 31s
Qualify the prospect	Loop back	0	17	2×	17	13	+4	6.2 h
Open the prospect profile	Loop back	0	16	2×	16	12	+4	3.8 h
Open work item	Loop back	0	16	2×	16	15	+1	2.2 h
Open Sales Navigator	Loop back	0	15	2×	15	15	0	6.2 h
Open the prospect profile	Loop back	0	14	2×	14	12	+2	5.8 h
Qualify the prospect	Loop back	0	9	2×	9	9	0	4 h

Rework cost €604–906 · 25 cases · 30 h Costed at the €25/h loaded rate used everywhere in this dashboard.

Cases

Showing 16 of a 40-case sample drawn from 176 cases, across the 24 variants listed on the Variants tab. The totals above are exact; this table is sampled.

Variant				Roles	Departments		Conformance
V-01	2026-07-10 10:42:43	50m 18s	9	Sales Ops ManagerAccount Executive	sales	0	Conforming
V-02	2026-07-09 11:54:54	3.9 h	11	Account ExecutiveSales Ops Manager	sales	3	Deviating
V-11	2026-07-09 10:47:08	2.2 h	10	Account ExecutiveSales Development	sales	2	Deviating
V-01	2026-07-09 09:35:55	1.6 h	9	Sales Development	sales	0	Conforming
V-05	2026-07-08 16:53:59	2.1 h	9	Sales Ops ManagerAccount Executive	sales	2	Deviating
V-09	2026-07-08 14:45:49	2.4 h	12	Account Executive	sales	0	Deviating
V-01	2026-07-08 10:46:44	3.2 h	9	Sales DevelopmentSales Ops Manager	sales	0	Conforming
V-01	2026-07-07 14:52:41	82m 19s	9	Sales Ops ManagerSales Development	sales	0	Conforming
V-01	2026-07-07 08:10:47	29m 19s	9	Sales Ops ManagerSales Development	sales	0	Conforming
V-06	2026-07-06 16:54:14	1.8 h	11	Account Executive	sales	1	Deviating
V-06	2026-07-06 16:15:01	29m 24s	11	Sales Development	sales	1	Deviating
V-01	2026-07-06 14:44:40	2 h	9	Sales Ops Manager	sales	0	Conforming
V-10	2026-07-06 11:11:44	1.7 h	12	Sales DevelopmentAccount Executive	sales	0	Deviating
V-04	2026-07-03 08:03:51	2 h	11	Account ExecutiveSales Development	sales	2	Deviating
V-06	2026-07-02 14:43:46	2.5 h	11	Sales Ops ManagerAccount Executive	sales	1	Deviating
V-13	2026-07-01 12:06:38	2.1 h	11	Sales Ops ManagerSales Development	sales	2	Conforming

16 of 40

Live 88% confidence

Automation design

The Map tab is what the event log shows. This is the automation you are designing from it.

CRM (web)LinkedInChrome

7h reclaimed / week across everyone who runs it

Case V-01 Conforming

—

· Process: LinkedIn → CRM enrichment sync · Correlation key lead_id

Total duration

Working Waiting Steps · Rework

Field	Value
`lead_id`	LED-2026-77097
`account`	Atlas Papeleria SA
`amount_eur`	€5,604.52
`region`	Benelux
`owner_role`	Sales Ops
`contact_phone`	+34 ••• ••• 236 · masked at capture (Phone number masked at capture)

Field	Value
`lead_id`	LED-2026-93973
`account`	Nordvant Components BV
`amount_eur`	€45,272
`region`	Benelux
`owner_role`	Sales Ops
`contact_phone`	+34 ••• ••• 553 · masked at capture (Phone number masked at capture)

Field	Value
`lead_id`	LED-2026-07090
`account`	Atlas Papeleria SA
`amount_eur`	€39,810.4
`region`	Nordics
`owner_role`	Sales Ops
`contact_phone`	+34 ••• ••• 932 · masked at capture (Phone number masked at capture)