The Moment That Made This Real

• Tell me briefly what happened that led you to consider a smart home device now.
• When did that event occur and how often have similar incidents happened since? Options: Within the last week, Within the last month, Several times in the last year, A single incident older than a year, Ongoing issue
• Who in your household was most affected and who would use the device day to day? Options: Me alone, Partner or spouse, Shared among adults, Teen or child, Caregiver or outside person, Other
• Which single outcome would make you feel this purchase was a clear success at three months? Options: Reliable remote access, Fewer false alerts, Clear improvement in safety, Lower energy costs, Simple hands off operation, Other
• Describe how checking in on your home currently feels, for example smooth, frustrating, or unreliable.
• Select the primary trigger that started your interest in one device today. Options: Package theft or porch incident, Suspicious activity nearby, Break in scare, High energy bill, Curiosity about home automation, Other
• If nothing changed, name the most important consequence you expect over the next year.

When the App or Voice Is Your Only Way In

• If your internet went out right now, which essential tasks would stop working and cause the most immediate disruption?
• How often do you try to control devices remotely during a typical weekday? Options: Multiple times per day, Once per day, A few times per week, Rarely, Never
• Walk me through the last time you tried to view a camera feed or use voice controls from work, what happened step by step?
• Which devices in your home would you call critical for safety or comfort, and why? Options: Door lock, Doorbell camera, Indoor cameras, Smart speaker, Thermostat, Smart lighting, Other
• Who else needs access to live feeds, automations, or alerts and what level of control should they have? Options: Full control, View only, Notification only, No external access, Other
• Select the top reliability concern that most worries you for remote control. Options: App crashes or freezes, Slow or delayed notifications, Cloud outage that stops features, Local voice stops working during outage, Battery or connectivity dropouts
• Name one device failure that would make you stop adding devices to this system.

Privacy, Listening, and the Moments You Worry About

• Imagine a camera recorded a private conversation by accident, how would that change your willingness to use cameras in the house?
• On a scale from 1 to 5, how concerned are you about microphones or cameras recording when you expect privacy? Options: 4, 1, 2, 3, 5
• List the rooms or spaces where you would not accept cameras or always on microphones.
• Would you prefer controls that let you pause recording, opt out of cloud storage, or anonymize data, or a combination? Options: Pause recording locally, Disable cloud uploads, Scheduled privacy modes, Physical mute or cover, Granular sharing controls, Combination, Other
• Choose the privacy features that would make you comfortable using cameras and voice devices in your home. Options: Local only processing, End to end encryption, User controlled deletion, No persistent audio storage, Access audit logs, Timed auto delete
• What single privacy guarantee would make you sign a purchase that otherwise feels risky?

Household Realities That Break Promises

• When power outages, pets, or children interact with devices, where do things usually go wrong in your home?
• How stable is your home Wi Fi and where in the house does signal drop most often? Options: Very stable everywhere, Mostly stable with occasional drops, Intermittent in parts of the house, Unstable across most rooms, I do not have Wi Fi
• Tell me who in your household typically handles device or network troubleshooting and how confident they are. Options: Very confident, Somewhat confident, Not confident, No one identified
• Pick any physical characteristics of your home that will affect device placement. Options: Single level home, Multi story home, Thick walls or concrete, Large property with outbuildings, Apartment or condo, Shared building
• Estimate how many hours per month you would tolerate spending on setup or maintenance before it feels like too much. Options: Less than 1 hour, 1 to 2 hours, 2 to 4 hours, More than 4 hours
• Name a single household limitation that would prevent this from moving forward.

Who Decides, and Who Needs a Say

• Identify the person in your household who must approve this purchase and the most likely reason they might say no. Options: Homeowner, Partner or spouse, Joint decision, Property manager, Landlord, Other
• Describe your typical decision process for home technology purchases, including timeframes and who signs off.
• Pick any external stakeholders who must be involved before installation. Options: Partner or spouse, Teen or child with access, Landlord, Property manager, Neighbor with shared access, Caregiver
• Explain what proof or evidence would convince the person who controls billing that the cost is justified.
• By when does the critical approver need to be convinced for this to fit your timeline? Options: Immediately, Within 2 weeks, Within 1 month, This quarter, No fixed deadline

The Alternatives You Are Seriously Considering

• What would have to be true about your current setup for you to keep it instead of buying new devices?
• List the other options you are evaluating, including retail displays, other brands, or DIY mixes.
• Choose the most attractive aspect of the alternative you are considering. Options: Lower upfront cost, No cloud dependency, Stronger privacy controls, Works with current devices, Professional install included, Brand familiarity
• Has anyone on your side proposed solving this with a do it yourself approach instead of an outside vendor or platform? Options: Yes, household DIY, Yes, local installer proposed, No one proposed DIY, Other
• Identify the one benefit that would make you keep the current option rather than switch today.

