Map, build, launch.

Before work starts you get it in writing: what is being built, what it connects to, what it does not cover, and a firm price. Anything outside that is explained and priced before it happens — you will not discover extra work for the first time on an invoice. The published ranges (Shopify fixes at $250–$750, for example) exist so you know the likely size before we ever speak.

You do, from day one. The code lives in your account, and the Shopify admin stays in your name with us added as a helper. Accounts with other companies — phone numbers, messaging, calendars — are set up under your billing wherever they allow it, so cancelling us does not cancel your phone number.

Automation plans cancel any month; logins are handed back within 24 hours and there is no exit call to sit through. Project work ends when the agreed list is done. Notes are written for whoever comes next, so the system never depends on the person who built it.

Mountain time, Monday to Friday, with a first reply inside four working hours. Live systems are watched outside those hours and raise an alert on their own; people are not on call overnight.

Work is done in a copy you can look at, not typed straight into the live site. A change is checked automatically before it lands, and a failed check puts the old version back rather than leaving a half-changed site in front of customers. The check looks at the page a visitor sees, because a page can be correct in the code and broken on the screen.

Anything we got wrong is covered for 30 days after a project goes live. After that, monthly support covers keeping an eye on it and fixing things; one-off problems are priced before they are fixed. If we broke it, fixing it is not billable.

We ask for the least access that does the job, and for access that expires where a platform allows it. Your customer data stays in your systems; we do not take copies of it, and anything we can see while working is covered by the same confidentiality you would expect of an employee.

Normal, and often better. Work arrives somewhere they can read it before it goes live, in the code they already have. If they would rather own the work, we plan it, build the first version and hand it over rather than competing for the relationship.