<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: SARVO</title>
    <description>The latest articles on DEV Community by SARVO (@joinsarvo).</description>
    <link>https://dev.to/joinsarvo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4253849%2F87bf2808-8026-4f15-94ed-0f386770a1cb.jpg</url>
      <title>DEV Community: SARVO</title>
      <link>https://dev.to/joinsarvo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/joinsarvo"/>
    <language>en</language>
    <item>
      <title>Software Implementation Guarantee: The Access, Sandbox and Handover Hygiene That Keeps a Claim Clean</title>
      <dc:creator>SARVO</dc:creator>
      <pubDate>Fri, 20 Nov 2026 10:10:10 +0000</pubDate>
      <link>https://dev.to/joinsarvo/software-implementation-guarantee-the-access-sandbox-and-handover-hygiene-that-keeps-a-claim-clean-4mjb</link>
      <guid>https://dev.to/joinsarvo/software-implementation-guarantee-the-access-sandbox-and-handover-hygiene-that-keeps-a-claim-clean-4mjb</guid>
      <description>&lt;p&gt;A software implementation guarantee is usually discussed as a commercial term: money back if the work is not delivered. For the IT lead, it also has a technical side that nobody mentions in the sales meeting. If you ever need to use it, you will have to show what was delivered, stop using it, and return or delete it as the agreement sets out. That is far easier if the project was set up cleanly from day one.&lt;/p&gt;

&lt;p&gt;This guide covers that technical side, using the terms of the SARVO Verified guarantee as the example.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the software implementation guarantee actually says
&lt;/h2&gt;

&lt;p&gt;On SARVO, the guarantee applies only when you hire a &lt;strong&gt;SARVO Verified&lt;/strong&gt; partner &lt;strong&gt;through SARVO&lt;/strong&gt;, and the clause is in your contract. Under it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the &lt;strong&gt;partner&lt;/strong&gt; refunds 100% of the &lt;strong&gt;initial project fees&lt;/strong&gt; if the agreed work is not delivered,&lt;/li&gt;
&lt;li&gt;you can also cancel in writing within the first 14 days, with no reason needed,&lt;/li&gt;
&lt;li&gt;the partner pays the refund within 14 days,&lt;/li&gt;
&lt;li&gt;if a refund is not honoured, SARVO reviews both sides and mediates. SARVO is not a party to the contract and does not hold payments; you pay the partner directly.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Not covered: work or licences already delivered and used, third-party software costs such as vendor subscriptions, requests made after the window, and partners who are not SARVO Verified. The full terms are on the &lt;a href="https://joinsarvo.org/guarantee" rel="noopener noreferrer"&gt;SARVO Verified guarantee page&lt;/a&gt;. Confirm the clause is in your agreement before you sign.&lt;/p&gt;

&lt;p&gt;The claim steps are all in writing: tell the partner, stop using the work and return or delete anything delivered as the agreement sets out, then receive the refund.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why handover hygiene matters for a guarantee
&lt;/h2&gt;

&lt;p&gt;"Stop using the work" is simple when the work is a document. It is harder when the work is configuration inside your production tenant, scripts running on a schedule, or integrations moving data every hour. If delivered work is tangled into live systems, it becomes hard to show what was delivered, hard to stop using it, and hard to agree what "used" means. Clean setup avoids that argument.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Keep accounts and ownership in your name
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Create the software tenant, subscriptions and admin accounts under your company's email domain.&lt;/li&gt;
&lt;li&gt;Give the partner named user accounts with the roles they need, not shared logins.&lt;/li&gt;
&lt;li&gt;Turn on audit logs where the product supports them.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If the partner leaves, you remove their accounts. Nothing else has to move.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Separate sandbox from production
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Ask for all build work to happen in a sandbox or test environment first.&lt;/li&gt;
&lt;li&gt;Promote to production only after you accept a deliverable in writing.&lt;/li&gt;
&lt;li&gt;Keep a simple change log: what was promoted, when and by whom.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This gives you a clear line between "delivered and accepted" and "in progress". It also makes the 14-day window easier to judge, because you can see what has actually reached you.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Write deliverables as checkable items
&lt;/h2&gt;

&lt;p&gt;A guarantee is about whether the agreed work was delivered. Make the agreed work checkable:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;list each deliverable (for example, "lead capture form connected to CRM with duplicate check", not "CRM setup"),&lt;/li&gt;
&lt;li&gt;add a one-line acceptance test for each,&lt;/li&gt;
&lt;li&gt;record acceptance in writing, by email or a shared tracker.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  4. Put code and scripts in a repository you own
&lt;/h2&gt;

&lt;p&gt;Custom functions, integration scripts and report definitions should be stored somewhere your company controls, with history. If a claim is ever needed, the repository shows what was delivered. If the project goes well, it is your documentation.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Keep data movement reversible
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Run trial migrations into the sandbox, not production.&lt;/li&gt;
&lt;li&gt;Keep exports of source data before each migration.&lt;/li&gt;
&lt;li&gt;Document any integration that writes into another system, and how to switch it off.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  6. Know which costs sit outside the guarantee
&lt;/h2&gt;

&lt;p&gt;Vendor subscriptions and other third-party software are not covered. Keep those purchases separate from the partner invoice, ideally bought directly by your company, so it is obvious which payment is initial project fees and which is a licence.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Plan the first 14 days deliberately
&lt;/h2&gt;