Practical Readiness and Technical Constraints

• Provide a list of systems such as your router, security panel, HVAC controller, or third party services that would need to connect but currently cannot.
• Mark any integration constraints that apply from this list. Options: No API access, Vendor requires proprietary cloud, No guest Wi Fi network, Locked panels or proprietary wiring, ISP blocks certain services, Other
• Explain the technical skills someone at your home would need to support a multi device setup, for example changing router settings or applying firmware updates.
• Mark who would own ongoing support after installation. Options: Homeowner, Spouse or family member, Property manager, Paid support plan, No one identified
• Is there any regulatory, landlord, or HOA rule that would prevent installation of cameras, speakers, or door sensors? Options: Yes HOA restrictions, Yes landlord restrictions, Yes local privacy rules, No known restrictions, Unsure

The Proof You Need Before You Buy More

• State the exact metric you would use to decide a 30 day pilot succeeded, for example fewer than two missed notifications per week or voice response under 400 milliseconds.
• Provide the acceptance tests you would require in your home, for example offline voice response, doorbell motion reliability, or thermostat hold accuracy.
• Please indicate a timeframe for a proof of concept that fits your schedule. Options: 1 week trial, 2 week trial, 1 month pilot, 3 month pilot, Unsure
• Would you accept a pilot that runs only local processing without cloud features during the test? Options: Yes, Maybe, No
• Check any outcomes that would lead you to buy more devices immediately after the pilot. Options: Reliable live view under 2 seconds, Offline voice control works, Privacy controls meet expectations, Automations trigger without internet, Partner approval achieved, Reduced energy usage
• Assuming the pilot meets those criteria, what obstacle or approval would still keep you from signing the week after?

Practical Next Steps and Timing

• Suppose we could deliver a working pilot in your home within two weeks, would you be ready to proceed? Options: Yes ready, Maybe with notice, No not ready
• Indicate your preferred contact method for scheduling, for example phone, email, or a household coordinator. Options: Phone, Email, Text message, Household coordinator, Other
• By when would you like the pilot to start? Options: Within 1 week, Within 2 weeks, Within 1 month, No hurry
• Point to the obstacle that, if unresolved, would stop us from scheduling a pilot this quarter.

• Connected Home Experience Session

• Confirm the current state and its cost
• You confirm the demonstrated local voice behavior and simulated outage maintain control to the level you need.
• Run a tailored reliability test on the buyer's network and deliver a short report showing latency and offline-voice performance before the next session.
• Provide a recommended device expansion plan for the buyer's home layout, showing which features require cloud services and which run on-device.
• Run your real-scenario reliability check
• You confirm the privacy settings map to household roles and scenarios and that the defaults are acceptable or identify required changes.
• Simulate an internet outage and validate offline voice behavior
• You confirm that the cloud-fallback and on-device option descriptions reduce the risk of device obsolescence enough to consider additional purchases.
• Confirm the list of household members and preliminary privacy preferences to use as test scenarios in the follow-up session.
• Walk through privacy controls with your scenarios
• Show cloud-fallback and device-add choices
• Validate this maps to your needs

• Connected Home Experience Session
• Connected Home Experience Deck
• Solution Brief — Connected Home Experience

• meeting
• slides
• document

• Ship starter device and accessory kit
• Provision account and secure device registration
• Activate mobile app and voice assistant
• Guided app-based self-install walkthrough
• Pair and configure doorbell or security camera
• Install and configure smart speaker local voice
• Install and configure smart thermostat
• Install and configure smart lock
• Configure indoor and outdoor lighting scenes
• Enable cross-device automation routines
• Enable offline local-control fallback
• Set privacy controls and local storage options
• Connect existing third-party smart devices
• Enable remote alerts and live notifications

• Purchase Order Confirmation
• Cloud Service Subscription Agreement
• Limited Product Warranty
• Privacy Preferences & Consent Record
• Cloud-Fallback & Service Continuity Addendum
• Support & Maintenance Terms
• Returns, Refunds & Cancellation Policy

Environments & Endpoints

• Deployment instance name for the buyer-facing app (enter a short label used to name the provisioning bundle; Default: home-1)
• Primary deployment region for provisioning and OTA checks (Default: us-east-1) Options: us-east-1, us-west-2, eu-west-1, ap-southeast-1, Other (specify next)

Account & Onboarding

