A lead provider says you'll own the website, and you're about to sign. That can mean you control the domain and get editable files. It can also mean a login to their platform that lasts only while you pay, or rights to some of the content. Before you sign, ask the provider to list each piece and what happens to it when you leave. Trojan Digital Marketing sells owned microsite networks, and on ours the domains are registered in your business name. If you stop renewing, the sites stay live on your domains and our managed work ends. Jeff Clerisier, our founder, works out each scope with you, and we document the hosting and handoff details before you sign. Bring the agreement you're weighing: the first strategy call is free, and during business hours we aim to reply within five minutes.
This is a commercial review framework for making the scope understandable. It does not determine the legal meaning of an unseen agreement. If ownership, licensing, or cancellation language is disputed or materially unclear, resolve that wording with the appropriate adviser before relying on an assumption.
Ask for an asset schedule
An asset schedule lists the items the engagement will create or use. Include domains, websites, written content, design files, images, forms, tracking numbers, integrations, and reporting accounts. For each item, record who controls it during the engagement and what the business receives when the agreed work is complete.
The owned lead generation guide explains why this matters. Asset control, day to day operation, and commercial performance are separate questions. A proposal should make all three visible rather than allowing one phrase to stand in for the entire arrangement.
| Agreement statement | Question to resolve | Practical evidence |
|---|---|---|
| Domains belong to the business | Which entity and registrar account will be used? | Registration details and demonstrated access |
| Website included | What files, platform access, or export are delivered? | A named deliverable inventory |
| Content is yours | Which content and creative rights are included? | Specific scope and relevant licenses |
| Tracking provided | Who controls the numbers, accounts, and data? | Account and routing documentation |
| Cancel at any time | Which services stop, and what transition work remains? | A clear termination and handover description |
Distinguish registration from an invoice line
A domain charge on an invoice doesn't show whose name is on the registration. We check that name first, since the website and its contact routes depend on that domain. Ask which registrar will be used, how the business will access the account, who receives renewal notices, and who pays recurring fees. The answer should identify a real operating process.
ICANN provides registrant rights and responsibility information. Use the registrar's current documentation alongside the proposed scope. The agreement should not leave the business dependent on a departing employee's personal inbox for a critical renewal or recovery message.
Define what “website files” includes
A finished site may depend on a CMS, a repository, a hosting service, plugins, fonts, purchased assets, or a deployment process. Ask what a receiving developer would need to maintain the current site and whether those items are included in delivery.
A website project scope should identify the relevant platform and handover format. If an export has limitations, describe them before approval. If a subscription is required to keep the site operating, identify the subscription and responsible payer.
Do not assume that an editable file and a right to reuse its contents are the same thing. Request a record of third party assets and the applicable usage terms. Clear documentation helps future teams make decisions without reconstructing how every image or font entered the project.
Check access at the system that matters
- Domain and website
- Document ownership and access.
- Analytics and records
- Define access and the handover.
A reporting portal can be convenient while leaving the underlying systems outside the business's control. Ask which original accounts the business will be able to inspect and administer. Identify the specific property or account rather than accepting a general statement that “analytics access” is included.
Google Analytics documents distinct permission levels. The broader marketing account inventory helps apply the same practical review to advertising, forms, phone routing, and CRM connections. Have your own authorized user log in while the provider watches.
Make lead distribution language precise
If the proposal describes direct or exclusive inquiries, ask what the provider actually promises. Does it agree not to distribute those inquiries to competing businesses? Does it reserve a territory for the client during an active agreement? Does exclusivity apply to a website, a service category, or a specific product?
Those terms should not imply control over the customer's independent behavior. A person can submit a form to your site and contact another contractor separately. A useful agreement distinguishes the provider's distribution practice from the customer's freedom to compare options.
For a microsite engagement, also ask how market boundaries are defined and what happens when the business adds a service or location. Avoid treating a diagram or a sales page as a substitute for the actual agreed boundary.
Review the exit while the relationship is beginning
Ask which services end when management stops: hosting, content updates, reporting access, call tracking, advertising, or another function. Then identify what must be arranged for continuity. Keeping the domain doesn't keep every connected service paid and running. On our owned networks, once you stop renewing, you pay the domain renewals yourself.
The lead website transfer plan can become an acceptance checklist. It should cover account access, files, routing, exports, and named responsibilities. If transition assistance has a separate scope or cost, make that visible before a deadline makes the decision urgent.
A hypothetical review meeting
- Observe → review
- Check the page and its evidence.
- Update → recheck
- Publish the change and check the result.
Imagine a contractor reviewing a proposal for a new lead website. The proposal says the business owns the asset, but the hosting line does not describe cancellation. Instead of debating the slogan, the owner asks the provider to show the domain account, list the delivered files, explain the hosting dependency, and demonstrate where inquiries arrive.
The parties then add a concrete handover schedule: the business receives the agreed content and account access, the receiving operator tests a draft update and a form submission, and recurring services are assigned before the old arrangement ends. Treat it as an example of a promise you can check. Your actual contract clause still needs its own wording.
Approve the scope against evidence
Mark each important statement as documented, demonstrated, or unresolved. A documented term explains the arrangement. A demonstrated task proves that access or routing works. An unresolved item identifies a decision still needed before the business can rely on the proposal.
That method keeps the review focused. The objective is not to make every agreement longer. It is to remove the few ambiguities that could prevent the business from operating the channel it believes it is buying.
Request a free marketing audit to review the public channel and identify the ownership, access, and handover questions worth resolving in the next project scope.
