This is an example of what the platform produces — a completed deliverable and the structured feedback our Verification Engine returns. The candidate, company and project below are fictional and anonymised.
Project Context Summary
TechCorp is consolidating three legacy customer systems — a billing platform, a support desk, and a marketing CRM — into a single customer data platform. The migration is being driven by a board commitment to reduce annual licensing costs and to give customer-facing teams one reliable view of each account. The programme has executive sponsorship from the COO and a hard deadline tied to the expiry of the existing billing-system contract in nine months.
The core problem this deliverable addresses is that the three systems hold overlapping but inconsistent customer records, with no agreed definition of a "customer" across teams. Sales counts organisations, support counts individual contacts, and billing counts paying accounts. Without a shared definition and a clear migration scope, the new platform risks inheriting the same fragmentation it is meant to solve.
Scope boundary. This summary covers the customer and account domains only. It explicitly excludes product-catalogue and finance-ledger data, which are owned by separate programmes and are out of scope for this migration. In-scope: customer master records, contact records, consent and marketing-preference data. Out-of-scope: invoices, payment instruments, and product SKUs.
Key stakeholders. COO (sponsor), Head of Customer Operations (primary business owner), Data Protection Officer (consent and retention sign-off), and the platform engineering lead (technical feasibility). Early alignment on the shared customer definition with these stakeholders is the critical dependency for every downstream requirement.
Success measures. A single agreed customer definition adopted by sales, support and billing; zero duplicate master records above an agreed tolerance after migration; and consent data migrated with a complete, auditable lineage back to its source system.
Verification Engine feedback
Verified — strong structural rigour
Strengths. The problem is stated concretely with a specific, testable root cause (three inconsistent definitions of "customer") rather than a vague restatement of the brief. The scope boundary is explicit on both sides — what is in and what is out — which is a frequent gap in weaker submissions. Success measures are specific and measurable rather than aspirational.
Gaps. The dependency on agreeing the shared definition is identified but not yet linked to a date or owner's commitment, so its impact on the timeline is implied rather than quantified. Stakeholder interests are listed but their potential points of conflict (e.g. sales vs billing definitions) are not yet drawn out.
Recommended actions. Attach a target date and named owner to the definition-alignment dependency, and add one line on how a disagreement between stakeholder definitions would be resolved.
Produce your own verified deliverables — join as a Founding Member for £29/month