A pipeline that follows the work
Use practical stages: new enquiry, contacted, assessment or measurement booked, proposal sent, contract agreed, installation scheduled and completed. Each stage should describe an observable event. Lost and disqualified records keep their reasons instead of disappearing.
Three levels of CRM scope
Start with the least complex system the team can maintain. The packages page compares a foundation, an operations workflow and a connected system.
- Foundation: records, pipeline, owners and next tasks
- Operations: measurement, proposals and installation handoffs
- Connected: agreed forms, sources and reporting integrations
Responsibilities before automation
An administrator checks incoming records and duplicates. A sales owner contacts the homeowner and logs the next step. An estimator records the measurement or site visit. An operations coordinator schedules fulfilment. The owner reviews exceptions and outcomes. One person can hold several roles in a small team.
Data and handoffs
Agree required fields, permissions, contact history and when an opportunity can move forward. For windows, this may include property type and approximate openings. For shutters, room and product preferences help prepare the visit. Avoid storing unnecessary personal information.
Implementation and acceptance
Map the current process first, configure the agreed scope, test sample records and run a team walkthrough. A handoff is accepted only when the right person sees the right record and knows the next action. No existing client CRM is exposed in this preview.
What remains planned
Voice AI, automatic qualification and advanced cross-system actions are roadmap items. Their inclusion depends on staffing, vendor support, consent requirements and successful testing. They are not represented as a live product.
