Delivery Policy

RISOSI delivers professional services and digital work products—code, designs, documentation, builds, and related artifacts—according to an agreed proposal or SOW. We do not ship physical retail products as a primary business model. If an IoT engagement includes hardware samples or devices, logistics for those items will be specified separately in the SOW.

Delivery typically occurs through secure digital channels: repositories, design files, staging URLs, package registries, cloud environments, or encrypted file transfer—not courier parcels.

An engagement starts after written acceptance of the proposal/SOW and receipt of any required deposit. Kickoff usually includes confirming goals, success criteria, stakeholders, communication channels, tools access, and an initial backlog or work plan.

Client delays in providing access, content, or decisions may shift the schedule. We will note material blockers in writing and update milestone dates when needed.

Target dates in proposals are estimates based on assumed Client responsiveness, stable scope, and third-party availability. Fixed deadlines apply only when explicitly stated as commitments in the SOW.

We usually deliver in milestones (for example: discovery → design → build → QA → launch). Each milestone may have its own acceptance step before the next phase begins. Parallel workstreams may be used when scope allows.

Business days follow Bangladesh time (UTC+6) unless the SOW defines another calendar. Public holidays in Bangladesh may affect staffing; we will communicate known holiday impacts early.

During active projects we provide regular updates via the agreed channel (email, chat, or project board). Status includes completed work, upcoming tasks, risks, and decisions needed from you.

Urgent production incidents for supported systems should be raised through the contact method defined in your support or warranty terms. Marketing-site inquiries via hello@risosi.com are answered within roughly 1–2 business days and are not a substitute for production on-call unless contracted.

When we submit a milestone, you will review against the SOW and any written acceptance criteria. Unless the SOW states otherwise, you have seven (7) to fourteen (14) calendar days to accept or provide consolidated, written feedback. Silence after the review window may be treated as acceptance so the project can proceed.

Feedback should be specific and within scope. Out-of-scope requests are handled as change orders. Minor defects found after acceptance may still fall under a limited warranty window if one is included.

At the end of an engagement (or per milestone if agreed), handover may include some or all of the following, depending on scope and payment status:

We typically develop against staging or preview environments before production launch. Production cutover responsibility is defined in the SOW—sometimes RISOSI deploys, sometimes your team does with our support.

App store reviews, DNS propagation, SSL issuance, Client UAT staffing, and third-party API approvals are outside our sole control and may extend go-live dates even when engineering work is complete.

We will notify you promptly if we foresee a delay on our side and propose a revised plan. Delays caused by late Client feedback, missing assets, unpaid invoices, scope changes, third-party outages, or force majeure (including natural disasters, widespread outages, or events beyond reasonable control) extend delivery dates accordingly.

Chronic unpaid invoices may pause delivery until accounts are current. Paused projects may require a re-kickoff and revised timeline when restarted.

If an engagement ends early, we deliver work-in-progress that has been paid for, in a commercially reasonable format. Incomplete features may be unfinished or unsuitable for production; we will label known limitations.

We are not obligated to continue hosting Client environments after the engagement unless a hosting or retainer agreement says otherwise. Migration assistance can be scoped separately.

When a project includes physical components, the SOW will state who procures devices, who pays shipping, and where items are delivered. Risk of loss for Client-owned hardware follows the SOW; typically risk transfers on delivery to the address you provide or on handover at our Dhaka studio if agreed.

Customs, import duties, and courier delays for international hardware are the responsibility of the party named in the SOW.

Creative and product work usually includes a defined number of revision rounds per milestone. Extra rounds are billable. Consolidated feedback in each round keeps delivery predictable; continuous ad-hoc micro-changes may be treated as additional scope.

For schedule or handover questions on an active project, contact your project lead. General inquiries: hello@risosi.com · +880 1619-749239 · Dhaka, Bangladesh · Sat–Thu · 9:00–18:00 (UTC+6).