Voice & Tone — Mountaineer.fi / Remote Valley OS
Speak like a climber sitting by the stove at base camp.
Authoritative but accessible. Honest about risk, honest about price. No corporate jargon. Less manifesto, more README.
Core Characteristics
Inspiring, not hyperbolic
We move people with facts. Let the story do the lifting. A 28,000-foot wind does not need an exclamation point.
Respectful, not reverent
Climbers are people, not legends. The mountain is the only legend in the room. Honour without hagiography.
Authentic, not performative
Primary sources or it did not happen. Cite the journal, name the photographer, credit the Sherpa. No anonymous quotes, no recycled tropes.
Knowledgeable, not gate-keeping
Use the technical word, then explain it. A beginner should leave the page knowing more, not less.
Visionary, not preachy
On the Remote Valley OS side: pragmatic, technical, buildable. We are shipping a blueprint, not preaching a future.
Key Phrases
| Phrase | Context |
|---|---|
| Peaks, not paperwork. | Brand tagline |
| For climbers, by climbers. | About / identity |
| Your Himalayan shortcut. | Booking hero |
| Dry-priced permits. No markups. No middlemen. | Booking positioning |
| Fork the Alps. Climb the Himalayas. | Remote Valley OS tagline |
| Regenerative by design, open by default. | Remote Valley OS principle |
Tone by Surface
Expedition Booking
Direct. Transactional. Prices upfront.
“Here is the permit. Here is the basecamp. The climb is yours.”
- State the price, the altitude, the risk — in numbers
- Never hide pricing behind “contact us”
- No “epic,” “ultimate,” or “unforgettable journey”
Content Archive / History
Reflective, well-sourced. Long sentences allowed.
- Cite everything
- Name the photographer, credit the Sherpa, cite the year
- Write like a field journal — present-tense moments, real weather
Training & Gear Articles
Clear, authoritative, no fluff.
- Like a senior climber writing for a junior
- Use the technical word — col, sérac, fixed line, acclimatisation — and define it once
- State risk honestly. Climbers respect the truth.
Remote Valley OS
Pragmatic engineer voice. Lowercase, technical, modular.
“fork, deploy, adapt”
- Write in code voice — assume the reader can read a README
- Less manifesto, more README
- No marketing-deck second person (“Imagine yourself…”)
- The reader is already building
Social / Short-Form
Single-line truths. Image-first.
- Let the mountain talk
- One thought per post
- No hashtag stuffing
Do
- Use the climber’s word — col, sérac, fixed line, acclimatisation — and define it once for new readers
- State the price, the altitude, the risk. In numbers.
- Name the Sherpa. Credit the photographer. Cite the year.
- Write short paragraphs with present-tense moments and real weather
- On RV-OS: lowercase, code voice (fork, deploy, adapt), assume the reader can read a README
Don’t
- Never use “epic,” “ultimate,” “unforgettable journey,” or any travel-brochure adjectives
- Never soften risk. Climbers respect the truth.
- Never hide pricing behind “contact us.” List the number.
- Never write in marketing-deck second person (“Imagine yourself standing on the summit…”). The reader is already on the mountain.
- Never conflate the three lanes. Booking voice ≠ archive voice ≠ OS voice.
Voice in One Paragraph
Mountaineer.fi is built by climbers, for climbers. We sell dry-priced permits and basecamp access on four Nepalese peaks — Lobuche East, Island Peak, Mera, Ama Dablam — with no markups and no packaged tours. We publish a deep archive on training, gear, and Himalayan history. And we steward Remote Valley OS, an open-source blueprint for self-sufficient, regenerative valley communities. Peaks, not paperwork. Fork the Alps. Climb the Himalayas.
Remote Valley OS Voice (Extended)
The RV-OS voice is a deliberate departure from the main brand. Where Mountaineer.fi speaks in reflective prose, RV-OS speaks in documentation.
| Mountaineer.fi | Remote Valley OS |
|---|---|
| Reflective | Pragmatic |
| Story-driven | Spec-driven |
| ”We climbed" | "You deploy” |
| Long sentences | Short blocks |
| Journal entry | README |
| Inspirational | Instructional |
RV-OS Writing Rules
- Lowercase headers preferred
- Use code formatting for commands, filenames, variables
- Assume the reader is technically capable but new to the domain
- Explain the “why” with a sentence, not a paragraph
- Bullet points over paragraphs
- Numbers over adjectives
- A single RV-OS page should answer: “What is this, why should I care, and how do I start”
RV-OS Key Phrases
- Fork the Alps. Climb the Himalayas.
- Regenerative by design, open by default.
- Open-source framework for remote communities.
- All hardware, software, and documentation are free.
- Valleys decide their own roadmap. Always.
Mountaineer.fi — Brand Voice. Licensed under CC BY-SA 4.0.