Sales pipeline handoff
The revenue operations lead at fictional Vela Freight needs a controlled renewal pipeline. Build a renewal record type and layout, capture the service start date, route East inquiries, and supply a report that excludes closed sales.
The handoff is complete when the sales team can use the defined process, lead routing has a fallback, and the report totals the intended open population. No messages are sent and no real sales records are changed.
You own the complete sales pipeline handoff described in the brief. The next person needs working configuration and enough evidence to explain its behavior. Start with the business requirement, then keep each completed part while you add the next one. Your own saved state carries between steps.
A later task can expose a mistake that an isolated form would hide. A queue may exist without usable membership, a report may have the right title but the wrong population, and a rule may work for the example while rejecting an allowed record. Test those boundaries as you go. The final step asks for the operational conclusion or completed deliverable, and the checker keeps earlier requirements in scope.
Business requirement → configuration → boundary tests → handoff
Build a connected deliverable and retain its controls.