Proposals
AuraScore 79/100

Unified Commerce POS Replacement Proposal Assessment

Produce an enterprise business case report proposing in-store POS and omnichannel commerce technology modernization.

Use this template when submitting enterprise software and hardware proposals to retail CIOs and Heads of Store Operations.

Template

Role: Enterprise Retail Solutions Principal Architect and Commercial Bid Director.

Context

  • Retail enterprise account: {{retail_chain_name}}
  • Physical store network footprint: {{store_count}}
  • Current store systems: {{legacy_pos_system}}
  • Target deployment timeframe: {{target_implementation_window}}
  • Loss prevention objective: {{shrinkage_reduction_goal}}
  • Projected sales conversion impact: {{projected_gmv_lift}}

Task

Formulate an executive proposal assessment report demonstrating the total economic impact, operational efficiency, and risk mitigation of modernizing checkout architecture for {{retail_chain_name}}.

Method

  1. Benchmark maintenance overhead, failure rates, and customer friction of {{legacy_pos_system}} against cloud-native unified POS.
  2. Model a phased rollout across {{store_count}} stores that preserves operational uptime and avoids seasonal peak trading periods.
  3. Calculate store-level payback timelines using revenue expansion derived from {{projected_gmv_lift}}.
  4. Quantify margin protection resulting from automated checkout validation to achieve {{shrinkage_reduction_goal}}.
  5. Structure software-as-a-service licensing, payment processing fees, and edge hardware amortization.
  6. Build a risk mitigation matrix addressing offline transaction queuing, network resilience, and field technician training during {{target_implementation_window}}.
  7. Detail a multi-year total cost of ownership (TCO) comparison against maintaining existing infrastructure.

Constraints

  • MUST present a quantified financial payback model including IRR and net present value across 3 years.
  • MUST NOT schedule store rollouts during standard Q4 retail change freeze windows.
  • Clearly delineate software subscription fees from hardware staging, field dispatch, and integration professional services.
  • Reference core in-store retail metrics: queue time reduction, basket conversion, and transaction latency.

Output format

    1. Executive Business Case & Strategic Justification (under 250 words)
    1. Modernization Architecture vs. Legacy POS Comparison
    1. Phased Rollout Schedule & Store Deployment Plan (table format)
    1. Financial Payback, TCO & ROI Schedule (incorporating shrinkage and GMV models)
    1. High-Availability SLA, Offline Resiliency & Support Architecture

Self-review

  • Confirm that the store rollout timeline respects {{target_implementation_window}} without trading disruption.
  • Validate that shrinkage reduction numbers mathematically reflect {{shrinkage_reduction_goal}}.
  • Verify all migration risks associated with {{legacy_pos_system}} have explicit technical fallbacks.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering8/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-proposals
retail-consumer-goods
retail-tech
pos-systems
enterprise-sales