01 / Websites

Business website development that gives every public page a job.

For a business that needs a readable public website, a sensible editing boundary and an enquiry journey that does not lose people between pages.

Discuss a request

The offer is public-facing website structure. It does not include a signed-in customer record system by implication.

Scope-based estimate in USD after inquiry
Structured website content fields beside a public page preview
Illustrative content editor and page preview. It is a design study, not a claimed client delivery.
Public structure / content boundary

The page should answer before the form asks.

A business website carries the parts of an offer that a visitor needs before they make contact: what the business does, who it suits, what the next step is and what information belongs on the page rather than behind an account.

Small business website design in Austin starts with the content you actually have. Name the page types and decide who owns the copy. Then give each page an action worth taking instead of treating every screen as a blank canvas.

Discuss a request
02 / Commercial basis

Scope before a number.

The price is not a hidden starting rate. Tervuq gives a scope-based estimate in USD after inquiry, based on the page structure, editing requirements and existing content or migration work.

That means an estimate can account for a five-page rebuild with difficult redirects differently from a new site with prepared copy. A submitted inquiry is not a binding quote or an order.

Catalogue item / Websites

Public-facing business websites organized around readable content and a usable enquiry route rather than signed-in account workflows.

Scope-based estimate in USD after inquiry
What the estimate needs to account for
Page structurePublic page types, navigation, relationships between pages and the action each route should make clear.
Editing boundaryWhich text, images and structured fields the business can change, and which changes require technical work.
Existing materialCopy, photographs, redirects and content migration that already exist or need a decision.
Enquiry routeForm fields, reply route, consent wording and the safe description of a problem or project.
03 / Structure in practice

Public page, not private workspace.

A website can explain a service and collect an enquiry. It should not be sold as a customer portal simply because a login could be added later.

A / Public website

Readable content with a deliberate route to contact.

Visitors can inspect the offer without an account. The structure can include service pages, location facts supplied by the operator, useful search language and a form that asks only for what the inquiry needs.

  • Page hierarchy that survives a small screen.
  • Content fields with a clear editing responsibility.
  • Enquiry states for success, error and missing reply routes.
B / Permissioned portal

Records and actions controlled by role.

A portal starts with who can see what. It needs account invitations, recovery, authorization checks and records that are not made public by a styling decision.

  • Signed-in visibility tied to an agreed role.
  • Actions that explain why access is unavailable.
  • Connections to existing systems scoped before build.
Compare customer portal development
04 / Content and enquiry

Editing is a responsibility, not a promise that everything is editable.

Useful boundaries prevent a page from becoming a fragile collection of fields. The site should show what a content editor can safely change and where a technical request begins.

Start with the visitor's question.

Write the page around a decision. A service page may need a plain description, a boundary, a way to ask and enough evidence to make the enquiry specific. Tervuq will not invent reviews, customer names, star ratings or delivery statistics.

Search language such as business website development belongs where it describes the work, not in a hidden list.

Make content changes predictable.

Some businesses need to edit opening copy and service details. Others need a technical hand for navigation, redirects or a new page type. The scope records that difference instead of pretending every change has the same risk.

For website maintenance in Austin, describe the requested change and the page it affects. A new page type may need development even when ordinary copy edits do not.

Keep the enquiry small enough to answer.

The form asks for a name and a reply route, then leaves room for the page address or intended workflow. Do not send passwords or confidential client records. A useful reproduction step beats a full database export.

If the problem is already live, website troubleshooting starts with the URL, device or browser if known, and what happened after the action.

05 / Rebuild scope

A rebuild is a content decision before it is a visual one.

There is no fixed project schedule in this page. The work moves when the relevant material and review responsibility are clear.

01

Read the current route.

Inquiry

Send the current URL, the pages that matter and the point where the existing site stops doing its job. If the site is being replaced, say what must remain discoverable.

List the old addresses that still receive visitors, including links used in advertising. Each needs an explicit decision: keep the page, redirect it to a relevant replacement, or return a useful not-found response. Sending every retired address to the homepage can leave a visitor with no answer to the question that brought them there.

Check redirects for loops and chains, and update internal links to point straight to the new destination. A redirect does not guarantee that a page keeps its search position. Domain access and the ability to configure redirects must be confirmed before migration is included in the scope.

Useful output: an old-to-new address list, with unresolved pages marked for a content decision.

02

Separate content from system work.

Definition

We identify what belongs in the public website and what needs an authenticated workflow. This is where editing needs, enquiry handling, integrations and asset readiness affect the estimate.

Useful output: a written scope basis in USD, not a binding online price.

03

Review the states.

Build and review

Reviewers check headings, keyboard order, form errors, empty content and the path from public page to enquiry. A website is not finished because its default page looks tidy.

Useful output: agreed acceptance boundaries and a route for changes.

06 / A direct answer

Who is this for?

It is for a business that needs a public website to explain its offer without making a visitor decode the navigation. It is also for a team that can name who will review content and what should happen when an enquiry arrives.

It is not a ranking or revenue guarantee. The scope sets out the pages and behavior to review; it does not promise how many visitors will enquire. Bring material you have permission to publish. If a claim cannot be supported, it does not belong on the new site.

Support after release remains practical. Website technical support can investigate a fault or scope an agreed change. It is not an unlimited plan.

07 / Start with the page

Tell us what should work differently.

Send the current page address, intended page structure or a description of the rebuild. Leave out passwords and confidential records.

Tervuq / websitesPublic structure
Clear enquiry route
Website inquiry / 01Reply route required

Describe the current public page and the change you need. For a rebuild, say what must remain available.

Tell us what content is ready and who will edit it. Note any old page addresses that need a replacement.

Phone and email are individually optional. One reply route is necessary.

Prefer a direct reply? Email [email protected] or call +1 (638) 555-4623.