<h2 class="compact-content-heading">A transparent path from <span class="handbook-highlight-pink">first call to go-live</span>.</h2>
<p class="compact-content-paragraph">ERP implementation is a <span class="handbook-highlight-blue">partnership</span>, and success depends on both sides. We do not sell aggressively; we guide you through a <span class="handbook-highlight-black">structured, fully transparent onboarding process</span> so you can decide on the <span class="handbook-highlight-black">merits, risks, and benefits</span>.</p>
<div class="handbook-onboarding-metric-cards">
<div class="handbook-metric-card"><strong>30-50</strong><span>page detailed scope document</span></div>
<div class="handbook-metric-card"><strong>8</strong><span>structured kickoff alignment areas</span></div>
<div class="handbook-metric-card"><strong>100%</strong><span>milestone-based transparency</span></div>
<div class="handbook-metric-card"><strong>24/7</strong><span>global post go-live support</span></div>
</div>
<h3 class="compact-content-heading">We Begin Work Together</h3>
<h4 class="compact-content-heading">The right partnership beats the hard sell.</h4>
<p class="compact-content-paragraph">We're <span class="handbook-highlight-black">selective on purpose</span>. The clients who get the most from ERPNext share a few traits, and we'd rather set that expectation <span class="handbook-highlight-blue">honestly</span> than oversell.</p>
<table class="handbook-onboarding-partnership-table"><tbody>
<tr><th>#</th><th>Partnership Trait</th></tr>
<tr><td>01</td><td><span class="handbook-service-name">Eager to improve:</span> We only work with customers who genuinely want to improve their organization through ERPNext, not just check a box.</td></tr>
<tr><td>02</td><td><span class="handbook-service-name">Aligned leadership:</span> Ideal clients have leadership that's hands-on, aligned bottom-to-top, and committed to the implementation journey.</td></tr>
<tr><td>03</td><td><span class="handbook-service-name">Decide on the merits:</span> No pressure. We walk you through a transparent process so you can weigh the merits, risks, and benefits and decide for yourself.</td></tr>
</tbody></table>
<h3 class="compact-content-heading">Pre-Sales to Project Handover</h3>
<h4 class="compact-content-heading">From the first call to a fully briefed delivery team.</h4>
<p class="compact-content-paragraph">Before any work begins, we <span class="handbook-highlight-blue">set expectations on the call</span>, understand your business, and hand the project to delivery with <span class="handbook-highlight-black">everything they need to scope it properly</span>.</p>
<div class="handbook-onboarding-timeline">
<div class="handbook-onboarding-timeline-item">
<div class="handbook-onboarding-timeline-index">1</div>
<div class="handbook-onboarding-timeline-content">
<span>Pre-Sales</span>
<h3>Setting the expectation</h3>
<p>The first call sets the expectation for the conversation itself — what we'll cover, what we need from you, and what you can expect from us.</p>
</div>
</div>
<div class="handbook-onboarding-timeline-item">
<div class="handbook-onboarding-timeline-index">2</div>
<div class="handbook-onboarding-timeline-content">
<span>Discovery</span>
<h3>Let's take a look at your business</h3>
<p>We dig into how your business runs today so the conversation is grounded in your real processes — not generic ERP talking points.</p>
</div>
</div>
<div class="handbook-onboarding-timeline-item">
<div class="handbook-onboarding-timeline-index">3</div>
<div class="handbook-onboarding-timeline-content">
<span>Handover Package</span>
<h3>A clean handover to delivery</h3>
<p>The signed proposal, approved scope, initial BRD draft, key client contacts, commercial terms, SLA expectations, and any demo recordings all move together to the project team.</p>
</div>
</div>
<div class="handbook-onboarding-timeline-item">
<div class="handbook-onboarding-timeline-index">4</div>
<div class="handbook-onboarding-timeline-content">
<span>Purpose-Built for ERPNext</span>
<h3>Implementation-ready detail</h3>
<p>The handover includes module-wise requirements, custom feature requests, integration notes such as e-commerce, payroll, or POS, and known data-migration constraints.</p>
</div>
</div>
<div class="handbook-onboarding-timeline-item">
<div class="handbook-onboarding-timeline-index">5</div>
<div class="handbook-onboarding-timeline-content">
<span>Outcome</span>
<h3>Ready to scope, day one</h3>
<p>The project team starts with a CRM intake record, the client's completed questionnaire, and direct access to the primary decision-makers to begin detailed scoping immediately.</p>
</div>
</div>
</div>
<img class="handbook-certificate-image" src="/files/service-agreement.png" width="485" height="782" alt="Service agreement step before project kickoff" />
<img class="handbook-certificate-image" src="/files/detailed-scop-work.png" width="475" height="701" alt="Detailed scope of work step before project kickoff" />
<h3 class="compact-content-heading">Project Kickoff Meeting</h3>
<h4 class="compact-content-heading">One meeting that aligns everyone on the same plan.</h4>
<p class="compact-content-paragraph">The kickoff formally initiates the project, aligning every stakeholder on <span class="handbook-highlight-blue">scope, expectations, timelines</span>, and ways of working before execution begins.</p>
<div class="handbook-onboarding-kickoff-table">
<div class="handbook-onboarding-kickoff-header">
<span>What's Covered</span>
<strong>8 alignment areas</strong>
</div>
<table><tbody>
<tr><th>#</th><th>Kickoff Discussion Area</th></tr>
<tr><td>1</td><td>Project objectives, success criteria, and expected outcomes</td></tr>
<tr><td>2</td><td>Confirmed scope, modules, and implementation approach</td></tr>
<tr><td>3</td><td>Project plan, phases, milestones, and timelines</td></tr>
<tr><td>4</td><td>Team structure, roles, and responsibilities (both client and Hybrowlabs)</td></tr>
<tr><td>5</td><td>Communication plan (channels, frequency, escalation matrix)</td></tr>
<tr><td>6</td><td>Governance model and reporting cadence</td></tr>
<tr><td>7</td><td>Key risks, assumptions, and dependencies</td></tr>
<tr><td>8</td><td>Next steps and immediate action items</td></tr>
</tbody></table>
</div>
<div class="handbook-onboarding-kickoff-table">
<div class="handbook-onboarding-kickoff-header">
<span>Who Attends</span>
<strong>5 participant groups</strong>
</div>
<table><tbody>
<tr><th>#</th><th>Participant</th></tr>
<tr><td>1</td><td>Client stakeholders (business owners, process owners, IT/ops leads)</td></tr>
<tr><td>2</td><td>Hybrowlabs Project Manager</td></tr>
<tr><td>3</td><td>Functional Consultant / Business Analyst</td></tr>
<tr><td>4</td><td>Technical Lead (as needed)</td></tr>
<tr><td>5</td><td>Key delivery team members (optional based on project size)</td></tr>
</tbody></table>
</div>
<div class="handbook-onboarding-kickoff-summary">
<div class="handbook-onboarding-kickoff-summary-card">
<span>Duration</span>
<strong>60-90 minutes</strong>
<p>For standard projects. Larger or multi-entity implementations can extend to 2-3 hours.</p>
</div>
<div class="handbook-onboarding-kickoff-summary-card">
<span>Outcome</span>
<strong>A shared, clean plan</strong>
<p>Everyone leaves with the same understanding of the <span class="handbook-highlight-pink">plan, roles, and expectations</span>, ensuring a smooth transition into execution.</p>
</div>
</div>
<h3 class="compact-content-heading">Stakeholder Mapping</h3>
<h4 class="compact-content-heading">We map the people, so decisions never stall.</h4>
<p class="compact-content-paragraph">Clear stakeholder mapping ensures <span class="handbook-highlight-black">accountability</span>, <span class="handbook-highlight-pink">faster approvals</span>, and smoother collaboration, reducing project risk and improving delivery efficiency.</p>
<table><tbody>
<tr><th>#</th><th>What We Do</th></tr>
<tr><td>1</td><td>Identify key stakeholders across functions such as Finance, Operations, Sales, and IT.</td></tr>
<tr><td>2</td><td>Define roles and responsibilities for each stakeholder in the project lifecycle.</td></tr>
<tr><td>3</td><td>Establish a clear decision-making hierarchy to avoid delays.</td></tr>
<tr><td>4</td><td>Map primary points of contact for day-to-day coordination.</td></tr>
<tr><td>5</td><td>Create an escalation matrix for issue resolution.</td></tr>
</tbody></table>
<table><tbody>
<tr><th>#</th><th>Roles Identified</th><th>Responsibility</th></tr>
<tr><td>1</td><td>Executive Sponsor</td><td>Provides strategic direction and final approvals</td></tr>
<tr><td>2</td><td>Project Owner / Coordinator</td><td>Main client-side POC driving the project internally</td></tr>
<tr><td>3</td><td>Department / Process Owners</td><td>Provide requirements, validate workflows, and support UAT</td></tr>
<tr><td>4</td><td>IT / Technical Contact</td><td>Handles infrastructure, integrations, and access</td></tr>
</tbody></table>
<table><tbody>
<tr><th>Why It Matters</th></tr>
<tr><td>Clear stakeholder mapping ensures <span class="handbook-highlight-black">accountability</span>, <span class="handbook-highlight-blue">faster approvals</span>, and smoother collaboration, reducing project risks and improving overall delivery efficiency.</td></tr>
</tbody></table>
<h3 class="compact-content-heading">What ERPNext Onboarding Looks Like</h3>
<h4 class="compact-content-heading">Structured, with clear decision points along the way.</h4>
<p class="compact-content-paragraph">Onboarding takes time and care. As your ERP implementation champion, expect a <span class="handbook-highlight-blue">structured process</span> with multiple approvals, clear communication, and <span class="handbook-highlight-black">decision points you control</span>.</p>
<div class="handbook-onboarding-timeline">
<div class="handbook-onboarding-timeline-item">
<div class="handbook-onboarding-timeline-index">1</div>
<div class="handbook-onboarding-timeline-content">
<span>Demos</span>
<h3>Module-Wise Demos</h3>
<p>We demonstrate the ERPNext modules relevant to your business, showing how it handles <span class="handbook-highlight-blue">your processes</span> and where custom solutions may be needed.</p>
</div>
</div>
<div class="handbook-onboarding-timeline-item">
<div class="handbook-onboarding-timeline-index">2</div>
<div class="handbook-onboarding-timeline-content">
<span>Discovery</span>
<h3>Process Introspection</h3>
<p>We discuss your processes, <span class="handbook-highlight-blue">pain points</span>, and priorities, assessing user personas and adoption readiness before recommending next steps.</p>
</div>
</div>
<div class="handbook-onboarding-timeline-item">
<div class="handbook-onboarding-timeline-index">3</div>
<div class="handbook-onboarding-timeline-content">
<span>Scope</span>
<h3>Detailed Scope Document</h3>
<p>Once you're comfortable, we share a <span class="handbook-highlight-blue">detailed scope and legal document</span>, typically 30-50 pages, that forms the foundation of the project agreement.</p>
</div>
</div>
<div class="handbook-onboarding-timeline-item">
<div class="handbook-onboarding-timeline-index">4</div>
<div class="handbook-onboarding-timeline-content">
<span>Approvals</span>
<h3>CRM Intake & Approvals</h3>
<p>Initial details are <span class="handbook-highlight-black">captured, approved, and saved</span> in our CRM. You choose whether to send the proposal or keep it under review before committing.</p>
</div>
</div>
</div>
<h3 class="compact-content-heading">Project Start & Invoicing</h3>
<h4 class="compact-content-heading">When scope is approved, the work begins.</h4>
<p class="compact-content-paragraph">We collect 30-50% in advance to begin your project. This ensures <span class="handbook-highlight-black">mutual commitment</span> and lets us allocate the <span class="handbook-highlight-blue">right ERPNext implementation team</span> to your business from day one.</p>
<h3 class="compact-content-heading">Access Requirements From Clients</h3>
<h4 class="compact-content-heading">What we need from you to start on time.</h4>
<p class="compact-content-paragraph">To ensure a <span class="handbook-highlight-blue">smooth, timely start</span>, Hybrowlabs requires key access, data, and documentation upfront.</p>
<table><tbody>
<tr><th>#</th><th>Requirement Category</th><th>Inputs Needed</th></tr>
<tr><td>1</td><td>System & Infrastructure Access</td><td>Server access (cloud/on-prem) or hosting setup details; <span class="handbook-highlight-blue">domain and DNS access</span> (if applicable); admin credentials for ERPNext (if already installed); access to third-party tools (CRM, eCommerce, payroll, etc. for integrations).</td></tr>
<tr><td>2</td><td>Data & Migration Inputs</td><td>Data exports from existing systems (masters, transactions, opening balances); data templates filled in agreed formats; clarity on <span class="handbook-highlight-blue">data scope</span> (what needs to be migrated vs archived).</td></tr>
<tr><td>3</td><td>Business & Process Documents</td><td>Process flows / SOPs (if available); reports, formats, and <span class="handbook-highlight-black">compliance requirements</span>; Chart of Accounts, item masters, customer/vendor lists, etc.</td></tr>
<tr><td>4</td><td>User & Access Details</td><td>List of users, <span class="handbook-highlight-blue">roles, and permissions</span> required; approval hierarchies and workflows.</td></tr>
<tr><td>5</td><td>Compliance & Configuration Inputs</td><td>Tax structure (GST/VAT), regional settings, currencies; company structure (<span class="handbook-highlight-blue">entities, branches, warehouses</span>).</td></tr>
</tbody></table>
<img class="handbook-wide-image handbook-access-zoom-image" src="/files/access-requirements.jpg" width="1025" height="652" alt="ERPNext access requirements from clients overview" />
<h3 class="compact-content-heading">Communication Setup</h3>
<h4 class="compact-content-heading">Clear channels, from day one.</h4>
<p class="compact-content-paragraph">Every task-level discussion happens on a <span class="handbook-highlight-blue">named project channel</span>, and every scope change runs through a <span class="handbook-highlight-pink">formal change-control workflow</span>.</p>
<table><tbody>
<tr><th>#</th><th>Communication Setup</th></tr>
<tr><td>01</td><td><span class="handbook-service-name">Primary channels:</span> Dedicated <span class="handbook-highlight-blue">WhatsApp group</span> for quick clarifications; email for <span class="handbook-highlight-pink">formal approvals</span>; ticketing/helpdesk for issues and bug tracking.</td></tr>
<tr><td>02</td><td><span class="handbook-service-name">Project tools:</span> Shared project board (Gantt/kanban), document repository, and a <span class="handbook-highlight-pink">dedicated upload link</span> for BRD materials.</td></tr>
<tr><td>03</td><td><span class="handbook-service-name">Best practice:</span> Use the named <span class="handbook-highlight-blue">"ERPNext project communication channel"</span> for all task-level discussions and a formal <span class="handbook-highlight-pink">"ERPNext change control"</span> workflow for scope changes.</td></tr>
</tbody></table>
<h3 class="compact-content-heading">Business Requirements & Document Collection</h3>
<h4 class="compact-content-heading">Secure, traceable, and free of email chaos.</h4>
<p class="compact-content-paragraph">We send a <span class="handbook-highlight-blue">predefined questionnaire</span> to collect everything needed for a detailed BRD and give you a <span class="handbook-highlight-black">dedicated upload link</span> so documents are shared securely.</p>
<ul class="handbook-onboarding-check-list">
<li>A predefined questionnaire captures the details needed for the BRD.</li>
<li>A dedicated upload link replaces messy email attachments.</li>
<li>The result is a clean, traceable onboarding with fewer delays.</li>
</ul>
<h3 class="compact-content-heading">Inside the BRD</h3>
<h4 class="compact-content-heading">A complete picture of your business</h4>
<p class="compact-content-paragraph">Your business requirements, current workflows, operational challenges, ERP process mapping, customisation requirements, approval hierarchies, integrations, and the <span class="handbook-highlight-blue">proposed ERPNext solution design</span>, all in one document.</p>
<img class="handbook-certificate-image" src="/files/business-requirement-1.png" width="532" height="728" alt="Business requirements questionnaire for detailed BRD" />
<img class="handbook-wide-image" src="/files/business-requirment-2.png" width="1025" height="652" alt="Dedicated upload link for secure business requirement document collection" />
<h3 class="compact-content-heading">BRD & Project Tracking</h3>
<h4 class="compact-content-heading">Complete transparency through every milestone.</h4>
<p class="compact-content-paragraph">Progress and implementation milestones are shared continuously through our <span class="handbook-highlight-blue">project-management and task-tracking platform</span>.</p>
<p class="compact-content-paragraph"><strong class="handbook-point-heading">Our ERPNext project tracking system ensures</strong></p>
<ul class="handbook-onboarding-tracking-grid">
<li>Better communication between teams</li>
<li>Clear visibility into progress</li>
<li>Faster issue and task resolution</li>
<li>Structured deployment planning</li>
<li>Improved accountability and timelines</li>
</ul>
<p class="compact-content-paragraph">This collaborative approach helps ensure a <span class="handbook-highlight-blue">smooth, organised, and successful ERPNext implementation</span> for your organization.</p>
<img class="handbook-wide-image handbook-large-detail-image" src="/files/communication-setup-1.png" width="1317" height="816" alt="ERPNext project communication setup overview" />
<img class="handbook-wide-image" src="/files/communication-setup-2.png" width="790" height="812" alt="ERPNext communication channel and project setup details" />
<img class="handbook-wide-image" src="/files/BRD-project-1.png" width="1025" height="652" alt="BRD and ERPNext project tracking overview" />
<h3 class="compact-content-heading">Approvals, Billing, Support & Handover</h3>
<h4 class="compact-content-heading">The questions every buyer asks, answered upfront.</h4>
<table><tbody>
<tr><th>Your Question</th><th>Our Answer</th></tr>
<tr><td>How do we take sign-off?</td><td>We collect <span class="handbook-highlight-black">formal approvals</span> at key milestones, including requirements sign-off, design acceptance, and final UAT completion.</td></tr>
<tr><td>How will we bill you?</td><td>Billing is <span class="handbook-highlight-blue">milestone-based</span>, with advance payment, periodic invoices, and agreed release criteria.</td></tr>
<tr><td>How will we support it?</td><td><span class="handbook-highlight-blue">Post-go-live ERPNext support</span>, issue resolution, and ongoing maintenance as part of our customer support plan.</td></tr>
<tr><td>How will we hand it over?</td><td>Handover includes documentation, training, access to the ERPNext system, and a final review to confirm the solution is <span class="handbook-highlight-black">ready for your team</span>.</td></tr>
</tbody></table>