Business English for Working with a Shopify Agency
If English isn’t your first language and you’re about to hire a Shopify agency, whether you’re a non-native-English-speaking founder based in the US, a brand manager in Europe working with a UK agency, or an operator running a global brand and partnering with US developers, the business-English vocabulary of ecommerce development can be intimidating. Agencies use specific jargon that doesn’t appear in general business English courses. Miscommunication in this vocabulary has real consequences: wrong features get built, scope creeps, timelines slip. This guide decodes the most common terms, phrases, and communication patterns you’ll encounter when working with a Shopify agency.
The vocabulary you’ll hear on the first call
“Discovery phase”
A paid preliminary engagement (usually 2-4 weeks, $10-30k) where the agency scopes the work in detail before committing to the full build. Don’t skip this, the discovery phase is where scope misunderstandings get fixed cheaply.
“Statement of work” (SOW)
The contract document that defines scope, deliverables, timeline, and payment schedule. Read it carefully. Ask for changes in writing, not in meetings.
“Scope creep”
When the project expands beyond the original agreement without formal scope change. Often happens in small increments, a feature here, a request there, and then suddenly the project is 40% bigger. Healthy agencies flag this early. Less healthy ones quietly let it grow and invoice for it later.
“Change order”
Formal documentation of a scope change. When you ask for a new feature mid-project, a good agency responds with a change order that quantifies the cost and timeline impact before doing the work.
“Ticket” / “Issue”
A specific unit of work tracked in project management software (Jira, Linear, ClickUp, Asana). Most agencies organize work as tickets/issues rather than loose email requests.
“Sprint”
A fixed-duration work cycle (usually 1-2 weeks). At the start of each sprint, the team commits to a list of tickets. At the end, they review what shipped and what slipped.
“Backlog”
The list of all identified work that hasn’t been scheduled into a sprint yet. Your backlog will grow as you think of new things. Not everything in the backlog will get built, some items get deprioritized or killed.
“Retrospective” (or “retro”)
A team meeting after a project milestone to discuss what went well, what didn’t, and what to change. Good agencies run retros. Less mature ones skip them.
“Theme” vs. “Custom theme” vs. “Headless”
- Theme: A pre-built template for your Shopify store. Fast to set up, limited customization.
- Custom theme: Built from scratch (or heavily customized from a base like Dawn or Impulse). Slower to build, much more flexible.
- Headless: Frontend built as a separate application (typically on Hydrogen or Next.js) that consumes Shopify data through APIs. Most complex, most powerful, most expensive.
Phrases that mean more than they sound like
“Let’s circle back on that”
Agency-speak for “I don’t want to answer that right now.” It might mean the answer is complicated, or that they don’t know, or that they need to check with the team. Don’t let circle-backs pile up, if an issue hasn’t come back within a week, ask again.
“That’s a great question”
Often filler used when the answer is complicated or awkward. Not rude, just a language tic. Don’t over-interpret it.
“It’s on the roadmap”
Means “we plan to work on it later.” Ask for a specific timeline. “On the roadmap” can mean “next sprint” or “maybe in six months”, they sound identical.
“Let’s take that offline”
Means “this isn’t a productive group-meeting topic, let’s discuss it separately.” Usually legitimate. Occasionally used to defer awkward conversations indefinitely.
“We can look into that”
Non-commitment. If you need a yes/no answer, follow up with “would you be able to give me a yes or no by Friday?”
“We’ll do our best”
Means “we don’t fully control this timeline.” Follow up with “what would have to go right for this to ship on time, and what’s most likely to go wrong?”
How agencies actually communicate (written vs. verbal)
Most US and UK Shopify agencies default to asynchronous written communication, Slack, email, project-management tool comments. Meetings are reserved for specific needs: design reviews, sprint planning, retros, escalations.
If English writing isn’t your strength, this can feel harder than verbal communication, because you can’t rely on body language or tone. Three tips:
- Over-communicate in writing. If you’re not sure you were understood, restate your point in different words. “So to confirm: we want X, not Y. Is that your understanding too?”
- Use bullet points. Complex requests in paragraph form are harder to parse. Bullets force clarity.
- Ask for written confirmation of verbal decisions. After any call where decisions were made, send a written summary. “Per our call today, we agreed to [X]. If I misheard anything, please correct me by tomorrow.”
Good Shopify agencies are used to international clients and will accommodate communication-style preferences if you ask. Some will default to more calls if you prefer verbal. Others will send detailed written summaries as standard practice. It’s worth asking upfront.
What to say in common situations
Asking for clarification without seeming lost
“I want to make sure I’m tracking with you on this. Could you walk me through how [X] will work in the finished product?”
This is better than “I don’t understand”, it shifts the burden to the agency to explain, without making it feel like a knowledge-gap.
Pushing back on a recommendation
“Help me understand the tradeoff here. Why this approach instead of [alternative]?”
Agencies respect pushback that’s framed as curiosity rather than resistance.
Raising a concern about progress
“Looking at where we are vs. the original timeline, I want to understand what’s driving the pace. Are we on track? What would have to change to pull things forward?”
Direct but not accusatory. Invites the agency to explain and propose adjustments.
Asking for a change in scope
“I know this is outside the original SOW. Can you send a change order with the cost and timeline impact? I want to make an informed call before we commit.”
Signals that you understand the professional process, which the agency will appreciate.
Declining a recommendation
“I hear you on why you’d recommend [X]. For [business reason], we want to go with [Y] instead, even knowing the tradeoffs.”
Acknowledges their expertise, explains your decision, moves forward.
Cultural notes for non-US founders working with US agencies
- Directness varies. US agencies tend to be direct in feedback, which can feel blunt to founders from more indirect cultures. It’s not usually disrespectful; it’s operational.
- Punctuality matters. US business culture takes start times seriously. Joining a call 5 minutes late is noticed.
- Email response time. Business-hours same-day for important emails; next-day for non-urgent. If you send Friday at 5pm, expect Monday response.
- Holidays differ. US agencies take off Thanksgiving (late November) and Christmas through New Year. UK agencies take longer summer holidays and different bank-holiday patterns. Ask about their calendar upfront.
Red-flag language from agencies
Watch for these phrases, they often signal trouble:
- “Trust us on this one”, Usually means they don’t want to explain or justify.
- “That’s just how it is”, Evasion of a real discussion about tradeoffs.
- “We always do it this way”, Process rigidity that may not fit your project.
- “We’ll figure it out”, No plan. Pay for a discovery phase instead.
- “Let’s start building and see where we land”, Recipe for scope creep.
Final note
The language of working with a Shopify agency is learnable. Most of the confusing vocabulary is just specific terminology, not fundamentally difficult concepts. Full-service Shopify agencies worth working with, like Netalico and others that regularly partner with international brands, explain themselves clearly and are patient with clarifying questions. The ones that make you feel bad for asking are usually not the right fit regardless of the language gap.
