Scope before sales
Know what you are buying.
Landscapers separating recurring maintenance from design, hardscaping, and project-estimate inquiries.
Not a fit: Businesses expecting a public website to replace crew scheduling, route planning, or site inspection.
- What does this first release include?
- A public website and inquiry path using an agreed page list and supplied content. Property calculations, crew availability, instant pricing, and CRM automation are not part of the website starting scope. Deliverables: Maintenance and project-service paths; Authorized project gallery; Coverage and estimate-request information; Mobile inquiry form with a clear next step.
- When should we use existing software instead?
- Keep an existing field-service platform when it already supports your service categories and inquiry handoff. A simple form may be enough before a custom estimator is warranted.
- What determines the project price?
- Starting project price: $397. Service categories, project-gallery organization, copywriting, redesign redirects, languages, quote qualification, and integrations. Final scope and price must be approved before implementation.
- What data and permissions are required?
- Provide actual coverage, service minimums, authorized photos, and a follow-up owner. External booking and CRM tools require supported access and confirmed routing rules.
- What can this service not promise?
- Lot size alone cannot establish a landscaping price. Access, grading, materials, drainage, and a site assessment may change the work. The demonstration never calculates a job price.
- Who owns the site and maintains it?
- Confirm source-code and design rights, third-party licenses, repository access, credentials, deployment, and handoff in the agreement. Use business-owned domain and vendor accounts where possible. Hosting, domains, paid tools, content changes, and ongoing support are separate responsibilities and recurring costs; no unlimited maintenance is implied.
Replacing an existing site or workflow?
Inventory current URLs, content rights, form destinations, vendor access, and data export options before choosing a redesign or migration. Agree the redirects, backup, validation, launch, and rollback plan first. No third-party platform support or data transfer is assumed until its access and export capabilities are reviewed.
The demo is original illustrative work by Luna Studio, not a client result. Our service framework reflects proposed implementation scope, not market-average pricing or independently tested software comparisons. About the studio in Córdoba, Argentina.