Received: from smtp-out-01.detailplace.com (smtp-out-01.detailplace.com [66.96.91.171])
	by mail.itpartnership.com with ESMTPS
	(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256)
	; Thu, 7 Aug 2025 06:41:14 +0100
Received: from inbound-int-01.detailplace.com (inbound-int-c00996-00001 [10.250.3.230])
	by smtp-out-01.detailplace.com (Postfix) with ESMTPS id A29F9827A4
	for <bob@sarahharvey.com>; Thu,  7 Aug 2025 05:41:12 +0000 (UTC)
Received: from 29077656-0d5b-4b1d-b915-ba8568701bf1.local (ec2-3-91-220-68.compute-1.amazonaws.com [3.91.220.68])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	(Authenticated sender: jurisbaums@checkhyperscan.com)
	by inbound-int-01.detailplace.com (Postfix) with ESMTPSA id 26A4B3F05F
	for <bob@sarahharvey.com>; Thu,  7 Aug 2025 05:41:12 +0000 (UTC)
From: "Juris Baums" <jurisbaums@checkhyperscan.com>
To: <bob@sarahharvey.com>
References: <5a88b3b3-1667-49a5-84de-28a9c2b09a3c@checkhyperscan.com>
In-Reply-To: <5a88b3b3-1667-49a5-84de-28a9c2b09a3c@checkhyperscan.com>
Subject: Re: Sourcing time
Date: Thu, 7 Aug 2025 06:41:12 +0100
Message-ID: <29077656-0d5b-4b1d-b915-ba8568701bf1@checkhyperscan.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Mailer: Microsoft Outlook 16.0
List-Unsubscribe: <https://proxwannishscaries.com/unsub/1/bc9fd321-d56d-4bd4-95bf-f6b4d471f155>
Thread-Index: AQMc5T9r5RkkWRCc/4FEiK2PMoKdqAISwuhT
X-OlkEid: 00000000CC09373165EA424894A88D7C135300090700C3B68E10F77511CEB4CD00AA00BBB6E600000000000B0000F3CAA7D39DC9FE498D8F5D237175EB78000000006F060000E81530A2F48F3E4A808788B23382AAEA

Doesn’t seem like a match? Totally fine - I’ll step back.

We’re recruiters building for recruiters - even a quick reply helps. Mind 
picking one?

 1. Sounds useful, but timing’s off - check back later.
 2. Not a fan of using AI in recruitment.
 3. We’re good with what we’re using now.


Other reason? We're open to hearing it.



Juris Baums
Founder @ Hyperscan(.)co



Prefer no contact? Simply send 'pass' to end it here.


On Mon, August 4, 2025 8:20 AM, Juris Baums <jurisbaums@checkhyperscan.com>
[jurisbaums@checkhyperscan.com]> wrote:

> In case you like a video, I can share a short clip.
>
> It demos how Hyperscan re-ranks profiles to highlight most suitable 
> profiles faster.
>
> Should I share it?
>
>
> Juris
>
>
>
>
> Not your thing? Just reply 'pass'
> On Thu, July 31, 2025 6:14 AM, Juris Baums <jurisbaums@checkhyperscan.com>
> [jurisbaums@checkhyperscan.com]> wrote:
>
> > Hey Bob,
> >
> > You and Sue appeared to be the right people to reach out to.
> >
> > Imagine this sourcing flow:
> >
> > Search LinkedIn using your top filters.
> >
> > Define your custom profile criteria, like:
> >
> >
> > - "Has led teams of 12+ people?"
> > - "Has experience across 3 different business functions?"
> >
> > Then our tool highlights most relevant profiles saving hours - nobody 
> > excluded, simply reranked.
> >
> > Curious if this might support your current process?
> >
> >
> >
> > Juris Baums
> > Founder @ Hyperscan(.)co
> >
> >
> >
> > Not relevant? Just send 'pass' to end communication.
> >
> >