Watch it work · the first two weeks Sample data

Watch an activation agent run customer onboarding

Every step lands in the tools your team already uses: Slack, email, the sandbox, HubSpot, and Asana. A person approves every customer-facing message.

Day 0

nerve · activation agentlive

Ledger · for leadership Sample data

Signed, not yet live

Every account from signature to its first live transaction. Built from HubSpot, Asana, each customer's Slack channel, and sandbox API logs.

Updated 8:02 AM · Wed Sep 23

Illustrative, not a customer result

L3 · Recommends 5 stalled 30,700 projected transactions/mo

Recover the 5 accounts stalled on the customer side

Three have no backend developer for the build. One has a developer who has been silent for 12 days, and one is waiting on a field list from its data team. The plays are drafted for your approval: a CEO escalation, two starter-integration offers, a check-in, and a move to the hosted path.

In onboarding

18

7 on track · 6 at risk · 5 stalled

Go-live rate

58%

Apr to Jun cohorts · 76% predicted · goal 82%

Days to go-live

71

Median, completed cohorts · plan 45

Volume/mo not yet live

98,000

Transactions projected at kickoff

Leading indicators · they move weeks before the go-live rate does

vs. 14 days ago

Accounts silent 7+ days

71

Silent accounts go live 19% of the time

Kickoff to first sandbox call

9d3d

Median days after kickoff

Days in developer build

26d15d

Where 64% of lost accounts stopped

Test transactions passing by day 30

41%72%

Share of accounts

Wait on your team's steps

46h9h

Median hours per step

Monthly cohorts · where each signed account ended up

Live within 4 weeks 5 to 8 weeks 9 to 12 weeks Still onboarding Never went live

Forecast · September cohort

4 of 7

Live by day 45 (Nov 7)

2

Already at risk

22,500

Transactions/mo by day 90

One of the at-risk accounts has no backend developer on its kickoff roster. The other is waiting on a data migration file. The agent has drafted a check-in for each, waiting on your approval.

Days stalled by reason · accounts in onboarding

L3 · RecommendsUpstream fix

Add "backend developer named at kickoff" to the sales qualifiers

3 of the 5 stalled accounts signed without one. Those three account for 170 stalled days this quarter.

✓

Accounts in onboarding · sorted by what needs a move

Showing 10 of 18

AccountStepDaysWhy it's stuckWaiting onGo-liveVolume/moNext move

Today · for the onboarding team Sample data

5 moves need you

Every card leads with the move, drafted and one click away. Customer-facing messages wait for your approval. Internal updates the agent has earned run on their own and leave a receipt.

Wed Sep 23

5Need you 4Internal updates logged today Every customer message waits for approval

L3 · Recommends Always approved by a person: customer exec 7,400 transactions/mo

Escalate Fabrikam to their CEO: backend developer silent 12 days on webhook setup

To Fabrikam's CEO · email · from your onboarding lead

Hi, quick flag on your integration. Webhook setup has been waiting on your backend developer since Sep 10, and we haven't heard back in your Slack channel since then. Your planned launch was Oct 16 and that date is now at risk. Could you confirm who owns the build this week? If capacity is the issue, we can send a starter integration your team can finish in a day or two.

Why

Webhook setup (step 12) assigned to their developer on Sep 10
3 approved check-ins in their Slack channel (Sep 14, 17, 21), no reply
No sandbox API calls from Fabrikam since Sep 4
Go-live now predicted Nov 2, 17 days past plan

SlackSandbox API logHubSpot

✓

L3 · Recommends Always approved by a person: production credentials Go-live Sep 25

Release production credentials to Northwind Traders

✓5 of 5 synthetic test transactions passed
✓Webhook signatures verified on every event type
✓Data agreement countersigned Sep 3
✓UAT signed off by their CTO in Slack, Sep 22
✓No historical data to migrate

Why

Every gate before step 21 is complete, with evidence on file
Releasing today puts go-live 11 days ahead of plan

Sandbox API logContract recordSlack

✓

L3 · Recommends Drafted for your approval 17,800 transactions/mo · 2 accounts

Offer a starter integration to Tailspin Toys and Adventure Works

Neither has a backend developer, and both are stuck at developer build (49 and 55 days). The agent built a starter integration for each stack that passes the sandbox test transactions as-is.

Tailspin Toys · Slack · their shared channel with your team

Hi team, we built a starter integration for your stack (Next.js on Vercel): webhook handler, signature check, field mapping, and a test script. It passes our sandbox test transactions as-is. Want a 30-minute walkthrough with your contractor on Thursday?

Adventure Works · Slack · their shared channel with your team

Hi team, since backend help has been hard to line up, we built a starter integration for your platform. It covers the webhook, signature check, and field mapping. Drop it in and run the included test script. Happy to walk through it this week.

webhook-handler.tsverify-signature.tsfield-map.tsrun-test-transactions.sh

✓

