Last Updated: April 2026 // DOTODD Service Terms
We carefully review each system inquiry, business request, or design plan received through our contact channels. To maintain a high level of code execution and project care, we only accept projects that match our current team capacity, technical stack specialization (including specialized restaurant engineering), and schedule availability.
Any project estimations, budget scopes, proposed timelines, or feature maps provided before an official contract signing serve as informational guides based on early inputs. Confirmed scopes, system features, precise pricing milestones, and explicit operational directions are finalized only within a signed service agreement.
We build projects using structured development stages with clear feedback check-ins. Clients are requested to review and approve work at the end of each milestone stage (such as system architecture, design approvals, beta tests, or staging reviews) before our development team proceeds to subsequent layout and integration phases.
We understand that operational plans can change during development. If a client requests new functionality, layout updates, structural database modifications, or integrations not specified in the original agreement, these adjustments will be handled under a separate scope update, requiring custom cost estimates and updated timeline approvals.
Our payment structures are organized around predictable deposit structures or explicit milestone progress check-ins. Development tasks begin immediately upon receipt of the initial deposit, and subsequent project blocks or final production handovers are contingent upon completing the respective milestone payments within the agreed timeframes.
Building custom corporate tools requires consistent client collaboration. Delays in providing necessary project resources (such as copywriting assets, menu items, branch imagery, branding elements, or access credentials) or delays in milestone approvals can extend delivery schedules proportionally.
Before deploying a platform to a live environment, we perform rigorous tests in a private staging setting. The client is responsible for reviewing and testing the platform during this stage to confirm that the business logic behaves exactly as outlined in the initial functional specifications before public deployment.
To ensure smooth early operations, we include a standard technical support period immediately following live deployment to address bugs or structural code anomalies. Requests for ongoing maintenance, database hosting administration, security adjustments, or additional feature upgrades can be handled under a separate ongoing support retainer.
After the agreed payment is completed, clients receive ownership of the agreed project deliverables, source code, and handover materials unless otherwise stated in the project agreement. We may retain rights to reusable internal tools, general development methods, frameworks, and non-client-specific components used to deliver the work.
We aim to build reliable and maintainable systems, but we cannot guarantee results that depend on external factors such as hosting outages, third-party service failures, search engine rankings, advertising performance, payment provider decisions, user behaviour, or business sales outcomes. Any known limitations will be communicated where reasonably possible.