# Client handover guide

Updated 25 October 2026 · Gautam Singh · gautamk1512@gmail.com.

## What the client receives

Provide the production HTTPS website address, their own account and the public user guide. Let the client set their own password. Share supported features, connected markets and known delayed/unavailable feeds. Do not supply source, environment files, server/admin credentials, provider keys or the WhatsApp pairing session.

An in-person preview can use your own computer. A localhost/127.0.0.1 address does not work on a remote client's computer. Remote access needs a separately prepared hosted deployment; a development server is not a hosting service.

## Before the meeting

1. Test the actual hosted address, HTTPS, login/logout and provider availability. Keep administrator screens out of the client session.
2. Compare a quote with the same source, symbol, currency, contract, interval and event time. Do not call every market live while required NSE/BSE/MCX entitlements are absent.
3. Confirm operator/contact details and published Terms, Privacy, Risk and Grievance notices. Arrange legal review of the real business, data processing, market-data permissions and commercial offering before launch. Policy pages alone do not certify compliance.
4. Confirm the intended audience and India-appropriate products. Do not imply that an offshore broker or AI signal establishes regulatory authorisation.
5. Use a dedicated demo account without other users' personal information or private management links. Do not approve or message unconsenting recipients for demonstration.
6. Keep signal email off until Zoho is configured and explicitly enabled. Pair WhatsApp and verify a fresh eligible event before claiming actual delivery.

## Ten-minute walkthrough

- Homepage: explain sources, data freshness, Smart Money preview and signup.
- India Desk: show reference sessions, FII/DII/OI/PCR availability, ban/calendar sources and the rupee calculator.
- Chart: choose an exact venue/instrument; describe structure/FVGs as analysis.
- Strategy Lab: run supported rules against real history with fees/slippage. Show losses as well as gains; do not pitch a backtest as guaranteed performance.
- Subscription: show Pending approval and stopping alerts. Follow the real approval/consent process for actual users.
- Policies/support: show grievance contact and privacy choices.

## Acceptance record

Record client/account, date, hosted URL, enabled features, connected providers, delayed/unavailable feeds, notification channels, support contact and open issues. Do not record passwords or API secrets. Confirm what is research, simulation and an actual integration.

Check login/logout, public policy links, calculator invalid inputs, quote source/time, unavailable-feed behaviour, approval gating and duplicate suppression. Verify actual WhatsApp delivery separately from API acceptance. Confirm public downloads contain only the client workflow illustration and no internal infrastructure references.

## After handover

The operator retains responsibility for hosting, backups, renewals/entitlements, administration, incident response and verified correction/deletion requests. Agree support hours and commercial terms separately; no unimplemented SLA is promised here.

Keep operator documentation in restricted storage with a private backup. Sanitising README and hosted downloads does not remove old public Git commits, previously distributed copies or other tracked technical files. Restrict repository access before treating source as confidential. This work does not change repository visibility or erase history.


## Presentation route

Start at `/docs` for the ten-minute presenter script and model workflow image. Use the browser Print / Save PDF command to share a handout. Then visit the homepage, Smart Money, India Desk, one chart and Strategy Lab in that order. Keep admin and provider configuration in a separate unshared browser profile. The client guide explains both models, source differences, feed pauses, asset approval and active-signal tracking.