Web work
Web projects
Information architecture, website content architecture, copy structure, and responsive website implementation treated as one deliverable. Useful for a new public site or a difficult set of existing pages.
Open web projectsAustin, Texas / digital studio
Web work that leaves the working parts intact.
We take on web projects, automation, and one-off consultations. We shape the pages people need to find, connect the repeatable operation, and repair an existing website before anyone talks about a rebuild.
Directory / start here
Based in Austin, Texas.
Working with small organisations in the United States.
The index
Choose the work in front of you.
We use this page as a map, not a funnel. Choose the room when the problem has a name.
Automation
Workflow automation
Small business workflow automation that names the trigger, the data boundary, and the failure path before an API connection is made. Good for a repeatable task that is still being copied by hand.
Open automationConsultation
One-off consultation
A website audit consultation or focused technical review with supplied material, a bounded session, and written decisions afterwards. It ends with a next step, not a retainer invitation.
Open consultationSupport
Existing-project support
Website repair and support for a working project with a narrow issue, accessible code or CMS, and a need for a clean handoff. The first question is what already works.
Open supportProcess
How the work moves
The process from inquiry to scope, review, acceptance, and documentation. Read it before sending a long brief if the boundary of the request is unclear.
Read the processContact
Contact and specification
Send the object being changed, the access you have, the point where it fails, and the outcome you can inspect. A short note is enough to start.
Start an inquiryAnnotated plate
A structure you can hand to someone else.
A responsive website is not finished because the first viewport looks tidy. The content order has to survive a phone, a keyboard, a CMS edit, and the person who inherits it next month.
01Structure before decoration. Start with the pages people cannot find.
02Failure is visible. An automation is worth keeping only when its failure can be found.
03Handoff is part of the work. We write it while the decision is still fresh.
Working notes
The useful sequence is usually shorter.
We keep the sequence clear so a small project does not turn into a vague transformation story.
Keep what works.
We begin with the current site, workflow, or code. A working form is evidence. A familiar content model may be worth more than a fresh visual system.
Make the brief testable.
Pages, fields, systems, content state, and access become visible inputs. If a result cannot be checked in a browser or a log, it is not a useful acceptance point.
Automate the repeat.
Small integrations get a trigger, a limit, and an exception path. We do not attach an API to a process nobody has described.
Leave a usable handoff.
The final note names what changed, where it lives, and what to inspect when it behaves badly. That is the part that protects a working project from becoming mysterious.
Planning range / USD
Put rough inputs against the work.
This per-unit estimator gives an indicative planning band. It is not a quote. The final range depends on the actual content, access, systems, and limits we agree after an inquiry.
A range is honest until the inputs are clear.
The next useful action
Start an inquiry with the object in view.
Tell us what needs changing, what already works, and where the failure shows up. We review the request before discussing scope or a price basis.