• Default buyer account creation method during onboarding (Default: In-app email account) Options: In-app email account, Buyer self-serve via OIDC IdP, Buyer self-serve via SAML IdP
• If using OIDC or SAML, provide the IdP issuer URL (format: https://... ). Leave blank if not applicable.
• Default username prefix to create local homeowner accounts (used to generate device owner usernames; Default: homeowner_)

Network & Device Provisioning Defaults

• Default Wi‑Fi SSID buyers will use for initial device provisioning (enter exact SSID to validate provisioning flows)
• Default local LAN DHCP range to validate offline control during verification (format: CIDR; Default: 192.168.1.0/24)
• Default local device hostname prefix assigned during setup (Default: ch-device)

Privacy Defaults & Data Retention

• Default camera/microphone recording mode at first boot (Default: On-device-by-default with opt-in cloud upload) Options: On-device-only (local storage only), On-device-by-default with opt-in cloud upload, Cloud-enabled (upload recordings by default), Disabled (no recording enabled)
• Default retention period for local recordings (days) (Default: 7)

Local-Fallback, Offline Voice & Verification

• Enable local (edge) voice processing capability during offline mode? (Default: Yes) Options: Yes, No
• Offline voice-command latency acceptance threshold for the buyer acceptance test (milliseconds) (Default: 400)
• Number of representative rooms/devices the buyer will include in the acceptance test (Default: 3)

Credentials Handoff & Non-Secret Exchange

• Owner of the integration identifiers needed at provisioning (choose one) (Default: Buyer homeowner) Options: Buyer homeowner, Buyer IT contact, Seller representative, Platform support team
• Channel to exchange non-secret identifiers and the mechanism to deliver secrets at kickoff (choose one; secrets themselves are not uploaded here) (Default: Your secrets manager) Options: Your secrets manager (e.g., your secrets manager), Platform secure upload portal, Encrypted email via buyer IT, Other (specify next)
• If you selected Other for exchange channel, specify the exact channel name (enter the channel identifier)

• Go-live health check (async)
• First measurement checkpoint (async, weeks 4-10)
• Acceptance gate decision (async, around day 90)
• Ongoing quarterly success checkpoint (async)

• Publish the firmware rollout calendar and expected impact notes for customer review before the next quarter.
• Restate acceptance criteria and numeric targets
• Obtain a documented acceptance decision from the buyer in the shared workspace, based on the outcomes versus targets recorded in Solution Scope.
• For any failed acceptance criteria, capture a remediation plan with explicit tasks and resolution dates.
• Schedule the follow-up verification checkpoint for any remediations within the agreed timeframe.
• Publish the formal acceptance record or documented rejection with remediation items to the shared workspace.
• Create remediation backlog items for each failed criterion with target resolution dates and verification steps.
• If all criteria passed, mark the accepted deliverable as operational and enable the ongoing success cadence.
• Trend review of core metrics
• Confirm that device online reliability rate remains within the acceptable band and that the number of privacy incidents is stable or declining.
• Clear or re-prioritize any persistent tickets and confirm the firmware rollout plan for the next quarter.
• Verify that any legacy system decommission tasks are on track or formally closed to avoid dual-operation.
• Publish the quarterly metric snapshot and a short narrative of any variance from targets recorded in Solution Scope.
• Open or re-prioritize operational tickets for persistent issues and enhancement requests, including target verification steps.
• Re-confirm agreed success criteria and owners (deployment-level)
• Confirm that every shipped device is installed and reports basic health, or list the devices that are not and why.
• Produce a prioritized list of open blockers with owners and target resolution dates.
• Verify local-fallback voice behavior is demonstrably active on at least one installed speaker or the documented remediation plan is in place.
• Publish deployment validation report with serial numbers and connectivity status to the shared workspace.
• Create remediation tickets for each open blocker, including reproduction steps and target resolution dates.
• Collect sample logs showing local voice response and attach them to the deployment report for verification.
• Present first-period metrics against Solution Scope targets
• Determine whether device online reliability rate and automation success rate are trending to the targets recorded in Solution Scope.
• Agree a time-bound remediation plan for any metric outside the acceptable band, including the next verification checkpoint.
• Attach the supporting evidence and logs needed for the acceptance gate review.
• Publish the metric dashboard export and annotated root-cause evidence to the shared workspace.
• Schedule and publish a firmware rollout plan or automation rule updates with target verification dates.
• Document any required customer-side changes, such as router settings or guest account configuration, and provide step-by-step instructions.
• Present outcome data against each criterion
• Diagnose gaps and root causes
• Deployment and device validation
• Open persistent issues and enhancement requests
• Firmware and software update inventory
• Early adoption signals and usage patterns
• Document pass/fail and buyer decision
• Agree corrective actions and timelines
• Legacy system decommission status
• Open issues and blockers
• Confirm timeline to acceptance gate
• Agree remediation plan and next verification step
• Agree operational actions for the quarter
• Agree immediate remediation actions