Terms of Use

01Who these terms are between

Devdwell is a web design and development studio. We design, build and optimise Webflow websites for growing brands, and we have been doing it since 2022. We are a 100% remote team, there is no office to visit and no phone line to call, and info@devdwell.com is the channel we answer.

These terms cover two things: using this website, and engaging us for work. “We” and “us” means Devdwell. “You” means the person or the business we are quoting for or working with.

Where a signed proposal, statement of work or order form says something different from this page, that document wins for that project. This page is the default, not an override.

Still to be completed. The legal entity behind Devdwell, its registered address and any company or tax registration number belong in this section. This draft does not invent them.

02What we do, and what we do not

We design and build Webflow websites, migrate sites onto Webflow, do technical SEO work, optimise performance, build interactions, and support and maintain sites after launch. What is included in your project is whatever your proposal lists: not everything on this list, and nothing that is not on yours.

Some things we are explicit about not doing:

• We do not guarantee search rankings, traffic, revenue or any other commercial outcome. Anyone who guarantees a ranking is guessing with your money.
• We do not give legal, tax or financial advice, and nothing we produce should be relied on as any of the three. That includes any policy page we build for you.
• We do not warrant that a third-party platform will keep behaving the way it behaved on the day we built against it.
• We do not take responsibility for content you publish after handover, or for changes made to the site by anyone other than us.

03Quotes, packages and payment

Flat, transparent packages starting at $2,000. You get the figure before work starts, so there is a budget you can plan around rather than an hourly estimate that drifts.

How a quote works

• Packages are flat and start at $2,000. The figure is fixed in writing before any work begins, and it does not drift because something took longer than we thought.
• A quote covers the scope it describes and nothing else. Anything added later is a change request, quoted separately, and you decide whether to take it.
• Quotes are valid for 30 days unless the document says otherwise. After that we may re-quote, usually because a third-party cost has moved.
• Prices exclude any sales tax, VAT or equivalent that applies where you are. If a tax applies, it is added to the invoice.
• Third-party costs (Webflow plans, domains, fonts, stock imagery, paid integrations) are yours, and they are itemised rather than buried.

Paying

The payment schedule for your project is set out in your proposal. As a rule that means a deposit before work begins and the balance before the site goes live, with longer engagements split across agreed milestones. Retainers are billed on the cycle the agreement states.

Invoices are due within the period printed on them. If an invoice goes unpaid past that date we may pause work and hold handover until it is settled. We will tell you before we do, not afterwards.

To be confirmed before publishing. The deposit percentage, the milestone split, the invoice payment window, any late-payment interest or fee, and the currency and payment methods accepted. Those are commercial decisions, and this draft does not make them for you.

04Scope, and what happens when it changes

The proposal describes the scope: the pages, the templates, the CMS collections, the integrations, the number of revision rounds and what launch includes. That document is the definition of “done”.

Projects change, and that is normal. When something is asked for that is not in the scope (an extra template, a new integration, a second language, a rebuild of a section already approved) we say so at the time, price it, and wait for a yes. Nothing extra is ever done quietly and invoiced later.

Timelines

Most projects run four to eight weeks end to end, across discovery, design, build, QA and launch. Timelines hold because the sequence is the same every time. A timeline assumes content, feedback and access arrive when they are due. If they do not, the schedule moves, and we will tell you by how much rather than absorbing it silently and shipping something rushed.

05Revisions

Every project includes a stated number of revision rounds at each stage, design and build, and the number is written in your proposal.

A revision is a refinement inside the direction already agreed. That includes:

• Copy, spacing, sizing, colour and imagery changes within the approved design.
• Layout adjustments to a section that already exists.
• Fixing anything that does not match what was agreed. That is not a revision at all; it is us finishing the job, and it is never counted against your rounds.

A new direction is not a revision. That includes:

• Replacing an approved design with a different concept.
• Adding pages, templates, collections or integrations that were not in scope.
• Reopening something that was signed off in a previous stage.

Those are change requests: named, priced and agreed before they start. Feedback given in one consolidated pass per round is what keeps the included rounds sufficient for almost every project.

06What we need from you

Half of every timeline belongs to the client. None of the following is a disclaimer. It is the list of things that decide whether a project lands on the date in the proposal.

Content and assets

Copy, imagery, logos, brand guidelines and product information, either supplied by you or commissioned separately as part of the project.

Access

The accounts the build touches: Webflow, the domain and its DNS, analytics, Search Console, and any platform being migrated from. We ask for the least access that will do the job and give it back at handover.

One decision-maker

A named person who can approve work. Feedback from four people that disagrees with itself is the single most common cause of a timeline moving.

Feedback in one pass

Consolidated rather than trickled, inside the window the proposal sets. A round of revisions is a round, not a conversation with no end.

The right to use what you give us

You confirm that you own, or are licensed to use, the content and assets you hand over, and that publishing them breaks no law and no third party’s rights.

If a project stalls on our side, we absorb it. If it stalls on yours for a long stretch, the rule of thumb is 30 days with no response, we may close the file, invoice for the work completed, and re-quote when you are ready to start again.

07Intellectual property and handover

The short version: you own what was made for you, we keep what we brought with us, and anything licensed from somebody else stays licensed from somebody else.

Yours, on full payment

The finished website as delivered, the page designs made for you, the copy and imagery you supplied, and the CMS structure and content behind it.

Ours, licensed to you

The components, utilities, snippets, patterns and know-how we brought with us and reused on your build. You get a perpetual, unrestricted licence to keep using them as part of your site. We keep the right to use them again.

Nobody’s, and licensed to both of us

Fonts, stock photography, icons, templates and third-party integrations. These come with their own licences and their own renewal dates, and they stay subject to whatever the licensor says rather than to anything in this document.

