U:L Website RFP

Appearance

MoSCoW Priorities (Draft) ​

Important

This prioritisation is Newism's interpretation of the RFP requirements. The RFP does not explicitly prioritise features, so these categories represent our assessment based on:

  • Urban List's stated strategic objectives
  • Technical dependencies (what must exist before other features work)
  • Launch-critical vs post-launch enhancements

These priorities should be validated and refined collaboratively during discovery.

MUST HAVE (Launch blockers) ​

Editorial & Content ​

  • Standard article templates (news, features, evergreen, guides)
  • Listable and shoppable formats with affiliate integrations
  • Partner advertorial templates with dynamic commercial placements
  • Component-based page builder with reusable modules
  • Built-in SEO fields and schema support
  • Versioning, approvals, scheduling, preview
  • Multi-market architecture (20+ locations)
  • Native media embedding (YouTube, podcasts)

Structured Content & Taxonomy ​

  • Taxonomy and metadata framework
  • Relationship mapping across listing types
  • Searchable directory assets embedded in editorial
  • Structured tagging for segmentation

Directories ​

  • Business listings (editor-curated + claim)
  • Hospitality listings (conditional fields on business listing)
  • Event listings (submission + approval + auto-expiry)
  • Faceted search and filtering
  • Map-driven experiences

Membership ​

  • Insiders (freemium tier)
  • Insiders+ (paid tier)
  • Member dashboards
  • Stripe subscription billing
  • Saved collections / favourites
  • Logged-in user data capture
  • Member location preferences

Commercial & Advertising ​

  • Google Ad Manager integration
  • Linkby integration
  • Sponsored listing placements
  • Commercial placements across templates

Technical ​

  • Core Web Vitals (Good scores)
  • WCAG accessibility
  • Structured schema (Article, Event, LocalBusiness)
  • Canonical/sitemap management
  • GA4/GTM event framework
  • Role-based permissions
  • Multi-market capability
  • Staging/production environments

Migration ​

  • Representative content migration (demo)

SHOULD HAVE (Important, not launch blockers) ​

Editorial & Content ​

  • Art-directed/mini-site capability (Ceros replacement path)
  • Author profiles

Directories ​

  • Tiered listing plans (free/paid/premium)
  • Boost/promote logic
  • Product directories (internal + affiliate)
  • Review capability
  • Listing moderation queue

Membership ​

  • Access-controlled content and perks
  • Renewal, expiry, failed payment handling
  • Consent and preference management

Personalisation ​

  • Personalised content feed (basic)
  • Location-aware content defaults
  • "Because you saved" recommendations
  • CDP/CEP integration hooks

Commerce ​

  • Coupon and promotional code logic
  • Order history and dashboards

Commercial ​

  • Video pre-roll capability (third-party player integration, e.g. Dailymotion)
  • Infinite scroll monetisation
  • DSP activation readiness (DV360, Trade Trade Desk)

Technical ​

  • Audit trails
  • RSS feeds
  • CSV/API export

Design ​

  • Full design system documentation
  • Interactive prototypes

COULD HAVE (Nice to have, stretch goals) ​

Editorial ​

  • Automatic translation capability
  • Notion workflow integration

Directories ​

  • Jobs directory

Personalisation ​

  • Behaviour-driven homepage modules
  • Dynamic content surfacing rules

Commerce ​

  • Ticket sales for owned events
  • Merch and digital product sales

Technical ​

  • Snowflake/data warehouse APIs
  • Slack integration (alerts, notifications)
  • AI Overview/generative search optimisation

Reporting ​

  • Internal reporting dashboards
  • Partner-facing reporting

WON'T HAVE (This phase - future roadmap) ​

Out of Scope ​

  • Full CDP/CEP implementation (hooks only)
  • Full content migration (representative only in scope)

Beyond the RFP (Future Opportunities) ​

  • Personalised "For You" standalone page (cacheable architecture)
  • Friends / social discovery layer
  • Native mobile app
  • Digital wallet cards
  • Geographic market intelligence dashboards

Notes ​

  1. The RFP presents comprehensive requirements without explicit prioritisation. Discovery will confirm these assumptions.

  2. Ceros replacement - RFP says "EOY 2026" suggesting SHOULD, not MUST for initial launch.

  3. Translation - Listed in RFP but operationally complex. Recommend COULD.

  4. Template counts (RFP 9.4-9.6) - Wishlist-level detail. Discovery defines actual requirements.

  5. Personalisation - Infrastructure (tagging, data capture) is MUST. Basic feed is SHOULD. Advanced features are Beyond the RFP.

  6. Accommodation types - Hotels, Airbnbs and other accommodation types are handled via conditional fields on business listings, not separate listing types.