You received an email from me

That bug was not found by accident.

I look at company websites for what is visibly broken. Whatever is in your email, I verified on your live site first. If I cannot find something I can prove, I do not write.

01

A finding, exactly as you would receive it

From a real company website. Name and numbers changed, the fault is real.

ihre-firma.de/kontakt
Observation
The phone number appears as text on the contact page and is set up to be tapped. The number shown is not the number linked. Two digits differ in the area code.
Displayed
0 30 12 34 56 78
Linked
0 30 21 34 56 78
Impact
Anyone at a desktop reads the correct number. Anyone tapping on a phone, which is most people, calls someone else. There is no error message and nothing in your inbox. An owner can go years without noticing, because he never taps his own number.
Check it yourself
Open your contact page on a phone, tap your own number, wait until it appears in the dial field, compare digit by digit. You do not have to place the call.
Effort
One line. Faults like this almost always come from a move or a change of number: the visible text gets updated, the underlying link stays as it was.
02

How a finding comes about

STEP 01

Look at it like a visitor

I open your site on a desktop and on a phone and walk the paths a customer walks. Home, navigation, contact, pricing, ordering.

STEP 02

Look at what money depends on

A crooked margin costs you nothing. A contact form that never arrives, a number that dials wrong, a link into nowhere, a price that reads differently in two places: that costs you enquiries.

STEP 03

Try to disprove my own suspicion

This is the step that makes up the work. A lot of what looks broken is deliberate: a menu item with no target because a submenu opens beneath it, or a scrolling logo strip whose contents appear twice in the code so the loop does not jump. Findings like that get thrown out.

STEP 04

Check again right before sending

Days can pass between the finding and the email. Anything already fixed gets dropped. If my description is not exactly right, I rewrite it before the email goes out.

That is why your email contains exactly one fault and not a list. A list would be quick to generate. It would just be mostly wrong.

03

What I do not do

I see exactly what any visitor to your website sees. No login, no access, no testing against your systems. I change nothing, I leave nothing behind, and I store no data about you.

Every observation I send you can be reproduced by simply opening your own site. If you have an agency or in-house IT, just pass the finding on to them. They will reach the same result, and that is the point.

04

What I have built

All built and shipped by me. You can open every one of them before you reply.

05

Who is checking

My name is Nikita Senderovych and I work alone. No team, no sales department, no agency behind me. If you reply to the email, you are writing to the person who found the fault.

That is also why I spot these things. I run something myself, and I have built the same faults myself. A form that quietly went nowhere. A payment that never arrived because a setting in the background was wrong and sent nobody an error. I know these not from a course but from the week I spent hunting them down.

What is missing from this page: testimonials, client logos, case studies, numbers.

None of it is here, because I have only just started this work and have no clients in it yet. I could write something that looks good. You would not be able to verify it, and verifiability is precisely the point here.

What you can verify is in the email, it is on your own site, and it is above under “What I have built”. That is the only evidence I have right now, and it is the only kind that counts.

06

What it costs

The finding itself costs nothing. You already have it, whether we work together or not.

Small, clearly bounded fault

300 to 800 euros

A wrong link, a placeholder, a number, a dead link, an element that slips on mobile. Fixed price, quoted up front, it does not change afterwards. I do not bill by the hour.

Fault that enquiries or orders depend on

2,000 to 15,000 euros

Not a repair job but a full review. I walk every path along which a customer comes into being on your site, and you get a list of findings with priority, reasoning, evidence and an implementation plan. Where you land in that range depends on the size of the site. I tell you that before you commit, not after.

Finding and fixing are separate

Finding I can do from the outside. Fixing I cannot. That needs access to your site, and whether and how that works we settle beforehand, not halfway through. If you already have an agency doing the implementation, that is the faster route. Then I write the finding up so your people can act on it without follow up questions, and you pay only for the review.

07

What happens next

The simplest thing is to reply to the email. One sentence is enough.

You just want this one fault gone.

Tell me so. You get a fixed price and a date, and then it is done.

You want to know whether there are more of them.

Then I go through the whole site and send you what I find, with context and a price. If I find nothing worth mentioning, I write you exactly that.

You are not interested.

Reply with a single word and I will not write again. The fault is still in the email. You are welcome to keep it.

I reply within one working day. If you would rather talk, I schedule it in your time zone.

nikita@senderbuilds.com
Nobody answers but me.