Services / scope before commitment
Norevixa provides web design in Austin, Texas, small business workflow automation, and one-off web consultation for organisations with a specific job to finish. Choose the deliverable, not the largest package.
Inquiry-only / USD planning bands
A one-page web project has an internal planning band of 900–1800 USD. A consultation-only review has a planning band of 300–650 USD. Neither is a quote. Content state and implementation depth matter more than a package label.
Automation is scoped by systems and exceptions. Support is scoped by issue count, access, and duration. No purchase or payment takes place on this site.
Four engagements / one small studio
Compare the starting points
A page that needs a better content order is not automatically a rebuild. A workflow that nobody can explain is not ready for a connection.
For a public site whose structure or responsive behaviour needs work. The deliverable combines a page hierarchy and content structure with implementation, rather than leaving the words to be squeezed into a finished layout.
Basis: page count, content state, integrations, implementation depth.
For an operation that repeats with known inputs. A form-to-system handoff or a small API integration needs an explicit trigger and a visible failure state, not just a successful first demonstration.
Basis: number of systems, trigger volume, data fields, exception handling.
For a decision you need to make before commissioning implementation. Bring the current site or materials and one review question. The work ends with written decisions and a next step that can stand on its own.
Basis: review area, supplied materials, session length. Planning band: 300–650 USD.
For a working project with a correction to make. Content changes, debugging, or a narrow maintenance task belong here when the surrounding structure is useful and a full replacement would create more risk than value.
Basis: issue count, current-code or CMS access, support duration.
Working boundary
Websites and workflows meet at the edges: a form sends a record, an editor changes a field, or a failed request needs somebody to notice. That edge belongs in the scope. Otherwise the apparent saving becomes another manual task.
Norevixa is a small Austin studio, not a packaged software vendor. We work on the public site and the small operation behind it. The studio principles explain why keeping a useful existing system is often the better starting point.
Deliverables / not subscriptions
These are scope starting points, not a promise that every request fits. Access and the existing system decide what is possible.
| Engagement | Useful input | Scope to agree | Not implied |
|---|---|---|---|
| Web project | Existing URLs or a proposed page list; an honest account of which copy exists. | Page hierarchy, responsive implementation, content responsibilities, and review points. | A hosting bundle, a brand overhaul, or a guaranteed number of inquiries. |
| Workflow automation | A repeatable operation, source and destination systems, and a safe sample record. | Trigger conditions, field mapping, failure reporting, and the boundary of retries. | Unlimited event volume or support for an API that the destination does not expose. |
| Consultation | The question to settle and materials to inspect before the session. | Review area, session length, and the form of the written next step. | Implementation work or a standing obligation to manage the project. |
| Support | Steps that reproduce the issue and the code or CMS access available. | The correction, affected pages or systems, and a check of the changed behaviour. | Round-the-clock monitoring or an unagreed response-time commitment. |
Cost drivers
Two sites with the same page count can have different scopes. Ready copy in a consistent template is a different job from unclear navigation and unfinished service descriptions. A connection to a documented endpoint is different from a workflow with several exceptional records.
The homepage planning estimator lets you vary the inputs. Its range is a budgeting aid. It is not an offer to perform an unspecified project for the displayed amount.
The one-page base is 900–1800 USD. Each additional page adds 180–360 USD, and each integration adds 450–950 USD. An unfinished content state adds 350–700 USD. A support month adds 180–420 USD to this internal planning model.
Those increments do not price a standalone automation or guarantee a particular maintenance service. A high-volume trigger with many exceptions needs its own scope. So does a site where the current code cannot be inspected.
Review comes first. Norevixa discusses the scope and price basis after reading the inquiry; sending a form does not reserve work or create a contract.
From request to work
A review point should answer a practical question: can someone complete the task, can the owner edit the content, or can a failed operation be found? The process page sets out how those decisions become a scope.
At inquiry, give the link or system name and describe the desired change. Do not send passwords or a live customer export. A safe example is enough to explain the problem.
After review, the work needs named inputs and limits. If the question is still too broad, a consultation may be the useful engagement instead of a speculative build.
During delivery, compare the agreed result with the actual pages or operation. A new requirement is discussed as a scope change rather than quietly folded into the original task.
At handoff, the owner needs to know what moved and where to look next. Further support is a separate duration or task to agree, not an automatic subscription.
Before you choose
You do not need to commission a redesign to ask for website repair and support. If the navigation works and the issue is one broken form, keep the navigation. Existing website improvement starts with the part that is costing time, not the part that looks easiest to replace.
Send the symptom. If a mobile page hides the action or a record stops arriving, describe where you can observe that behaviour. You do not need to choose a technical cause before asking for help.
This is not a packaged SaaS platform or an always-on operations desk. Requests for guaranteed leads, undefined transformation programmes, or urgent commitments without access are not a good fit. A bounded web task or repeatable workflow is.
The next decision
Name the page or operation you want to change. If more than one engagement seems relevant, say so; the boundary can be settled after review.