&lt;p&gt;Use the walk-away window to see how the partner works, not just to wait:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;kickoff with the named delivery team,&lt;/li&gt;
&lt;li&gt;sandbox access granted to you,&lt;/li&gt;
&lt;li&gt;a first written plan and deliverables list,&lt;/li&gt;
&lt;li&gt;one early deliverable you can inspect.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If something feels wrong, you have a written, no-reason exit inside the window.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Tenant and admin accounts in your company's name&lt;/li&gt;
&lt;li&gt;[ ] Named partner accounts, audit logs on&lt;/li&gt;
&lt;li&gt;[ ] Sandbox for all build work&lt;/li&gt;
&lt;li&gt;[ ] Deliverables list with acceptance tests&lt;/li&gt;
&lt;li&gt;[ ] Code and scripts in your repository&lt;/li&gt;
&lt;li&gt;[ ] Source data exported before migration&lt;/li&gt;
&lt;li&gt;[ ] Licences bought separately from project fees&lt;/li&gt;
&lt;li&gt;[ ] Guarantee clause confirmed in the contract&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The same hygiene makes any project easier to manage, guarantee or not. For the migration part, SARVO's &lt;a href="https://joinsarvo.org/guides/data-migration-checklist-erp-crm" rel="noopener noreferrer"&gt;data migration checklist for ERP and CRM&lt;/a&gt; is a good starting template.&lt;/p&gt;

&lt;p&gt;If you want a partner who offers these terms, send a free matching request on the guarantee page and filter for SARVO Verified partners.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I work on SARVO.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>erp</category>
      <category>saas</category>
      <category>security</category>
      <category>productivity</category>
    </item>
    <item>
      <title>ManageEngine Implementation Partner in India: Plan Pilot Rings, Change Windows and Rollback Before Anyone Installs an Agent</title>
      <dc:creator>SARVO</dc:creator>
      <pubDate>Fri, 20 Nov 2026 10:04:24 +0000</pubDate>
      <link>https://dev.to/joinsarvo/manageengine-implementation-partner-in-india-plan-pilot-rings-change-windows-and-rollback-before-3753</link>
      <guid>https://dev.to/joinsarvo/manageengine-implementation-partner-in-india-plan-pilot-rings-change-windows-and-rollback-before-3753</guid>
      <description>&lt;p&gt;Choosing a ManageEngine implementation partner in India is usually framed as a product question: which modules, how many endpoints, which licence. The harder part is operational. ManageEngine tools such as endpoint management, patching and service desk touch every laptop, server and ticket in the company. A rushed rollout can push a bad patch to every machine or break a ticket workflow the support team depends on.&lt;/p&gt;

&lt;p&gt;This guide is a deployment plan you can hand to any shortlisted partner. How they respond to it tells you most of what you need to know.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the rollout plan matters more than the module list
&lt;/h2&gt;

&lt;p&gt;ManageEngine products are often deployed by an internal IT team with a partner's help. The partner brings product knowledge; you bring knowledge of your network, users and change rules. The best partners make this split explicit. The weakest ones install agents everywhere in week one and tune later.&lt;/p&gt;

&lt;p&gt;Ask every partner to respond in writing to the plan below and point out where they would do it differently. Disagreement backed by reasons is a good sign.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choosing a ManageEngine implementation partner in India: the plan to send them
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Phase 0: Inventory and access
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;List sites, subnets, VPNs and remote users.&lt;/li&gt;
&lt;li&gt;List directory services (on-premises Active Directory, Azure AD/Entra ID, or none).&lt;/li&gt;
&lt;li&gt;Decide who holds the admin accounts. They should belong to your company, not the partner.&lt;/li&gt;
&lt;li&gt;Agree where the server or cloud instance will run and how it is backed up.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ask the partner: what do you need from us before the server goes up, and how long does that usually take?&lt;/p&gt;

&lt;h3&gt;
  
  
  Phase 1: Pilot ring
&lt;/h3&gt;

&lt;p&gt;Start with a small pilot group: IT staff plus a handful of volunteers from different departments and locations.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Deploy agents only to this ring.&lt;/li&gt;
&lt;li&gt;Run inventory and check that hardware and software records match reality.&lt;/li&gt;
&lt;li&gt;Test remote control, software deployment and one patch cycle.&lt;/li&gt;
&lt;li&gt;For service desk, run a week of real tickets from one team through the new workflow.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ask: what results from the pilot would make you stop and change the plan?&lt;/p&gt;

&lt;h3&gt;
  
  
  Phase 2: Early adopters
&lt;/h3&gt;

&lt;p&gt;Expand to perhaps one department or one site.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Introduce patch policies with approval steps, not automatic deployment to all.&lt;/li&gt;
&lt;li&gt;Set maintenance windows that match how the department works.&lt;/li&gt;
&lt;li&gt;Confirm reports reach the right people.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ask: how do you decide which patches are auto-approved and which need testing?&lt;/p&gt;

&lt;h3&gt;
  
  
  Phase 3: Broad rollout
&lt;/h3&gt;

&lt;p&gt;Roll out in batches, with a pause after each one to review failed installs, help desk tickets and user complaints.&lt;/p&gt;

&lt;p&gt;Ask: how many endpoints per batch, and what is the pause between batches?&lt;/p&gt;

&lt;h2&gt;
  
  
  Change windows and communication
&lt;/h2&gt;

&lt;p&gt;Every phase needs a change window and a message to users. Ask the partner for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a template user notice for agent installation,&lt;/li&gt;
&lt;li&gt;the reboot policy and how users can postpone,&lt;/li&gt;
&lt;li&gt;how emergency patches are handled outside the normal window.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A partner who has a ready template has done this before.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rollback: the question most partners skip
&lt;/h2&gt;

