Delivery Policy
Digital delivery, handled clearly.
BroDev delivers websites, apps, dashboards, bots, plugins, automation tools, source files, builds, and support work electronically. This policy explains how project delivery, handover, revisions, deployment, and client approvals work.
01
Digital only
No physical shipping is involved. Delivery happens through online access, files, links, builds, or deployment.
02
Scope based
Timelines and deliverables depend on the purchased service, confirmed scope, required assets, and feedback.
03
Clear handover
Final delivery may include project files, live deployment, credentials, documentation, or usage instructions.
Delivery Identity
No boxes.
No shipping delays.
Everything we provide is digital. That includes custom software work, deployed websites, source code, app builds, plugins, bots, admin access, integrations, maintenance, and technical support.
How Delivery Works
Delivery depends on what we build for you.
A small website update may be delivered as a completed live change, while a larger Laravel system may include source code, database setup, admin dashboard access, deployment support, and handover instructions.
Android app work may be delivered as an APK, AAB, source code, Firebase setup, release preparation, or Play Console support depending on the service agreement.
Bot, plugin, API, and automation work may be delivered through a working setup, repository access, downloadable files, connected accounts, or documented configuration steps.
Delivery Methods
Files, links, access, deployment, and documentation.
Depending on the project type, BroDev may deliver the work through one or more digital methods agreed during the order or project discussion.
Email delivery
Download links
Git repository
Hosting server
Admin dashboard
APK / AAB builds
Plugin files
Setup documentation
Telegram bot setup
API configuration
Database migration
Deployment support
Timelines
Delivery starts when the project is ready to begin.
Work normally begins after payment confirmation and after we receive the required project information, content, branding assets, access credentials, product details, technical requirements, and approvals.
Smaller tasks may be completed within a few business days. Larger websites, apps, dashboards, integrations, or custom systems may require more time based on feature complexity and revision cycles.
Any timeline shared by BroDev is an estimate unless a fixed delivery date is clearly agreed in writing. Delays may happen if feedback, content, access, third-party approval, or required information is late.
Delivery Details
What can affect delivery.
Client information
Missing content, images, hosting access, API keys, app assets, or product details can delay delivery.
Scope changes
New features, redesigns, or major changes outside the original scope may require extra time and payment.
Third-party services
Hosting, domains, Paddle, Google Play, Firebase, Telegram, WordPress, and API providers can affect timelines.
Testing and approval
Some projects require testing, client review, corrections, and final approval before completion.
Deployment access
Deployment support may require domain, hosting, server, database, store, or platform access from the client.
Platform review
App stores, payment providers, and plugin marketplaces may require review time outside BroDev’s control.
Delivery Process
From order confirmation to handover.
01
Order confirmation
We confirm the selected service, payment status, project type, required information, and expected delivery method.
02
Information collection
You provide the required content, assets, access credentials, product details, technical notes, and approval requirements.
03
Project preparation
We review the scope, prepare the development setup, confirm missing details, and organize the delivery path.
04
Development or setup
We build, configure, customize, integrate, deploy, or prepare the digital work according to the agreed scope.
05
Testing and revision
We test important flows and apply included revisions that match the original project agreement.
06
Final delivery
We deliver files, access, links, builds, deployed work, setup notes, or documentation through the agreed digital method.
07
Completion
The project is considered delivered once the agreed digital work, access, files, or deployment has been provided to the client.
Important Terms
Clear rules for digital delivery.
No physical shipment
BroDev does not ship physical goods. Any shipping address, shipping carrier, or physical delivery timeline does not apply to our digital services unless clearly stated otherwise in a separate agreement.
Revisions and approval
If revisions are included, they apply only to the agreed project scope. Extra features, major redesigns, new pages, new integrations, or changes outside the original agreement may require additional time and cost.
Deployment support
If deployment support is included, BroDev may help configure hosting, domain settings, SSL, environment files, databases, app builds, bot webhooks, WordPress setup, or plugin installation according to the purchased service.
Hosting, domain, server, Play Store, payment gateway, API, plugin, license, or third-party platform fees are not included unless clearly stated.
Third-party delays
Some deliveries depend on third-party services such as hosting providers, domain registrars, Paddle, Google Play, Firebase, Telegram, WordPress, API providers, email services, or payment gateways. Delays caused by these platforms are outside BroDev’s direct control.
Delivery completion
A project may be considered delivered when the agreed files, build, website, plugin, bot, dashboard, access details, setup notes, or deployed system has been provided to the client through the agreed delivery method.
Need Help?
Questions about your delivery or handover?
Contact BroDev if you need clarification about your project timeline, delivery method, required information, deployment, or final handover.