SE Signals
Your POCs and POVs ranked by technical risk, each with the next technical action it needs.
Included with secronjob . A seat without it sees an upsell here instead of the page.
Overview
SE Signals gives the sales engineer a per-opportunity technical-risk score, ranked highest first, with the next technical action on each row. It is the SE equivalent of the deal-inspection view an AE gets, focused on the technical health of a proof of concept rather than the commercial deal.
What it is for, on the page. Under the headline, this page says what it produces, what makes it run, and where the output lands. Every Work page reads that line from one registry, so the three answers cannot drift from the page.
How the technical-risk score works
The score is deterministic. It combines how deep the technical discovery went, how much of the POC's exit criteria is still unmet, how many technical blockers are open, and how engaged the buyers were in the demo. A POC with no defined exit criteria reads as risk, not assumed complete, so the score rewards a POC that is actually scoped and progressing. The top drivers behind the number are shown, and the next action is chosen from the highest-weighted driver.
Where the POCs come from
You record them, under "Record a POC" below the risk table: an id, the account, how deep technical discovery went, exit criteria met against the total, open blockers, demo engagement, and optionally the ARR at stake and the close date. Saving scores the whole book straight away, so the new POC takes its place in the ranking as soon as you add it.
Recording the same id again updates that POC rather than adding a second one, which makes this the weekly update as much as the first entry: move the exit criteria from 3 of 5 to 4 of 5, drop the blocker count, and the risk moves with it. A field you leave blank stays unknown rather than counting as done, so a POC with no exit criteria reads as risk. That is the point, not a gap.
The technical-risk table shows the real inputs behind each score: discovery depth, the exit-criteria progress bar (how many of the POC's criteria are met), the count of open blockers, and the demo-engagement band. Until you record a POC the board is honestly empty rather than filled with placeholders.
Answer freshness and field product gaps
Below the risk table, two panels round out the technical picture. Answer-library freshness lists your reusable answers scored for confidence and flagged when they go stale, so you catch an answer that has drifted before it lands in a customer response. Field product gaps rolls up the recurring "can't do X" reports the field logs against deals, ranked by the revenue each gap is blocking, with ARR summed only from reports that carry a real figure.
When a load fails
If the page cannot load, every panel on it says so. Painting the failure into only one card used to leave its neighbours on "Loading…" indefinitely, which reads as still-working rather than failed.
What is not shown
The design mockup included a per-step demo-engagement table (steps viewed, drop-off step, completion percent). That is omitted here because we do not store per-step demo telemetry, and showing it would mean inventing the numbers. The demo-engagement band on the technical-risk table is the honest, tracked signal we do have.