Key takeaways
- Get a written, fixed-price scope before any work starts. On a cross-border build, hourly billing is where budgets quietly double.
- Confirm who owns the repository and the domain on the day the final invoice is paid, not only at project sign-off.
- A workable scope-change clause puts a day rate or fixed fee for additions in writing before the first milestone is paid.
- The invoicing currency matters as much as the headline price. A studio that invoices in your currency removes an exchange-rate risk you never agreed to take.
- A studio that works in your time zone, even partly, answers questions the same day instead of a day and a half later.
What a Portfolio Doesn't Tell You When You Hire a Remote Web Studio
When you hire a remote web studio, check the contract before the portfolio. Six terms decide whether the project goes well:
- a written fixed-price scope
- a fair payment schedule
- ownership of the code and domain once the final invoice is paid
- a priced scope-change clause
- the invoicing currency
- real overlap with your working hours
Most studios that make your shortlist can make a site look good. Far fewer put the commercial terms in writing before the work starts.
We are Meant. We build bespoke website design and development in Next.js, headless Shopify storefronts and AI automation for founders who are mostly outside the UAE. So we see the hiring decision from the studio's side of the table, and we know which clauses cause the arguments later.
A portfolio shows taste and finish. It doesn't show what happens when you ask for a new page halfway through. It doesn't show whether you can move the site to another developer next year, or whether a question sent in the morning gets answered before you close the laptop. Those are the parts that go wrong with a remote web development agency, and none of them appear in a case study.
The rest of this article goes through each one and ends with a table you can hold against any proposal.
Payment Milestones: What a Fair Schedule Looks Like
A fixed price web project only protects you if the payments are tied to things you can see. The milestone schedule is how both sides keep each other honest. The studio isn't funding months of work on trust, and you aren't paying for work that doesn't exist yet.
At Meant, builds are quoted as a fixed price for a written scope, agreed after a scoping call. Projects start at $2,000. There is no hourly billing, and the price is in writing before anyone opens an editor.
Why a 100% upfront deposit is a warning sign
Paying everything upfront removes your only leverage. Once the money has moved, the studio has no commercial reason to prioritise your project over the next one. It also tells you how the studio thinks about risk: all of it sits with you.
The opposite extreme is a bad sign too. A studio that takes nothing until launch is either very cash-rich or about to cut corners to get paid. Neither helps you.
What a workable split looks like
A fair schedule ties each payment to a deliverable you can check without taking anyone's word for it:
- A deposit to start. This secures the slot and covers discovery and early design. It should be a clear minority of the total.
- A payment on design sign-off. You approve the designs in writing, and the build begins.
- A payment on a working staging site. You can click through it on your own phone before you pay.
- A final payment on launch and handover. This releases ownership, which the next section covers.
The exact proportions vary by project. The principle doesn't: every invoice should match something you have already seen working.
Who Owns the Code: IP and Repo Ownership
This is the clause founders skip, and it causes the most trouble later. Many people assume that paying for a site means owning it. In many places that isn't how copyright works.
Under UK law, a contractor owns the copyright in work they create by default. Payment alone does not transfer it, and a written assignment clause is needed to move the IP to the client. UK law also treats IP differently for employees and non-employees, so the rules that cover your own staff don't cover an outside studio. The "work for hire" idea common in US-style contracts does not automatically apply outside the US and has to be written into the contract.
When you work with a remote web development agency in another country, you may be dealing with two legal systems at once. Don't rely on defaults. Get the assignment in writing.
The repo handover moment
The clause you want says, in plain words, that on payment of the final invoice all rights in the code, designs and content pass to you. It should also list what is handed over:
- the Git repository, transferred to an account or organisation you control
- the domain, registered in your name at a registrar you can log in to
- hosting and deployment accounts, or full admin access to them
- the content management system, analytics and any third-party API keys
"On payment of the final invoice" is the important phrase. Sign-off on designs is not the trigger, and neither is launch. Agree the trigger before work starts so nobody argues about it at the end.
Domain work is part of many projects. The Grumpus rebrand (see the project) included moving the site from paulgrumpus.com to grumpus.io, alongside full-stack development, hosting and frontend management. A rebrand that touches the domain, DNS and hosting accounts shows why the contract should name who holds each of those accounts.
Why this matters if you ever switch agencies
Ownership disputes rarely appear at launch. They tend to surface after the client has already built on top of the work, once money has gone into branding and growth, and by then a developer may restrict access. For contractor-built digital assets, the IP usually belongs to the contractor unless there is a written assignment.
If a developer builds your site and disappears, owning the repository means that's an inconvenience you can fix by hiring someone else. If you don't own it, you may have to start again. For the technical side of this, see the eleven questions to ask a Next.js development agency.
Scope-Change Clauses: Pricing the Thing You Didn't Ask For Yet
Every project changes. You see the staging site and realise you need a booking form, a second language or a page you hadn't thought of. That is normal. What matters is whether the contract already says how those changes get priced.
A fixed price web project holds only as long as the scope holds. A good scope-change clause doesn't stop changes. It makes them visible and priced, so the fixed price stays fixed for everything that was agreed.
How a change request should be priced
Ask for a clause that works like this:
- You request the change in writing.
- The studio replies in writing with a fixed fee, or a day rate and an estimate, plus any effect on the timeline.
- Nothing is built until you approve that price.
- Approved changes are added to the next milestone invoice as a separate line.
The day rate or the method for setting fees should be written into the contract before the first milestone is paid. If you only find out the rate when you need the change, you have no room to negotiate.
The phrase that should never appear in a quote
"Additional work billed hourly as required." It looks harmless and it is open-ended. It doesn't say what counts as additional, what the hourly rate is, or who decides how many hours something took.
This is how a fixed-price project turns back into an hourly one. Ask for that line to be replaced with a named rate and a written-approval step.
Invoicing Currency and Cross-Border Payment Terms
This is the question most founders forget to ask a remote web development agency, and it changes the real cost of a fixed price web project. A quote in a foreign currency is only fixed in that currency. If your own currency weakens between the deposit and the final payment, you pay more for the same work. Nobody discussed it, and nobody will refund the difference.
Ask these questions before signing:
- Which currency is the quote in, and which currency are the invoices in? These are sometimes different. Get both in writing.
- Is the price fixed in that currency for the whole project? A quote that can be "adjusted for exchange rates" is not fixed.
- Who pays transfer and intermediary bank fees? On an international payment, fees can be taken at more than one point. Agree whether the studio receives the invoiced amount in full or absorbs the fees.
- Which payment methods are accepted? Bank transfer, card and payment platforms each come with different fees and settlement times.
- How is tax shown? Ask how tax is presented on the invoice, and check the treatment with your accountant.
None of this is exciting, and all of it lands on your bank statement. A studio that answers these questions plainly in the proposal is likely to be just as plain about everything else.
Time Zone Fit: How Fast Can You Actually Get an Answer
The time zone question isn't really about geography. It's about how long a decision waits. If your studio's working day ends as yours begins, every question has a full day of delay built in. A two-question exchange can take most of a week.
When you hire a remote web studio, check three things:
- The overlap. How many working hours a day do you and the studio share? A few overlapping hours are enough for same-day answers.
- Who answers. Is it the person building your project, or an account manager who relays messages to someone else?
- Where calls happen. Does the studio hold calls in your time zone, or in theirs?
A time zone web studio doesn't have to sit in your city. What matters is whether the hours overlap and whether the person who replies is the person actually writing your code. At Meant, you talk to the person doing the work, not a relay.
For the day-to-day detail, read how a remote project actually runs across time zones.
The Checklist Before You Sign
Hold any proposal against this table. If a row has no clear answer, ask for one in writing before you pay a deposit.
| Check | What to ask for | Red flag |
|---|---|---|
| Price | A fixed price for a written scope | Hourly billing or "estimate only" |
| Payments | Milestones tied to deliverables you can see | 100% upfront, or nothing until launch |
| Code ownership | IP assignment on payment of the final invoice | No ownership clause, or "licence to use" |
| Repo and domain | Repository, domain and hosting in your name | Domain registered to the studio |
| Scope changes | Written approval with a named fee or day rate | "Additional work billed hourly as required" |
| Currency | Invoice currency and fixed price stated in writing | Price "subject to exchange rates" |
| Bank fees | An agreement on who pays transfer fees | Not mentioned |
| Time zone | Stated overlap hours and who answers | Replies only through an account manager |
| Calls | Meetings held in your working hours | Calls only in the studio's day |
If you want to see how a studio answers each row before you commit, book a call with Meant and ask.
Frequently asked questions
What should be in a fixed-price web contract?
A written scope listing every page, feature and integration, plus the total price and the currency. It should include a milestone schedule tied to deliverables, a scope-change clause with a named rate, and an IP assignment that takes effect on payment of the final invoice. It should also list what is handed over: repository, domain, hosting and admin access.
How do remote web studios handle time zones across continents?
The good ones agree working-hour overlap at the start and hold calls in the client's time zone. Ask how many hours a day you will share and who answers your messages. A few overlapping hours are enough to get same-day replies on most questions.
Who owns the website code if the agency relationship ends?
That depends on the contract, not on the fact that you paid. Under UK law, for example, a contractor owns the copyright in their work unless a written assignment transfers it. Get an assignment clause that passes all rights to you on the final invoice, and keep the repository and domain in accounts you control.
What's a reasonable deposit for a web development project?
A deposit large enough to secure the studio's time and cover discovery, but a clear minority of the total. The remaining payments should follow deliverables you can check, such as signed-off designs and a working staging site. A 100% upfront payment removes your leverage and is a warning sign.
How do I check a remote studio's past work before hiring?
Look for case studies with named clients and live URLs you can visit yourself. Test the sites on your own phone for speed and usability. Then ask the commercial questions a portfolio can't answer: ownership, scope changes and payment terms.
Should a web studio invoice in my currency or theirs?
Your currency is better for you, because it removes exchange-rate risk between the deposit and the final payment. If the studio invoices in its own currency, budget for possible rate movement and agree in writing who pays the bank transfer fees.
If you're weighing up studios for a remote build, book a call with Meant. We'll put the scope, the milestones and the ownership terms in writing before anything starts.
