Wakehold

Features

What Wakehold
gives the fleet.

An ops layer around the agents you already run: a harness for continuity and proof, plus Workflow Runs — the durable thread for work that spans several steps and tools.

The harness

Four primitives.
One ops layer.

The harness is the control plane around agents you already run. Wakes, proof, packets, and policy keep work honest when paths flap and handoffs cross lanes. For a step-by-step sales-lead walkthrough, see How it works.

01
⌁

Wake continuity

Durable wakes, watermarks, and catch-up when wake paths flap. The right lane wakes — even after a blip.

right work · right time
02
✓

Proof receipts

“Done” only with evidence — message, tracker, or system ids on the record.

evidence · not vibes
03
→

Work packets

Owned handoffs of context between agents and lanes — intent, state, and expected outcome in one packet.

clean handoff · no drift
04
◈

Policy capsules

Versioned operating rules at decision time — guardrails that travel with the work.

rules · in context

Full wake → proof → handoff → policy walkthrough →

Workflow Runs

The durable thread
for the whole path.

Wakes and proof receipts catch moments. A Workflow Run is the board that holds the whole path: where things stand, what finished with evidence, and which tools are involved.

01 / THREAD

One path.
Several steps.

Work that spans people and tools gets a durable thread — not a pile of chat and tickets. You see the path, the open steps, and the proof already on record.

02 / HARNESS

Moments vs.
the whole path.

Wakes, receipts, and packets are moments. A Workflow Run holds them together so continuity doesn’t stop at a single handoff.

03 / YOUR STEPS

You design
the path.

Name the steps for your company. Self-serve — not a fixed industry template gallery we ship as “the” playbook.

04 / TOOLS

Several tools.
One thread.

Link the systems you already use. Updating one doesn’t quietly finish another. Side paths can move without finishing the main path.

EXAMPLE · HIRING A TEAMMATE PATH VIEW

Someone applies. Your team screens, interviews, decides, and brings them on. The Workflow Run holds that path — with proof for what finished and links to the tools involved.

Applied Screened Interviewed Offer out Started

What “finished” means

  • Screened only counts when the scorecard (or ATS note) is on the record.
  • Offer out only counts when the signed offer document id is on the record.
  • Started only counts when the start-date confirmation is on the record.

Side path · background check

While interviews run, background check can move on its own timeline. A clear background check does not mark the person as started. An accepted offer does not close the background check for you.

Same hire, several tools

ATS candidate id, interview calendar event, offer document, HRIS profile — all on one thread. Updating the calendar doesn’t invent an offer. Creating the HRIS profile doesn’t invent “screened.”

Result: path held · proof required · tools linked · side path separate You name the steps

Same idea elsewhere

  • Release — build green → QA handoff → published
  • Onboarding — kickoff → configured → trained → go-live
  • Claims — intake → review → decision → payout
  • Course launch — outline → draft → reviewed → live

Simple rules

  1. You name the steps.
  2. A step isn’t done without evidence.
  3. One thread can link to more than one tool.
  4. Side paths (like a background check) don’t sneak-finish the main path.
  5. Your approval habits stay yours — Wakehold keeps the path honest.

Next step

See packs, the portal,
or the walkthrough.

Pricing Portal How it works