Questions before a project.

Yes. A website can be the first scope: explain your capabilities, capture useful requirements and make the next sales action clear. Agree the pages, forms and handover before adding deeper operational modules.

Start by reviewing your current records, ownership and export options. A connection depends on the CRM's API, permissions and an agreed integration scope. No external CRM connection is included automatically.

This site demonstrates a working local website and assessment, non-production Business Core foundations and illustrative dashboards. It is not a ready-to-activate operating suite. Production setup and integrations require a defined implementation.

The number of workflows, content readiness, data quality, integrations, review cycles and handover requirements determine scope. Pricing and timing follow an agreed proposal; no fixed package entitlement is implied here.

Ownership, hosting accounts, software licences, data access and export responsibilities should be written into your agreement. Discuss these before starting; this website does not replace project-specific terms.

Agree maintenance responsibilities, backups, update coverage, support hours and the handover process in the project scope. Ongoing support and response targets are not automatically included.