Real Problems. Real Conversations.
A portfolio can show you what someone built. These conversations show you how we think.
Not every business owner who contacts Valhalla Computers needs a new website. Sometimes they need someone to listen, look at what is actually happening, explain what they find, and help determine the most sensible next step.
The examples on this page come from real conversations and real website problems. Unless a client specifically gives permission to be identified, names, website addresses, and identifying details are removed. The problems, investigative process, and lessons remain real.
The New Store Wasn’t Quite as New as It Looked
An ecommerce business owner had recently moved a long-running online store to a newer platform. The new storefront looked modern, but she was still encountering problems and wasn’t sure whether work she had already paid to have corrected had actually been completed.
The Concern
The conversation began with concerns about the new ecommerce site and whether several problems inherited from the previous store had really been resolved. The business owner had already worked with another developer and had paid for additional changes, so our job was not to immediately sell her another website or start replacing things.
The first job was simply to listen.
She explained what she had been told, what changes were supposed to have been made, what continued to concern her, and how she wanted the business to operate going forward.
We Started Clicking
Rather than assuming the existing developer was right or wrong, we opened the website and began using it like a customer. We followed navigation links, opened product pages, reviewed wording, searched for older material, and looked at how someone unfamiliar with the business would experience the site.
That immediately led to an important question: if a visitor had never purchased one of these products before, would they actually understand what they were buying and how they were supposed to use it?
The business owner knew exactly how her products worked because she had worked with them for years. A new customer did not have that knowledge. That conversation led to the realization that the website needed clearer instructions and a dedicated explanation of how the products are used.
Then We Looked Under the Hood
As questions became more technical, we investigated further. Old URLs from the previous ecommerce system were checked. Individual product pages were examined. Page source and metadata were reviewed. Search-engine behavior and the relationship between the old store and new storefront were considered.
Instead of relying solely on what somebody said had been fixed, we looked for evidence of what was actually happening.
Legacy Store Pages
Older ecommerce pages remained publicly accessible even though a new storefront had replaced the previous system.
Old Product Language
References to an earlier digital-product business model remained even though the company had moved toward physical printed products.
SEO Plumbing
Product pages contained useful content but were missing or underusing several important product-specific SEO signals.
Development Remnants
Some production metadata still referenced assets associated with the platform or tools used during development.
Customer Confusion
Certain wording assumed customers already understood the product instead of clearly explaining what it was and how it should be used.
Conflicting Messages
Different parts of the site occasionally described the product or purchasing experience in ways that did not completely agree with each other.
We Explained What It Meant
Finding technical problems was only part of the conversation. The business owner did not need a lecture about source code, metadata, redirects, structured data, ecommerce architecture, or search-engine indexing. She needed to understand what those things meant for her business.
We explained the difference between removing something from a visible menu and actually making an old page inaccessible. We discussed why search engines can continue finding older material when that material is still being served by the website. We explained how contradictory wording can leave both customers and search engines uncertain about what is actually being sold.
When something required deeper technical research, we investigated it. When it could be explained in plain English, we explained it in plain English.
The goal was not for the client to become a web developer during the phone call. The goal was for her to understand her own website well enough to make informed decisions about it.
We Didn’t Tell Her to Fire Her Developer
This is an important part of the story.
We did not know every decision that had been made during development. We did not know every instruction the previous developer had received or every limitation they had encountered. It would have been irresponsible to pretend otherwise.
Instead, we focused on what could actually be demonstrated. Here is what the site is doing. Here is what remains accessible. Here is what appears inconsistent. Here is why it could matter to a customer. Here are the questions worth asking.
The business owner could then take that information back to her existing developer and ask for the work to be completed or clarified before spending more money.
The Result
No website was sold during this conversation. No unnecessary software was installed. No immediate rebuild was proposed.
Instead, the business owner finished the conversation with a clearer understanding of what was happening on her website, several specific issues to discuss with her current developer, ideas for improving the customer experience, and a better understanding of what should be addressed before paying for additional work.
Sometimes that is the most valuable result a consultation can provide.
How We Approach a Website Problem
Listen
What are you seeing? What concerns you? What has already been tried?
Look
We actually use the website and examine the problem from the customer side.
Verify
When something needs deeper investigation, we research, test, inspect, and confirm.
Explain
We translate what we find into language that makes sense to the business owner.
Prioritize
We separate what matters now from what can wait or may not need changing at all.
Not Every Conversation Ends With a Sales Pitch
Sometimes the right answer is that your existing developer should correct something. Sometimes a problem can be fixed in a few minutes. Sometimes a website needs a larger project. Sometimes the thing worrying you is not actually worth spending money on.
We believe you deserve to know the difference.
Valhalla Computers does not measure the size of your invoice by how confused you are. We would rather explain what is happening, identify what actually matters, and let you decide what makes sense for your business.
More Real Conversations Are Coming
As Valhalla Computers works with more small businesses, this page will continue to grow with examples of actual problems, actual investigations, and the practical solutions that came from them.
Some will be technical. Some will involve content, navigation, search visibility, ecommerce, customer experience, or simply looking at a familiar website through unfamiliar eyes.
The details will change. The approach will remain the same: listen first, investigate the problem, explain what we find, and recommend what makes sense.
Something About Your Website Doesn’t Seem Right?
You don’t need to know the technical terminology. Tell us what you’re seeing and what concerns you. We’ll start there.
Schedule a Free 30-Minute Consultation Contact Valhalla Computers