&lt;p&gt;Ask each partner, in writing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How do we remove an agent cleanly from a machine if it causes problems?&lt;/li&gt;
&lt;li&gt;How do we roll back a patch that breaks an application?&lt;/li&gt;
&lt;li&gt;If the service desk workflow fails, how do we route tickets in the meantime?&lt;/li&gt;
&lt;li&gt;Where is the configuration backed up, and how do we restore it?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If the answer is "that won't happen", move on.&lt;/p&gt;

&lt;h2&gt;
  
  
  Integrations to plan early
&lt;/h2&gt;

&lt;p&gt;Common integrations include directory sync, email for ticket creation, single sign-on, and connections to asset or HR systems. For each, ask who configures it, how failures are noticed, and who maintains it after go-live.&lt;/p&gt;

&lt;h2&gt;
  
  
  Handover checklist
&lt;/h2&gt;

&lt;p&gt;At the end, you should have:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;all admin accounts under your company's control,&lt;/li&gt;
&lt;li&gt;documented policies: patch approval, deployment groups, ticket categories, SLAs,&lt;/li&gt;
&lt;li&gt;a runbook for common tasks and for rollback,&lt;/li&gt;
&lt;li&gt;training for your IT team, recorded,&lt;/li&gt;
&lt;li&gt;a support arrangement with named contacts and response times.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Questions to compare partners
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Who on your team will run our rollout, and how many similar deployments have they done?&lt;/li&gt;
&lt;li&gt;Which parts of this plan would you change, and why?&lt;/li&gt;
&lt;li&gt;What do you need from our IT team each week?&lt;/li&gt;
&lt;li&gt;What is included in support after go-live?&lt;/li&gt;
&lt;li&gt;Can we speak to an IT lead from a recent client?&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What a realistic timeline looks like
&lt;/h2&gt;

&lt;p&gt;There is no single timeline, because it depends on the number of endpoints, sites, modules and integrations, and on how quickly your team can approve changes. Instead of asking "how long will it take?", ask each partner for a dated plan per phase, the exit criteria for each phase, and the assumptions behind the dates (for example, how many hours a week your IT team will give). Compare the plans and the assumptions, not only the end date. A plan that finishes later but has clear exit criteria is usually the one that finishes on time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building the shortlist
&lt;/h2&gt;

&lt;p&gt;At the time of writing (20 November 2026), SARVO lists 9 ManageEngine implementation partners across India. You can &lt;a href="https://joinsarvo.org/technologies/manageengine" rel="noopener noreferrer"&gt;compare listed ManageEngine partners in India on SARVO&lt;/a&gt; by services, industries and published reviews, and send your rollout plan to two or three of them at once. If you are still deciding between ITSM products, SARVO's guide on &lt;a href="https://joinsarvo.org/guides/how-to-choose-manageengine-partner-in-india" rel="noopener noreferrer"&gt;choosing a ManageEngine partner in India&lt;/a&gt; covers the buyer-side checks.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I work on SARVO.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>devops</category>
      <category>itsm</category>
      <category>security</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to Choose an SAP Business One Partner in India: An IT Lead's Checklist for Add-ons, Integrations and Upgrades</title>
      <dc:creator>SARVO</dc:creator>
      <pubDate>Fri, 20 Nov 2026 10:01:50 +0000</pubDate>
      <link>https://dev.to/joinsarvo/how-to-choose-an-sap-business-one-partner-in-india-an-it-leads-checklist-for-add-ons-3k95</link>
      <guid>https://dev.to/joinsarvo/how-to-choose-an-sap-business-one-partner-in-india-an-it-leads-checklist-for-add-ons-3k95</guid>
      <description>&lt;p&gt;Finance usually leads the SAP Business One decision, but the IT lead or developer is the one who lives with it afterwards. If you are figuring out how to choose an SAP Business One partner in India, this checklist is for you: the technical questions about add-ons, integrations, environments and upgrades that rarely come up in a sales demo but decide how painful year two will be.&lt;/p&gt;

&lt;p&gt;SAP Business One is SAP's ERP for small and mid-sized businesses, covering finance, sales, purchasing and inventory. It is sold and supported through partners, so in practice you are choosing a partner as much as a product.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to choose an SAP Business One partner in India: start with the landscape
&lt;/h2&gt;

&lt;p&gt;Before you talk to anyone, write down what the ERP has to connect to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;your current accounting system and how many years of history finance wants,&lt;/li&gt;
&lt;li&gt;e-commerce, marketplace or distributor portals,&lt;/li&gt;
&lt;li&gt;banking and payment systems,&lt;/li&gt;
&lt;li&gt;GST e-invoicing and e-way bill tools,&lt;/li&gt;
&lt;li&gt;reporting tools management already uses,&lt;/li&gt;
&lt;li&gt;any warehouse, manufacturing or field-service systems.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Send this list to every partner and ask them to mark each item as standard, add-on, or custom build. This one exercise filters out partners who have not thought about your setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Add-ons: know what you are adding and who maintains it
&lt;/h2&gt;

&lt;p&gt;Industry depth in SAP Business One often comes from add-ons, some built by the partner and some by third parties. For each add-on in a proposal, ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Who built it, and who supports it?&lt;/li&gt;
&lt;li&gt;Is it licensed separately? What does it cost each year?&lt;/li&gt;
&lt;li&gt;Has it been kept compatible through recent product upgrades? Ask for the last two upgrade dates.&lt;/li&gt;
&lt;li&gt;What happens to your data and processes if the add-on vendor stops supporting it?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A proposal with five add-ons is five extra dependencies. Ask the partner to justify each one against a specific requirement.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Integrations: ask for the error path, not the happy path
&lt;/h2&gt;

