I watch for the moment, then act on it

    Habits are the work I run on a schedule. Triggers are the work I run because something happened. You pick the event, the action I take, and whether I do it myself or ask you first.

    Start for freeBook a demo

    $100 of credits on us. No card required.

    Job changeNew role, 45 days in
    Shipped projectPublic repo, 4.1k stars
    Conference talkPayments meetup, 2024
    Company signalHiring freeze at rival
    23 people worth a message

    Pick the event and the response

    In one sentence. When a saved candidate changes jobs, tell me. When a stage sits five days, chase the owner.

    #hiring

    I hold the context in the background

    Your saved candidates, your live reqs, your ATS records and the public web. I only speak when something actually moved.

    Sourced2
    Maria K.
    Tomasz W.
    Screening1
    Ravi M.
    Onsite0
    Offer0

    Notify, draft, or handle it

    Each trigger has its own autonomy. Some just ping you. Some arrive as a finished draft. Some run end to end and log it.

    #hiring

    This is what lands in your channel

    Not a dashboard to check. A result you can act on, with the evidence attached, sitting right where you already work.

    Sourced2
    Maria K.
    Tomasz W.
    Screening1
    Ravi M.
    Onsite0
    Offer0

    The events worth acting on, and what I do about them

    A candidate changes jobs

    Someone you liked gets promoted, moves, or lands somewhere that just had layoffs. I surface them with the old thread attached, so you remember why they mattered.

    A silver medallist becomes reachable

    The person you lost to a counter offer hits 12 months in role. I bring them back up before a competitor thinks to.

    New public work appears

    A repo, a talk, a launch, a write up. When the evidence changes, the score changes, and I tell you which candidate moved.

    A pipeline stalls

    Nobody moved a stage in five days, or a hiring manager owes feedback after an interview. I chase the person holding it up, not the whole channel.

    A req opens in your ATS

    A new role appears and I start the first search off the job description, so there is a shortlist waiting when the kickoff call happens.

    An inbound applicant matches an active search

    I read them against the same bar as the people I sourced, and only interrupt you when someone clears it.

    The bar shifts

    The same rejection reason lands three times. I flag the pattern, reweight the search, and show you what I changed.

    A transcript or record lands

    Your notetaker drops an interview, the ATS record is missing evidence, the weekly report is ready. I close the loop before anyone asks.

    Why I'm different

    Firing on an event is the easy half. The hard half is knowing that a title change at a mid stage startup is worth a message, and the same change at a consultancy usually is not.

    Taste, not another search box

    Search is the easy half. The hard half is knowing which nine of two hundred people are worth your Tuesday, and saying why.

    I read potential, not keywords

    Titles lie and stacks change. I look at what someone shipped, who they shipped it with, and how fast they grew into the work.

    Every call comes with its evidence

    You get the commit, the talk, the customer they carried, the line in the release notes. If I cannot show why, I do not claim it.

    The same rubric, every candidate

    Your bar becomes a written rubric I apply the same way on Monday and on Friday, so a shortlist is comparable instead of moody.

    You can argue with me

    Disagree with a score and I show the reasoning behind it, then carry your correction into the next batch.

    What people ask before switching triggers on

    Will this turn into notification noise?

    No, because I judge before I speak. A title change only reaches you when it changes whether the person is worth contacting. Everything else is logged, not announced.

    Can a trigger message a candidate on its own?

    Only if you explicitly allow that trigger to. The default is a draft under your name that needs your approval. Sending stays a human action.

    How is this different from an ATS automation rule?

    An ATS rule fires on a field changing inside your own database. I also watch the open web and the public work your candidates ship, and I apply your bar to what I find.

    Do I have to configure anything technical?

    No. You describe the trigger in plain language in the channel and I confirm what I will do and when. No builder, no webhook, no rule tree.

    Where to go next

    The rest of what I do

    Laidback

    Tell me what should never be missed

    Start for freeBook a demo

    Name one moment you always find out about too late, and I will watch for it.