Integrating BPO Services into Pegorion's Website
Designing a clear digital experience for a new business offering.
Overview
Pegorion is primarily a SaaS products company. BPO is a new revenue line added to that identity, and the `/bpo` page needed to establish its own credibility as a standalone B2B outsourcing offering — Healthcare, Publishing, and Customer Experience Operations — rather than read as a software company's side project.
I designed the page end to end, then came back afterward and ran a full content and IA audit of my own work, holding it to the same scrutiny I'd apply to someone else's design. This case study covers both: what I designed and shipped, and what I found and refined when I reviewed it.
How do we make a broad BPO offering easy to understand?
BPO isn't a single service. The offering spans multiple operational areas, including:
That created a hierarchy problem.
If every service and capability received the same visual importance, the experience could quickly become overwhelming.
I therefore framed the challenge around three questions:
Where the structure needed to earn trust
During the content/IA audit, I identified three important points where the way information was organized on the page could affect whether a new enterprise client would trust Pegorion.
Structuring the BPO Offering
Turning a broad service portfolio into a clear hierarchy.
"Let users understand the category before asking them to understand the details."
The Principle
The larger service domains that help users quickly understand the breadth of the BPO offering.
More detail, surfaced once a user already understands the broader service areas.
The industries Tier 1 and Tier 2 get sold into.
Making Services Scannable
Once the service hierarchy was established, the next challenge was interaction. BPO services can require a lot of explanation, but users don't necessarily want to read every description before deciding whether something is relevant.
I therefore designed the service presentation around quick recognition first, deeper exploration second. Each service needed to communicate its purpose quickly while still giving users a clear path to learn more.
Quick recognition first, deeper exploration second — each level only asks for more attention once the previous one has earned it.
Creating the Conversion Journey
Mapping every section I'd shipped to a five-stage journey - surfaced a real point of friction right at the finish line: my own CTA labels.
Discover → Explore → Understand → Trust → Connect
How the sections work together
Answers: What can Pegorion help me with?
Answers: How does the operation work?
Answers: Can I trust the process?
Answers: What supports these claims?
Answers: What can I do next?
The full designs, page by page
Every vertical's full page.
Outcome
The BPO page I designed gave Pegorion a structured way to introduce its new business offering, communicate its capabilities, explain its operational process, and guide potential clients toward engagement. Coming back to audit my own work afterward turned up two structural gaps I'm naming here rather than glossing over.
Designing beyond the page
The hardest trade-off was deciding what stayed on the main `/bpo` page versus what moved to the three subpages. I kept the main page as a map, not a manual, and trusted each subpage to carry the depth.
The redundancy between "Who We Are" and "Our Services" wasn't intentional — it was two passes at introducing the same verticals without noticing the first one already did the job. Catching that in my own audit is what this project is really about.
BPO needed something Pegorion's SaaS pages don't: proof of trust in a partner a visitor has never worked with, not proof of feature value in a tool they can try themselves. That shaped every structural decision toward hierarchy over feature breadth.
While designing, I referred back to the UX audit throughout the process — and the Core Features numbering and CTA proliferation kept surfacing as open gaps. Rather than fixing them quietly and moving on, I kept iterating against the audit, found the mistake, and corrected it to reach the outcome I was aiming for. That's a more honest version of the story than claiming it was right the first time.
✦ ✦ ✦