A focused website build with a finish line.
Vexbun builds an agreed web page or route, not an open-ended list of requests. Our small digital studio in Austin, Texas handles responsive layouts and agreed content placement. Work on the rest of the site stays outside the brief unless we agree otherwise.
Quotation basis / USDQuoted against the named route, assets, and approval boundary. A single route can contain substantial interaction work. Its states and dependencies matter more to the quotation than a count of pages.
Send a briefNo fixed package price. The inquiry does not reserve production time or authorize a purchase.
One URL is not a specification.
A landing page with supplied copy is different from a form route with validation and a connected service. Both may occupy one URL. The written scope names the behaviour as well as the visible page.
| Boundary | What is named | Why it changes the work |
|---|---|---|
| Page or route | The location to create or change, its entry point and the visitor action it supports. | A new destination is not included just because the agreed page links to it. |
| Content and assets | The supplied copy, image rights, design references and files that the build can rely on. | Missing or changing material can alter layout and approval timing. |
| Interface states | Relevant menu behaviour, form responses or other states within the named route. | A static view does not describe what happens after a visitor acts. |
| Approval boundary | The person accepting the work, the review arrangement and the agreed delivery format. | Unowned sign-off leaves a short website project open indefinitely. |
| Dependencies | The existing environment and any services or access required for the agreed output. | A third-party dependency may need a separate decision before implementation. |
The service is inquiry-only. A quotation follows review of the actual route and its required material.
Make the small decisions repeatable.
Focused interface design still needs a type hierarchy and a clear action. A narrow scope is not a reason to leave either to chance.
If the page belongs to an existing site, we establish which design rules must carry through. A new heading style should not accidentally become a site-wide redesign. Any departure needs a reason connected to this route.
Designing a one-page website also means deciding how its text wraps and how much content each section can hold. A label that fits a short mockup can break when the approved wording arrives. We work with the supplied material rather than treating text as an interchangeable block.
A set of local interface decisions does not become a complete brand system. Wider component documentation or a redesign of shared navigation needs to be named in the agreement.
Finished content is part of the build.
Loose copy is not ready just because it is in a document. The build needs to know which heading belongs to which section, and where each action sends the visitor.
The client supplies approved business facts and material they are entitled to use. We agree the placement and identify gaps before relying on that content for acceptance. Copywriting, image sourcing or editing beyond the named task is not silently included.
- Copy
- Supply the wording intended for publication, separated by page section. Mark anything that still needs approval.
- Images and files
- Provide usable source files and confirm the right to publish them. A screenshot of an image is not a substitute for its original asset.
- Action destinations
- Identify where links go and what a form is supposed to do. A visible submit button does not establish the receiving service.
- Required statements
- Provide any business or policy wording that must appear. Implementation is not legal advice about whether that wording is sufficient.
If the approved material changes after layout review, we look at the effect before continuing. Replacing a sentence may be local. Adding a long comparison table can change the whole narrow-screen treatment. Those are different requests.
Check the route where space runs out.
A responsive web page build must do more than shrink the desktop view. Reading order and control behaviour have to survive the change in width.
We check the agreed route for text that clips, actions that lose their labels and content that forces the page sideways. A long heading or a form error can reveal a failure that the resting view hides.
Relevant interaction checks include keyboard focus and touch use. Where forms are in scope, the review distinguishes empty, invalid and successful responses rather than accepting the initial form as the whole feature.
The accepted scope identifies the checking boundary and any known dependency. These route-level checks are not a complete accessibility certification, a security audit or a promise that every external service will remain unchanged.
Give the finish line an owner.
The handoff is agreed before there is something to hand over. A finished file is not useful if nobody knows who deploys it or what remains outside it.
- Confirm the build boundary.
The quotation identifies the route and required behaviour. Agree the content responsibilities, review arrangement and timing before production begins. There is no automatic delivery deadline attached to the service name.
- Prepare the supplied material.
Check that the content and assets needed for layout are available. Questions affecting the route are resolved or recorded as dependencies; they are not left to become surprises at sign-off.
- Build and review against the scope.
Review the defined output with its relevant responsive and interaction states. Feedback is compared with the accepted task. Requests for additional behaviour are discussed before they become additional work.
- Deliver to the agreed recipient.
The handoff identifies the delivered output, notes on open decisions and the agreed next action. Delivery format, usage rights and any deployment responsibility follow the written project agreement.
After handoff
A website handoff service is not a continuing maintenance commitment. If another person or provider is responsible for deployment, that responsibility is explicit. Work on a live environment is included only when agreed.
A new request gets a new decision.
A second route does not become part of the first because it uses the same header. Nor does an extra integration become a small visual change because its control occupies little space.
We identify the change to the agreed output and discuss its effect on quotation and timing before proceeding. Corrections against the accepted scope are considered separately from expansion. Review rounds and correction obligations belong in the written agreement.
Choose a contained task, not a spare team.
This service suits an owned page or route with a checkable outcome. It is not a substitute for an ongoing product team or an undefined backlog. Hosting, continuing maintenance and third-party subscriptions need explicit written agreement when relevant.
If the route is not yet clear, a scope consultation can establish the decision first. If an existing page needs a targeted correction rather than a build, use the precision pass.
Before production
Settle the practical questions early.
The working arrangement needs to match the actual route. A small page can have a complicated dependency; we would rather identify it before quoting.
Can you build within an existing site?
The request can concern one route within an existing site. The current implementation and access requirements need review before a quotation. Compatibility with an unexamined system is not assumed.
Is unfinished copy a reason to wait?
Not necessarily, but the missing content must be named. We agree which material is needed before layout work and who supplies it. A build dependent on unapproved copy cannot have a reliable acceptance boundary.
How many revision rounds are included?
No fixed number of rounds is published. The review arrangement belongs in the accepted scope. Correcting a mismatch with that scope is different from adding a new route or changing the agreed content structure.
Does handoff include hosting and maintenance?
Not automatically. Hosting, continuing maintenance, third-party subscriptions and deployment responsibilities need explicit written agreement when relevant. The handoff states where Vexbun's work stops and what the receiving person needs to do.
Read the guarantee termsA page with a defined end
Put the route in front of us.
Include the page to be built, the material already approved and who will accept delivery. Those details give a focused website build its quotation basis. Unresolved scope can be discussed before production is agreed.
Send a brief