&lt;p&gt;For each integration in scope, ask the partner to describe in writing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the tool or method used (service layer API, integration platform, file exchange),&lt;/li&gt;
&lt;li&gt;which system owns each field,&lt;/li&gt;
&lt;li&gt;how failures are logged and who gets alerted,&lt;/li&gt;
&lt;li&gt;how a failed record is re-sent,&lt;/li&gt;
&lt;li&gt;who maintains the integration after go-live and at what cost.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If the integration is custom code, make sure your company owns the code and receives it with documentation at handover.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Environments: insist on a test company
&lt;/h2&gt;

&lt;p&gt;Every change and every upgrade should be tried in a test environment first. Confirm:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a separate test database or company will be set up,&lt;/li&gt;
&lt;li&gt;how often it will be refreshed from live data,&lt;/li&gt;
&lt;li&gt;who can deploy changes to live, and how changes are recorded.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If a partner treats the test environment as optional, treat that as a warning.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Data migration: count, reconcile, sign off
&lt;/h2&gt;

&lt;p&gt;Ask for a migration plan that includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;master data list (business partners, items, chart of accounts, price lists, bills of material),&lt;/li&gt;
&lt;li&gt;transaction history scope (full, opening balances or summaries),&lt;/li&gt;
&lt;li&gt;number of trial migrations,&lt;/li&gt;
&lt;li&gt;reconciliation reports for record counts and balances,&lt;/li&gt;
&lt;li&gt;a sign-off step for your finance owner.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The guide &lt;a href="https://joinsarvo.org/guides/data-migration-checklist-erp-crm" rel="noopener noreferrer"&gt;SARVO's data migration checklist for ERP and CRM&lt;/a&gt; is a useful template to send partners so their answers follow the same structure.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. India localisation: see it, don't hear it
&lt;/h2&gt;

&lt;p&gt;Ask for a short demonstration, in the version you will run, of:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;GST invoices for inter-state and intra-state sales,&lt;/li&gt;
&lt;li&gt;e-invoicing and e-way bill flow,&lt;/li&gt;
&lt;li&gt;TDS on vendor payments,&lt;/li&gt;
&lt;li&gt;the GST return export.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Also confirm where your database will be hosted and how backups work.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Upgrades: ask about the last one
&lt;/h2&gt;

&lt;p&gt;The best predictor of your future upgrades is the partner's last one. Ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;When did you last upgrade a client of our size?&lt;/li&gt;
&lt;li&gt;How long did testing take?&lt;/li&gt;
&lt;li&gt;What broke, and how was it fixed?&lt;/li&gt;
&lt;li&gt;Is upgrade work included in support or charged separately?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  7. People and support
&lt;/h2&gt;

&lt;p&gt;Get in writing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the names and experience of the consultants on your project, including whether they are certified Business One consultants,&lt;/li&gt;
&lt;li&gt;who handles support after go-live and the response times,&lt;/li&gt;
&lt;li&gt;how support requests are logged and tracked.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A short scoring sheet
&lt;/h2&gt;

&lt;p&gt;Score each partner from 1 to 5 on add-on clarity, integration design, environment discipline, migration plan, localisation demo, upgrade track record and named team. Add one sentence of evidence for each score. When two partners are close, prefer the one whose answers were written and specific.&lt;/p&gt;

&lt;h2&gt;
  
  
  Red flags
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;No test environment in the plan.&lt;/li&gt;
&lt;li&gt;Admin and database credentials held only by the partner.&lt;/li&gt;
&lt;li&gt;Integrations described as "standard" with no error handling.&lt;/li&gt;
&lt;li&gt;Add-ons with no named maintainer.&lt;/li&gt;
&lt;li&gt;A scope that says "as discussed".&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where to find partners to evaluate
&lt;/h2&gt;

&lt;p&gt;Shortlist two to four partners who list SAP Business One, work in your industry and can support your locations. You can &lt;a href="https://joinsarvo.org/technologies/sap" rel="noopener noreferrer"&gt;browse listed SAP partners in India on SARVO&lt;/a&gt;, check the products, services and industries each company lists, and send all of them the same requirement for free. For a non-technical summary of what to check, share SARVO's guide on &lt;a href="https://joinsarvo.org/guides/how-to-choose-sap-business-one-partner-in-india" rel="noopener noreferrer"&gt;how to choose an SAP Business One partner in India&lt;/a&gt; with your finance team.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I work on SARVO.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>erp</category>
      <category>sap</category>
      <category>saas</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to Choose a Tally Partner in India: A Technical Checklist for TDL, Data and Remote Access</title>
      <dc:creator>SARVO</dc:creator>
      <pubDate>Fri, 20 Nov 2026 07:56:42 +0000</pubDate>
      <link>https://dev.to/joinsarvo/how-to-choose-a-tally-partner-in-india-a-technical-checklist-for-tdl-data-and-remote-access-1g48</link>
      <guid>https://dev.to/joinsarvo/how-to-choose-a-tally-partner-in-india-a-technical-checklist-for-tdl-data-and-remote-access-1g48</guid>
      <description>&lt;p&gt;Most advice on how to choose a Tally partner in India is written for the accountant. That makes sense: Tally is accounting and inventory software, and the finance team uses it every day. But in a lot of Indian businesses, the person who gets the phone call when Tally will not open, the remote branch cannot connect, or a custom report breaks after an update is the in-house IT person or developer. This checklist is for that person.&lt;/p&gt;

&lt;h2&gt;
  
  
  What SARVO's guide says to check
&lt;/h2&gt;

