Our small web studio gives short projects a clear boundary.
Vexbun is a small web studio in Austin, Texas, for businesses that need a defined piece of website or interface work. Vexbun, trading at vexbun.com, operates this site. We work on short projects where the scope can be written down and the finished output can be checked.
Digital work / By inquiry
Scope and quotation by written agreement.
Studio information effective October 10, 2026.
01 / Working posture
A small brief should reduce uncertainty, not hide it.
A short website project still needs decisions. Someone supplies the content. Someone approves the output. A change to a shared component can reach much further than the page where it first appears. Calling the request small does not remove those responsibilities.
We favour bounded work because a written decision is easier to act on than a running conversation about everything a site might become. The scope identifies the task and the edge of it. That leaves room to do the work without treating every nearby idea as another deliverable.
Calm communication is practical. A question should identify the decision it needs, and a handoff should say what remains open. Neither needs a sales presentation.
See the service boundariesTurn a request into work that can be agreed.
Our website scope consultation separates an intended outcome from the work around it. The output is a written scope direction, not an instruction to rebuild everything. It identifies assumptions and exclusions, including the decision needed before an implementation quote. An existing URL is useful, but the request can also begin with material for a page that has not been built. Read about Scope consultation
Build the route, not an unnamed next phase.
A focused web build makes one defined page, route or small interface change ready for handoff. Content placement and responsive behaviour belong in that work when agreed; they are not details to discover at delivery. A second route is not included merely because it looks similar to the first. Different content or a different approval owner can change the task substantially. Read about Focused web build
Correct the issue without losing the boundary.
The precision pass is a website refinement service for an existing page. It reviews the stated issue and separates observations from corrections you actually request. A narrow layout that clips an action or a form error that leaves the next step unclear can be a useful starting point. Those are examples of review subjects, not evidence of a fault on your site. Unrelated findings stay separate unless the scope changes. Read about Precision pass
A service catalogue, not a shop
Each service invites an inquiry. No payment is taken on vexbun.com, and selecting a service does not book work. Quotations depend on the material and the agreed boundary; the site does not publish a fixed rate or a binding package price.
Focused interface design can be a modest change or a substantial task. A visible screen alone does not show the cost of integrating it. The quotation needs to account for the route and its dependencies, not just its apparent size.
05 / Written decisions
Make the finish line inspectable.
A handoff should not require someone to reconstruct the entire conversation. These are the working distinctions we use to keep a short project legible.
| Record | Question it resolves | Why it matters |
|---|---|---|
| Scope boundary | Which page, route or component is actually part of this request? | A nearby fault or a new idea does not become accepted work just because it is visible during review. |
| Content responsibility | Who supplies the material, and what is ready to use? | A layout built around unfinished copy can change when the real content arrives. The agreement needs to reflect that dependency. |
| Approval boundary | Who can say that the output meets the agreed task? | Unowned approval leaves a small project open. A decision should have an owner before delivery, not after conflicting feedback arrives. |
| Handoff note | What has been delivered, and which decisions remain open? | The next person should be able to distinguish the finished output from an observation or a possible later phase. |
The record describes a working method. The accepted project agreement defines the actual deliverables and timing. Scroll the table within its frame on a phone.
Short is a boundary, not a deadline claim.
We do not attach a standard number of days to an unfamiliar page. Access restrictions, unfinished assets or an unresolved approval can determine when work is possible. Naming those dependencies early gives a deadline something to rest on.
If a launch date is fixed, say so at inquiry. It is a constraint to assess before agreement, not a reason to hide required work. We do not treat an urgent label as a substitute for a usable scope.
Not a replacement for a product team.
The studio’s working shape suits a defined task. It does not suit an open-ended backlog presented as a single small request, or continuing maintenance assumed to be included with a one-off handoff.
A project can reveal a sensible next step. We can name it without folding it into the current work. If the request needs a wider engagement, that should be apparent before the smaller task is accepted.
06 / Direct contact
Reach the studio directly.
The email and phone below are the public contact routes for Vexbun. Use email for an inquiry, an existing project question or a data request.
Vexbun, trading at vexbun.com
[email protected]
+1 (784) 555-7475
7 Workshop Way, Werkstatt 2, Austin, Texas 31523, Austin, Texas, United States
We do not publish staffed phone or chat hours, and a message does not carry an immediate-response promise. Email lets you leave the context without needing an open conversation. The postal address is supplied for correspondence; this site does not offer appointment booking.
For a new task, the contact page gives you a structured inquiry route. Name the outcome and include the existing page when there is one. There is no need to send account credentials, payment details or private customer information to explain the work.
Data requests also go to [email protected]. A data request is answered within 7 days. The Data request page explains access, correction and deletion requests and how to provide a reply route without unnecessary sensitive documents.
Send a briefPublic site / Visitor choices
The inquiry is separate from advertising consent.
Google Ads, Microsoft Advertising and Meta Ads send paid traffic to vexbun.com. Their landing links can contain gclid, msclkid and fbclid, respectively. An identifier in a URL is not permission to save it in optional storage.
Consent Mode v2 holds ad_storage, ad_user_data, ad_personalization and analytics_storage denied until you allow the corresponding storage, and sets them back to denied when you decline or withdraw. Microsoft and Meta optional advertising storage follows your advertising choice too. Global Privacy Control, including the Sec-GPC header, is honoured as an opt-out without asking again. Denied storage does not mean there are no network requests.
You can decline optional storage and still inquire. The required consent to use your message for a reply does not authorize advertising storage. Details are in our privacy and cookie statements, including the distinction between optional measurement and the preference record or a support conversation you start.
Vexbun / Defined web work
A specific task is enough to begin the conversation.
You do not need an agency brief. Tell us what should change and what cannot move. The first question is whether the work has a boundary we can agree, not how many other services can be added to it.
Send a brief