Service Delivery Policy
Last updated ·
1. Overview
FieldAXIS (Activity eXecution and Intelligence System) is a product operated by .
TezBytes products are software platforms delivered as a service over the internet. There is no physical product and no physical delivery. Access to the platform is granted digitally following the completion of applicable prerequisites. This policy describes how TezBytes delivers its products, what the Client can expect from the onboarding process, what timelines are involved, and what responsibilities each party carries during and after implementation.
2. How Platform Access Is Delivered
For products requiring assisted onboarding — which applies to FieldAXIS ONE, and to FieldAXIS ILP and FieldAXIS Warranty where the Client has selected the assisted setup path — delivery follows a structured engagement process. This process begins only after TezBytes has received the full setup fee and a signed proposal or commercial agreement is in place.
The first stage of delivery is discovery. TezBytes works with the Client's appointed Point of Contact to build a thorough understanding of how the business operates — its territory structure, team hierarchy, workflow requirements, data formats, integration needs, and go-live expectations. This understanding shapes everything that follows.
Configuration comes next. TezBytes builds the Client's workspace around the findings from discovery, configuring modules, workflows, roles, and settings to reflect how the business actually works rather than requiring the business to adapt to a generic template.
Where the Client has existing data to bring into the platform — dealer lists, product catalogs, outstanding balances, territory assignments, contact records — that data is imported and structured within the workspace as part of the implementation.
Training is conducted for the different groups within the Client's organisation. Field representatives are trained on the flows they will use every day. Managers are trained on the reporting and oversight tools available to them. Administrators are walked through the configuration and management interface.
User Acceptance Testing, or UAT, follows training. The Client's team tests the configured platform against an agreed set of acceptance criteria. Issues identified during UAT are documented and resolved by TezBytes. The go-live stage is not reached until the Client has signed off on the platform meeting the agreed criteria.
Production access is granted following Client sign-off and receipt of the first month's subscription fee in advance. From this point, the platform is live and the Client's team has full operational access across all configured modules.
3. Delivery Timelines
Delivery timelines are indicative and depend on the complexity of the engagement, the Client's responsiveness during the process, and the readiness of data and decisions on their side.
FieldAXIS ONE typically takes between nine and ten weeks from the date of signed agreement and setup fee receipt to go-live. FieldAXIS ILP assisted onboarding typically takes three to four weeks. FieldAXIS Warranty assisted onboarding typically takes two to three weeks. For FieldAXIS CRM and for ILP or Warranty on the self-serve path, access is provisioned within 24 hours of successful account registration and payment, and configuration is managed by the Client using the platform interface and documentation.
Where FieldAXIS ONE and FieldAXIS ILP are being deployed together, the ILP onboarding runs in parallel with the ONE onboarding, with both products going live at the same time or within a short window of each other.
4. Client Responsibilities
The pace and quality of delivery depends significantly on the Client's active participation throughout the process. The Client is required to appoint a dedicated Point of Contact who has the authority to make decisions, attend scheduled review sessions, and coordinate internally across departments or branches. This person is the single point of communication between TezBytes and the Client's organisation during the engagement.
The Client is responsible for providing the data required for migration in the agreed formats and within the agreed timeframes. This typically includes dealer and contact lists, product catalogs with pricing, outstanding balance records, territory and branch structures, and — for ILP — existing carpenter or influencer lists if available. The Client is also responsible for attending training sessions and completing UAT within the scheduled window.
Delays resulting from the Client's unavailability, deferred decisions, incomplete data submissions, or missed sessions extend the delivery timeline accordingly. TezBytes is not liable for delays attributable to the Client's side of the engagement.
5. Scope and Out-of-Scope Work
The scope of each delivery is defined by the agreed commercial proposal or signed agreement. TezBytes will deliver what is described in that scope. Any additional requirements that emerge after the agreement is signed — new modules, additional customisations, integrations not originally in scope, or workflow changes beyond what was agreed — will be evaluated by TezBytes and communicated to the Client with a separate commercial estimate before any work on those requirements begins. No out-of-scope work is undertaken without the Client's written agreement to the revised scope and cost.
6. Post-Delivery Support
Following go-live, the Client has access to TezBytes through the support channels established during onboarding. The platform continues to receive updates, improvements, and new features as part of the active subscription. Support is available for operational queries, technical issues, and guidance on platform use.