L3 · Recommends Earning autonomy: 3 of 5 8,300 transactions/mo

Reassign Proseware's data migration to a second solutions engineer while the owner is out

Why

The owner is out until Sep 30 and holds data migration on 4 accounts, with no backup
Proseware has been blocked on this step for 6 days
The second engineer finished data migration for 3 accounts this quarter

AsanaGoogle Calendar

✓

L3 · Recommends Always approved by a person: path change 2,400 transactions/mo

Move Wide World Importers to the hosted integration path

66 days in with no dev team and 3 custom patch requests. They would not pass today's qualifiers. The hosted path needs no custom code on their side.

✓

Handled by the agent · internal onlyL4

9:12 AM

Closed integration testing for Contoso in Asana and HubSpot, with the passing test log attached

L4Policy: steps close on recorded evidence

8:40 AM

Marked UAT sign-off complete for Northwind Traders from their CTO's approval in Slack

L4Policy: steps close on recorded evidence

8:05 AM

Filed Fourth Coffee's kickoff notes and developer checklist to their HubSpot record

L4Policy: internal records only

7:30 AM

Updated predicted go-live dates on 6 accounts from overnight sandbox activity

L4Policy: internal records only

Customer-facing messages never land here. Each one waits in a card on the left until a person approves it.

API

Integration portal Sample data

Signed in as Contoso · onboarding lead assigned

Run by an agent on Nerve

Your path to a first live transaction

Step 14 of 24 · Integration testing

On track for go-live Oct 22

Kickoff Setup Build Test Migration Go-live

Your next step · owner: your team

Fix webhook signature verification

2 of 5 synthetic test transactions passed. The 3 failures are all rejected with a signature mismatch. Your handler checks the parsed JSON body; check the raw request body instead, before parsing.

app/api/webhooks/platform/route.ts · illustrative

import { verifySignature } from "@/lib/platform";

export async function POST(req: Request) {
  const raw = await req.text(); // raw body, before JSON.parse
  const sig = req.headers.get("x-signature");
  if (!verifySignature(raw, sig)) {
    return new Response("invalid signature", { status: 401 });
  }
  const event = JSON.parse(raw);
  // transaction.created, transaction.completed, transaction.refunded
  return Response.json({ received: true });
}

Test transactions · last run 9:10 AM

🔒Synthetic test transactions only. No production customer data passes through this portal.

Ask the integration agent

Do we need to handle transaction.cancelled?

Yes. It fires when a transaction is voided before it completes. Release anything you reserved for it on your side; the API only needs a 200 response.

Source: Webhooks guide · Events

Answers come from the API docs. Anything the agent can't answer goes to your onboarding lead with the question attached.

Credentials

SandboxActive

sbx_••••••••••••7c1e

ProductionLocked

Released when every item is done:

○5 of 5 test transactions pass (2 of 5 today)
✓Data agreement countersigned
✓Account configuration approved
○UAT sign-off from your team

Waiting on us

Nothing right now. Our next step is security review sign-off (step 18), which starts as soon as your test transactions pass.

All 24 steps

Sample path. In an engagement, the steps come from your documented process, checked against what your systems show.

Autonomy · permissions Sample data

What the agent may do

Access is granted in two steps: read access for levels 1 and 2, then write access one action type at a time for level 4. Internal actions earn autonomy from their track record. Customer-facing messages stay with a person, and every action has a ceiling.

L3 · Recommends5 of 5 clean approvals

Promote "Assign internal follow-up tasks" to L4

The fifth approval with no edits came in this morning. The agent will create and assign Asana follow-up tasks for your team on its own and log a receipt for each. You can demote it any time.

✓

L1 · See

What's happening

Where every signed account is, right now

Needs: Read access to HubSpot, Asana, and sandbox API logs. Status and timestamps only.
You get: The Ledger

L2 · Diagnose

Why it's happening

The reason each account is stuck, with evidence

Needs: Read access to shared customer Slack channels, onboarding email, and API event metadata. Never your end customers' records.
You get: A stall reason and sources on every account

L3 · Recommend

What you should do

The move, drafted and one click away

Needs: No new access. It reasons over L1 and L2 data.
You get: Every card leads with a recommended action

L4 · Act

The agent does it

Done, with a receipt

Needs: Write access, granted one internal action type at a time
You get: Internal updates handled inside your rules, visible in Today

L3 is the floor. Once L2 access is on, every card leads with a recommended move. Customer-facing messages stay at L3: the agent drafts, and a person approves every send.

Actions · current level and how it got there

ActionLevelModeTrack recordCeiling

Earn

5 approvals in a row with no edits, for the same internal action, and the agent recommends promotion. A person confirms it.

Lose

One rejection resets the streak to zero and drops that action back to L3. Edited approvals never count toward promotion.

Stop

One switch pauses every L4 action across all accounts. Every action keeps a receipt: what, why, the evidence, and who approved its level.