Website development your team can maintain
Help visitors understand your offer, compare their options and enquire. Growmoon plans the pages, content, editing tools and enquiry flow around those tasks. We scope application features and Shopify storefronts separately.

Identify the visitor’s next decision
Start with the information a visitor needs to compare your services or prepare an enquiry. Record what they should be able to do next. That will help you decide whether the project calls for a visual refresh, a clearer service structure or both.
- Name the main audience and useful visitor tasks.
- Identify the pages and information needed for each task.
- Agree who approves the content and enquiry journey.
From visitor decision to enquiry
- Visitor taskUnderstand the offer and compare services.
- Relevant pageFind the approved information for that decision.
- EnquirySend useful project context to the intended destination.
Define the scope of the website
A content website is different from an application with customer accounts, permissions and business transactions. Identify booking, portal, workflow or data-management features separately so they are not hidden inside a page-design estimate. Shopify storefronts also have their own catalogue, checkout and platform scope. Choose the delivery approach after the editing, integration and operating requirements are understood.
Separate templates, pages and content
A reusable service layout can support several pages, but each page still needs its own approved information. Inventory the required layouts, URLs, copy, images, downloads and languages. Decide which material is retained, rewritten or supplied by the business. Identify content and component permissions, accessibility needs and the devices that matter before the scope is priced.
- List reusable layouts and individual page URLs.
- Assign copy, image and approval responsibilities.
- Separate first-release content from later additions.
The website content inventory
- Templates
- Reusable layouts for the agreed page types.
- Pages
- Individual URLs and visitor tasks.
- Content
- Copy, images, downloads and languages.
- Approval
- Content owners and the first-release boundary.
Plan how your team will edit the site
Describe the changes your team expects to make after launch, such as updating a service paragraph or publishing a resource. Agree which roles may make and approve those changes, and how drafts, backups and recovery are handled. A static design preview does not establish a working editing system. Platform choice, editor access, training and documentation should match the tasks that actually need to be maintained.
Follow the enquiry from page to inbox
Map how a visitor reaches the relevant service, understands the scope and sends useful project context. Specify required information, helpful validation and what happens if a submission fails. Agree where an accepted enquiry must be stored or received and how duplicates or test records are handled. A submitted request or visible success message alone does not establish delivery to the intended destination.
- Keep the selected service clear throughout the journey.
- Ask for enough context without collecting unnecessary confidential data.
- Check the accepted result and the visitor-facing state separately.
Essential journey agreed
Meaningful exceptions included
Evidence ready to inspect
Plan a redesign or migration
If existing content, files, URLs or systems will move, inventory the starting point and intended destination. Agree redirects where appropriate, account access, content checks and a rollback path. A redesign that keeps the same URLs has different dependencies from a platform or URL migration. Keep important visitor journeys and ownership responsibilities visible, and avoid treating a migration plan as a guarantee of unchanged search positions.
Agree ownership, costs and support
The proposal should identify included layouts, content work, integrations, testing and handover. Separate domain, hosting, themes, subscriptions and ongoing support from the build. Confirm who owns the accounts, how authorized editors receive access and which documentation or training is included. Agree review milestones, meeting overlap and support expectations for the actual engagement rather than assuming an unlimited maintenance arrangement.
Website handover
- Editing access
- Authorized editors and account ownership.
- Documentation and training
- Instructions for the agreed content tasks.
- Running costs
- Domain, hosting, themes and subscriptions.
- Support
- Review milestones and the maintenance boundary.
Questions about website development
What should a business website development scope include?
It should identify visitor tasks, reusable templates, individual pages, content responsibilities, editing needs, integrations and the enquiry journey. Include migration work where relevant, along with account ownership, recurring costs, acceptance checks and handover. A page count alone does not describe all of those obligations.
Is copywriting, content loading and editing access automatically included?
These need explicit scope. List who supplies and approves copy, images and product or service information, how much content is loaded, and how authorized people will update it later. Agree revisions, training and continuing content work separately where needed.
Can a redesign guarantee the same rankings after launch?
No search position should be promised as a build deliverable. Define the actual content and URL changes, protect useful visitor paths, check any intended redirects and agree post-release monitoring. Website acceptance and observed search performance are different records.
Share your pages and editing requirements
Share the existing site URL, the reason for the change, an outline of pages and content, and who will maintain them. Add required forms or integrations and whether existing URLs or data must move. Include timing and budget context; keep passwords and private customer data out of your message.
Discuss website scope