Short answer
The old site organized itself around our service categories, which is accurate but not useful: nobody arrives saying "I need custom software," they say their manual process is breaking at scale or their data sits in three places. So the rebuild reorganized the navigation and service pages around those problem types, replaced pages that were too generic to be cited by AI-assisted search with content that answers the questions we hear in scoping calls, and split the single "Get in touch" CTA into separate paths for ready-to-talk and research-phase visitors. It is early, but the contact form completion rate is up and time-on-site for service pages has improved.
The previous version of blackbyrds.digital had been live for about two years. It looked fine. Clients found us through it. We did not hate looking at it. Those are not good enough reasons to keep a site.
We rebuilt it. The reasons were structural, not aesthetic, and it is worth writing them down because the same issues affect most studio and agency sites we have looked at.
The Information Architecture Problem
The old site organized itself around service categories at a level of abstraction that was accurate but not useful. "Custom Software" is a category. It does not tell a prospect what they are actually getting or whether it is relevant to their problem.
We had learned from client conversations that the way people describe their problems does not map to service categories. A business does not come to us saying "I need custom software." They come saying "our manual process is breaking at scale" or "we have data in three places and nobody can see the full picture" or "we need to automate the part that takes four staff members two days every month."
The redesign organized around those problem types. The service pages reframed from "here is what this service is" to "here is the problem this solves and who it is for." The navigation changed to reflect how people arrive with questions rather than how we internally categorize work.
Answer Engine Optimization
The search landscape has changed materially in the past eighteen months. A growing proportion of research and discovery happens through AI-assisted search - ChatGPT, Perplexity, and AI-augmented results in traditional search. The content requirements for appearing in those contexts are different from traditional SEO.
Traditional SEO optimizes for keyword matching and domain authority. Answer engine optimization - AEO - requires content that answers specific questions well enough to be cited in AI-generated responses. That means structured, specific, authoritative content rather than keyword-rich but vague content.
We audited every page of the old site against this lens. Most pages were too generic to be citable. A page titled "Custom Software Development" that describes the service in broad strokes will not be referenced when someone asks an AI "what should I look for in a software studio in the Philippines." A page that answers specific questions about how we scope work, what our process looks like, and what types of problems we have actually solved is more useful.
The new site is longer on specifics and shorter on marketing language. Every major service page has a section that directly answers the questions we most commonly hear in scoping calls.
Conversion Path Clarity
The old site had one CTA: "Get in touch." That is not wrong, but it did not differentiate between a visitor who is ready to talk to us today and a visitor who is still in the research phase.
We mapped out the conversion journey more carefully and built different paths for different intent levels.
High-intent visitors - people who are ready to talk - go directly to a contact form with a focused brief. We reduced the number of fields and made the ask specific.
Research-phase visitors get content that earns trust without requiring a commitment: case context (without fabricated specifics), how we work, what our process looks like. The goal is to be the studio they remember when they are ready to move.
We also added clearer pricing context. Not exact numbers - every project is scoped individually and the cost depends on the scope - but enough information about how our pricing works and roughly what different types of engagements involve that visitors can self-qualify before reaching out.
What the UX/UI Design Process Looked Like for Our Own Site
We treated it like a client project, which meant a written thesis, a defined scope, and a fixed timeline. We ran through our own discovery process on ourselves, which was more uncomfortable than we expected - you see the gaps in your own positioning more clearly when you have to write them down.
The site went through three rounds of feedback from the team before we touched design. Then design, then build, then a staging review with fresh eyes.
No launch announcement, no countdown timer. We pushed it live and started watching the data.
It is early. But the contact form completion rate is up and the time-on-site for service pages has improved. We will keep iterating.
Questions · 04
Frequently asked questions
The old site looked fine and clients found us through it. Why rebuild?
Looking fine, generating clients, and not being unpleasant to look at are not good enough reasons to keep a site. The problems were structural: an information architecture built around how we internally categorize work, an abstraction level too generic to be citable, and one conversion path for every visitor regardless of intent. None of that shows up in a screenshot.
What does answer engine optimization change about a service page?
Traditional SEO optimizes for keyword matching and domain authority, while answer engine optimization requires content specific and authoritative enough to be cited in AI-generated responses. A page titled "Custom Software Development" that describes the service in broad strokes will not be referenced when someone asks an AI what to look for in a software studio in the Philippines. Every major service page now has a section that directly answers the questions we most commonly hear in scoping calls.
Does the new site show pricing?
Not exact numbers, because every project is scoped individually and the cost depends on the scope. What the site does give is context on how our pricing works and roughly what different types of engagements involve, so visitors can self-qualify before reaching out.
How did you run a redesign process on your own studio?
Like a client project: a written thesis, a defined scope, and a fixed timeline, with our own discovery process run on ourselves. That was more uncomfortable than expected, because you see the gaps in your own positioning more clearly when you have to write them down. The site went through three rounds of team feedback before we touched design, then design, then build, then a staging review with fresh eyes, and we pushed it live with no announcement and started watching the data.
