Oxbury X / Small studio / Austin

We keep small project work contained.

Oxbury X offers small studio project support and focused business consultation from Austin, Texas. The studio is for a question that needs an outside reading, or a piece of work that needs finishing without turning into a larger engagement.

Oxburyx, trading at oxburyx.com, operates this site under the public brand Oxbury X. This is a small service studio, not a software product or a marketplace for other providers.

42 Oak Lane, Floor 2, Austin, Texas 23250, Austin, Texas, United States

Operator information effective October 8, 2026.

Start an inquiry
Open studio notes beside a pencil and a marked working edge
Working principle / Mark the boundary before adding work.

The actual work

A second reading. A usable handoff.

The studio works with material you already have. A consultation examines a stated question and ends with a written next useful step. A one-off task turns a defined request into a finished piece. Project support holds an agreed part of a live project while its owner keeps the wider responsibility.

Project brief review is a good example of the scale. The subject is the brief itself: what it asks someone to do, what is available to work from, and which questions remain unanswered. A review should expose an unclear instruction, not bury it beneath a longer document.

That distinction matters. A clean-looking revision is not useful if the underlying decision is still missing. We separate changes that can be made from questions that need your answer, so you can see what the handoff does and does not settle.

Compare the working routes

Contained-brief method

The edge is part of the work.

“Have a look at this” is a starting point, not a brief. It gives permission to read but says nothing about what would make the reading useful. We turn that opening request into something a person can finish.

The method is deliberately small. A narrow brief makes it easier to notice a wrong assumption and easier for you to decide whether the returned work answers the question you brought.

01

Name the question

Start with what needs deciding or changing. Background comes after that. A useful question tells the reader where to concentrate rather than asking them to discover the purpose somewhere in the files.

You do not need polished language. “These two instructions disagree” gives the studio a better starting point than a broad request to improve the entire project.

02

Identify the working version

A current draft and an old reference have different jobs. Mark which one is authoritative and which is there for context. If no version has been agreed, say so; otherwise a revision can accidentally preserve the wrong instruction.

Only share material you are permitted to share. A short description is enough to open an inquiry. There is no need to send confidential records simply to find out whether the request fits.

03

Agree what leaves the studio

The output might be a decision note or a marked revision. It needs a name and a boundary before work starts. A request for “help” becomes easier to judge when both sides can point to what will be returned.

Scope is confirmed by inquiry. There is no public price and no binding quote on this site. The material and requested handoff determine what needs to be discussed before an engagement is accepted.

04

Keep open points visible

A handoff should not disguise uncertainty as a finished decision. Where the supplied material leaves a question open, the note identifies it. You keep the authority to decide what happens next in your project.

Additional work is a new scope discussion, not an invisible extension of the first request. This keeps a contained task from becoming an obligation neither side has actually agreed.

Choose by output

Different needs. A stated finish.

The route follows the job, not the other way round. If you need judgement before action, begin with a consultation. If the action is already clear, a one-off task may be enough. Support is for a piece that sits within work already under way.

Focused consultation

For a question you can describe but cannot yet resolve. The useful outcome is a written next step, not a bigger pile of possibilities. This route leaves the choice with you while giving it a clearer basis.

Read about consultation

Judgement firstA bounded conversation and written next step. Scope confirmed by inquiry.

One-off task

For a piece whose finish can be described. Supplied working material becomes the basis of the task, rather than a reason to reopen every earlier project decision. The agreement is about that piece, not indefinite availability.

Read about one-off tasks

A defined deliverableOne bounded piece of work. Scope confirmed by inquiry.

Project support

For an agreed edge of a live project. Support should fit around the existing owner rather than confuse who is responsible. The handoff identifies what the studio has addressed and what still belongs to the wider project.

Read about project support

Limited responsibilityHelp around a live brief. Scope confirmed by inquiry.

A useful limit

We do not turn a small task into a programme.

A contained request does not need a presentation about everything it could become. It needs an honest assessment of the work in front of it. If the next useful step is simply to clarify one instruction, that is where the discussion should stay.

The studio declines open-ended ownership disguised as a small task. A request to manage every dependency or accept new work without a revised boundary does not fit this service. Nor does a promise to produce a business result that depends on decisions outside the agreed deliverable.

We also do not invent a deadline or a fixed quote before understanding the material. A desired date helps frame the inquiry; it does not become an accepted delivery date just because it appears in a message. Read the terms of use for the distinction between an inquiry and agreed work.

You can bring an uncertain brief. That is different from expecting an unlimited engagement. Tell us which part is unclear, and the inquiry can begin there.

Start an inquiry

Contact the operator

A question goes to the studio.

Use the contact details here for a service inquiry or a question about the site. These are also the operator's contact details for personal data requests.

Inquiries are reviewed and answered through the contact route you supply. There are no published service hours or guaranteed response times for project inquiries, and chat is not a promise of an immediate live answer. If timing matters, include the date you are working towards in your message.

A data request is answered within 7 days. The data request page explains how to ask for access, correction or deletion without sending unnecessary identity documents. For a barrier using this site, use the same email and describe the affected page; the accessibility information gives more detail.

You do not need an account to make contact. No payment or card details are taken on this site. An inquiry starts a scope discussion, not a purchase.

Before sending material

Start with the question and a short account of what you have. Keep passwords and unrelated personal records out of your message. The privacy statement explains inquiry handling and retention, while cookies and consent describes your storage choices.

Start an inquiry