UIPrompt Library
Account
App DashboardsFreeOperationssingle-screenStructure checked

CRM Handoff Desk with Readiness and Capacity Checks

Build a working CRM-to-delivery handoff flow with per-account drafts, readiness checks, capacity limits and exact local receipts.

Prompt output preview

CRM Handoff Desk with Readiness and Capacity Checks

CRM Handoff Desk with Readiness and Capacity Checks prototype poster
AI-reviewed exampleExample overview
Open interactive preview

Try the working example

  • Edit per-account readiness and scheduling drafts
  • Record a capacity-checked local handoff receipt
  • Compose filters and recover empty results

Example output from this prompt. Your result will vary with your AI tool and edits.

Prompt
Build Shiftline, a responsive CRM-to-delivery handoff desk for a RevOps lead choosing which accounts can start, in which week, with which delivery pod. Return one complete standalone HTML document with internal CSS and JavaScript. Implement the actual interface, not another brief. No framework, external asset, font download, network request or storage. All accounts are fictional; commitments exist in page memory only and reset on reload. Never imply a CRM was updated or a customer contacted.

Inputs and customization: expose BRAND, WEEKS, PODS, CAPACITY and DEALS as named constants near the start of the script. Defaults: Shiftline; weeks Sep 28, Oct 5, Oct 12 (2026); pods Pod A, Pod B, Pod C. Every pod/week has capacity for two accounts except Pod B / Oct 12, which has zero available slots. Each successful local commitment consumes one slot. No real availability is implied. Deal fields: id, name, owner, arrUSD, type, week, pod, checks (label and done), note. Use exactly five records:
- D-101 Northstar Foods; Maya Chen; 184000; Expansion; Sep 28; Pod A; MSA approved=true, Integration scoped=true, Procurement PO received=false; note: Procurement PO is still missing. Review it before reserving a delivery slot.
- D-102 Civic Cartage; Owen Park; 126000; New account; Oct 5; Pod B; Security review complete=false, EDI mapping assigned=false, Kickoff brief ready=true; note: Security review and an EDI owner are needed before scheduling.
- D-103 Aster Clinics; Lena Ortiz; 92000; Renewal; Sep 28; Pod A; Terms signed=true, Training plan confirmed=true, Support owner assigned=true; note: Existing workflow and delivery owners are confirmed.
- D-104 Harbor Supply; Iris Bell; 211000; Expansion; Oct 12; Pod C; Pricing approved=true, DPA signed=false, Ops review complete=false; note: Legal and operations reviews are still open.
- D-105 Meridian Labs; Noah Singh; 71000; New account; Oct 5; Pod B; Security passed=true, Sandbox connected=true, Kickoff agenda drafted=true; note: A small implementation with a confirmed sandbox.

Visual direction: a cool white operations worksheet, navy ink #172e48, muted blue-grey #51677d, cobalt #245bcc, pale blue #edf3fc and divider #ced9e5. Use a system humanist sans (Trebuchet MS with system fallbacks), strong 32px heading, 20px account names, 14–16px body and tabular financial values. The distinguishing element is a real week-by-pod capacity matrix tied to committed accounts; its visible slots change only when a handoff succeeds. Do not show invented confidence percentages, decorative charts, fake live-sync controls or a generic navigation sidebar. Keep the capacity matrix compact and the account list plus selected-account worksheet dominant. Use borders to separate rows, generous whitespace around the task heading, and a cobalt primary action. No photos or icons needed.

Layout: compact brand header and Source prompt link; heading “Turn a ready deal into a clear handoff.”; an honest “Fictional data. Saved only in this page.” disclosure; a derived portfolio summary; capacity matrix; search and status filter; a list of matching accounts beside the selected worksheet. Summaries cover ALL five accounts, explicitly labelled Portfolio: Ready to schedule 2 / $163,000 ARR; Blocked 3; Committed 0 initially. Ready means all checks complete and not committed. Totals are always derived, never hardcoded or changed by search. Row status is Blocked, Ready or Committed; show account, ARR, chosen week/pod and number of open checks. Default selected account is Northstar Foods. The right worksheet shows the exact owner, type, ARR, note, and real readiness checkboxes for that record. Checking a requirement is explicitly a local checklist edit, not evidence of an external review.

