Scope consultation
A one-off web design consultation for the request that still has loose edges. Separate the desired outcome from surrounding work and leave with a written scope direction. Implementation is a separate decision.
Consultation scopeVexbun / Small digital studioAustin, Texas, United States
Short website projects with a clear scope.
We’re Vexbun, a small Austin studio for short website projects. We offer scope consultation, focused web builds and precision passes on existing pages. If your task is not clear yet, our consultation gives you written scope direction: the proposed task, assumptions, exclusions and the decision needed next.
Contact Vexbun7 Workshop Way, Werkstatt 2, Austin, Texas 31523
United States
office@vexbun.com
+1 (784) 555-7475
Price basis / Quoted after review of the request, existing material and agreed boundary. No fixed service price is published; the quotation is agreed in writing before work begins.
The brief / Define the work
The first useful document is a clear scope.
A page is not a scope. Its content, behaviour and approval route are what make it a manageable piece of work.
A request to “tidy the website” can mean a spacing correction. It can also mean rewriting the offer and replacing the navigation. We separate those decisions before treating them as the same short website project.
Website scope consultation is useful when you know what is wrong but cannot yet say what should change. The output is written scope direction: the proposed task, the assumptions behind it, the work left outside it, and the decision needed next.
That direction gives you something to inspect. You can see whether the proposed work solves the actual request before a build is agreed. A consultation is not an instruction to rebuild everything that happens to be nearby.
Scope test / Can the requested change be described and checked without relying on “make it better”?
The work / Services by inquiry
Give one web problem the room it needs.
Choose the work by the decision you need to make, not by a package size.
Not every page needs a new design. A working site may need a targeted website fix; an undefined request may need a conversation and a scope note before any implementation makes sense.
These services are inquiry-only. There is no checkout, and sending a brief does not reserve work or accept a quotation. Each service has a different basis because reviewing a request is not the same task as building a route.
Compare inputs and outputsSend a brief
Focused web build
A focused website build for a named page, route or small interface change. Agreed content placement and responsive behaviour belong in the work, not in a list of surprises at handoff.
Build scopePrecision pass
A website refinement service for an existing page with a stated fault. Review a clipped action, an unclear form state or a layout that breaks when content grows. Findings stay separate from corrections you ask us to make.
Refinement scopeThe handoff / A checkable finish
A small build still needs a finish line.
The final page should not arrive with an unanswered question about what happens next.
A defined output makes the work inspectable. Handoff notes identify open decisions and the agreed next action, rather than leaving a reviewer to infer whether a route is finished, awaiting content or outside the accepted scope.
For a responsive web page build, the boundary includes how the agreed material behaves on narrow screens. A desktop composition alone cannot show whether a long action label fits, or whether the page still reads in the right order after columns stack.
- 01
- Before the quote. We review the request and identify the route or issue. If a dependency prevents a useful estimate, that dependency is named rather than buried in an assumption.
- 02
- Before work starts. Scope, quotation and timing are agreed in writing. The material needed from you and the person responsible for approval are made explicit.
- 03
- During the work. The agreed task is built or reviewed. A new route or a changed requirement is discussed as a change to scope, not quietly absorbed.
- 04
- At handoff. You receive the agreed output with notes on unresolved decisions and the next action. The accepted project agreement defines delivery and any correction obligations.
Timing follows the actual brief. A short project can still depend on content that has not been approved or access that has not been arranged. We do not publish a standard number of days or revision rounds that ignores those dependencies.
See the build and handoff responsibilitiesThe boundary / Keep the project honest
We do not hide extra work inside a short brief.
A small request should not become an open-ended commitment.
This studio suits a business that can name a decision and give someone responsibility for accepting the result. It is not a substitute for a continuing product team or an unbounded retainer. If the real need is broader, we say so before agreeing to a small piece that cannot stand on its own.
Already have a site? Keep what works. A precision pass can address a specific issue without turning it into a full redesign. An observation elsewhere on the page is not automatic permission to change it.
Not ready with every detail? An uncertain boundary is a reason to consider consultation, not a reason to invent a finished specification. A real deadline can be discussed; it is not a delivery promise until timing is agreed.
Hosting, ongoing maintenance and third-party subscriptions are not silently included. Neither is a new approval round caused by an unnamed stakeholder. Those responsibilities belong in the written agreement whenever the project needs them.
The working relationship is deliberately small. Read why the studio favours bounded projects, or check the inquiry and project terms before you send anything.
Send a brief
Next action / A short website project
Send the page, the constraint, and the decision to make.
A URL and a plain description are enough to open the discussion. Say what is fixed and who can approve the work. Do not send account passwords or private customer records; access can be discussed once the request is understood.
Send a brief