Service Delivery
& Cancellation

What happens from clarification through launch, how reviews and care work, and what clients can expect when a service ends.

Effective
July 24, 2026
Delivery type
Digital services
Physical shipping
Not applicable
  • Scope comes firstDeliverables and assumptions are written down
  • Milestones stay visibleReview and approval happen throughout
  • Care has boundariesMaintenance is distinct from new scope
  • Exit terms are documentedConsequences are explained before cancellation
Project agreement controls

This page is the public baseline. The accepted proposal or statement of work will identify the deliverables, review periods, launch conditions, ongoing care, handoff, and cancellation rules for the actual project. If it provides more specific terms, those terms control.

Scope and project start

Breauti begins by understanding the problem, users, desired outcome, existing systems, and practical constraints. You do not need a finished brief. Breauti may help turn an early idea into a defined first phase, but work does not begin merely because a request or conversation occurred.

A project starts after both parties accept a written engagement and any required initial payment clears. The engagement should identify the deliverables, included features, design or content responsibilities, supported devices or platforms, material integrations, accessibility target, assumptions, exclusions, milestones, fees, and ongoing responsibilities.

The standard Education Site Package is available only when the organization's needs fit the published package. Larger, multi-location, heavily customized, regulated, or operationally complex work receives a tailored scope and quote.

Milestones and communication

Projects may move through clarification, planning, design, build, content integration, verification, launch preparation, and handoff. The exact sequence depends on the work. Breauti may provide prototypes, preview links, demonstrations, test builds, screenshots, written summaries, or other evidence appropriate to a milestone.

The client should identify a decision-maker and provide timely feedback, content, credentials, and approvals. A delayed decision or missing dependency can pause work and move later dates. Breauti will explain material blockers and proposed next steps, but does not promise a general response-time or completion-time service level unless the engagement states one.

Communication may occur through email, call, text, or—when activated—the client workspace, according to the agreed preference. Accounts, in-site messages, notifications, and SMS are not active on the current public site.

Review, revisions, and acceptance

Breauti expects to refine the work with the client inside the agreed scope and realistic technical, schedule, and budget constraints. The engagement will identify included revision rounds or another review method. “We will keep working until you are satisfied” means reasonable correction and refinement of the agreed deliverables—not unlimited new scope, perpetual redesign, or work outside the accepted project.

Clients must review milestones within the stated review period and identify specific defects, missing agreed requirements, or requested refinements. A request that changes the approved direction, feature set, platform, integration, data model, or audience may be treated as a change request.

Acceptance may occur through written approval, successful completion of agreed criteria, launch authorization, use in production, or expiration of a stated review period without a material rejection. The project agreement will define the applicable method and any correction period.

Ongoing care

The Education Site Package includes required ongoing care at $65 per month. The accepted order will describe the actual maintenance, updates, security work, and support included. Care begins on the date stated in the order and continues until canceled according to the agreement and this policy.

Ongoing care is intended to keep the agreed product supported; it is not an unlimited development subscription. Major new features, substantial redesigns, new applications, large migrations, uncommon integrations, premium third-party services, or work caused by an unapproved external change may require a separate quote.

For custom projects, ongoing care may be included, optional, or separately quoted. The engagement should state who controls domains, hosting, app-store accounts, cloud projects, source repositories, backups, licenses, provider billing, and production credentials.

Cancellation, suspension, and deactivation

A client may request cancellation through the method identified in the agreement or, when available, the client billing portal. Before confirming, Breauti will state the effective date and explain material consequences. The future portal is intended to show ongoing care, payment-plan status, invoices, payment history where applicable, and a transparent cancellation path; it is not active today.

When ongoing care ends, maintenance, security work, updates, monitoring, and support supplied under that care also end. If Breauti controls hosting as part of the canceled service, the website or app may be deactivated after the paid service period unless the parties arrange a handoff, continued hosting, or another written transition. Breauti will not describe a cancellation as consequence-free when continued operation depends on the service.

Breauti may suspend work or service for nonpayment, unlawful use, a material security threat, abuse, or a material breach after notice and an opportunity to cure when reasonable. Immediate protective action may be taken where delay would create substantial harm or legal exposure. Accrued fees, completed work, committed costs, and launch-cost installments remain governed by the accepted agreement and Payments & Refunds Policy.

Handoff, data, and third-party services

The engagement will identify what is handed off and in what form, which may include production access, source code, design files, content exports, documentation, credentials, or client-owned provider accounts. Reusable Studio tools, licensed assets, open-source software, third-party components, and provider accounts remain subject to their own ownership and license terms.

Before a hosted service ends, Breauti and the client should agree on any reasonable export or transition work, its format, timing, security method, and fee. Breauti may retain records required for taxes, accounting, security, disputes, or legal claims and will handle personal information under the Privacy Policy. A client should download available exports before the stated deactivation date.

Domains, hosting providers, app stores, Firebase, Stripe, email or SMS providers, APIs, banks, and other external platforms can change rules, prices, features, review outcomes, or availability. Breauti will make reasonable efforts to plan for material dependencies but cannot guarantee a third party's continued operation or approval.

No physical shipping applies to Studio's digital services. If a project later includes hardware or another physical item, separate written delivery, risk-of-loss, return, warranty, and address terms must be agreed before purchase.