I’ve reached out to hardware vendors, including NVIDIA and AMD, seeking review samples for Tech Business News, but so far, all I’ve heard back is crickets.
Meanwhile, I watch channels such as Gamers Nexus and Linus Tech Tips, featuring Linus Sebastian, publishing hardware reviews while I’m still trying to arrange product access.
They’ve built substantial audiences, and I understand why manufacturers would see value in having their products reviewed by people with that kind of reach and recognition.
But I keep coming back to the same question: where does that leave smaller publications and individual reviewers who have experience and something worthwhile to contribute?
I founded Tech Business News in 2020 after spending roughly two decades working in IT, and I want to bring that practical background into hardware reviews.
The challenge has been getting equipment into my hands so I can form an opinion based on using it, then explain that experience honestly to readers.
What about the smaller voices?
When I watch established reviewers working through the latest hardware, access appears considerably easier from the outside than it has been through my own vendor enquiries.
I don’t know what arrangements sit behind each review, how equipment was obtained or how much work went into establishing those relationships with the companies involved.
What I do know is that I’ve approached vendors about reviewing their hardware and haven’t received the replies needed to move those conversations towards actual testing.
That’s frustrating when you’re trying to build coverage, particularly when the request is about obtaining access to equipment so you can assess it properly for readers.
A smaller audience doesn’t automatically mean a reviewer has less useful experience, just as a large audience doesn’t automatically establish the quality of an individual review.
There should be room for different perspectives, including someone who wants to explain what a product feels like to use outside a tightly controlled benchmark session.
Can you actually notice the difference?
My own interest in hardware starts with a fairly ordinary question: will someone notice a meaningful improvement after spending their money and installing the new component?
A CPU might have a slightly higher clock speed, but that alone doesn’t tell me whether my everyday experience will improve enough to justify an upgrade.
I want to know whether a game feels smoother, whether an application responds faster and whether the improvement remains noticeable once the excitement of upgrading wears off.
For me, chasing small benchmark differences can become a hobby in itself, especially when the discussion centres on advantages that are difficult to perceive during use.
There’s an audience for that level of comparison, but my preference is to investigate what those results translate into when someone sits down at their computer.
If I need a chart to distinguish between two experiences that otherwise feel much the same, I’d want to make that clear in my review too.
That doesn’t make the measured difference irrelevant, because some buyers have workloads where relatively small gains become useful, particularly when repeated across long periods of work.
It does mean I’d want to explain who benefits, under what circumstances, and whether someone using the hardware differently should expect to notice the same advantage.
Playability deserves more attention than a winning number
With gaming hardware, I’m interested in the experience of playing, including whether movement feels consistent and whether interruptions become distracting during the parts that demand responsiveness.
An average frame rate gives useful information, but I’d also want to investigate stuttering and performance drops that might explain why a game sometimes feels uncomfortable.
Measurements can help identify those problems, while time spent playing helps me describe how they affect the experience and whether they would influence my buying decision.
My approach would combine those observations with enough testing detail for readers to understand what I experienced, including the settings and other hardware in the system.
I’m comfortable giving a personal opinion, provided I explain what supports it and acknowledge that someone with different equipment or priorities might reach a different conclusion.
That’s the kind of review I want to publish: a practical account of whether the hardware improved my experience and who might find that improvement worthwhile.
Experience still needs equipment
My years working in IT give me a foundation for assessing hardware, but they can’t replace direct access to the particular product I’m supposed to review.
I can read specifications and report a manufacturer’s claims, although an independent assessment requires testing that gives me something of my own to say about performance.
Without the product, I can’t investigate whether a promising specification becomes a useful improvement, or whether an unexpected limitation changes how I’d assess its overall value.
Buying hardware provides another route, but every purchase adds an expense before accounting for the time involved in preparing tests, investigating problems and writing the review.
For a smaller publication, those costs influence which products can realistically receive coverage and how often there’s an opportunity to compare equipment under similar testing conditions.
A loan sample could help make that work possible, with clear arrangements about testing timeframes and returns, alongside the editorial freedom needed to publish the findings.
A reply would be a useful start
I’m not suggesting that NVIDIA or AMD owes me equipment, and I can’t explain why my approaches haven’t received replies or assume what caused that silence.
I’d still appreciate an answer, even if it simply explained that review samples weren’t available, because that would give me something definite to work with instead.
At present, the silence leaves me trying to develop hardware coverage without knowing whether there’s a suitable contact or a realistic opportunity to arrange product access.
I want the chance to assess equipment through my own experience, bringing a smaller publication’s perspective to a conversation that already includes some very prominent voices.
If an upgrade makes a noticeable difference, I want to explain where I experienced it, while being equally clear when the benefit is harder to recognise.
Readers deciding whether to replace a working computer deserve that context, particularly when a technically faster component might deliver less practical improvement than they were expecting.
