Design a weekly sales tracker in Excel

Auteur: AILesson7 min de préparationTesté avec:ChatGPTRévisé: 2026-08-28

Réponse rapide

Define activity, pipeline, outcomes, targets, and ownership without mixing their meanings. Fournir: Sales workflow and users, Metrics and targets, Data and status rules. Résultat attendu: A maintainable input table, weekly summary, formulas, and review routine.

1

Ajouter votre contexte

Votre texte reste dans ce navigateur. AILesson Prompts ne l’envoie ni à un modèle ni à un serveur.

2

Votre prompt

Les champs non remplis restent visibles sous forme d’espaces réservés, afin que vous puissiez quand même copier et modifier le prompt.

Design a weekly sales tracker in Excel.

Workflow, users, update cadence, and decisions:
[workflow]

Metrics, targets, currency, and date definitions:
[metrics]

Data, stage, and status rules:
[rules]

Separate row-level source data from weekly summaries. Define one row's grain and stable keys, required input columns, controlled lists, date ownership, and formulas. Distinguish activity, current pipeline, newly created pipeline, and closed outcomes. Return table layouts, validation, target-versus-actual calculations, overdue follow-up flags, PivotTable views, and a weekly review checklist. Prevent double counting when opportunities change stage or week.
Essayer dans le Playground
Privé par défautL’assemblage du prompt se fait localement dans votre navigateur. Évitez de placer des informations confidentielles dans un service d’IA, sauf si votre organisation l’autorise.

De l'entrée au résultat

Un exemple détaillé

Voyez comment un contexte concret transforme cette recette en résultat utilisable.

Entrée réelle

Sales workflow and users
Five account executives update opportunities every Friday. Stages: Qualified, Discovery, Proposal, Commit, Won, Lost. The manager reviews pipeline coverage, follow-ups, and closed revenue for the week.
Metrics and targets
Opportunity value in GBP; weekly won target £50,000; pipeline target is 3× the next four weeks' target. Activity counts are stored separately. Week starts Monday.
Data and status rules
OpportunityID is unique. Owner and Stage required. CreatedDate never changes; ExpectedCloseDate may change; ClosedDate required for Won/Lost. NextActionDate required for open stages. Won value counts only by ClosedDate.

Exemple de sortie

Create an Opportunities Excel Table with OpportunityID, Account, Owner, Stage, ValueGBP, CreatedDate, ExpectedCloseDate, ClosedDate, NextAction, NextActionDate, LastUpdated, and ReviewReason. Use controlled lists for Owner/Stage and validation that closed stages require ClosedDate while open stages require NextActionDate.

Add WeekCreated, WeekExpectedClose, and WeekClosed helper columns using each distinct date. OverdueFollowUp: =AND(NOT(OR([@Stage]="Won",[@Stage]="Lost")),[@NextActionDate]<TODAY()). Keep TODAY-based flags separate from historical snapshots.

Weekly summary: WonRevenue = SUMIFS(ValueGBP,Stage,"Won",ClosedDate,week bounds); WonCount = COUNTIFS using the same rules; CurrentOpenPipeline = sum open opportunity values with expected close in the selected four-week horizon; Coverage = CurrentOpenPipeline / four-week target. A PivotTable shows Owner rows and Stage columns for current pipeline; another uses WeekClosed for Won/Lost outcomes. Never sum weekly snapshots of current pipeline. Friday review: uniqueness, missing required dates, stale updates, overdue actions, target gap, large-value changes, and source-to-summary reconciliation.

Pourquoi cela fonctionne

  1. 1

    Stable opportunity keys and explicit date meanings prevent pipeline from being counted as weekly revenue.

  2. 2

    Separating inputs from summaries keeps formulas reproducible and edits auditable.

Vérifier le résultat

  • Is each opportunity counted once in every intended measure?

  • Are created, expected-close, and actual-close dates used for distinct questions?

  • Do closed revenue totals reconcile to closed opportunity records?

Utilisez-la en toute confiance

Questions fréquentes

Des réponses pratiques sur le bon moment pour utiliser cette recette, ce qu’il faut fournir et les cas où une vérification humaine reste nécessaire.

What should I prepare before using “Design a weekly sales tracker in Excel”?

For “Design a weekly sales tracker in Excel,” prepare Sales workflow and users, Metrics and targets, and Data and status rules. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Design a weekly sales tracker in Excel” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A maintainable input table, weekly summary, formulas, and review routine—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Design a weekly sales tracker in Excel”?

The published test record for “Design a weekly sales tracker in Excel” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Plus de façons d'explorer

Où se situe cette recette

Faites avancer votre travail