The rules that govern working with 7thDM.

Last updated 2026-07-28. Project-specific terms in a signed agreement take precedence over this page where they conflict.

Starting work

7thDM does not begin production work until a client has approved the project lane and scope, approved pricing, paid the required deposit or first invoice, and made a domain/DNS access decision and a maintenance-or-handoff decision. Projects may use milestone payments — for example a discovery payment, a build deposit, a design-approval payment, and a pre-launch balance. Launch may be paused until required balances are paid.

Domain and DNS access

Every project requires one of: registrar delegate access, DNS provider team access, nameserver transfer to a 7thDM-managed DNS provider, or client-completed DNS changes from written 7thDM instructions where the client can respond promptly. Ongoing shared usernames and passwords are not used as a long-term access method. If none of these are workable, 7thDM will decline or pause the project.

Hosting

Projects are hosted under a 7thDM-managed Vercel team by default, which lets 7thDM deploy, update environment variables, connect domains, and support the project without depending on client account access. Clients who want full hosting ownership can request a paid handoff, at which point support obligations are defined in writing separately.

Revisions and change requests

Each offer defines a set number of included revision rounds. Changes requested after an approval milestone — new pages, new forms, new integrations, new dashboard features, data model changes, or design-direction changes — are treated as change requests outside the approved scope. Change requests require approval before work begins and may affect timeline, budget, and launch date.

Data and content ownership

For app, CRM, and SaaS projects, ownership of client business data, user account data, uploaded files, database backups, export formats, and post-cancellation retention is defined in writing before launch. Client-provided content remains the client's responsibility for accuracy, permissions, and legal use. 7thDM-created content may be used by the client under the active agreement once required payments are complete. 7thDM does not use unlicensed images, fake testimonials, false claims, unsupported guarantees, or misleading business information in client-facing work.

SEO and lead generation — no guaranteed results

Search visibility and lead volume depend on factors outside 7thDM's control — competition, search demand, site history, content quality, technical health, reviews, location, authority, and platform changes. 7thDM does not promise first-page rankings, map-pack placement, traffic volume, lead count, revenue, or closed sales. What 7thDM commits to is the defined setup, reporting, optimization, content, campaign, and qualification work described in the active agreement. Clients are responsible for providing accurate business information, responding to qualified leads promptly, and maintaining the real-world service quality that supports results.

Outbound marketing and AI calling

7thDM's lead generation defaults to inbound, opt-in, first-party workflows. Cold outbound, scraping, purchased contact lists, mass unsolicited email, automated texting, and outbound AI voice calling are not default services and require explicit compliance review and written approval before 7thDM will build or run them — some of these 7thDM will decline outright. Any outbound AI voice work requires documented consent, disclosure, and applicable federal and state compliance review before use; prerecorded or synthetic sales messages and voice cloning without written permission are not built under any circumstance.

Google Business Profile work

Where Google Business Profile work is part of a project, 7thDM uses accurate, client-approved information only — no fake locations, no fake reviews, no review-gating, and no misrepresented services, hours, categories, or service areas. The client must own or authorize management of the profile and remains responsible for business accuracy and responding to customer feedback.

Automation scope

7thDM does not automate workflows that are undefined, subjective, undocumented, or unsupported by reliable data. Automation work requires a clear start event, a clear end outcome, a named process owner, defined inputs and outputs, deterministic decision rules, known exceptions, and client sign-off on the resulting process document. If a workflow isn't automation-ready, 7thDM will scope discovery or documentation work first rather than automate an unclear process.

Maintenance, handoff, and closure

Every launched project ends in one of three states: an active 7thDM monthly or annual care plan, a paid handoff with client-owned hosting responsibility, or a written closure with no ongoing support obligation. No ongoing support is implied without an active plan, an approved hourly arrangement, or a written exception. Handoff transfers operational responsibility — it is not the same as ongoing support.

Cancellation

Cancellation terms — what payments are refundable, what work product is delivered, what happens to hosting and domain/DNS changes, and what support remains available — are agreed before work begins as part of the project agreement.

When 7thDM will decline a project

7thDM may decline or end an engagement where a prospective or current client refuses required access, refuses payment terms, wants software-level complexity priced as a simple website, expects unlimited support, will not approve a maintenance or handoff outcome, requires risky credential sharing, wants an undefined workflow automated anyway, or wants cold outbound, scraping, purchased lists, mass email, or outbound AI voice calling as the default lead generation strategy.