DLDesheng LuContact
All work
ShippedPublic

Startup Product / Shipped product proof

TruWorld

A mobile product designed to turn digital curiosity into real-world exploration and local-business visits.

How a two-sided product thesis connected consumer exploration with intended value for local partners.

  • 0→1 product thesis
  • Two-sided journey design
  • Beta learning system
  • GTM as product
Product stageShipped · Public product
Leadership scopeCo-founder and product leader across product, marketing, and operations within a shared founder structure.
Actual public TruWorld mobile product screen showing a location-based map and nearby discovery markers
Historical public product screenThe world is the interface

A historical public mobile screen from the shipped location-aware exploration product; not presented as current live-product state.

0→1
Public mobile MVP
45K+
Community
30+
Retail partnerships
~$500K
Completed strategic investment

Approved public figures. Definitions, attribution limits, and unresolved measurement details are stated later in the case.

Evidence first

What is proven, what I changed, and what remains open.

A 90-second evidence map for hiring review. Synthetic product views explain mechanics; they never count as outcome proof.

Verified now
A shipped public mobile product, historical product screens, a 45K+ community, 30+ retail partnerships, and approximately $500K in completed strategic investment.
Next evidence gate
A tighter evidence chain from consumer and partner discovery to the shipped loop, retention, visits, and monetization.
01

User / workflow evidence

Supported synthesis

Historical consumer and local-business journey work informed a location-based loop combining exploration, discovery, rewards, and partner engagement. The exact research method and sample are not yet documented publicly.

02

Product decision

Verified record

I treated physical action, not screen time, as the product outcome and connected the consumer discovery loop with partner participation, community, and commercialization.

03

Product / system judgment

Supported synthesis

Location context, gamified exploration, rewards, and partner destinations were composed into one public experience; historical screens show the real product rather than a synthetic replacement.

04

Evaluation → change

Open evidence gap

Experiment, retention, visit-conversion, and campaign-learning records have not yet been connected to the public case, so the page does not invent a product-iteration result.

05

Outcome / boundary

Verified record

The product, community, partnerships, investment, and shared founder-team scope are approved claims. Community is not relabelled as active users, partnerships as simultaneous campaigns, or investment as revenue.

AI product decision record

The choices behind the product, architecture, and release gate.

Do not retrofit generative AI into a shipped location product when geospatial relevance, incentives, and marketplace liquidity drive value.

01

AI fit

Supported synthesis

Keep the shipped core centered on location, discovery, rewards, and partner participation; treat AI personalization as optional future leverage.

The product outcome is a real-world action, and the primary risks are relevance, supply, incentive design, and repeat use.

Alternative consideredA conversational AI layer would add novelty without solving destination quality or marketplace liquidity.

02

Knowledge & context

Supported synthesis

Use structured geospatial, campaign, reward, and partner records rather than RAG for the core experience.

The user needs ranked, time- and place-aware options with reliable eligibility, not generated factual prose.

Alternative consideredA vector knowledge base is the wrong primitive for location availability and reward state.

03

System architecture

Supported synthesis

Use product APIs and marketplace records; do not introduce agents or MCP without a real cross-system user job.

The shipped loop benefits from predictable interactions, low latency, and measurable funnels.

Alternative consideredAgentic complexity would make a consumer action loop slower and harder to instrument.

04

Evaluation & release

Open evidence gap

The correct eval is the consumer and partner funnel: discovery relevance, activation, real-world action, retention, and partner value.

The public record currently proves scale inputs but not how experiments changed the core loop.

Alternative consideredCommunity size alone cannot substitute for active use, retention, visits, or monetization evidence.

Evidence I still need from the private project record3 open items
  1. 01

    Core-loop user-research method and the product changes it caused.

  2. 02

    Active-user, retention, visit, campaign, or monetization definitions.

  3. 03

    How the consumer product and partner advertising proposition connected in the shipped experience.

Verified = direct approved recordSupported = defensible synthesisReported = source receipt pendingDesigned = future test or control

Zero-context product contract

What this product did, for whom, and why it mattered.

Historical end-to-end journey reconstructed from the shipped product screen and approved consumer, partner, and prototype artifacts. It is not presented as current live-product state.

Primary user
Explorers looking for a reason to discover nearby places, and local partners seeking participation beyond a digital impression.
Trigger
An explorer wants a meaningful nearby activity, or a partner wants to bring people into a location-based campaign.
Product action
Connect map-based discovery, a nearby challenge, physical participation, progress, and a partner moment in one loop.
Output
An intended real-world activity for the explorer and a participation moment designed to create value for the local partner.
Decision enabled
Which place or challenge to pursue next, and which partner activation should be adjusted or repeated.

Product mechanics

See the product work before reading the retrospective.

The walkthrough uses fictional records to make the interaction and decision flow tangible. It does not replace the approved historical evidence or imply that every reconstructed state was shipped exactly as shown.

Simulated product scenarioTruWorld

Maya explores a fictional neighbourhood mission and a local partner reviews the resulting visit signal.

Product state · Discover

Turn a neighbourhood into a mission

The product presents a small set of place-based actions instead of an endless feed.

User action
Accept the route or replace one stop before beginning.
Explorer intent“Show me three independent places worth visiting this Saturday.”
Mission state

Mission

Harbour Loop · 3 stops · 2.8 km · food, design, and public art

Illustrative acceptance benchmark

every mission makes distance, effort, reward condition, and partner relationship visible before start.

Inputs to product direction

What the available record supports.

Verified facts, historical artifacts, and public-safe reconstruction are kept distinct. Each item states the product implication without turning a plausible inference into a confirmed result.

01Consumer journey mapping

Discovery alone did not create enough motivation to leave the screen and explore a place.

Product implicationMake movement, place discovery, and progress part of one visible loop.

