The Sales TravelerIndependent · Reader-funded · A partnership buys reach, never a ratingIndex Desk Live
The Sales TravelerThe decision desk for revenue travel
Open the Index Desk
For revenue teams that must defend the trip

Decide the trip before the budget asks for a defense.

Every trip is a commercial bet. I help you decide whether a meeting earns the flight, write down the ROI case, and separate real signal from travel theater before your team commits the spend.

By Rachel Julian · Founder & editor · human judgment, source-backed, correctable in public
My recommendation: Score the trip before it reaches the calendar, judge revenue risk instead of trip cost alone, and make the follow-up evidence visible so your team can defend the outcome after the meeting.

Score a trip in 10 minutes →Fix your approval matrix

Turn one decision into a repeatable team practice.

Start free. Move up only when your team needs reusable data, a repeatable process, or Rachel’s judgment on a consequential decision.

The number that matters herePublished commitments onlyDecision quality beats travel theater

Recommended for your role

All briefs →
  • Travel Approval Should Ask One Question: What Will Change? — Editorial analysis · verified 2026-07-02

    A sales trip should be approved only when the requester can explain what commercial condition will change because someone is physically present. The change might be stakeholder access, deal risk, renewal confidence, executive alignment, field intelligence, or follow-through velocity. Without a clear change statement, the request is motion, not revenue travel.

  • The Conference Follow-Up Map: Turn Hallway Moments Into Account Motion — Editorial analysis · verified 2026-07-03

    A Conference Follow-Up Map turns event conversations into account motion by sorting each interaction into customer, prospect, partner, market-signal, or dead-end categories and assigning the right next action within 48 hours.

  • The Account Visit Pre-Mortem: Kill the Weak Trip Before It Burns the Quarter — Editorial analysis · verified 2026-07-02

    An account visit pre-mortem asks why the trip might fail before it happens. It protects the quarter by exposing weak access, vague outcomes, missing stakeholders, bad timing, and follow-up risk early enough to redesign or cancel the trip.

  • AI Travel Agents Will Not Save Bad Sales Policy — Editorial analysis · verified 2026-07-02

    AI travel agents help sales teams only when the policy underneath them knows the commercial job of the trip. If the rules are generic, the agent becomes a faster way to enforce the wrong tradeoffs.

  • How to Choose the One Conference Worth Traveling For — Editorial analysis · verified 2026-07-02

    Choose the one conference worth traveling for by ranking events against account density, stakeholder access, meeting availability, partner leverage, timing, and follow-up capacity—not brand prestige, booth size, or fear of missing out.

  • The Sales Traveler Boundary Script: How to Decline Bad Travel Without Looking Soft — Editorial analysis · verified 2026-07-02

    A sales traveler can decline bad travel without looking soft by affirming the commercial goal, naming the specific risk in the proposed trip, offering a stronger alternative, and defining what conditions would make travel worth approving. The script should protect the outcome, not center personal discomfort.

I selected these briefs for their relevance to sales leaders. Each brief shows how I reached the view, which sources I used, when I verified them, and how confident I am.

The Field Brief · For Sales Leaders

Get this in your inbox weekly.

One framework, one benchmark, one field note — written for sales leaders, not a general travel audience.

Free, weekly, via Substack · no sponsor picks the stories

Weekly, free, via Substack, unsubscribe anytime · archive at thesalestraveler.substack.com

Use wallet infrastructure only when it improves the revenue decision

Start with role questions for payment, access, attribution, privacy, recovery, and when not to use blockchain.

Review the revenue-leader questions →