Free Marketing Agreement Template
A marketing agreement covers the workflow build scope, payment and change terms, ownership, portfolio use, limits of liability, and how the project ends.
Share template
Automation work can look tidy on a whiteboard, but the buyer is picturing the moment a workflow fires at the wrong time, consent gets missed, or sales handover breaks and nobody can explain why. The marketing agreement gives the HubSpot workflow build a written set of terms to sit alongside an accepted proposal, so the scope, boundaries, and sign-off points stay clear while the build is in motion.
The contract starts by anchoring the agreement to the accepted proposal, then spells out What you get in plain deliverables, including a lifecycle and data map, consent and lead-capture fixes, workflows, nurture emails, testing notes, and a handover pack. Payment and Changes cover staged invoicing, what counts as a revision round, and how extra work gets priced before it happens, and Limits calls out what can go wrong when lists, triggers, or settings get changed after handover. The pages sit under Raleway headings with Inter body text, with an olive lead colour and a stronger blue used where the call to action needs to stand out... and the structure keeps the client reading the scope and responsibilities before they reach the ending terms.
- Hubspot workflow build services agreement Ties the contract to the accepted proposal and explains what happens if the two documents conflict.
- What you get Lists the deliverables and boundaries, including what gets built inside HubSpot and what stays out of scope unless added in writing.
- Payment Defines the project fee basis, how staged invoices work, and when work pauses if payments go overdue.
- Limits Sets expectations around consent, deliverability, and responsibility when others change lists, triggers, or settings after handover.
- Ending the project Covers notice, what gets paid on termination, and what gets handed over in a usable state, with a signature at the end.
Once the terms, dates, and fees match the proposal, you send the agreement and the client signs online. The signed copy records what was included, what was excluded, and what gets handed over if the work ends early, so day-to-day running and “what’s live vs paused” don’t get left to memory.
We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.
What to include in a marketing agreement
| Part | What it covers |
|---|---|
Hubspot workflow build services agreement | Links the agreement to the accepted proposal and explains how conflicts between the two get handled before work starts. |
What you get | Spells out the deliverables and what stays out of scope unless it gets added to the proposal in writing. |
Payment | Explains the project fee basis, staged invoicing, payment terms, and when non-essential work pauses for overdue accounts. |
Changes | Defines what counts as a revision round and separates normal review edits from strategy shifts that need separate pricing and written approval. |
Who owns what | Says what the client owns after full payment and what the provider keeps, including reusable templates and building blocks. |
Portfolio | Covers how finished work can be shown publicly in redacted or anonymised form, and how to request privacy in writing. |
Limits | Sets responsibility boundaries for consent, deliverability, and changes made by staff or other suppliers after handover. |
Ending the project | Covers notice and termination costs, what gets handed over, and includes the Signature block at the end. |
Who it is for
Marketing automation consultants and HubSpot workflow builders quoting a build-and-handover project for a client who needs clear consent and sales-handover boundaries.
The contract in full
Hubspot workflow build services agreement
This is my working agreement for the HubSpot workflow build project described in the accepted proposal, and it sits alongside that proposal. If anything in the proposal and this agreement clash, I will flag it before I start so we can agree which version you want me to follow.
What you get
I will deliver the project described in the accepted proposal, based on what’s already in your tools unless we agree a rebuild. Deliverables included: Lifecycle and data map; Consent and lead-capture fixes; HubSpot workflows built; Nurture emails drafted and built; Testing checklist and results; Handover pack. I will set up and test in your HubSpot portal (or your chosen platform where agreed), using your existing lists, forms, properties and pipelines where they are fit for purpose. Anything not listed above, like new landing pages, full CRM re-architecture, data enrichment, or ongoing campaign management, is not included unless it is added to the proposal in writing.
Payment
This is a project fee in GBP, as shown on the proposal. I usually invoice in stages (for example, an initial invoice to book the work and a final invoice at handover), and the exact stages and amounts are the ones on your proposal or invoice. Invoices are payable within the payment terms shown on the invoice. If a payment goes overdue, I will pause non-essential work until the account is up to date, because I cannot responsibly keep switching on automations without knowing the project is funded. If you need an internal purchase order reference or vendor setup to pay on time, tell me before I start.
Changes
I include revision rounds as set out in the proposal. A revision round means you review what I have built (for example, a workflow, email copy, naming, or handover notes), send me one consolidated list of changes, and I apply those changes once. It does not include a change of strategy, a new audience, new entry criteria, or new offers after we have agreed the map, because that usually ripples through consent rules, lists and sales handover. If you want changes beyond the included rounds, I will price them and get your written ok before I do the extra work.
Who owns what
Once you have paid in full, you own the finished assets I create for you as part of the deliverables. That usually means the workflow logic and configuration inside your HubSpot account, the email copy I write for you, and the documentation in the handover pack. I keep ownership of my own templates, checklists, naming conventions, and any reusable building blocks I use to work quickly, even if they are adapted for your project. If I use any third-party tools, fonts, or templates that require a separate licence, I will tell you and you will own or maintain that licence in your own name.
Portfolio
I may show the finished work as an example of what I do, for example a redacted workflow map, anonymised screenshots, or a short case study focused on the approach and outcomes. I will not share your customer list, sensitive commercial data, or anything that would expose personal data. If you want this work kept private, tell me in writing before the project starts. If you ask after the fact, I will take it down from future use and stop sharing it going forward, but I cannot always pull back copies already published by third parties.
Limits
I will take care with consent, suppression, and handover to sales, but you stay in control of your systems and I need accurate inputs from you to keep things safe. I am not responsible for problems caused by changes made by your staff or other suppliers after I hand over, including edits to lists, properties, forms, domains, sending settings, integrations, or workflow triggers. I am also not responsible for deliverability issues caused by your sending reputation, purchased lists, or historic email practices. If something I built causes an unexpected send during the project, tell me straight away so I can help you stop it and diagnose what fired and why.
Ending the project
Either of us can end the project if it is not working, but I want it done cleanly. The notice period and any non-refundable booking amount are the ones set out in the proposal or invoice. Up to the end date, you pay for work completed and any non-cancellable costs I have already agreed with you. On termination, I will hand over what I have completed so far in a usable state, including the latest workflow map, any drafted email copy, and notes on what is live, what is paused, and what still needs decisions. If I am waiting on information from you for an extended period, I may treat the project as paused and reschedule it when you are ready.
Signature
Questions about this contract template
What should a marketing automation contract include?
A marketing automation contract usually covers scope and deliverables, what’s out of scope, payment terms, how change requests work, and who owns the finished assets. Many also include portfolio permissions, responsibility limits, and what gets handed over if the project ends early.
Can the workflow build be based on an accepted proposal?
A workflow build contract can sit alongside an accepted proposal and treat the proposal as the source for the specific scope and pricing. The agreement should also say what happens if the proposal and the contract conflict, so the build doesn’t start on mixed instructions.
How do you prevent the wrong emails from sending during a HubSpot workflow build?
A contract can set expectations around consent, suppression, and testing, and it can define what inputs the client needs to provide. The limits section can also spell out that changes to lists, triggers, and settings after handover can cause unexpected sends.
Who owns HubSpot workflows and email copy after the project?
Ownership depends on the terms, but this agreement says the client owns the finished assets after full payment, including workflow configuration and written email copy. The provider keeps ownership of their underlying templates, checklists, and reusable building blocks.
What counts as a revision round on an automation project?
A revision round can mean one consolidated list of edits to what’s been built, applied once, covering things like workflow naming, email copy, or handover notes. Strategy shifts like a new audience, new entry criteria, or new offers often sit outside included rounds because they ripple through consent, lists, and sales handover.
What happens if an automation project ends early?
An ending clause can set a notice period and confirm payment for work completed and any non-cancellable costs. This agreement also commits to handing over what’s been completed so far, including the latest workflow map, drafted email copy, and notes on what’s live, paused, and still awaiting decisions.
Start free today
Your entire business, one login away
No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.
No credit card required