Until the invoice is paid

Ownership of the deliverables transfers on receipt of full payment. Before that, the work is ours and no licence to use it has been granted, which matters mostly in the rare case where a project ends badly, and it is fairer than any alternative to both of us.

What handover actually is

• The Webflow project is transferred into your own workspace, so the site is yours and does not sit inside our account.
• You get hands-on, one-to-one CMS training so your team can update the site without calling a developer.
• Any credentials you gave us are handed back, and we ask to be removed from your accounts rather than keeping standing access.
• Design source files are provided where the project included design.

08Platforms, subscriptions and third parties

A Webflow site is built on somebody else’s platform, and that has consequences worth stating plainly.

• Webflow plans, domains, and any paid integration are contracts between you and that provider, on their terms and at their prices. Those prices change and we do not control them.
• If we hold a subscription on your behalf during a build, it transfers to you at handover. Standing subscriptions in our name are not a thing we do.
• We are not responsible for a third party’s downtime, a pricing change, a discontinued feature or an API that changes shape. Where a change breaks something we built, we will quote to fix it, and on a support retainer that work is usually already covered.
• Your use of those platforms is governed by their own terms and privacy policies, not by this page.

09Showing the work

Unless you tell us not to, we may show the finished site in our portfolio and case studies: your name, screenshots, a description of what we did, and results that are either already public or that you have agreed we can publish.

Say the word and we stop, before, during or years after. Tell us at any point and the work comes off the site at the next update. Anything you mark as confidential never appears in the first place.

10Confidentiality

Both directions. Anything non-public that either of us learns about the other during a project (figures, plans, credentials, unreleased products, pricing) stays private and is used only for the work in front of us.

That does not apply to information that:

• Was already public, or becomes public without either of us breaking this clause.
• Either of us already knew, or works out independently.
• Has to be disclosed by law, in which case we tell you first, if we are allowed to.

We are happy to sign your own non-disclosure agreement, and we will read it rather than waving it through.

11Warranties, and what we do not warrant

We warrant that the work will be carried out with reasonable skill and care by people who know what they are doing, and that what we deliver will materially match what your proposal describes.

Defects in what we built, something that does not work the way it was agreed to work, are fixed at no charge during the defect period stated in your proposal. That is 30 days from launch unless your document says otherwise. A change of mind after launch is not a defect; it is a change request, and it is quoted like one.

We do not warrant, and it would be dishonest to:

• That the site will be uninterrupted or entirely error-free. No system is, and anyone who claims otherwise is selling something.
• Any particular search ranking, traffic level, conversion rate or revenue figure.
• Behaviour in browsers, devices or assistive technologies outside the support matrix agreed for the project.
• The performance, availability or continued existence of any third-party platform, plugin or integration.
• That content you or anyone else publishes after handover meets any legal or accessibility requirement.

To the extent the law allows, everything else that would otherwise be implied (by statute, by custom or otherwise) is excluded. Where the law where you are does not allow that exclusion, it does not apply to you.

12Limitation of liability

Neither of us is liable to the other for indirect or consequential loss: lost profits, lost revenue, lost business, lost data, or loss of goodwill, however it arises.

Our total liability for any claim connected with a project is capped at the fees you have actually paid us for the engagement that the claim relates to.

Nothing in these terms limits or excludes liability that cannot lawfully be limited or excluded, including death or personal injury caused by negligence, and fraud or fraudulent misrepresentation.

To be confirmed before publishing. Whether a fees-paid cap is appropriate for the size of the projects you take on, whether it should be time-limited or per-claim, and whether professional indemnity insurance sits behind it. A cap a court will not enforce is worse than no cap, and this is exactly the clause to have a lawyer look at first.

13Ending the engagement

Either of us can end a project by writing to the other. No ceremony is required and no reason has to be given.

• If you end it, you pay for the work completed up to that point, plus any third-party cost already committed on your behalf. Anything you have paid for beyond that is refunded.
• If we end it for any reason other than your breach of these terms, we refund the unearned portion of what you have paid and hand over the work completed to date.
• Non-payment lets us suspend work and withhold handover until the account is settled, and continued non-payment lets us end the engagement.
• What survives: confidentiality, the ownership and licence positions for work already paid for, the limits on liability, and anything else that by its nature is meant to outlast the project.

Support retainers run month to month unless the agreement says otherwise, and either side can stop one with 30 days’ notice. We do not lock anybody into an annual commitment to make a monthly number look better.

14Governing law and disputes

These terms, and any dispute arising out of them, are governed by the law of[jurisdiction to be completed], and the courts of[jurisdiction to be completed] have exclusive jurisdiction.

Before anything formal, both of us agree to try to sort it out by talking, a call, in good faith, within 14 days of one of us raising it in writing. Most disagreements about web projects are about expectations rather than about law, and they are cheaper to fix that way.

Still to be completed. The governing law and the forum for disputes depend on where the entity behind Devdwell is established and where its clients are. This draft deliberately leaves both blank. Fill them in with advice, and check whether any client you sell to is a consumer rather than a business, because consumer protection rules can override a choice of law entirely.

15Changes to these terms

We update this page when the way we work changes. The date at the top is the date of the current version, and it is the fastest way to tell whether anything has moved since you last read it.

The version that governs a project is the one in force on the day your proposal was accepted. We do not change the rules of an engagement that is already running by editing a web page.

16Getting in touch

One address covers all of it, questions about these terms, a proposal you want explained line by line, an invoice query, or a disagreement you would rather resolve before it becomes one:

info@devdwell.com

A reply within one business day, from a person. If you are starting from scratch, thecontact page has the form and everything that goes with it.

Back to the top of these terms ↑