Stances

How I work, on the record.

Ten stated positions on how I engage with clients, tools, pricing, and responsibility. Not aspirations, and not marketing. These are the commitments I hold myself to, written down and published so you can hold me to them too.

Most of what goes wrong in a project goes wrong because an expectation was never said out loud. Someone assumed a rate, a scope, a level of access, or a standard of care, and nobody wrote it down until it had already turned into a disagreement. I would rather you know where I stand before we ever get on a call. If one of these positions is a dealbreaker for you, that is genuinely useful information: it means we found out now, cheaply, instead of three weeks into a project that was never going to work.

They are grouped three ways. How I bill and price answers the questions a procurement reader asks first: what it costs, why it is fixed, and what one rate for everyone actually means. What I will and won’t build is the craft floor, the things I hold to whether or not anyone is checking: accessibility from the start, careful judgement about every plugin that touches your site, and code I would be comfortable handing to a stranger. What I do beyond the build is the part of the work that lives on after a project ships, the rescue work, the teaching, and the mentoring. Read whichever group matters most for your decision.

None of this is meant to sound rigid. A stance is a starting position, not a wall, and most of them carry a clear sense of when I would make an exception. But the default matters. When you hire one senior person instead of an agency, what you are really buying is their judgement, and judgement you cannot predict is not worth much. Each of these shows up somewhere concrete in how I work, which is where they stop being words and become the rules the engagement actually runs on.