We built JourneyFuse — a travel advisor CRM — from a blank page into a product used by agencies and advisors across the industry. Along the way we learned a few things that now shape how we build software for everyone.
1. Model the real workflow, not the org chart
Travel advisors don't think in database tables; they think in trips, clients, and deadlines. The version of JourneyFuse that worked was the one that mirrored how advisors actually spend their day — not how we, as engineers, wanted to structure the data.
2. Non-technical users have to feel in control
The best software disappears. If a busy advisor needs a manual to build an itinerary, we've failed. We spent as much time on clarity and defaults as on features — and it's why the tools we build for clients are simple enough to run without us.
3. Performance is retention
Slow software gets abandoned, quietly. Making JourneyFuse fast wasn't a polish step at the end; it was a constant constraint that shaped architecture decisions from day one.
4. Integrations beat silos
No tool lives alone. The value of a CRM multiplies when it connects to the systems people already use. Designing for integration early saved us painful rework later.
5. Ship, listen, repeat
The roadmap that mattered came from watching real users, not from our assumptions. Tight feedback loops — release, observe, adjust — turned a decent product into one people rely on.
These are the same instincts we bring to client work. If you're building something ambitious, let's talk.