Your web project starts with a defined request.
No purchase is made here. A quotation follows a review of the work, not a form submission.
Send a briefBring a short website project to Vexbun, a small web studio in Austin, Texas. A page that needs building or a form that needs fixing is enough to start a conversation. Tell us what should be different when the work is finished.
Quotation basis / USD
A website scope consultation is quoted after the request and existing material are reviewed. A focused website build is quoted against the named route, assets and approval boundary. Targeted website fixes are quoted against the page, issue list and correction boundary.
No service price is published. Sending an inquiry does not reserve time, accept a quotation or authorize work.
Before the form / Make the request inspectable
Send the page, not a pitch.
You do not need a presentation. A public URL and a plain description of the problem usually give the conversation a better starting point than a long list of possible features. If there is no existing page, describe the route a visitor needs to take.
- The existing material
Give the page URL or explain what is ready. Say whether the copy and images are approved. Do not send a login or a private document link that exposes other people's information.
- The outcome you can check
For example: the inquiry action should remain readable on a narrow phone, or a new page should use supplied content. “Improve everything” is not a checkable finish line.
- The fixed constraint
Name a real deadline, platform restriction or content dependency. A requested date helps us assess the work; it is not a delivery promise.
- The approval owner
Say who can accept the result. A role is enough for the first message. There is no need to share another person's contact details.
The studio is reachable without a form.
Email the same brief if that is easier. You can also call to discuss the request. Either route reaches Vexbun; neither commits you to a project or turns the service catalogue into a booking.
7 Workshop Way, Werkstatt 2, Austin, Texas 31523
United States
This is a digital project inquiry, not an appointment request. The postal address is contact information; no in-person visit is arranged by submitting the form.
Project inquiry / No payment
Give the work a boundary.
Your name and consent are required. Add a phone number or an email address so we can reply; either is enough. Everything else helps define the request, but a finished specification is not required.
Vexbun keeps the submitted inquiry and associated request information to handle correspondence and protect this form from abuse. Read what the form records. To report a problem using the form, use the direct email or phone route above; accessibility information is also available.
After sending / A decision before a commitment
The next step is a scope check.
A short website project still needs agreement on where it stops. We review the request before proposing work. A form receipt means the message arrived, not that a deadline or a fee has been accepted.
- The request is read against its boundary.
We look at the outcome you describe and the material you have supplied. If the message mixes a page build with ongoing maintenance, those are separate decisions rather than assumed parts of one small job.
- Missing information becomes a question.
You may be asked for a public route, a clearer description of an issue or confirmation that content is ready. Access credentials do not belong in this first exchange. Any access needed for agreed work is discussed separately.
- The proposed work is put in writing.
A quotation identifies the work it covers and the relevant approval boundary. Timing depends on the request and the inputs needed to carry it out. Do not treat a date you typed in the form as a reserved delivery date.
- You decide whether to proceed.
Work starts under the accepted agreement, not because an inquiry was sent. If the request is wider than the studio's short-project shape, we say so rather than silently reducing what you asked for.
Not sure which service fits?
A website scope consultation fits an unresolved decision. A focused website build fits a defined output. A precision pass fits a known issue on an existing page. Choose “Not decided yet” in the form if the distinction is still unclear.
You can also compare the service boundaries before sending anything.
A small request is not an open retainer.
This inquiry route is not a fit for continuous staffing or an undefined stream of new features. It also cannot establish a guaranteed search ranking or a commercial result. An existing website can need a much larger intervention than the visible fault suggests; the scope check is where that distinction belongs.
A budget constraint can be part of your brief. It does not turn an unknown quantity of work into a fixed-price offer. Any agreed correction obligations are set out in the project agreement; see the guarantee terms.
One decision / Put it in writing
A plain message is enough to begin.
Start with the page that matters most. If the request needs more definition before a build can be quoted, that is the first conversation.
Send a brief