&lt;p&gt;SARVO's buyer guide for Tally lists three partner-specific checks:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;TallyPrime experience and GST workflows&lt;/li&gt;
&lt;li&gt;Customisation using TDL, if you need it&lt;/li&gt;
&lt;li&gt;Data migration and multi-user or remote access set-up&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It also recommends asking every partner five standard questions: who runs the project, what is in the written scope, how migration, testing and training are handled, what support is included after go-live, and whether you can speak to two recent clients.&lt;/p&gt;

&lt;p&gt;Below, each check is turned into questions you can ask and evidence you can request.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to choose a Tally partner in India: TDL customisation
&lt;/h2&gt;

&lt;p&gt;TDL (Tally Definition Language) is how Tally is customised: extra fields, custom vouchers, custom reports, integrations. It is powerful, and it is also where long-term support problems come from.&lt;/p&gt;

&lt;h3&gt;
  
  
  Questions to ask
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Which of our requirements need TDL, and which can be met with standard TallyPrime features? Show us the list.&lt;/li&gt;
&lt;li&gt;Will we receive the TDL source files, or only compiled files?&lt;/li&gt;
&lt;li&gt;Who owns the TDL once we have paid for it?&lt;/li&gt;
&lt;li&gt;What documentation comes with each customisation: what it does, which vouchers or reports it touches, how it is loaded?&lt;/li&gt;
&lt;li&gt;When TallyPrime is updated, who checks that our TDL still works? Is that included in support?&lt;/li&gt;
&lt;li&gt;If another developer had to maintain this, what would they need?&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Why source access matters
&lt;/h3&gt;

&lt;p&gt;If you only hold compiled files, every future change depends on the original developer. That may be fine for a single small report. It is a real risk for anything that touches voucher entry or integrations. Put source access and ownership in the scope.&lt;/p&gt;

&lt;h2&gt;
  
  
  Data migration
&lt;/h2&gt;

&lt;p&gt;Even within Tally, migration happens more than people expect: moving from an older release to TallyPrime, splitting or merging companies, moving a branch onto a central set-up, or restructuring masters.&lt;/p&gt;

&lt;h3&gt;
  
  
  Questions to ask
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;What exactly moves: ledgers, groups, stock items, godowns, opening balances, open bills, history?&lt;/li&gt;
&lt;li&gt;How will you verify the migration? (Ask for specific checks, for example trial balance and stock summary matching before and after.)&lt;/li&gt;
&lt;li&gt;How many trial runs before the final cut-over?&lt;/li&gt;
&lt;li&gt;Who on our side signs off each run?&lt;/li&gt;
&lt;li&gt;What is the rollback plan if the final migration has problems?&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Data hygiene before you start
&lt;/h3&gt;

&lt;p&gt;Before migration, run a clean-up: duplicate ledgers, inactive stock items, inconsistent GST details on parties. Partners can do this, but it is cheaper if your team handles the obvious parts and the partner handles the tricky ones.&lt;/p&gt;

&lt;h2&gt;
  
  
  Multi-user and remote access
&lt;/h2&gt;

&lt;p&gt;This is the part most likely to land on IT. Branches, work-from-home accountants and an auditor who needs access at year-end all create access requirements.&lt;/p&gt;

&lt;h3&gt;
  
  
  Questions to ask
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;What set-up do you recommend for our number of users and locations, and why?&lt;/li&gt;
&lt;li&gt;Where will the data live, and who has admin access to that machine or server?&lt;/li&gt;
&lt;li&gt;How will remote users connect, and how is that access secured?&lt;/li&gt;
&lt;li&gt;How are user roles and rights set up in Tally, and who maintains them when staff change?&lt;/li&gt;
&lt;li&gt;What is the backup routine, where are backups stored, and when was a restore last tested?&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  What good looks like
&lt;/h3&gt;

&lt;p&gt;A partner should be able to describe a backup routine, an access-control plan and a recovery process without hesitating. If they say "we will set it up" without specifics, write your expectations into the scope.&lt;/p&gt;

&lt;h2&gt;
  
  
  GST workflows
&lt;/h2&gt;

&lt;p&gt;The guide lists TallyPrime experience and GST workflows as the first check. For a technical evaluator, the useful test is to ask the partner to walk through your actual documents:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A multi-rate B2B sales invoice&lt;/li&gt;
&lt;li&gt;An inter-state and an intra-state sale&lt;/li&gt;
&lt;li&gt;A credit note&lt;/li&gt;
&lt;li&gt;A purchase with reverse charge if you have them&lt;/li&gt;
&lt;li&gt;Any e-invoicing or e-way bill requirements that apply to you&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ask which parts are standard and which depend on configuration or TDL.&lt;/p&gt;

&lt;h2&gt;
  
  
  Testing and training
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Which processes will be tested end to end, with whose data?&lt;/li&gt;
&lt;li&gt;Who on your side does acceptance testing?&lt;/li&gt;
&lt;li&gt;Will training be role-based (data entry, approvals, reporting) and recorded?&lt;/li&gt;
&lt;li&gt;Will your IT person get a separate session on backups, user management and loading TDL?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last question is often forgotten. Ask for it explicitly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Support after go-live
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;What support is included, for how long, and through which channel?&lt;/li&gt;
&lt;li&gt;What response time applies to "Tally will not open" versus "a report looks wrong"?&lt;/li&gt;
&lt;li&gt;Who handles TallyPrime updates and checks custom TDL afterwards?&lt;/li&gt;
&lt;li&gt;How are support charges calculated after the included period?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When Tally is not the answer
&lt;/h2&gt;

&lt;p&gt;Sometimes the evaluation reveals that the business has outgrown Tally: many branches, manufacturing workflows, or a need for deep integration with CRM and e-commerce. That is worth knowing before you invest heavily in TDL. SARVO's article on &lt;a href="https://joinsarvo.org/resources/moving-from-tally-to-an-erp" rel="noopener noreferrer"&gt;moving from Tally to an ERP&lt;/a&gt; covers when that move makes sense.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building the shortlist
&lt;/h2&gt;

