Client-owned accounts
Domains, hosting, email, CRM, automation tools, analytics, AI accounts, and business-critical subscriptions should usually belong to the client.
Hosting, tools & add-ons
Clear ownership. Practical recommendations. No surprise tool or subscription costs.
MethodMade Studio helps choose, configure, connect, document, and maintain tools while keeping ownership, ongoing costs, and support boundaries clear.
Tool ownership map
Your business should not be trapped inside someone else’s account.
Clients should own their core accounts whenever possible. That keeps the business in control if tools, vendors, or support needs change later.
Step 1
Own the account
Core business tools should be created under the client’s email, billing, and administrative control whenever possible.
Step 2
Understand the costs
Monthly subscriptions, paid add-ons, API usage, sending limits, seats, and storage should be visible before the work begins.
Step 3
Document the handoff
Logins, billing ownership, tool purpose, setup notes, and support boundaries should be clear enough to maintain later.
Step 4
Watch usage limits
Cheap tools can become expensive when automations, submissions, AI usage, storage, traffic, or team seats increase.
Service fees are separate. Third-party subscriptions, hosting fees, paid plugins, premium themes, domains, AI tools, automation platforms, and usage costs are billed separately unless included in writing.
Clear cost visibility
Recommendations should account for monthly fees, usage limits, upgrade triggers, seat pricing, data ownership, and cancellation risk before a tool becomes part of the business.
Managed support when useful
Managed setup, monitoring, or maintenance can be added when it creates real value, but the scope and responsibility should be written down clearly.
Costs and scope
Separate tool costs from service work.
The cleanest setup is usually simple: the client owns and pays for business tools, while MethodMade scopes the recommendation, setup, configuration, documentation, and support work.
Usually client-paid
- ✓Domain registration
- ✓Website hosting
- ✓Business email
- ✓CRM or form tools
- ✓Automation platforms
- ✓AI/API usage
- ✓Paid plugins or themes
- ✓Analytics or reporting tools
Usually service scope
- ✓Tool recommendation
- ✓Setup or configuration
- ✓Workflow connection
- ✓Testing and review
- ✓Documentation or walkthrough
- ✓Light troubleshooting when scoped
- ✓Handoff notes
- ✓Usage-limit guidance
Usage to watch
Low-cost tools still need clear limits and ownership.
Many tools start cheap and become expensive when usage, seats, automations, storage, or traffic increase. Tracking limits early helps prevent avoidable surprise costs later.
Watch
Monthly subscription cost
Watch
Storage limits
Watch
Automation or task limits
Watch
AI/API usage limits
Watch
Email sending limits
Watch
Form submission limits
Watch
Website traffic limits
Watch
Seat or user pricing
Watch
Integration limits
Watch
Upgrade triggers
Watch
Cancellation or export limits
Watch
Admin ownership and recovery access
Add-ons
Add specific support without expanding the core package.
Add-ons are useful when a package needs one extra piece, but not a larger engagement. They keep the scope clear and prevent extra requests from becoming a second project without being planned or priced.
Additional strategy session
A focused planning session for tool choices, workflow priorities, or next-step decisions.
Extra page copy or page structure
Additional website page planning, content structure, or copy support outside the core package.
Contact or intake form setup
Form fields, routing, confirmation language, notification setup, and simple handoff notes.
Automation add-on
One scoped automation or workflow connection when the process is ready and the tool limits make sense.
AI workflow add-on
Reusable prompts, review steps, guardrails, or AI-assisted workflow support for a defined use case.
Documentation or SOP add-on
Practical handoff docs, checklists, internal instructions, or lightweight process documentation.
Dashboard or reporting add-on
Simple visibility into useful information, such as submissions, follow-ups, tasks, or workflow status.
Tool stack review
A focused review of current subscriptions, overlap, risks, ownership, and better-fit options.
Training session
A walkthrough for using the new page, workflow, automation, documentation, or tool setup.
Rush scheduling when available
Priority scheduling for a clearly scoped need when the calendar and project type allow it.
Boundaries
Clear add-on rules keep projects healthy.
This page is intentionally plain about money, ownership, and scope because those details are what keep a project sustainable after launch.
Add-ons are scoped before work begins; they are not unlimited support buckets.
Third-party subscriptions, paid plugins, hosting, domains, email tools, and usage-based charges are separate unless included in writing.
MethodMade may help set up tools, but the client should retain access, billing control, and ownership of business-critical accounts.
If an add-on grows into a larger need, it may become a sprint, larger project, or retainer instead of being added to the original package without a clear plan.
Next step
Need help choosing tools without overcommitting?
Start with a free Discovery Call, or choose a paid Tech Checkup when you need a deeper tool or workflow review.