Topia Horizon is here.
    Get early access

    Global mobility insights, delivered.

    Topia's research, guides, and compliance updates, straight to your inbox.

    Topia
    ‹  All insights
    • Letter to the industry
    • Topia Horizon
    • Global mobility

    The real reason we built Topia Horizon

    For twenty years, mobility technology has been sold in pieces. Employees don’t move in pieces.

    Dave Walters

    Chief Executive Officer, Topia

    November 5, 2026   ·   7 min read

    Follow one engineer’s move

    Illustrative. Drag to extend her trip.

    3 days

    Business traveler

    A three-day trip to Munich to support a client launch.

    A typical stack

    1

    system holds her data

    0

    re-keyed handoffs

    On Horizon

    1

    system holds her data

    0

    re-keyed handoffs

    For twenty years, the technology providers serving global mobility have failed the community they were built to serve. The cause was bad architecture and a stubborn refusal to admit it. Mobility leaders have spent two decades stitching together software that was never designed to fit together, and calling the result a program.

    We built Topia Horizon to fix that.

    An engineer takes a three-day trip to Munich to support a client launch. The launch slips, and three days become six weeks. Now she’s a short-term assignee, handled by a different team, in a different system. Six weeks becomes a year. Now there’s tax, immigration, payroll, a housing allowance, and a fourth vendor who has never heard her name. Eventually, she stays for good.

    At every one of those transitions, someone re-keyed her data, a handoff dropped context, and a compliance exposure opened that nobody was watching.

    The employee experienced one continuous move. Our industry experienced four unrelated transactions.

    What went wrong

    Mobility technology was built around vendor org charts and product categories. The typical program runs on a stack of point solutions (travel booking, assignment management, tax, immigration, payroll, expense) that don’t share a data model and barely share a vocabulary.

    Implementations take quarters and routinely outlast the executive who sponsored them. Changing a single policy threshold requires a professional services engagement, so mobility leaders can’t self-serve their own program. Navigation is so complex that companies hire people whose entire job is operating the software.

    When your customers have to staff up to use your product, you’ve sold them a second job.

    Topia built part of that stack. I’m not exempt from this critique.

    We also defined the problem too narrowly. “Global mobility” is a category our industry drew to match its own org charts. The problem is cross-border movement. Every time a person crosses a border, their work, pay, data, and tax and immigration exposure cross with them, whether for three days or thirty years. A business trip and a permanent relocation are two points on the same line, and software that only sees one end of it will always fail the person in the middle.

    Why it happened

    Business travel and talent mobility have lived in separate budgets and separate functions for decades, with travel under Finance and Procurement and mobility under HR. Compliance rules are fragmented by jurisdiction, and every fragment spawned a specialist vendor. Each of those vendors optimized its own slice, and many did it well.

    Nobody was responsible for the handoffs between vendors, which is where data gets re-keyed and compliance exposure goes unnoticed.

    Why now

    Three things changed at once.

    The line between travel and mobility dissolved.

    Distributed work turned a category boundary into a continuum. Remote work requests, extended trips, and commuter arrangements now outnumber classic expat packages at many companies. What we used to call edge cases are now the program.

    Regulatory exposure moved downstream to the business traveler.

    Permanent establishment risk, posted worker rules, shadow payroll, and state and local tax triggers now attach to trips nobody used to track. That three-day trip to Munich is where the next audit finding starts.

    AI changed what “hard to configure” means.

    Policy logic that once required a services engagement can now be interpreted, modeled, and deployed in days. The excuse that complexity requires consultants no longer holds.

    The products in the market weren’t built for any of them.

    Horizon

    Horizon is built on three commitments, each aimed at one of the failures above.

    One continuum.

    From a day trip to a permanent relocation, every cross-border movement lives on a single data spine. Our Munich engineer never changes systems, and her history travels with her.

    Implementation in weeks.

    The new standard is a dynamic implementation approach that delivers value as soon as the customer is ready.

    Configuration the customer owns.

    Mobility leaders change policy without filing a ticket or calling us.

    With Horizon

    The same six functions on one data model.

    One data spine

    Travel booking

    Shared data model

    Immigration

    Shared data model

    Assignment management

    Shared data model

    Payroll

    Shared data model

    Tax

    Shared data model

    Expense

    Shared data model

    Horizon also changes what a mobility team can ask of its data. Not long ago, a client’s mobility team told us they needed better reporting. We told them they could have anything they wanted and asked what that was. They didn’t have an answer. They just knew they needed something.

    That failure was ours. When your data lives in six systems, you’ve never seen the whole picture, so you can’t know which questions to ask of it. Put every movement on one spine and the questions start arriving on their own.

    Our clients have been describing this to us in quarterly business reviews for a decade, and we can now hand it to them.

    Three questions to ask any vendor

    Whether or not Horizon is ever on your shortlist, ask these of whoever you work with:

    • What happens to the employee’s data when a trip becomes an assignment?
    • Can my team change a policy rule without calling you?
    • What is your median time from contract signature to first production use?

    If the answers involve a migration, a ticket, or a calendar quarter, you’re buying another point solution.

    The measure

    An engineer is landing in Munich today for three days, and she may end up staying for good. Her company should already know where she is, what she’s exposed to, and what comes next.

    The measure is whether, five years from now, anyone remembers that business travel and relocation were ever separate categories of software.

    One continuum, from a day trip to a permanent move.