&lt;p&gt;SARVO's guidance is to shortlist two to four Tally partners and put their answers side by side. Use the same questions for every partner so the answers are comparable, and score them on specifics: source access, a named migration check, a described backup routine, a support process.&lt;/p&gt;

&lt;p&gt;You can browse listed Tally partners and the full checklist on SARVO's guide to &lt;a href="https://joinsarvo.org/guides/how-to-choose-tally-partner-in-india" rel="noopener noreferrer"&gt;how to choose a Tally partner in India&lt;/a&gt;, then send the same written requirement to the partners that fit.&lt;/p&gt;

&lt;p&gt;Disclosure: I work on SARVO.&lt;/p&gt;

</description>
      <category>tally</category>
      <category>accounting</category>
      <category>erp</category>
      <category>productivity</category>
    </item>
    <item>
      <title>SAP Implementation Partner With a Guarantee: Write Acceptance Criteria That Make 'Delivered' Testable</title>
      <dc:creator>SARVO</dc:creator>
      <pubDate>Fri, 20 Nov 2026 07:50:23 +0000</pubDate>
      <link>https://dev.to/joinsarvo/sap-implementation-partner-with-a-guarantee-write-acceptance-criteria-that-make-delivered-46p4</link>
      <guid>https://dev.to/joinsarvo/sap-implementation-partner-with-a-guarantee-write-acceptance-criteria-that-make-delivered-46p4</guid>
      <description>&lt;p&gt;If you are hiring an SAP implementation partner with a guarantee attached, the clause that matters most is not the refund clause. It is the definition of "delivered". A money-back promise on undelivered work only helps if both sides can agree, without a long argument, whether the work was delivered. For technical teams, that means acceptance criteria you can actually test.&lt;/p&gt;

&lt;p&gt;This guide shows how to write them, using the SARVO Verified Guarantee as the worked example.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the guarantee actually covers
&lt;/h2&gt;

&lt;p&gt;On SARVO, the Verified Guarantee applies when you hire a SARVO Verified partner through SARVO. The terms, as set out on the &lt;a href="https://joinsarvo.org/guarantee" rel="noopener noreferrer"&gt;SARVO Verified Guarantee page&lt;/a&gt;, are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;partner&lt;/strong&gt; refunds 100% of the &lt;strong&gt;initial project fees&lt;/strong&gt; if the agreed work is not delivered.&lt;/li&gt;
&lt;li&gt;You can also cancel in writing within the first 14 days, no reason needed.&lt;/li&gt;
&lt;li&gt;The partner pays the refund within 14 days.&lt;/li&gt;
&lt;li&gt;If a refund is not honoured, SARVO reviews both sides and mediates, and can remove the partner's Verified tick. SARVO is not a party to your contract and does not hold your payments; you pay the partner directly.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What it does not cover:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Work or licences already delivered and used&lt;/li&gt;
&lt;li&gt;Third-party software costs, such as vendor subscriptions&lt;/li&gt;
&lt;li&gt;Requests made after the window&lt;/li&gt;
&lt;li&gt;Partners who are not SARVO Verified&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Terms are set per agreement, so confirm the guarantee clause is in your contract before you sign. If it is missing, ask the partner to add it.&lt;/p&gt;

&lt;p&gt;Notice the phrase that carries the weight: &lt;strong&gt;agreed work&lt;/strong&gt;. For an SAP project, that is where your acceptance criteria come in.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why "delivered" is hard to define on SAP projects
&lt;/h2&gt;

&lt;p&gt;SAP projects tend to be large, phased, and dependent on your own team. A configuration can be technically complete but untested. A data load can run but produce a trial balance that does not match. An interface can work in a test system but not against production volumes. Without written criteria, "delivered" becomes a matter of opinion.&lt;/p&gt;

&lt;p&gt;That uncertainty hurts both sides. Buyers cannot tell whether a phase is done; partners cannot close a phase cleanly. Good acceptance criteria fix this, with or without a guarantee.&lt;/p&gt;

&lt;h2&gt;
  
  
  SAP implementation partner with guarantee: scope the initial phase tightly
&lt;/h2&gt;

&lt;p&gt;The guarantee refers to initial project fees. The practical implication for buyers is to make the initial phase a well-defined, testable piece of work, rather than a vague first payment against a large programme.&lt;/p&gt;

&lt;p&gt;Ways to do that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Define the initial phase as a discrete deliverable: for example, a fit-gap assessment with documented outputs, or a configured prototype for a named set of processes.&lt;/li&gt;
&lt;li&gt;List exactly what the initial project fees pay for.&lt;/li&gt;
&lt;li&gt;Keep licence costs and vendor subscriptions out of that list. Third-party software costs are excluded from the guarantee, so mixing them into the initial fees only creates confusion.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How to write acceptance criteria a developer would respect
&lt;/h2&gt;

&lt;p&gt;Use the same discipline you would use for a user story.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Name the process, not the module
&lt;/h3&gt;

&lt;p&gt;Weak: "FI module configured."&lt;br&gt;
Better: "Vendor invoice posting for domestic purchases with GST, from goods receipt to invoice posting, tested end to end with five sample invoices provided by the buyer."&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Specify the test data
&lt;/h3&gt;

&lt;p&gt;State whose data, how many records, and which edge cases. Provide the samples yourself, so the test is not designed around what already works.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Specify the expected result
&lt;/h3&gt;

