Jani Operations
Client information & engagement policies
A plain-language overview of how conversations, scope, information, deliverables, and approvals are handled.
How an engagement starts
Most engagements begin with a vetting call and a short discovery conversation. A proposal or scope summary is prepared after the call when the work is a fit. No form submission, estimate, or readiness result automatically creates a client commitment.
Scope and approvals
The written proposal is the source of truth for scope, deliverables, assumptions, exclusions, timing, fees, and payment milestones. Changes are documented and approved before work outside the agreed scope begins.
Client responsibilities
Clients provide timely access to people, systems, records, and decisions needed for the agreed work. Delays in information, review, or approvals may change the delivery schedule.
Information handling
Information is used to evaluate and deliver the requested service. Access is limited by workspace and role. Sensitive files are shared through the secure portal when available; email is used for notifications and scheduling, not as the system of record.
Deliverables and review
Drafts are reviewed with the client before release. A released deliverable is versioned, and later changes are issued as a new version. Client feedback and approval are recorded with the project.
Payments and cancellation
Fees, deposits, recurring support, payment milestones, cancellation terms, and any refund treatment are stated in the proposal or agreement for the engagement. Stripe payment pages and receipts reflect the approved commercial terms.
Questions about a specific engagement? Schedule a vetting call or request a specialized quote.