This Project Policy explains how Logicanvas.io (“we”, “us”, “our”) typically handles client engagements. Specifics in your proposal or Agreement override this page where they differ. See also our Terms and Refund Policy.
1. Engagement model
We work as a hands-on technology partner. Engagements are usually project-based, milestone-based, retainer-based, or a mix — confirmed in writing before kickoff.
2. Discovery & proposal
- Discovery call — We learn goals, constraints, and success criteria.
- Proposal / quote — Scope, assumptions, timeline, fees, and payment schedule.
- Confirmation — You accept in writing and complete any required deposit or first invoice.
Until confirmation and (where required) initial payment, we do not reserve delivery capacity as a started project.
3. Kickoff & start of work
After confirmation we schedule kickoff. At kickoff we typically:
- Confirm stakeholders and communication channels.
- Collect access, assets, and priorities.
- Agree the first delivery milestone and review cadence.
Kickoff (or the first billable task after confirmation) marks the project as started for refund purposes.
4. Delivery & communication
- Working rhythm — Async updates plus scheduled calls as agreed (often weekly or bi-weekly).
- Visibility — Progress shared early via demos, staging links, or work-in-progress reviews — not only at final handoff.
- Channels — Email, Slack, or another channel named in the Agreement. Decisions that change scope or budget should be confirmed in writing.
5. Scope & change control
The Agreement defines in-scope work. New features, platforms, or redesigns outside that scope are change requests. We will estimate impact on fee and timeline before proceeding. Work on out-of-scope items starts only after written approval.
6. Client dependencies
Timelines assume timely access, content, and approvals from your side. Waiting on client inputs may push dates without reducing fees already earned for work completed or capacity reserved, unless we agree otherwise in writing.
7. Reviews & acceptance
Milestone or deliverable reviews should be completed within the window stated in the Agreement (or a reasonable period if silent). Silence or use of deliverables in production may be treated as acceptance of that milestone.
8. Ownership & handoff
- Upon payment for a deliverable, you own the custom work created for you under that Agreement (subject to our Terms).
- We document as we go so your team can operate and extend the work.
- Credentials and access we create for delivery should be transferred to you at handoff.
9. Third-party services
Hosting, domains, licenses, APIs, and SaaS tools may be billed by third parties to you directly, or passed through at cost if agreed. Their uptime and policies are outside our control.
10. Support after delivery
Bug-fix windows, warranty periods, or ongoing retainers apply only if written in the Agreement. Otherwise, further work is scoped as a new engagement or change request.
11. Pause or cancellation
Either party may pause or end an engagement as allowed by the Agreement. Fees for work performed and non-cancellable costs remain due. Refunds follow the Refund Policy — no refunds once the project has started, except where a written payment discussion says otherwise.
12. Contact
Project questions: hello@logicanvas.io or Contact.