What a marketing technology partner is hired to do
A marketing technology partner is an agency, a freelancer or a consultant brought in to select, configure, connect or administer some or all of the business's marketing tools. The label changes from one provider to the next, and the work falls into three kinds. Advice looks at the stack and recommends: which jobs it serves, where it falls short, what to add, change or retire. Build sets up what was agreed by configuring a tool, connecting two tools, testing the result and writing it down. Run is the day-to-day administration that follows: requested changes, fixes and checks inside tools the business owns. A provider may offer one kind or all three, and the scoping section treats each on its own.
Three decisions remain the business's own, whoever does the work. The first is what the stack is for. The use-case list is the brief a partner works from: the jobs marketing needs the stack to do, each written as an outcome with no product in it. A provider who starts from a product instead of a job is describing a tool, not a need, and a business without the list can write it before asking anyone for a proposal. The second is whether to buy the work in at all, which the in-house versus agency comparison settles one type of work at a time. The third is what data a tool may receive: whoever owns data protection decides that, and the provider carries it out.
A provider working inside tools that hold customer records is handling personal dataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier. for the business, and under the GDPRThe EU regulation setting the rules for processing personal data, including its principles, lawful bases, individuals' rights and breach duties. a supplier that processes on the business's behalf is a processor. That sentence is the whole of the legal ground this guide covers. What a contract with a processor must contain, like the wording of any other clause in the agreement, is a question for the business's legal adviser; nothing here is legal advice.
This guide sits beside the specialist hiring guides, not above them. The agency selection guide owns the cycle of shortlist, pitch, contract and review that applies to any provider, and the hiring guides for tracking and for email own the objects those providers work in. None of them covers the provider who configures and runs the tools themselves, which is the appointment this page is for. Where the engagement covers procedures, sign-off steps and documentation around the tools rather than the tools themselves, the guide to hiring and evaluating a marketing operations consultant covers what stays with the business and how to accept that work.
What stays in the business's name
The marketing technology hub asks, for any tool, for a named person in the business who can sign in, set the tool up and renew it, and it lists an agency in that role as a warning sign. This section applies that ahead of time, by kind of object a provider touches. Each row says what to settle before the work starts and names the guide that owns the object; none of those guides is retold here.
| Object a provider touches | Settle before the work starts | Owned by |
|---|---|---|
| The tool administrator seat | Which person in the business holds it and who deputises, with the provider joining as a named user at the narrowest role its work needs | The access review tutorial checks supplier access against live engagements; the access request procedure grants it one request at a time |
| Integration and service credentials | The credentials each connection will run on and the person in the business who holds them, chosen before the connection is built so that nothing has to be moved later | The tutorial on documenting marketing integrations, which records credentials and treats a connection on a supplier's login as a finding |
| Configuration and its documentation | What the provider writes down as it builds, kept where the business can open it without the provider, plus a business-held export of settings where a tool offers one | The backing-up guide for tool data and settings |
| Copies and exports of records | Copies in the business's own storage, not the provider's folder, taken before the provider's access changes and given an end date by whoever owns data protection | The retention guide, which starts from finding where the copies sit; the backing-up guide describes taking them |
| The stack record, the registers and the use-case list | The business keeps them, the provider writes to them as part of the work, and a change the stack recordThe live register of every marketing tool: owner, deputy, cost, notice date, users, use cases and status, kept current by onboarding, reviews and retirement. does not show counts as unfinished | The stack management playbook, which keeps the stack record and the registers together under one stack owner and reads the use-case map in its audit of the stack |
| Tracking and email work | Appointed under their own hiring guides, which settle what those providers touch | The analytics agency guide and the email agency guide |
A copy kept in a provider's own folder belongs, in practice, to the provider, and a backup is personal data like the record it copies, which is why the copies row asks for the business's storage and an end date. The table leaves out the tracking objects and the email objects on purpose; the last row sends each to its own guide, and this page restates neither.
Scoping: advice, build or run
As general practice, give advice, build and run work separate scopes, written before the provider starts, and begin with advice or a small build, moving to run work once a build has been accepted.
| Kind of work | What the business should receive | What the scope should say |
|---|---|---|
| Advice | A written review or recommendation: findings against the use-case list, options, and a requirement list for any tool to be chosen. Nothing in a live tool changes | What is reviewed, from which records, who supplies read access and that the review alters nothing live |
| Build | Tools configured and connected as agreed, tested away from customers, with each connection written into the register and a record of what was built | The use-case lines it serves, the accounts it runs in, where it is tested, what is documented and the checks that accept it |
| Run | Day-to-day administration inside the business's tools: requested changes, fixes and checks | A route for requests, the changes the provider may make alone, the changes that need the tool owner's approval and how each is recorded |
Advice. As general practice, advice on the stack can follow the stack audit, done with outside eyes: the tutorial on running a stack audit builds the inventory and reaches the decisions, and the business supplies the provider with read access and keeps the stack record. Advice on which tool to buy is scoped as the business would run its own selection, using the choosing and evaluating tools guide for the method and the tool evaluation template for the record. As general practice, ask a provider who recommends a tool to name the use case it serves and to score the tool on the criteria used for those already owned, so that the recommendation arrives as a request like any other, through the route set out in the guide to handling requests.
Build. Scope a build to named lines of the use-case list, so that acceptance has something to check. Say which accounts the work runs in, where each change is tested, what the provider documents and which checks accept it. Where the build brings a new tool into the stack, the data and privacy review in the tool onboarding SOP comes before personal data reaches the tool; the provider does not clear it.
Run. Run work is continuing work. The agency selection guide's comparison of fee models fits a retainerA standing fee paid regularly to an agency or supplier for continuous work with a stable scope, as distinct from project fees, time and materials or commission. to continuous work with a stable scope, while a build or a review with a finish line is a project. Name a route for requests, say which changes the provider may make alone and which need approval, and put the provider's changes through the business's change controlThe routine a proposed change to a live system follows: written down first, reviewed, tested, signed off and recorded before it reaches customers or data., so that each change is written down before it is made and recorded when it goes live.
Writing it down. Confirm the agreed scope in the provider's statement of workA supplier's written confirmation of what it will deliver, by when, at what price and how it will invoice, against which the order is raised., which the work and the invoices are later read against. The agency scope of work template has fields for who owns the accounts and data and for exit and handover, and the table above goes into them. Put the split of duties between provider and business into a RACI matrix, the responsibility-matrix approach the in-house comparison asks for when it says to write the split into scopes, with one accountable role for each row as the framework page requires. Providers use AI tools inside their own work too, so add the outcome of AI rules for agencies and contractors to the same scope: the permitted uses, the business's data in those tools and what comes back at the end.
Questions to ask before appointing
The selection guide owns the questions about the team, cover, references and fees; the ones below concern the tool work itself. Put these among the questions in the agency RFP template that each candidate answers, so that responses line up for comparison. As general practice, the right-hand column is a guide, not a rule for any tool.
| Question | A careful answer includes |
|---|---|
| In whose accounts will the tools be set up, and who holds the administrator seat? | Accounts the business holds, the seat with a named person and a deputy in the business, and the provider as a named user whose access the business can withdraw |
| Which credentials will each connection you build run on, and who holds them? | Credentials the business holds, written into the register beside an owner, and no connection on the provider's own login |
| What will you write down as you build, and where will it live? | A register row for each connection and a written note of each configuration, in a place the business can open without the provider |
| Where will you test, and with which records? | Preview or a test place where a tool offers one, invented records that carry a marker, exclusions in place before the test and a clean-up afterwards |
| How will you check that consent is respected? | A test for each row of the consent map that the work touches, run with marked test contacts, and no decision by the provider on which basis a purpose relies on |
| What personal data will you see, where will your copies sit and which AI tools will touch the data? | Only what the work needs, copies in storage the business owns and lists with an end date, the staff and tools named, and AI use that fits the business's own rules for agencies |
| How will you recommend tools, and how will the business check a recommendation? | Each tied to a written use case, scored on the criteria used for tools already owned and sent through the business's request route |
| How does the arrangement end, and what is handed over? | A current register, copies handed over, credentials moved and access ended on a date written into the statement of work |
Rank the answers in a weighted scoring matrix. The framework page asks for criteria and weights to be agreed and dated before any proposal is read, for each score to carry its evidence and for must-haves to act as gates that remove a proposal whatever it scores elsewhere. Whose accounts the work will run in is a natural gate for this appointment, so that an attractive proposal cannot add up past it. Run the sensitivity check on the weights before deciding, as the framework describes.
Warning signs in a proposal
- Work proposed in the provider's own accounts. The containers and workspaces guide, which cites Google Tag Manager Help, says a container can be saved as a file and brought into another container, while one created inside an agency's own account can only be exported, not moved, and the history and permissions are left behind. As general practice, read a proposal to build any tool in the provider's own account the same way: the business ends up with a copy, not the original.
- Asked for the business's own login, or a shared password. A supplier gets a named account scoped to the role its work needs, because with a shared login nobody can tell which person made which change.
- Connections that run on the provider's credentials. A connection under a supplier's login is a finding even while it works, because it stops working the day that access is withdrawn.
- No test place and no test records. A plan to try changes in the live tools with real customer records risks messages and uploads that cannot be recalled.
- The settings screens as the documentation. When the only record of the build is whatever sits inside each tool, the business cannot say what the build does or what would break if a connection stopped.
- The provider as the only administrator. The backing-up guide names an agency holding the only administrator seat among the risks that a copy held by the business guards against.
- Silence on data, AI and the end. A proposal that does not say what personal data the provider will see, which AI tools it will use or how the arrangement ends has left those questions for a worse moment.
Accepting the work
Acceptance compares what the work does with what was agreed in writing, and a person who did not build it can do that by watching. As general practice, the person who signs for the business is someone other than the builder.
Accept against the use-case list. A line moves from planned to live when its job runs and someone other than the builder can show it working. A line the project was scoped to serve that cannot be shown working stays planned.
Test where customers cannot see. Messages sent, data uploaded to an ad platform, deletions and merges, and changes to how consent is handled or when tags fire are one-way, so the test environments guide has them tried first, on a staging copyA private copy of a website or tool where changes are tested before release, kept behind access control and out of search and production analytics. of the site or in the test places it describes. Ask the provider to show the exclusions switched on ahead of the test and the clean-up once it ends, and keep a record of who approved going live.
Walk the consent map. Take each row of the consent map that the new work touches and run the test that row already names with a marked test contact. The provider builds the routes. Whoever owns data protection decides the basis each row relies on, and the provider does not.
Compare the register with the settings. Someone who did not build the connections opens each tool's connected-app, webhook and key settings and compares them with the integration registerOne standing record of every connection between marketing tools: what moves, which way, keyed how, on what schedule, with whose credentials and owner.. A connection in the settings and not in the register is a finding. A row is complete when each field of the register is filled, the owner, the credentials the business holds and the check that would show the connection failing among them.
Take the copies and close the records. Before the provider's access changes, the business takes its own copies and brings the stack record, the access register and the use-case list up to date. The provider's notes feed those records, and the business's people sign them.
Changing or ending the arrangement
Ending is the job of the agency offboarding checklist. It orders the work by risk, from who owns each account to access removal and the close, with the keys the agency used rotated. This guide adds only what belongs to tool work, and asks for it at the start. Write into the statement of work the day the provider's access ends and what has to be true by then: a current register, copies in the business's storage and connections running on credentials the business holds. The business removes the access on that day. As general practice, a date agreed in advance gives the end a place on the calendar.
If the end arrives and the provider still holds an advertising account the business depends on, the troubleshooting page on recovering ad accounts from an agency sets out how to recover them, and in which order.
As general practice, a person at the provider who moves on is treated like any leaver: what they hold is handed over, then the account is removed. The reassigning CRM records tutorial sets that order for the CRM, reconnecting integrations under a lasting account before the old access goes.
As general practice, a change of provider starts from the register and the use-case list, not from the outgoing provider's memory. The agency onboarding checklist treats the new appointment as a relationship with people and sends software to the onboarding SOP, so the tool-level handover rests on the records described above.
Tools the provider chose are the business's tools and follow the life of any other. The renewal review tutorial weighs a tool against the use cases as they now stand, and the retirement tutorial takes one out when no job needs it. The next access reviewA periodic check of who can use each marketing tool: every account matched to a current person, supplier or integration, with owners, deputies and narrow roles. matches the provider's accounts against live engagements. Notice terms, exit fees and any other contractual point go to the business's legal adviser; this page states none.
A confectioner appoints its first technology partner (illustrative)
Sutrudor Confectioners appoints a consultant for its first project
Sutrudor Confectioners, an invented maker of nougat and toffee sold in gift tins through its own shop, has a marketing team of 4 and no technical staff. It wants a CRM with marketing automation and the connections from the shop to the CRM. Before asking anyone for a proposal, the team writes its use-case list: 14 lines, of which the first project serves 5. It sends the same written request to 3 providers and says that proposals should leave out any email platform, sending domain or consent-record build, which stay with a later, separate appointment.
Before any answer is read, the marketing lead writes down the gate and the weights. The work must run in accounts the shop holds, and the three weighted criteria are what is documented (35%), how changes are tested (35%) and what is left behind (30%).
| Criterion | Provider A, an agency | Provider B, a freelance consultant | Provider C, a small studio |
|---|---|---|---|
| Work runs in accounts the shop holds (gate) | Fails: the CRM account would sit in the agency's name | Passes | Passes |
| What is documented (35%) | Not scored | 5 | 3 |
| How changes are tested (35%) | Not scored | 4 | 2 |
| What is left behind (30%) | Not scored | 4 | 3 |
| Weighted score out of 5 | Not scored | 4.35 | 2.65 |
Provider A fails the gate, so it is removed before scoring and decides nothing. Moving ten points of weight from what is documented to what is left behind leaves Provider B ahead of Provider C, 4.25 to 2.65. The shop appoints Provider B for a scoped first project: set up the CRM and build the shop-to-CRM connections for the 5 lines. The statement of work names the shop's accounts, lists the register rows the consultant will write, says that changes are tested with marked test records first, and writes the end of the consultant's access into the document from the start: access ends on the project's last day, once the register is current and the copies are in the shop's own storage. The shop keeps the integration register, the access register and the copies itself.
At acceptance, the marketing lead, who did not build the work, runs a marked test contact through each of the 3 rows of the consent map that the connections touch. Two pass. The third fails because a contact who had objected still appears in the next sync, so the consultant corrects the filter and the row passes on the second run. The register lists 3 connections, while the connected-app settings show 4: a trial webhook left switched on. It is removed, and a row for it is added to the register and marked retired with the date. The shop's data protection owner has decided the basis each of those consent rows relies on. The 5 lines move from planned to live, and on the last day the shop removes the consultant's access after rotating the keys the consultant used.
The marketing tools hub places this guide beside the others on choosing, reviewing and retiring the tools a provider works on.
Common mistakes
- Choosing the provider before the jobs are written. Without the use-case list, proposals can describe products instead of needs, which makes them harder to compare.
- Letting the work start in the provider's accounts. Some objects can be exported but not moved, so open the work in the business's accounts from the start.
- Taking the provider's walk-through as acceptance. Run the marked test contacts and compare the settings, or have someone who did not build the work do it.
- Leaving the documentation to the end. A connection whose register row is incomplete is not finished, so write each row as the connection is built.
- Treating the statement of work as the whole agreement. It confirms the scope; contract wording, and whether anything more is needed, is for the business's legal adviser.
- Letting the provider choose what data a tool may receive. That decision sits with whoever owns data protection.
- Ending by removing access first. The provider can then no longer export or hand over, and the business has not yet taken its own copies.
- Forgetting that recommended tools are the business's tools. They need an owner, a renewal date and a row in the stack record like any other.
