MarketPulse build guide
Ecommerce Development Agency Near Me
How an ecommerce development agency runs a store build from the inside: who is on the team, what you sign off at each phase, what the statement of work must say and who owns the store at the end.
Every phase ends with something you approve in writing.
Hiring an ecommerce development agency near me means handing a team of several people the job of building your store, and the way they run that build decides how much of your time, money and nerves it costs. Good agencies follow a visible process: named roles, phases that end with your written approval, a staging site where you test before anything goes live, and a clear rule for pricing changes.
This page walks through that process so you know what to expect and what to ask for. It assumes you have already chosen a team over one freelancer; if you have not, read agency vs freelancer first. For judging the agency before you sign, the agency red flags guide lists the warning signs.
Who works on your store inside the agency?
A small agency build involves four to seven roles. In a ten-person studio one person can hold two of them; what matters is that each role is filled and you know who holds it.
| Role | What they do on your project | How much you deal with them |
|---|---|---|
| Project manager | Plans the phases, runs meetings, tracks budget and changes, answers your questions or finds who can | Weekly or more; your main contact |
| Designer | Wireframes (simple page layouts without styling), visual design, mobile layouts | During the design phase |
| Front-end developer | Builds the theme: what customers see and click | Through the project manager, sometimes in demos |
| Back-end developer | Apps, custom features, connections to your till, stock or accounting system | Rarely, unless a connection needs your input |
| Tester | Checks every feature against the agreed criteria on several devices before you see it | Rarely; you see their bug list |
| Data or migration specialist | Imports products, customers and orders; builds the redirect list on a platform move | When your data is involved |
| Account manager or director | Commercial side: contract, invoices, escalation | At the start, the end and when something goes wrong |
Ask for the names behind each role in the proposal. If the answer for “tester” is “the developers test their own work”, you will be doing the testing yourself.
What are the phases of a build, and what do you sign off at each?
Agencies name their phases differently, but most builds follow this shape. The column that matters is the last one: each phase ends with something you approve in writing, and work on the next phase starts only after that approval.
| Phase | What happens | You sign off |
|---|---|---|
| 1. Discovery | Workshops, review of your current store and data, technical checks on apps and connections | The statement of work and the project plan |
| 2. Design | Wireframes, then visual designs for the main page types: home, category, product, cart, checkout parts that can be styled | Designs for each page type, desktop and mobile |
| 3. Build | Theme development, app set-up, custom features, connections | Each feature demo on staging |
| 4. Content and data | Product import, page content, images, redirects | A sample of 20 products checked by you, then the full import |
| 5. Testing | Agency tests first, then you test (user acceptance testing: you check it does what your business needs) | The test list with every item passed or deferred |
| 6. Launch | Go-live on an agreed day and time, with the agency on standby | The go-live decision |
| 7. Aftercare | Bug fixing period after launch | The end of the warranty period |
Signing off quickly keeps the project on schedule; signing off without checking moves the cost of any mistake onto you, because later changes become paid change requests. Block time in your diary for each sign-off when you agree the plan. What to check once the store is live is in the after-launch checklist.
What belongs in the statement of work?
The statement of work (SOW) is the document that defines the project: what will be built, by when and for how much. Everything not in it is a change. A solid SOW for a small store build contains:
- Goals in one paragraph, so everyone can judge later decisions against them
- Scope: page types, features, apps to set up, connections, number of products to import
- Exclusions: written out, such as copywriting, photography, paid ads set-up, extra languages
- Acceptance criteria for each feature
- Phases with dates and the sign-off at each
- Your responsibilities: content by a date, feedback within a set number of working days, access to accounts
- Price and payment schedule tied to phases
- Change process and the rate for extra work
- Ownership of code, designs and accounts
- Warranty: how long bugs are fixed for free after launch, and what counts as a bug
A well-written acceptance criterion reads like a test anyone can run:
“Store pickup: at checkout, customers whose postcode is within the delivery list see ‘Collect from the shop’ as an option. Choosing it removes the delivery fee and asks for a collection day from the next three opening days.”
If you are comparing SOWs from two or three agencies, line them up with how to compare ecommerce service quotes.
Who owns the code, the store and the accounts?
Put this in writing before work starts: the store, the domain, hosting, payment accounts and analytics belong to you, and the agency works in them through its own named logins. Custom code and designs pass to you on final payment, apart from the agency’s reusable tools, which they license to you.
On Shopify
Shopify partners can build in a client transfer store. Shopify’s developer documentation on client transfer stores explains that the partner owns and configures the store during the build and then transfers ownership to the client when it is ready to go live, after which the merchant takes full ownership. Three details from that page are worth knowing:
- The partner keeps collaborator access by default after the transfer, so ask for it to be removed or limited once the warranty ends.
- The client picks the Shopify plan when accepting the transfer.
- A store with active Shopify financial products, such as Shopify Payments, cannot be transferred; the partner deactivates them first, so agree who sets up payments after the handover.
The same documentation notes that development stores used for testing apps cannot be transferred to clients. If an agency says your store “lives in our partner account”, ask which of the two kinds it is and when the transfer happens.
On WooCommerce
The hosting account and domain should be in your name and paid by you. The agency gets its own WordPress user. Per the WordPress roles documentation, the Administrator role has access to all administration features of a single site, so agree which agency users hold it and that they are downgraded or removed after aftercare. Ask for the code in a repository (a version-controlled store of the code) you own or can export.
How do staging and testing work?
A staging site is a private copy of your store where the agency builds and you test, without customers seeing anything half-finished. Every feature should reach you on staging first. No staging site means testing on the live store, which means your customers find the bugs.
Testing runs in two rounds:
- Agency testing. The tester checks each feature against the acceptance criteria on desktop and mobile and logs bugs.
- Your testing (user acceptance testing). You and a member of staff run through real tasks: find a product, buy it, choose pickup, apply a discount code, request a refund.
Agree how bugs are graded before testing starts, so arguments about urgency do not slow the launch:
| Grade | Meaning | Example | Must be fixed |
|---|---|---|---|
| Blocker | Stops sales or loses data | Checkout fails on one payment method | Before launch |
| Major | A feature does not work as agreed | Pickup option missing for some postcodes | Before launch, unless you agree otherwise in writing |
| Minor | Works, but looks or reads wrong | Button text wraps on small phones | Within the warranty period |
| Change | Works as agreed, but you want it different | A new colour for the sale badge | Priced as a change request |
The last row is where most disputes start. The acceptance criteria decide which row a problem belongs in, which is why they belong in the SOW.
How are changes priced once the build starts?
Every build gets change requests. A good agency has a short written process for them:
- You describe the change in writing.
- The agency replies with the estimate in hours, the cost and any effect on the launch date.
- You approve or decline in writing.
- Approved changes go on a change log that both sides can see.
Example (invented figures to show the arithmetic): a build quoted at $12,000. Midway, you ask for a gift message field at checkout (estimate 4 hours) and a second product page layout for furniture (estimate 10 hours). At an agreed change rate of $90 an hour: 14 hours x $90 = $1,260, so the project total becomes $13,260, an increase of 10.5%.
Two habits keep this under control. First, set aside a change budget when you agree the price; MarketPulse suggests planning with 10 to 15% of the build cost as a rule of thumb, not a market figure. Second, ask the agency to bundle small changes and review the change log every two weeks, instead of approving each one in passing.
If the agency charges for changes without a written estimate and your approval, that is a breach of the process you agreed, and it belongs on the list of agency red flags.
What meeting rhythm should you expect?
Meetings should be short and regular, and the important things should be in writing. A typical rhythm for a 10 to 14 week small store build:
| What | Frequency | Length | Who |
|---|---|---|---|
| Kick-off workshop | Once | Half a day | You, project manager, designer, lead developer |
| Status call | Weekly | 30 minutes | You and the project manager |
| Written status update | Weekly | One page | From the project manager |
| Demo on staging | Every two weeks during build | 45 minutes | You, project manager, a developer |
| Sign-off meeting | End of each phase | 30 to 60 minutes | You and the project manager |
| Launch call | Launch day | As needed | Everyone on standby |
The weekly written update should answer four things: what was done, what is next, what the agency is waiting for from you, and how the budget and change log stand. If you have to ask for that information, the process is weaker than the proposal suggested.
Does it help if the agency is nearby?
For the build itself, a remote agency works as well as a local one: staging sites, demos and calls all travel. Being close helps in specific moments:
- The discovery workshop, where seeing your shop, stockroom and till makes the scope more accurate.
- Point-of-sale set-up, when hardware and the online stock count have to be connected in your building.
- Product photography, if the agency arranges it.
- Staff training on the new order process before launch.
If you pick a distant agency, ask them to price one site visit for discovery and one for launch week. That keeps most of the benefit of a local team without limiting your shortlist to your town.
FAQ
How long does an agency take to build a small ecommerce store?
It depends on scope, the agency’s schedule and how fast you sign off. Ask each agency for a dated plan by phase, and add your own sign-off time to it. Slow sign-offs are the one source of delay fully in your control.
Should I pay the agency upfront?
Tie payments to phases: a deposit on signing, then payments when design, build and launch are signed off, with a final payment after the warranty period starts. Paying everything upfront leaves you nothing to hold back if the work slips.
Can I bring my own developer or designer into an agency project?
Many agencies accept that if it is agreed in the SOW, with clear lines on who owns which part and who fixes bugs in each. Expect the agency to exclude warranty cover for code they did not write.
What is user acceptance testing?
It is the round of testing done by you, the client, after the agency has tested. You check that the store does what your business needs, using real tasks such as placing an order or choosing pickup. Passing it is the last sign-off before the go-live decision.
What should happen if the agency misses a deadline?
The SOW should say how delays are handled: a revised plan in writing, and no extra cost when the delay is on the agency’s side. If the delay comes from late content or feedback from you, the plan moves too, which is fair.
Who should hold the domain during the build?
You. Keep the domain registered in your own account from day one and give the agency access to the DNS settings only when they need it for launch.
Does the agency keep access after launch?
Only for the aftercare period you agreed. On Shopify, a partner who used a client transfer store keeps collaborator access by default, so ask for it to be removed or limited once the warranty ends.
What should you do next?
Before signing with any agency, ask for three things: the names behind each role, a sample statement of work from a previous project, and their change request process in writing. Check that the SOW names you as the owner of the store, the domain and the code, and block your sign-off dates in the diary.
If you want help reading an agency’s proposal or SOW before you commit, send a short description through the MarketPulse contact form.
Around the agency build
Guides for the steps before the contract and after the launch.