Zoho Premium Partner
25 September 2026
Valid until 25 October 2026
Zoho CRM Implementation
for Glydus.
The requirement work is done. Your v5 specification, our working sessions and your follow-up documents now describe one commercial system covering both sales verticals, four routes to market in each, the SAP Business One handoff and the analytics your leadership asked for. This proposal prices that system in full, as a fixed price.
GMG Technotrades Pvt. Ltd.
Hingna MIDC, Nagpur
Steering Systems Sales CRM
Requirement Document v2.1
Rede Corporativa
+91 79996 45921
What this build now covers
The scope grew because the requirement work did its job. Ten things are now specified that the original brief left open — each one is built into the numbers in Section 06.
Outboard and Inboard, one business and one CRM. Segment tags — Outboard, Inboard Standard, Inboard Custom — are multi-select and drive ownership; a single account can carry all three.
Distributors under contract, end customers, OEMs and engine dealers with trials, and commission-based consultants — plus shipyards, channel partners, naval architects and government tenders on the Inboard side.
A contracted customer can send a requirement — often part numbers or an Excel — and go straight to a PI. The pipeline has to allow that without losing the commercial record.
Open with a Request Date, Forecasted or Released, Promise Date from production, linked production order, Ready for Dispatch, partial dispatch, closure — mirrored read-only in CRM.
The chase starts a week before the Promise Date, the accounts team confirms receipt, and only then does the order move to dispatched. Payment terms are tagged on every order.
Annual committed volume, staggered through the year, exclusivity, and a renewal review at month 10 driven by committed-versus-actual performance.
No GA drawing and rudder dimensions, no quotation. Torque calculation and steering selection become a rule set rather than a call to the factory.
The GeM portal has no integration path, so the tender flow runs in CRM as a reminder-driven process with technical qualification ahead of the commercial bid.
Exhibition lists imported and mass-mailed, four outbound channels tracked, and the nurture cadence for leads past the follow-up cap.
Committed versus actual per distributor, purchase history by year and forward projections — the strategic view that was asked for directly.
How information moves
One commercial record from capture to dispatch, one write into SAP, and everything operational coming back read-only. Every flow in detail — leads, quotes, orders, SAP and support — is in your requirement document at glydus-requirement-doc.pages.dev.
Scope by workstream
Seven workstreams. The hours against each are the same numbers that make up the total in Section 06.
Built on Zoho One
Zoho OneThe licence that covers every app below, for all your staff — no per-app decisions.
Zoho CRMLeads, accounts, the sales pipeline, quotes, PIs, contracts and the SAP bridge.
Zoho DeskComplaints and technical queries, turnaround targets and the knowledge base.
Zoho CampaignsExhibition mailers, outbound campaigns and the nurture cadence.
Zoho AnalyticsDistributor performance, sales against target and support dashboards.
Zoho FormsThe Customer Initiation Form and complaint form, feeding straight into the record.
The workstreams
CRM core & configuration70 h- Zoho One org, users, roles and profiles; territory model (Europe, Southeast Asia and the rest) driving lead and account ownership.
- Leads, Accounts, Contacts, Deals and the custom objects: Contract, Referred Lead, Trial, Tender.
- Segment tags (Outboard / Inboard Standard / Inboard Custom) as a mandatory multi-select that drives ownership and reporting; customer-type master covering distributor, end customer, OEM / engine dealer, channel partner, shipyard, consultant and tender.
- Sales pipeline as a Blueprint: qualified lead through quote (skippable for contracted customers), optional trial, confirmation, PI and dispatch — with the gates enforced, not advisory.
- Lead-to-account conversion on first order, with ownership handover and the CRM record replacing the manual handover document.
- Duplicate control, Excel bulk import with validation, list views and layout rules per vertical.
Quotes, contracts & documents30 h- Outboard and Inboard quote templates rebuilt from your own documents, with versioning and send-from-CRM.
- Price books: distributor contracted pricing and standard lists; quote lines drawn from the SAP material master.
- Quote-to-PI data carry-through, so the confirmed quote becomes the PI without the costing sheet being rebuilt by hand.
- Contract records for distributors and inboard channel partners: annual committed volume, staggered schedule, exclusivity clause, renewal review at month 10.
- Customer Initiation Form and the complaint form rebuilt as Zoho forms so submissions land on the record rather than in a separate inbox.
SAP Business One integration50 h- Create PI from CRM through the B1 Service Layer — salesperson-triggered after validation, never silent.
- Master-data validation before the call: customer code, item codes, quantity, price, currency and terms.
- Correlation ID on every call so a retried PI can never duplicate; errors surfaced with retry and resolve actions.
- Read-back of the PI lifecycle: Request Date, Forecasted / Released, Promise Date, linked production order, Ready for Dispatch, partial dispatch quantities and closure.
- Secure network path from Zoho to the B1 server, and an integration user with its own credentials.
- Production, BOM and the packing list stay inside SAP — CRM never writes an operational status it did not receive.
Engagement, campaigns & rules32 h- Engagement engine on a working-day calendar: importance-driven cadence, the seven-to-eight touch cap, then the marketing-nurture state.
- Bulk email for exhibition lists and outbound campaigns, with the low-frequency awareness cadence for non-responders.
- Trial follow-up automation — a task roughly every twenty days until the outcome is recorded.
- Distributor referral tracking: referred leads by name on the distributor account, follow-up prompts and closure with outcome and reason.
- Contract renewal trigger at month 10, and the annual activity checklist (seven to twelve items) auto-populating each account owner's queue.
- Payment-chase automation from the Promise Date, through the accounts-team confirmation, to dispatch.
Analytics & dashboards40 h- Distributor performance: committed versus actual volume for the contract year, purchase history by year and forward projections for the next one to three years.
- Sales against target by vertical, territory and owner, with the target basis agreed and configured.
- Pipeline, conversion, quote win ratio by count and value, and engagement mix.
- Referred-lead follow-through per distributor, complaint and technical-query turnaround, and PI creation turnaround.
- Personal dashboards plus manager-published shared dashboards, every card drilling through to the underlying records.
Support — Desk, complaints & technical queries22 h- Two departments with their own layouts, turnaround targets and ownership.
- Intake from the website form, WhatsApp and email, with the manual complaint-versus-query classification the team asked for.
- Standardised complaint form routed to the factory by email, since the factory stays outside the CRM, with root-cause and resolution capture on return.
- Knowledge base seeded from your historical query emails, FAQs and installation guides, with approved answers suggested on similar questions.
- Support history visible on the account, and sales records visible to support.
Meetings, data migration, UAT, training & handover16 h- Weekly review calls throughout the build, plus working sessions for design sign-off, the SAP partner hand-off and go-live readiness.
- One migration pass of accounts, contacts and open enquiries from your existing files.
- User acceptance testing with your team, against the scenarios in the requirement document.
- Two training sessions — sales and administrator — and written administrator documentation.
- Two weeks of hypercare after go-live.
The SAP Business One integration
Your landscape is the best case: Business One 10.0 on SQL with the Service Layer enabled — a modern REST interface, already switched on.
| What CRM writes | One thing only: the PI, created through the Service Layer when a salesperson clicks Create PI after validating the confirmed order. Master data — customer code, item codes, quantity, price, currency, terms — is checked before the call is made. |
| Duplicate safety | Every call carries a correlation ID linking the confirmation, the quote and the PI. A retry reuses the same ID, so a failed call can never produce two PIs. |
| What CRM reads back | Request Date, Forecasted or Released, Promise Date, the linked production order and its status, Ready for Dispatch, dispatched versus remaining quantity, and closure. |
| What stays in SAP | BOM, production orders, the packing list and every operational status. CRM displays them; it never writes them. |
| The one open item | Network reach. The Service Layer listens on your server; Zoho's cloud has to be able to reach it. Either your IT partner publishes it over HTTPS with a valid certificate, or we put a secure outbound tunnel on the B1 server — no inbound firewall opening, proper TLS, and a service token on every call. We settle this in the first working session with your SAP partner. |
Included and excluded
Included
- Everything in the seven workstreams in Section 03
- Zoho One setup — users, roles, profiles, territories, sharing rules
- SAP Business One PI creation and lifecycle sync through the Service Layer
- Outlook / Microsoft 365 and WhatsApp Business timeline logging
- Zoho Desk for complaints and technical queries, with the knowledge base seeded
- Zoho Analytics dashboards including the distributor performance view
- Bulk email and campaign setup for exhibitions and outbound
- Customer Initiation Form and complaint form rebuilt as Zoho forms
- Weekly review calls and working sessions through the build
- One-pass data migration, UAT support, two training sessions, written documentation
- Two weeks of post-go-live hypercare
Not included
- Zoho subscription licence fees — billed directly by Zoho to Glydus
- Any development, configuration or licensing inside SAP itself, and the B1 integration user licence
- GeM portal integration — no interface exists; the tender flow is reminder-driven in CRM
- WhatsApp Business API provisioning fees and Meta template charges
- Back-population of email or WhatsApp history from before go-live
- A distributor-facing or customer-facing external portal
- Commission calculation and payout processing for consultants and agents
- Zoho Books, GST e-invoicing and accounting workflows
- A custom mobile application beyond Zoho's standard apps
- Support beyond the two-week hypercare window — available as a separate retainer
Effort and investment
A fixed price, built from 260 hours at ₹1,800 per hour. It covers solution design, project management, written documentation, training and hypercare.
| Workstream | Hours | ₹ |
|---|---|---|
| CRM core & configuration | 70 | ₹1,26,000 |
| Quotes, contracts & documents | 30 | ₹54,000 |
| SAP Business One integration | 50 | ₹90,000 |
| Engagement, campaigns & rules | 32 | ₹57,600 |
| Analytics & dashboards | 40 | ₹72,000 |
| Support — Desk, complaints & technical queries | 22 | ₹39,600 |
| Meetings, data migration, UAT, training & handover | 16 | ₹28,800 |
| Fixed price | 260 | ₹4,68,000 |
Fixed for the scope in Sections 03 and 05. Exclusive of GST. Zoho subscription licences are additional and billed directly by Zoho to Glydus. Two weeks of hypercare are included at no extra cost.
How it is paid — advance recharge
The build is fixed at 260 hours. You fund it in advance by recharging hours in blocks of 50, 100 or 200 — any mix that reaches 260 — or all 260 at once, all at the same ₹1,800 rate. Hours are drawn down as work is delivered and reported to you every week. Anything left on the balance after go-live stays available for changes and support.
For example, the full 260 at kick-off, or 200 at kick-off and 100 before go-live — the 40 hours left over stay on your balance for changes and support. The first recharge starts the work; top up before the balance runs out.
What would change it
Only scope beyond Sections 03 and 05 — for example a steering calculator, a link to SAP receivables, a customer portal, commission processing or accounting workflows. Anything like that is estimated separately and agreed in writing before work begins.
Two to three months to go-live
The commercial core comes first so the team can start using it; the integration and analytics follow against a system already in daily use. Go-live lands between month two and month three, depending mainly on how quickly SAP access is arranged.
Zoho One org, users, roles, territories. Modules, fields and layouts for both verticals. Segment tags, customer types and the pipeline Blueprint with its gates. Roles, territories and rule sets configured as they arrive.
Capture and qualification, engagement engine, referral tracking. Quote templates, price books and the quote-to-PI carry-through. Distributor contracts with the month-10 review. Order flow with manual PI entry and the payment-before-dispatch chain.
Create PI through the Service Layer, lifecycle read-back, error handling and retry. Desk departments, complaint routing to the factory, technical queries and the seeded knowledge base.
Distributor performance, sales against target, pipeline and support dashboards. Bulk email, exhibition imports and the nurture cadence.
Data migrated and validated, acceptance testing with your team, corrections applied, two training sessions delivered, documentation handed over and the system taken live.
Two weeks of priority response on live issues and usage questions while the team settles in.
Commercial terms
| Validity | This proposal is valid for 30 days from 25 September 2026 and supersedes proposal RC-2026-GLY-01, which covered a narrower first phase. |
| Ownership | Glydus owns the Zoho subscription, all data and all configuration from day one. Full administrator access is provided at the start of the engagement, not at the end. |
| Documentation | The requirement document is already yours. Written administrator documentation covering the schema, Blueprint rules, Deluge functions and integration setup is handed over at go-live. |
| Communication | A dedicated WhatsApp group with your key users and a weekly review call. A single point of contact throughout — you will not be passed between people. |
| Change control | Requests outside the scope in Sections 03 and 05 are estimated in hours at the same rate and confirmed in writing before work begins. |
| Dependencies | A working session with your SAP partner early in the build, to settle network access and the integration user. Remaining inputs are collected as we go; late inputs move the schedule, not the price. |
| Taxes | All amounts are exclusive of GST, which will be charged at the applicable rate. |