A website audit consultation should end with decisions you can use.

A fixed conversation around one decision

The offer is a focused website structure review, not an open-ended retainer.

The consultation is for a small organisation in Austin, Texas, or elsewhere in the United States that needs a clear answer before spending on implementation. The subject can be a confusing navigation, a weak content hierarchy, an existing website improvement, or a small digital operation that has become awkward to run.

We work from the thing that is failing. A few pages people cannot find. A form that loses context. A responsive website implementation that works on a laptop and falls apart on a phone. The point is not to produce a long audit for its own sake. It is to identify the decision that changes the work.

The planning range depends on the review area, materials supplied, and session length.

A one-off web consultation is planned at 300–650 USD. That is an indicative planning band, not a binding quote. The lower end fits a defined page or flow with usable access and clear evidence. A wider review, incomplete material, or several connected decisions takes more preparation. The final scope is discussed after the inquiry is read.

There is no checkout and no payment flow on this site. Enquiries are reviewed before any scope or price is discussed. Norevixa will not turn the band into a promise, and will not use it to disguise an unknown implementation job as a consultation.

Send the awkward material first.

The best preparation is not a presentation. Send the URL or a private preview, then mark the place where the work stops making sense. Include the device or browser if the fault is visual. If the issue concerns content, send the current copy and the intended reader. If it concerns an API or automation, state the systems involved and what a failed run currently looks like.

• One sentence describing the decision you need to make.
• Up to five URLs, screenshots, files, or examples that show the problem.
• The access limit: public URL, staging login, recorded flow, or no access yet.
• The constraint that cannot move, such as a CMS, deadline, approval path, or existing form.
• The result you would accept, written as an observable change rather than a slogan.

Do not spend an afternoon making the evidence pretty. Raw is better. A failed submission, an untidy outline, or a phone recording often tells us more than a deck.

The working session stays on one track.

After the material is read, the consultation follows the narrowest useful route. We establish what is known, test the assumptions that could change the answer, and then work through the screen or structure in question. If a second problem is unrelated, it is recorded rather than allowed to hijack the session.

The format is agreed during scoping. It may be a live call with screen sharing, an asynchronous review of supplied material, or a short combination of both. Norevixa does not publish a response-time promise or pretend that a calendar slot exists before the request has been checked.

The handoff is part of the work, not a courtesy email.

A useful note names the page, field, trigger, or decision under discussion. It distinguishes a required correction from a preference. It also says what was not checked. That matters when someone else implements the change three weeks later and cannot ask the same question again.

For website content architecture, the note may include a proposed page relationship and a content gap. For an existing website improvement, it may identify the smallest safe change and the test that should follow. For a workflow question, it may show where a failure should become visible before a connection is added.

This is not for a vague strategy request.

Choose this route when you have a real object to inspect and a decision waiting behind it. It is not the right service for a broad “AI strategy” with no concrete operation, a full site build that needs its own implementation plan, or an emergency promise that depends on access nobody has supplied.

It also is not a substitute for legal, financial, security, or accessibility certification. Norevixa can make a web interface clearer and document what was checked. It does not claim a professional approval it has not been given.

A good inquiry can be short. Name the object, the failure, and the constraint.