1
You tell us about the mess.
Complete the intake and show us what exists, what is missing, and what is keeping the catalog from moving forward. If we are not the right fit, we tell you.
your store is your livelihood
Clear scope. Limited access. No weird surprises.
Giving someone access to your Shopify store is a big deal. Before we request access—or touch a single product—you know exactly what we are doing, what we are not doing, and what protects both sides.
the whole process
From “here is my chaos” to a clean handoff.
No vague scope. No mystery access. No surprise line items appearing halfway through.
2
We define the exact job.
You receive a Statement of Work listing the deliverables, exclusions, timeline, price, payment schedule, revision allowance, and any store access required.
3
Both sides approve it in writing.
You review and sign the Client Service Agreement and your project-specific Statement of Work. Payment and access come only after the plan is clear.
4
We do the agreed work.
We clean, organize, write, structure, or prepare only what is listed in scope. We do not quietly expand the project or change unrelated parts of your store.
5
You review before it is final.
You receive the work for review and provide one consolidated set of feedback within the agreed window. Revisions follow the written scope.
6
We deliver and close access.
After final payment, you receive the completed handoff. You revoke our Shopify access, and we remove project-only materials according to the agreement.
the boundaries
What we may touch—and what stays completely off-limits.
Most projects do not require store access at all. When Upload + Publish or QA is included, every permission is listed and approved first.
Limited project access may include:
- Products and variants included in your scope
- Approved product files and images
- Collections included in the project
- Publishing only when Upload + Publish is selected
- Specific approved apps or content areas
We do not need access to:
- Your owner password or store ownership
- Billing, banking, payouts, or payment processors
- Customer passwords or payment information
- Orders, refunds, chargebacks, or fulfillment
- Unrelated themes, code, apps, domains, or settings
protection built into the workflow
Trust is documented—not assumed.
Your signed paperwork records the exact scope, access level, responsibilities, data rules, payment terms, ownership, cancellation rights, and exit process.
Read the Full Standard Agreement →ready when the mess is
You should never have to wonder what happens after you hand over the files.
Review the standard agreement now, ask every question you have, and start only when the scope and safeguards feel clear.