Who you'd be
working with.

I've helped build software that met its launch deadline and then struggled when more people began using it. That changed the questions I ask before a build: what happens at ten times today's usage, which changes will the owner need to make, and who will maintain it?

For Mendivil Coffee, the first release focused on selling one product. The next put publishing, pricing, archiving, and restoring coffees in the owners' hands. They could start selling before the full catalog was ready, then take over the routine work without needing me for every change.

The same judgment applies to the tools I recommend. If a better form or a clear set of rules solves the problem, I will recommend that before an AI integration.

The person you talk to is the person writing the code. You see the work as it takes shape, so we can check it against the way your business actually works.

I work with clients alongside a full-time role, with ten to fifteen hours a week for client work. If your launch date cannot move, tell me at the start. I will assess whether the scope fits that date before committing to the build. Routine changes ship every couple of weeks.

For existing clients, a site outage, broken checkout, or data at risk gets a response within four hours, any day, with work starting immediately.