Interactions: labelled “Search accounts” matches account, owner or note case-insensitively; labelled “Status” select offers All accounts, Blocked, Ready, Committed. Filters compose. If the selected record is filtered out, select the first visible record. No matches replaces both list and worksheet with useful empty guidance and “Clear filters”; no hidden-account commit remains. Changing selection retains each account's checklist and draft week/pod. Controls should not lose keyboard focus after re-rendering; text search stays focused with caret intact. Each account button has a meaningful accessible name.

The worksheet has labelled “Start week” and “Ops pod” selects. The main “Commit handoff” button is disabled until all checks are complete and chosen capacity is available. Explain exactly what blocks it, including unavailable pod/week. Changes to drafts do not reserve slots. On commit, capture an immutable snapshot of id, checklist, week and pod, show “Recording handoff…” for about 500ms, disable controls that could alter the action (selection, filters and draft controls) but keep “Reset demo” usable. Commit applies the snapshot to the record and consumes exactly one capacity slot. The account row, worksheet, portfolio totals and receipt must agree. A committed record becomes read-only with no second commit; receipts contain the exact account, owner, ARR, week, pod, checked requirement labels and a deterministic local receipt ID. Label them “Local handoff receipt”. Include an always visible Session receipts section; list each receipt once. Never claim persistence beyond the page.

Demo state controls: a labelled “Fail next handoff” checkbox arms one simulated failure. On failure, do not mutate records or slots, show “Handoff was not recorded. Your choices are kept.” with “Try again” and “Cancel retry”. Keep selection/filters/drafts disabled until retry or cancel. Retry uses the original captured choices and can succeed exactly once. Cancel retry restores editing and preserves the draft. Reset demo immediately restores original data, filters, selection, zero receipts and no failure; invalidate any pending callback so it cannot write later. Reset works during loading, error and success. Reload also resets. Avoid dead controls and misleading archive/export/sync actions.

Responsive constraints: at 1440×900 put list and worksheet side by side. At 1024px, 768px, 390px and 320px avoid horizontal page overflow. Below 800px put a compact account selector/list above the worksheet, stack form fields as needed, and selecting an account scrolls/focuses its worksheet heading without hiding the selected context. Keep all five accounts reachable, capacity values legible, touch targets at least 44px, body text at least 14px and every control keyboard reachable. Use semantic headings/labels, visible focus, non-color status, sufficient contrast, polite live status updates and concise inline errors. Respect reduced motion; no autoplay, video or Save-Data downloads. Render user strings as text, not unsanitized HTML.

Include an unobtrusive relative Source prompt link to /prompts/app-dashboards-app-dashboards-prompts-for-operations-crm-pipeline-dashboard-20260703-free/. Site provenance metadata may be added without changing behavior.

Acceptance checklist: (1) initial portfolio equals 2 ready / $163,000, 3 blocked, 0 committed and nine matrix cells show correct capacity; (2) Northstar is blocked until Procurement PO received is checked; choose Oct 5 / Pod C and commit: row, selects and receipt retain that exact pair, ready ARR returns to $163,000, blocked becomes 2, committed becomes 1, capacity goes 2 to 1 only for that cell; (3) switching accounts preserves drafts, composed search/status filters select only visible accounts and empty results have no commit button; (4) Pod B / Oct 12 blocks commit without overwriting draft; two commitments fill a normal slot and further commitments are blocked; (5) failure keeps all counts/capacity/receipts unchanged, retry uses the original snapshot exactly once, cancel allows editing and reset during loading prevents late writes; (6) committed records cannot double-book, reload resets, keyboard focus is stable, no overflow at all five widths, no runtime error or external request. Keep this a truthful local prototype ready for buyers to adapt to their own CRM and capacity service.
Share a result example

Paste a public image URL from a result this prompt helped create. Submissions stay private until reviewed.

Related prompts