&lt;p&gt;Expected postings, expected tax amounts, expected report output. If a number must match, say which number and to what.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Name who tests and who signs off
&lt;/h3&gt;

&lt;p&gt;A named person on your side runs the test; a named person signs off. Give them a time box.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Define the evidence
&lt;/h3&gt;

&lt;p&gt;Screenshots, test logs or a signed checklist. Something both sides can point to.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Separate defects from change requests
&lt;/h3&gt;

&lt;p&gt;Agree how a failing test is classified: a defect against agreed scope (partner fixes) or a new requirement (change request). This one rule prevents most disputes.&lt;/p&gt;

&lt;h2&gt;
  
  
  A sample acceptance list for an initial SAP phase
&lt;/h2&gt;

&lt;p&gt;Adapt this to your scope. Each line should be testable by someone who did not build it.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Documented list of in-scope processes, signed by both sides&lt;/li&gt;
&lt;li&gt;Organisation structure configured as per the agreed design document&lt;/li&gt;
&lt;li&gt;Each in-scope process executed end to end in the test system with buyer-provided data&lt;/li&gt;
&lt;li&gt;Tax calculation matches the buyer's expected values for every sample document&lt;/li&gt;
&lt;li&gt;Agreed reports produce output that reconciles with the buyer's reference figures&lt;/li&gt;
&lt;li&gt;Agreed interfaces tested with sample volumes stated in the scope&lt;/li&gt;
&lt;li&gt;Open defects list reviewed; no defects classified as critical remain open&lt;/li&gt;
&lt;li&gt;Training for named key users delivered and attendance recorded&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The 14-day window and your test plan
&lt;/h2&gt;

&lt;p&gt;The 14-day written cancellation exists for a reason: it gives you an early exit if the engagement is not a fit. Use those two weeks deliberately:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Hold the kickoff and meet the actual delivery team&lt;/li&gt;
&lt;li&gt;Review the first design or fit-gap outputs&lt;/li&gt;
&lt;li&gt;Check that the team's understanding of your processes matches yours&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If something is clearly wrong, the window is the time to say so in writing. After it closes, the remaining protection is for agreed work not delivered, which is why the acceptance criteria above matter.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding SAP partners
&lt;/h2&gt;

&lt;p&gt;SARVO lists SAP implementation companies on its &lt;a href="https://joinsarvo.org/technologies/sap" rel="noopener noreferrer"&gt;SAP partners in India page&lt;/a&gt;. Listing a technology does not mean the company is an authorised SAP partner, and being listed is not the same as being SARVO Verified. The guarantee applies only when you hire a SARVO Verified partner through SARVO, so filter for SARVO Verified partners if the money-back terms matter to you, and confirm the clause is in your contract.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist before you sign
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Initial phase defined as a discrete deliverable&lt;/li&gt;
&lt;li&gt;Initial project fees itemised, with licences and third-party costs separated&lt;/li&gt;
&lt;li&gt;Acceptance criteria written per process, with test data and sign-off owners&lt;/li&gt;
&lt;li&gt;Defect vs change-request rule agreed&lt;/li&gt;
&lt;li&gt;Guarantee clause present in the contract&lt;/li&gt;
&lt;li&gt;Kick-off and first reviews scheduled inside the first 14 days&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Write the criteria once and you get a cleaner project whether or not you ever need the guarantee. If you want SARVO to introduce Verified partners, the free matching request on the guarantee page is the place to start.&lt;/p&gt;

&lt;p&gt;Disclosure: I work on SARVO.&lt;/p&gt;

</description>
      <category>sap</category>
      <category>erp</category>
      <category>projectmanagement</category>
      <category>testing</category>
    </item>
    <item>
      <title>Zoho vs Odoo Implementation Partner: An Integration and Data-Model Checklist for IT Leads</title>
      <dc:creator>SARVO</dc:creator>
      <pubDate>Fri, 20 Nov 2026 07:49:59 +0000</pubDate>
      <link>https://dev.to/joinsarvo/zoho-vs-odoo-implementation-partner-an-integration-and-data-model-checklist-for-it-leads-o7k</link>
      <guid>https://dev.to/joinsarvo/zoho-vs-odoo-implementation-partner-an-integration-and-data-model-checklist-for-it-leads-o7k</guid>
      <description>&lt;p&gt;When the debate is Zoho vs Odoo, the implementation partner question usually gets decided by whoever gave the better demo. If you are the IT lead or developer who will maintain the integrations afterwards, that is the wrong order. The platform choice and the partner choice should both be tested against the same thing: how your data flows today, and who will own those flows after go-live.&lt;/p&gt;

&lt;p&gt;This is a checklist for that evaluation, written for the technical person in the room.&lt;/p&gt;

&lt;h2&gt;
  
  
  The platforms, briefly
&lt;/h2&gt;

&lt;p&gt;SARVO's guide to &lt;a href="https://joinsarvo.org/guides/zoho-vs-odoo-vs-salesforce" rel="noopener noreferrer"&gt;Zoho vs Odoo vs Salesforce&lt;/a&gt; describes them like this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Zoho&lt;/strong&gt; is a suite of connected business apps (CRM, finance, inventory, HR and more). It suits small and mid-sized businesses that want many tools from one vendor with a common login and data model.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Odoo&lt;/strong&gt; is a modular business suite covering ERP, accounting, inventory, manufacturing, sales and more, with an open-source community edition. It suits businesses that want broad ERP coverage and room to customise, usually with a partner's help.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The guide's own framing is useful: it is a starting point, not a verdict, and a good partner should test it against your needs. Your job is to check that they actually do.&lt;/p&gt;

&lt;h2&gt;
  
  
  Zoho vs Odoo implementation partner: start from your integration map