02Partner journey mapping

Local businesses needed a clearer bridge between digital promotion and an in-person visit.

Product implicationDesign partner value around a real-world action rather than an impression.

03Shipped product and launch record

Moving from a two-sided thesis to a public product required product, marketing, operations, community, and partner work to move together.

Product implicationTreat launch and commercialization as part of the founder-level product system.

Journey transformation

Location-based exploration, rewards, and local business discovery

Historical end-to-end journey reconstructed from the shipped product screen and approved consumer, partner, and prototype artifacts. It is not presented as current live-product state.

  1. 01

    Explore

    User goal
    Find somewhere worth going.
    Original friction
    Digital discovery is passive and interchangeable.
    Product response
    A location-aware map makes the physical world the interface.
    Success signal
    A user begins an exploration path.
  2. 02

    Choose

    User goal
    Know what to do next.
    Original friction
    Places lack a compelling reason to act now.
    Product response
    Missions and venue context turn a place into a purposeful activity.
    Success signal
    A user selects a place or mission.
  3. 03

    Visit

    User goal
    Reach and experience the location.
    Original friction
    Most product engagement ends before physical action.
    Product response
    Progress depends on real-world exploration.
    Success signal
    Digital intent becomes a physical visit.
  4. 04

    Participate

    User goal
    Complete a meaningful action.
    Original friction
    Promotions rarely feel connected to the experience.
    Product response
    Partner moments are embedded in the exploration loop.
    Success signal
    A user completes the intended activity.
  5. 05

    Return

    User goal
    See progress and discover more.
    Original friction
    One-off discovery has little reason for repetition.
    Product response
    Rewards and progression create continuity across visits.
    Success signal
    A user resumes exploration.

Product decision and rationale

What should count as meaningful product engagement?

This is an evidence-backed reconstruction of the product logic. It is not presented as a verbatim or dated decision record.

What the evidence said
  • Consumers needed a reason to move from discovery to action.
  • Partners needed a clearer connection between promotion and physical participation.
  • The product thesis was built around real-world exploration.
Choice

Define the physical visit as the core outcome and design the map, missions, place discovery, and rewards around it.

Tradeoff

This made the MVP more operationally demanding than a conventional content or promotion app.

Consequence

Product experience, partner supply, community, and GTM had to be designed as one system.

Included in the core product
  • Location-aware exploration map
  • Place and mission discovery
  • Progress and rewards
  • Partner-led real-world moments
Outside the verified public record
  • Broader social world-building
  • Advanced personalization
  • Larger ecosystem features
Release gate

The core loop had to make a physical action understandable, usable, and repeatable before the ecosystem expanded.

Product and working evidence

The artifacts behind the claim.

Historical public screens and working artifacts are labeled separately. Their presence proves the artifact exists; it does not automatically prove research method, product state, or causal impact.

Actual public TruWorld mobile product screen showing a location-based map and nearby discovery markers
Historical public product screen

The world is the interface

A historical public mobile screen from the shipped location-aware exploration product; not presented as current live-product state.

Historical TruWorld consumer journey map with goals, touchpoints, emotions, pain points, and opportunities
Historical product artifact

Consumer journey evidence

Historical consumer-journey artifact. Its research method, date, and sample are not yet established in the public evidence record.

Historical TruWorld partner journey map with local business goals, touchpoints, pain points, and product opportunities
Historical product artifact

Partner journey evidence

Historical partner-journey artifact. Its research method, date, and sample are not yet established in the public evidence record.

Historical TruWorld product prototype showing map-based exploration on mobile screens
Historical product artifact

From thesis to interface

Historical prototype artifact connecting the product thesis to the mobile experience.

Delivery and adoption

The work around the product is part of the product.

Shipped public MVP alongside community building and partner development within shared founder leadership.

Cross-functional system
  • Product
  • Engineering and design
  • Marketing
  • Operations
  • Retail partners
Leadership moves
  1. 01

    Led shared founder decisions across product, marketing, and operations.

  2. 02

    Connected historical consumer and partner journey work to the product thesis and launch path.

  3. 03

    Connected partner acquisition and community growth to the product experience.

Product direction and program evidence

Place the product direction beside the approved evidence.

Adjacent evidence does not imply that one feature caused the full result. The approved metric language and attribution boundaries remain visible.

  1. 01
    Product direction

    Location-aware exploration loop

    Observed or intended operating shift

    Created a public product path from digital discovery to physical participation.

    Approved program evidence

    Verified shipped outcome: zero-to-one public mobile MVP.

  2. 02
    Product direction

    Partner moments inside the experience

    Observed or intended operating shift

    Made local businesses part of the product supply and user journey.

    Approved program evidence

    Verified program evidence: 30+ retail partnerships; causal attribution is not established publicly.

  3. 03
    Product direction

    Community and commercialization system

    Observed or intended operating shift

    Built market visibility and external confidence around the product.

    Approved program evidence

    Verified program evidence: 45K+ community and approximately $500K in completed strategic investment; sole causation is not claimed.

I led product, marketing, and operations within shared founder leadership, connecting journey design, beta learning, partner supply, community, GTM, and commercialization.

Evidence boundary

What the case proves, and what it does not.

Community is not relabeled as active users; partnerships are not relabeled as simultaneous campaigns; investment is not revenue or valuation.

Confirmed evidence
  • Shipped public mobile product and historical consumer, partner, and prototype artifacts.
  • 45K+ community and 30+ retail partnerships.
  • Approximately $500K in completed strategic investment; Desheng helped secure it within shared founder leadership.
Still unresolved
  • Active-user, retention, campaign-conversion, and monetization definitions.
  • How the location-exploration product and separately documented AI advertising proposition related in the shipped experience.
Return to the collectionShipped product proof