Create a weekly sales action board that makes the next step visible

Choose actions rather than broad stages

A sales stage tells you where a request sits; an action tells you what to do next. Convert prepare quote into a specific task with the required input and output. Use a verb and an inspectable finish, such as send the defined two-option estimate.

Keep the underlying enquiry record available. The board can show the next action without duplicating every private customer detail.

Give each action one owner

Assign the person responsible for moving the task, even when others contribute. Add a due date based on the customer expectation and actual workload. If everything belongs to the owner, make that explicit rather than leaving blanks.

Separate customer deadlines from internal review dates. A request awaiting a product link may need an internal check, but it is not a promised delivery task until the dependency is resolved.

Identify blockers and waiting states

Use a small state list: ready, in progress, waiting and done. For waiting work, name the dependency and who can resolve it. Avoid a waiting state with no explanation or review date.

Do not label every stalled enquiry waiting on customer. Missing internal pricing, unassigned response coverage or an unclear scope may be the business's responsibility.

Limit the work started at once

Choose a manageable number of active tasks based on available hours. Complete a few useful next steps before opening many unfinished ones. Identify which actions protect an existing customer commitment or resolve a real enquiry first.

A board should support delivery, not generate extra administration. Keep fields few enough that updating a task takes less time than reconstructing it from scattered messages.

Run a short weekly review

Inspect overdue actions, waiting dependencies and completed work. Decide the next action for each open request and remove tasks that are no longer useful. Confirm the week's coverage before assigning new due dates.

Use the review to resolve blockers rather than reading the whole board aloud. Record decisions that change scope, timing or ownership so the enquiry history remains understandable.

Measure movement and stale actions

Count completed next steps, overdue tasks and records waiting beyond their review date. Examine why work stopped. A growing action count may indicate more activity without better customer handling.

Connect the board to known decisions and delivery outcomes. A sent quote is progress in the process, but it is not a booked job or collected revenue.

Illustrative four-action Monday board

A hypothetical owner has four actions: answer a scope question, prepare one estimate, check a missing product link and confirm an accepted visit. Each has an owner and finish condition. The link check is marked waiting, with a review date.

The owner prioritizes the accepted visit and the customer question, then prepares the estimate. The waiting task remains visible without being counted as active production. These actions are illustrative and show task clarity, not a sales forecast or a benchmark for weekly productivity.

Questions about this task