MVPNexa · StartupNexa
MVPNexa Service Terms and Conditions
These terms govern the website and initial service requests. Project details are recorded in the approved proposal, scope and agreement, subject to mandatory law, customer rights and applicable advertising commitments.
Last updated: 14 September 2026
1. Provider
MVPNexa is provided by StartupNexa Company, a Saudi registered company, CR 7050559454, at Jeddah, Alrawdah, Alkhayyat Center, Prince Sultan Street. Official contact: [email protected].
2. Contract formation
Submitting a form, attending a call or receiving an estimate does not create a project contract. A contract begins only after written project acceptance, signature of the project documents, and receipt of the stated start payment.
3. Prices and scope
Published prices cover the illustrated versions: 18,500 for Web and 29,500 for SaaS. The examples are scope references, not compulsory templates or a promise to cover any project at the same price. We review project differences and confirm deliverables, complete price and timing before development. Launch Partners prices of 14,500 for Web and 22,500 for SaaS apply within the first-five-project campaign when confirmed in the proposal, without a claim about remaining places. A Scope Summary does not remove applicable advertising commitments or statutory rights.
4. MVP Direction Sprint
The introductory call is free, and ordinary build scoping is included in the package. When deeper work is useful, an optional 2,500 Direction Sprint produces scope, priorities, acceptance criteria and a build recommendation under a written brief. The full fee counts toward your project price if you confirm you’ll build with us within 14 days of receiving the plan. The Sprint is not compulsory for every project or an open-ended investigation.
5. Package coverage
The package includes a useful launch outcome and the supporting operations, accounts, permissions, security and error handling needed to deliver it, even when every implementation detail is not named. Web includes one standard business connection, such as payments when needed. SaaS includes company signup, isolated workspaces, invitations, straightforward subscription billing/access and one additional light connection with agreed operations. Arabic and English core UI are included; large-scale content or translation is scoped separately. Provider, operations and inputs are defined; SaaS billing does not imply collecting and settling client-company customer funds. Missing details are clarified, not automatically charged as extras.
6. Feedback and approvals
The customer appoints an authorised decision-maker and consolidates feedback through an agreed written channel. The plan includes one consolidated scope review, one design direction and refinement, two consolidated coded-prototype rounds, agreed progress demonstrations and final acceptance checks. Small refinements within the outcome and data/access model are assessed within the plan based on cumulative impact, not charged simply for a field, filter or role name. Defects, necessary outcome details we omitted and our estimating errors are not paid expansions or feedback rounds.
7. Acceptance
Each deliverable is reviewed against approved acceptance criteria. The customer provides clear acceptance or consolidated feedback within the agreed window, and the stage decision and production handover are documented. Use or a request to proceed is assessed in context under the agreement; it is not alone a waiver of latent defects or statutory rights. Exhausting review rounds does not justify leaving an agreed-scope defect unresolved.
8. Changes
A new outcome, material change to the business/data/access model or substantial rework of approved work prompts an impact review, not an automatic fee. We explain alternatives, any incremental price, timing, tests and credit for replaced work before authorised parties approve the change in writing. Electronic approval through the agreed channel is permitted; discussion alone is not acceptance without clear approval. Our estimate overruns and defect correction do not become retrospective customer surcharges.
9. Customer responsibilities
The customer supplies content, brand materials, data, accounts, licences and approvals on time, warrants the right to use them, and consolidates stakeholder feedback. Timing pauses to the extent of customer delay and its impact.
10. Payments and external costs
The written proposal defines payment milestones and the complete price before contracting. Agreed service/integration setup is part of development; recurring hosting, domain, gateway, email, paid API and external-asset charges are disclosed and estimated separately unless the proposal expressly covers them. Provider charges do not turn integration setup or essential notifications into paid add-ons. External services are not purchased at the customer's expense without agreement.
11. Timing and delay
Targets are 4–6 weeks for Web and 6–8 weeks for SaaS after scope approval, required inputs and necessary account approvals, under the written start and delivery plan. We explain the impact of delayed decisions, inputs, providers or approved changes, document the actual schedule adjustment, notify the customer and work to limit the effect. Targets are not unconditional guarantees; external blockers do not remove our agreed recovery responsibilities or statutory delay rights.
12. Third parties and environments
The package includes agreed staging and production setup, appropriate monitoring/backups, recovery instructions and operating handover. Hosting, domain and provider accounts should be in the customer's name where possible, with access and post-handover maintenance ownership defined. Provider approval, availability and prices are outside our control, but agreed integration setup, verification, failure handling and recovery remain our responsibility. The package is not a continuous 24/7 operating service.
13. AI-assisted delivery
AI-assisted tools may accelerate research, documentation, implementation and test preparation. Human experts remain accountable for decisions, review and quality. Confidential or production data will not be entered into an unapproved public service.
14. Intellectual property
Customer materials remain the customer’s. After full payment, transferable rights in listed bespoke deliverables are transferred and the repository is handed over. MVPNexa tools, NexaCore, reusable and open-source components, and third-party material remain with their owners and licences, with sufficient rights to operate and maintain the product.
15. Confidentiality and data
Each party protects the other’s confidential information and uses it only for the project. If MVPNexa processes personal data for the customer, the parties sign a data-processing addendum before real data is used. The Privacy Policy governs website and form data.
16. Testing and defect correction
We perform the agreed reviews/tests and correct approved-scope defects reported within 14 calendar days from agreed production handover. Handover is documented and causes are assessed; expiry does not close an unresolved covered report or remove statutory rights. A new preference or a fault caused solely by changes outside our work is not a defect in our delivery. Provider outages do not excuse agreed failure/recovery behavior. Ongoing maintenance and development are separate; error-free software or operation on unagreed environments is not guaranteed.
17. Commercial outcomes
Services are provided with reasonable professional care, but product-market fit, revenue, investment, growth or regulatory approval is not guaranteed. Launch-ready means ready for the agreed scope, environment and initial load.
18. Cancellation and termination
On customer cancellation, completed milestones, objectively measured work in progress and approved external commitments remain payable; unearned amounts are handled under the signed agreement and mandatory law. Paid usable work is delivered on termination.
19. Liability
Any contractual liability limits apply only to the extent permitted by law. Where lawful, MVPNexa's direct contractual liability is limited to fees paid for the affected order, with indirect losses and expected profits excluded only to the legally permitted extent. These limits do not cover fraud, gross negligence, tort liability or any liability or right that cannot lawfully be waived or restricted.
20. Complaints and disputes
Send complaints to [email protected] with the project number and records. Saudi Arabian law governs. The parties first seek a good-faith resolution; failing that, the competent Saudi court has jurisdiction unless another valid written mechanism applies.
21. General
The parties are independent and no partnership or agency is created. An invalid term does not invalidate the remainder. Updates apply prospectively and do not amend an existing project. The Arabic version governs if this translation differs.