&lt;/h2&gt;

&lt;p&gt;Before you speak to any partner, draw what exists today. One page, boxes and arrows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Every system that holds business data: accounting, CRM, spreadsheets, e-commerce, payroll, a warehouse tool, a custom app&lt;/li&gt;
&lt;li&gt;What flows between them, in which direction, and how often&lt;/li&gt;
&lt;li&gt;Which flows are manual (someone exports and re-imports a file) and which are automated&lt;/li&gt;
&lt;li&gt;Who owns each system and each flow today&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Send this map to every partner you shortlist, for both platforms. Ask each partner to mark which boxes their proposal replaces, which it integrates with, and which it leaves alone. You will learn more from that annotated diagram than from any demo.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions that apply to both platforms
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Data model
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Which of our current entities (customers, items, price lists, projects, branches) map cleanly to standard objects, and which need custom fields or custom objects?&lt;/li&gt;
&lt;li&gt;Where will the "master" copy of each entity live after go-live?&lt;/li&gt;
&lt;li&gt;How will duplicates be prevented when data enters from more than one channel?&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Integrations
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Which integrations will use built-in connectors, which will use the platform's API, and which will need middleware?&lt;/li&gt;
&lt;li&gt;Who writes and hosts any integration code? Who monitors it?&lt;/li&gt;
&lt;li&gt;What happens when an integration fails at 2 a.m.: who gets alerted, and is there a retry or a queue?&lt;/li&gt;
&lt;li&gt;Are there API limits or usage caps on the edition you are recommending that our volumes could hit?&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Customisation
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;What will you configure versus build?&lt;/li&gt;
&lt;li&gt;Where will custom code live, and will we have repository access?&lt;/li&gt;
&lt;li&gt;Who owns the custom code once paid for?&lt;/li&gt;
&lt;li&gt;How will customisations be kept working across platform updates?&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Handover
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;What documentation will we receive for every integration and customisation?&lt;/li&gt;
&lt;li&gt;Can our own developers make small changes after go-live, and will you train them?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Platform-specific questions to ask a Zoho partner
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;If we need several Zoho apps, will you implement them as separate apps or under a bundle, and what drives that recommendation?&lt;/li&gt;
&lt;li&gt;Which of our flows can be handled natively between Zoho apps, and which need custom functions or external integration?&lt;/li&gt;
&lt;li&gt;If custom logic is needed, where will it be written and how is it version-controlled?&lt;/li&gt;
&lt;li&gt;How do you handle a requirement that sits outside Zoho's standard apps?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Platform-specific questions to ask an Odoo partner
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Community or paid edition, and which of our requirements drive that? Which features would need custom modules on community?&lt;/li&gt;
&lt;li&gt;Where will it be hosted, and will we have admin and database access?&lt;/li&gt;
&lt;li&gt;Will custom work be separate modules? How do you estimate porting them to a newer Odoo version?&lt;/li&gt;
&lt;li&gt;How will Indian GST and e-invoicing be configured, and which parts are standard?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Score the answers the same way
&lt;/h2&gt;

&lt;p&gt;Use one scoring sheet for all partners, whichever platform they propose:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Integration clarity&lt;/strong&gt;: did they annotate your map, or wave at "we have connectors"?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ownership&lt;/strong&gt;: repository access, IP, documentation, admin access&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Failure handling&lt;/strong&gt;: monitoring, alerts, retries&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Upgrade path&lt;/strong&gt;: how custom work survives updates&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Team&lt;/strong&gt;: did you meet the person who will build the integrations?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Total cost over three to five years&lt;/strong&gt;, including support, as the SARVO guide recommends&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The last point matters. The guide's FAQ on which platform is cheapest gives the honest answer: it depends on users, modules and customisation, so compare total cost over several years, not only the licence.&lt;/p&gt;

&lt;h2&gt;
  
  
  The five decision questions, from a technical angle
&lt;/h2&gt;

&lt;p&gt;The SARVO guide lists five questions that decide between these platforms. Here is how each one shows up in technical work:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Mainly CRM, or full ERP covering accounts, stock and production?&lt;/strong&gt; This decides how many entities you migrate and how many integrations survive.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;How many users in two years?&lt;/strong&gt; This affects licence model, performance testing and API usage.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;How much customisation?&lt;/strong&gt; Every custom object or module becomes something you maintain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Which tools must it integrate with?&lt;/strong&gt; Your integration map answers this.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Total budget over three to five years, including support?&lt;/strong&gt; Integration maintenance is a real line in that budget.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Mistakes technical leads make in this decision
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Letting the platform decision happen before the integration map exists&lt;/li&gt;
&lt;li&gt;Accepting "it integrates with everything" without a named method for each flow&lt;/li&gt;
&lt;li&gt;Not asking who hosts and monitors middleware&lt;/li&gt;
&lt;li&gt;Leaving custom code ownership out of the contract&lt;/li&gt;
&lt;li&gt;Comparing a Zoho quote and an Odoo quote that cover different scopes&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Shortlisting partners
&lt;/h2&gt;

&lt;p&gt;Shortlist two or three partners per platform you are seriously considering, send them the same map and questions, and compare the annotated answers. You can tick two to four companies on &lt;a href="https://joinsarvo.org/compare" rel="noopener noreferrer"&gt;SARVO's compare tool&lt;/a&gt; to see their listed technologies, services, industries and published reviews side by side before you send the brief.&lt;/p&gt;

&lt;p&gt;Disclosure: I work on SARVO.&lt;/p&gt;

</description>
      <category>erp</category>
      <category>crm</category>
      <category>saas</category>
      <category>integration</category>
    </item>
  </channel>
</rss>
