Terminal is an Employer of Record (EOR) that vets international software talent and enables its customers to hire them full-time without setting up a local entity. In a competitive hiring market, efficiency is everything. Companies with the fastest, smoothest hiring processes consistently land the best candidates. That’s why, for Terminal, customers facing long times-to-fill were the most likely to churn.
While a customer-facing SaaS product technically existed, it was an early-stage MVP and not actively used. Terminal saw an opportunity to strengthen its customer experience and demonstrate greater value to prospects by transforming this prototype into a fully-realized SaaS solution.
As the primary designer on the B2B Products team, I partnered with the PM, engineers, and cross-functional designers to explore new directions for Terminal’s product. I led concept exploration and visual rebranding, while our group was encouraged to think broadly about potential product offerings.
To understand what contributed to long times-to-fill, I conducted lightweight discovery by interviewing Terminal’s internal recruiting team and reviewing internal documentation.
Terminal’s customer base was largely startups, where the person responsible for hiring was rarely a recruiter by trade. Depending on company size, it might be a founder, a manager, or an employee juggling multiple roles. To design effectively for this generalist persona, I mapped the entire recruiting journey—from awareness to retention—and focused on the jobs-to-be-done at each stage. This gave us a bird’s-eye view of what Terminal’s B2B experience might be missing, and where new opportunities could exist.
Because Terminal’s internal recruiting and legal teams absorbed most of the administrative work, customers’ pain points clustered around the Sourcing and Selection stages of their hiring journey. Secondary challenges appeared later, during Onboarding, Management, and Retention.
With a greenfield problem space to explore, my PM and I adopted the Double Diamond method by practicing divergent thinking individually, then converging our strongest ideas together. Even the worst ideas were valuable at this stage because they solidified our product direction.
Since we learned that most of the user pain points were in the sourcing and selection stages, the more detailed concepts revolved around those with some secondary concepts sprinkled in to gauge interest.
The concept of an advanced candidate search resonated strongly with stakeholders, who saw it as a solution to customers’ biggest pain point: lack of visibility into the talent pool. One executive noted: “This almost looks like a marketplace.”
That comment sparked a lightbulb: Terminal’s product could be positioned less like a static database and more like a dynamic hiring fair—where candidates could showcase their strengths, employers felt engaged and in control, and applications never disappeared into a void.
Concurrently, stakeholders asked me to refresh the B2B interface so it felt light and airy, yet professional and distinct from Terminal’s recruiting platform.
I drew inspiration from the whimsical pastel tones and illustrative style already established on the marketing site, experimenting with directions that carried that personality into the product. Taking an agency-like approach, I presented multiple brand options side by side to highlight tradeoffs in tone and usability.
The most successful direction turned out to be the simplest: reusing the recruiting palette but flipping its primary and secondary colors. This solution gave the interface its own identity while still feeling recognizably on-brand—balancing practicality with fresh visual energy.
The new platform positioned Terminal as a transparent, engaging, and fast hiring solution. By reframing the customer experience as a marketplace, we turned the product from a passive hand-off tool into a lively, self-service recruiting partner.
Through research-driven discovery, marketplace-inspired concepting, and iterative branding, we shipped a solution that:
With so little precedent to build on, I had to balance wide-open exploration with disciplined prioritization.