This page explains how a TarraCoata engagement works in practice. It is informational and describes our standard approach; the binding terms for any specific project are the signed proposal, statement of work or contract, which prevail in case of conflict.
1. Project workflow
Stage 1 — Discovery. We map objectives, users, constraints, integrations and success metrics, and agree the scope, budget and timeline. Output: a written proposal with milestones and acceptance criteria.
Stage 2 — Architecture and design. We define the system architecture, data model, security model and interface direction. Output: technical plan and design direction for approval.
Stage 3 — Build. Implementation runs in short iterations with a shared staging environment you can review at any time. We report progress at agreed intervals.
Stage 4 — Quality assurance. Functional testing, cross-browser and responsive checks, accessibility review against WCAG 2.2 AA, performance and security review.
Stage 5 — Launch. Deployment, domain and DNS configuration, analytics and monitoring, handover of repositories and credentials, and a walkthrough session.
Stage 6 — Post-launch care. A warranty window followed, optionally, by a maintenance retainer.
2. Deliverables
Each proposal lists deliverables explicitly. Typical deliverables include: production application or website, source code in a repository you control, design files, configuration and environment documentation, integration setup, admin training and a short handover guide. Anything not listed as a deliverable is out of scope.
3. Revisions
Each design and build milestone includes the number of revision rounds stated in the proposal — commonly two rounds per milestone. A revision round is a single consolidated set of feedback, submitted in writing within the review window.
Changes that alter agreed scope, add features, or repeat previously approved decisions are treated as change requests and are quoted separately before work continues. We will always tell you in advance when a request falls outside the included rounds.
4. Acceptance
When a milestone is delivered you have a review window — normally 7 business days — to test it against the agreed acceptance criteria and either accept it or submit a written list of defects. A defect is a deviation from the agreed specification, not a change of preference.
If no response is received within the review window, the milestone is deemed accepted so that the schedule can continue. Defects reported within the window are corrected at no additional cost.
5. Warranty
For 30 days after launch we fix, free of charge, any defect in our work that deviates from the agreed specification. The warranty does not cover changes to third-party services, new feature requests, content changes, or issues caused by modifications made by others.
6. Delays
- Client-side delays. Timelines assume feedback, content and approvals arrive within the agreed windows. Delays beyond 10 business days may require rescheduling into the next available delivery slot, and milestone payments already due remain payable.
- TarraCoata delays. If we fall behind for reasons within our control we notify you promptly, provide a revised date and, where the delay is material, agree a remedy under the Refund & Cancellation Policy.
- External delays. Third-party approvals, app-store reviews, API changes, hosting incidents and force majeure events extend deadlines by the period of the delay.
7. Client responsibilities
To keep an engagement on schedule, the client provides:
- A single named decision-maker empowered to approve milestones.
- Content, brand assets, product data and copy by the agreed dates.
- Timely access to accounts, domains, hosting, analytics and third-party services.
- Consolidated written feedback within the review windows.
- Any legal or regulatory requirements specific to their sector, disclosed in advance.
- Payment against the agreed schedule.
8. Communication
We work in Hebrew and English, by email and scheduled calls, with a shared written record of decisions. Urgent production incidents during a maintenance retainer have a dedicated escalation path defined in the retainer.
9. Maintenance
Optional monthly retainers cover: dependency and security updates, monitoring and uptime checks, backups verification, small content and layout changes, bug fixes, performance tuning and a monthly report. Retainer hours are defined per plan, do not roll over, and can be cancelled with 30 days' notice.
10. Confidentiality and data
We treat your business information as confidential and will sign a mutual NDA on request. Personal data handled during an engagement is processed under the Privacy Policy and, where we act as processor, the Data Processing Agreement.
11. Intellectual property
Ownership of deliverables, background IP and licensing is governed by the Copyright & Intellectual Property Policy.
12. Contact
To start a project or ask about an existing one: tarracoatainfo@gmail.com · [Phone Number] · [Registered Address].