Skip to the client story

Reference experience · fully rendered

  1. The problem

    The water keeps nothing.

    A cast lands. The ripple disappears. Everything your lodge learns can vanish with it by spring.

  2. Before he lands

    Nine seasons answer.

    J. Whitcomb’s returning cast wakes the beat, fly, and guide his lodge already knows.

    J. Whitcomb

    • Beat 4 · evening rise
    • Skated caddis
    • Asked for Ernesto
  3. The Client Loop

    And this week goes in with it.

    The same fly line carries this week through the loop. When it closes, nine trips become ten—then fourteen remembered experiences become seventeen.

  4. The next return

    Nothing is asked twice.

    His identity and history are already there. The next journey skips the cold beginning and starts at recognition.

  5. The horizon

    One loop. More ways to host.

    Fly Fishing proves the system in depth. The same movement is designed to carry other independently owned experience packs without pretending they are ready today.

Current chapter: The water keeps nothing.

Behind one seamless week

The guest sees one journey. Nanki keeps every part moving.

A remarkable trip is not one itinerary. It is a chain of prepared days, guide decisions, lodge awareness, and trusted handoffs—all carrying the same promise forward.

One guest promise

J. Whitcomb · one seamless fishing week

Coordinated through Programs · Trailhead field days

  1. The promise

    One guest. One expectation.

    Identity, history, preferences, and the commitments made before arrival stay attached to the same trip.

    Guest context · trip history · lodge commitments

  2. Prepared by operations

    The week becomes executable Programs.

    Each field day aligns the guide team, access, beat, readiness, gear, and timing without losing the shape of the whole week.

    Guide team · access · beat · readiness · timing

  3. Carried by guides

    Every guide receives the context that matters.

    The guide carries the Program into the field, keeps authority over the day, and shares enough live state for the lodge to support the experience as conditions change.

    Field judgment intact · Program live · lodge aware

  4. Written back

    Each completed day strengthens the whole.

    Reports, catches, feedback, and completion state return through their rightful owners, making the operated week accountable and useful again.

    Approved reports · catches · feedback · completion

What coordinated work leaves behind

The week closes accountable.

Program by Program, the operation earns a verifiable record—reports, catches, feedback, and completion—ready for the guest and lodge to carry forward in different ways.

After the Programs close

One delivered week becomes two kinds of memory.

Guides and operations have completed the work. Now Nanki keeps ownership clear: the guest shapes a private record and a separate Trip Story, while the lodge retains only approved context from the trip it coordinated.

Experience direction · My Journal is in local Alpha validation; sharing remains gated.

  1. Gathered

    The week leaves more than a wake.

    When Programs close, approved field outputs and private guest moments separate by owner. Beat 4. Three on a skated caddis. Ernesto's guide context. One reflection that belongs only to the guest.

    Trip fact

    Beat 4 · evening rise

    Shared Trip Moment

    Three on a skated caddis

    Guide context

    With Ernesto

    Private reflection

    Sealed for the guest

  2. Made for the guest

    Private pieces become My Journal.

    Trip structure and shared moments can gather around a private, encrypted record designed so lodge staff do not routinely read the guest's private words.

    My Journal · private

    Private reflection

    A week on the Río Chimehuín

    Private. Living. Owned by the guest.

    Place
    Beat 4 · evening rise
    Shared moment
    Three on a skated caddis
    Guide context
    With Ernesto

    Private reflection

    Sealed on the guest's device

  3. Chosen, never exposed

    A separate Trip Story travels outward.

    The guest selects client-safe moments and writes captions for the Story. Sharing creates a separate artifact; My Journal stays sealed.

    Separate Trip Story

    Chosen moments only

    Beat 4 · evening rise · Three on a skated caddis

  4. Two memories. One better return.

    The guest keeps the story. The lodge remembers its part.

    Reports, catches, feedback, preferences, and trip history—not private Journal content—give the next welcome a more personal beginning.

    Lodge memory

    Approved trip context only

    Next return · recognition first

Beyond one river

The loop stays. The experience changes.

Nanki keeps the shared journey stable while each experience owns its planning, readiness, field work, outcomes, and memories.

Reference experience · fully rendered

Fly Fishing

The first world rendered in depth: beats, guides, water, catches, client memory, and the next season.

Platform direction · not yet available

Hunting, Trekking, Horseback Riding, and Scenic Expedition are design horizons—not shipped Nanki packs.

  • Hunting
  • Trekking
  • Horseback Riding
  • Scenic Expedition

One connected platform

The whole operation, moving as one.

Nanki brings financial control, lodge operations, field execution, and retained intelligence into one monthly relationship.

Nanki Platform

$1,299

/ month

Monthly subscription for the capabilities available today.

  • SettleWise Premium financial control
  • Trailhead lodge and field operations
  • AI Assistant across the available platform
  • Inventory, payouts, and budgets
  • Platform updates, infrastructure, and support
Talk through your operation

Implementation and onboarding are scoped separately.

Your river remembers.

What will your river remember next season?

Share your operation with us. We’ll explore how the Client Loop could fit the way your lodge hosts, guides, and welcomes guests back.

Share your experience

A conversation, not a software demo.