Core and utility
Choose the problem you want to solve. The right next step might be a small fix, a planned project or some defined ongoing help.
01 / Core and utility
Use the starting points below to find the relevant scope. If several apply, identify the part blocking the next customer action first.
Give a new business or offer a clear, useful home.
Get a bounded fix or a practical care plan.
Choose between search improvements and advertising.
Map the handoffs and the part that needs human review.
02 / Core and utility
Websites, care, search, ads, content and automation each solve a different part of the customer journey.
Build, improve or fix the customer journey.
Keep a defined set of tasks in good shape.
Find the obstacle and choose useful changes.
Review readiness, scope and spending controls.
Explain the offer and answer the next question.
Connect a repeat task with a reliable handoff.
03 / Core and utility
Use the starting condition rather than choosing a package by name. These are scope examples, not guaranteed outcomes.
| Help | Starting condition | Tangible work | Your input | Dependency / reason to wait |
|---|---|---|---|---|
| Websites | No usable site or an unclear customer path | Reviewed page plan, built pages and handover | Accurate offer, assets and approver | Decide the visitor action and content ownership before scaling the design. |
| Website care | A repeatable upkeep task list | Defined checks, changes and completion record | Supported site, access owner and priorities | Use a one-off repair when no recurring need is established. |
| SEO | A discovery or page-relevance concern | Evidence-linked audit, roadmap or agreed page changes | Priority services, real markets and implementation owner | Diagnose a broken page or offer before multiplying content. |
| Google Ads | An offer ready for a paid-demand test | Reviewed campaign scope, settings and reporting plan | Approved budget, destination and qualified-action definition | Fix broken intake and establish response capacity before buying visits. |
| Content | The page does not explain the offer well enough | Source-backed copy or a defined editorial plan | Business facts, evidence, rights and reviewer | Do not draft claims the business cannot substantiate. |
| Automation | A stable repeated handoff | Mapped, tested workflow and recovery instructions | Named systems, owner and permitted data flow | Clarify a changing process and permissions before connecting tools. |
| Brand scope assessment | The message or visual application is inconsistent | A separately assessed messaging or identity brief | Audience, existing assets and usage needs | Validate specialist fit and rights; a routine edit does not require a rename. |
Once the useful deliverable is clear: Compare cost drivers and scoping
If the unresolved decision is words versus visual assets: Compare messaging and visual-identity scope
04 / Core and utility
A broken page, a complete website and a recurring task call for different arrangements. A small job starts with the specific problem and a finish line. A larger project needs a page plan and review points. Recurring help needs an agreed task list and available capacity.
05 / Core and utility
The owned projects section explains the context and evidence limits of the available examples. An owned project does not establish every service or industry specialization.
06 / Core and utility
Those are different jobs. Clarifying an offer, creating visual assets and applying an existing identity need different inputs and rights. A specialist scope should be assessed separately from a routine page edit.
07 / Core and utility
Describe what should become easier, what you use today and any real constraints. Leave passwords, private customer records and payment details out of planning notes.
