A marketing asset is supported by accounts that visitors never see. The domain points to the site, the host serves the pages, the form delivers a request, the CRM records it, and someone receives a notification. If one of those dependencies sits in an unknown account, the business may struggle to operate the channel even when it has the website files.
An account inventory makes those dependencies visible. Its purpose is not to collect every password in one document. It is to identify the system, the business responsibility, the appropriate access, and the evidence that the account can be used and recovered when needed.
Start from a real customer action
- Fit
- Explain the service scope.
- Trust
- Show supporting evidence.
- Next step
- Give a clear contact route.
Choose one important action, such as requesting a quote. Trace it from the page to the person who follows up. Write down every system that participates. Repeat the exercise for a phone inquiry and any other critical route.
This reveals accounts that a generic vendor list can miss. A form may use a separate delivery service. A notification may run through an automation owned by an individual. A phone number may sit under a provider account that is billed separately from the website.
The owned lead generation framework puts this inventory in context: control must be practical enough for the business to continue operating. A list of brand assets does not establish that the inquiry path will survive an account change.
Use fields that answer operating questions
| Inventory field | Why it matters |
|---|---|
| System and account identifier | Distinguishes the live account from a test or old account |
| Business function | Explains what stops working if access is lost |
| Administrative owner | Identifies who can authorize necessary changes |
| Working users and roles | Shows who can perform the current tasks |
| Billing and renewal responsibility | Prevents an important service from becoming an unowned invoice |
| Recovery route | Identifies how authorized access can be restored |
| Connected dependencies | Shows which other systems rely on the account |
| Acceptance check and date | Records whether the operating claim has been demonstrated |
Do not use “agency” or “office” as the only owner when a specific responsibility needs a person. A team can own the process, but someone should know who will act when a renewal fails or a connection expires.
Domain, DNS, and hosting are separate entries
Record the registrar and the domain registration details available to the business. Identify renewal billing and the authorized recovery contact. ICANN describes registrant information and responsibilities; the inventory should point to the actual registrar arrangement, not infer it from the website's branding.
DNS and hosting may use different providers or accounts. Note where the settings are managed and who can inspect them. If email also depends on those settings, record that relationship so a website change does not overlook a separate communication service.
A website delivery scope should explain the platform, release process, and continuing subscriptions relevant to maintenance. The inventory is the place to connect those instructions with real account ownership.
Measurement needs the correct property and role
- Event → record
- Define the event and check the record.
- Meaning → decision
- Review the business meaning before acting.
Analytics systems may contain several properties for old sites, tests, or related businesses. Record the one that measures the live channel and the person responsible for its configuration. A screenshot of a chart does not prove access to the underlying account.
Google Analytics documents account and property permissions. Confirm that each authorized user has the access needed for their actual task. Viewing reports, changing configuration, and managing users are different responsibilities.
Also identify Search Console, advertising accounts, tag management where used, and any reporting connector. If a dashboard depends on a private connection controlled by a departing user, the business needs a plan to replace or reauthorize it before the handover.
Forms and automations need dependency notes
For each inquiry route, record the form, delivery service, destination, CRM action, and notification. Identify any integration that authorizes the connection. The inventory should explain what a normal run looks like and where someone can inspect a failure.
An automation implementation should name the process owner as well as the technical account. A workflow that creates a task needs someone to receive it. A workflow that fails needs someone to notice and decide the next action.
Keep credentials and API secrets in the approved secure location. The inventory can reference where authorized staff obtain access without copying sensitive material into an ordinary project document.
Phone numbers require their own record
List the public numbers and any tracking numbers associated with the channel. Record which provider controls them, where they route, what billing supports them, and which business contact can request changes. Include numbers used in older materials if they still receive inquiries.
A number should not be retired solely because a campaign ended. Saved contacts, printed material, or old links may continue sending calls. The business should review current use and the relevant provider process before making a change.
Distinguish access from agreed rights
- Domain and website
- Document ownership and access.
- Analytics and records
- Define access and the handover.
Being able to log in does not answer every ownership question. A platform may allow access while the agreement defines different rights to content, creative assets, or exports. The agreement checklist helps resolve those terms separately.
Keep the inventory factual. Record the current arrangement and unresolved questions without presenting an assumption as a completed transfer. This makes the document useful during a provider change or an internal staffing transition.
A practical review drill
In a hypothetical quarterly review, the business owner asks the responsible team member to identify the live domain account, locate the next hosting renewal, open the correct analytics property, and follow a labeled form submission into the CRM. One connection fails because its authorization belonged to a former employee.
The useful result is a named correction: reauthorize the connection through the approved business arrangement, test the route, and update the inventory. The exercise does not require changing every account. It resolves a specific dependency before an actual customer request exposes it.
The website transfer guide uses the same evidence during a handover. Review the inventory after material changes, renewals, or role transitions so it remains a working document rather than an outdated attachment.
Request a free marketing audit to identify which account and inquiry dependencies deserve a closer review. A clear inventory makes the next website or automation scope easier to own and maintain.