Service Delivery
& Cancellation

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 and its $600 launch plus $65/month care are small-organization prices available only when the organization's needs fit the published package. Larger, multi-location, heavily customized, regulated, or operationally complex education work receives a tailored launch and ongoing-care quote.

The small custom-site offer—a typical $600 launch plus required $25/month care—is for solo professionals and very small businesses whose website can remain focused and uncomplicated. Apps, larger teams, advanced capabilities, substantial commerce or content needs, uncommon integrations, and other complex work receive a tailored scope and quote.

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.

Every project uses the Google-authenticated client workspace and the verified email on the signed-in Breauti account as its default communication channels. Project requests, messages, revisions, decisions, status updates, Drive-access notices, and agreements may be recorded in the workspace. Phone calls or non-marketing texts are optional and are used only when the client provides a number and the applicable consent; the Studio does not operate a marketing-SMS program.

A client or Breauti may request an optional project-related phone appointment for intake, clarification, review, a feature walkthrough, or support. Breauti offers available times from the shared Studio schedule and the client chooses a time through the workspace. A time is not reserved until the workspace confirms the selection. The client may request a different time or cancel; Breauti may reschedule or cancel when reasonably necessary. After confirmation, the client may open a prefilled Google Calendar event or download an Apple Calendar-compatible calendar file. These are personal convenience copies rather than the authoritative Studio schedule, do not give Breauti access to the client's calendar, and do not update automatically; after a reschedule, the client should add the new time and remove the old calendar copy. Appointment availability does not create a response-time or completion-time guarantee unless the signed engagement expressly states one.

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.

The project agreement defines how the client accepts work, any review and correction period, and the event that starts care billing. Some projects require express launch confirmation and do not allow silence, publication, or delivery alone to count as acceptance or authorize a care charge. If Breauti proposes a changed agreement after an agreement is already executed, the existing version remains active unless Breauti signs the proposed version and the client then signs that same version.

The small-organization Education Site Package lists required ongoing care at $65 per month. The straightforward small custom-site offer lists required ongoing care at $25 per month. Website Maintenance for an existing site starts at $50 per month by default and is confirmed after Breauti reviews the current site. The signed agreement states the exact care price and billing interval, which may be monthly, yearly, or another supported number of months; no unstated discount applies. Included care varies by project and may be limited to essential maintenance and defect fixes without new features. Care begins only under the signed agreement's stated date or launch condition and continues until canceled under its terms.

Clients may request changes and new features through ongoing care. Breauti may include a requested feature when its design, engineering, integration, and testing effort reasonably fits the active care relationship. Ongoing care is not unlimited development: a substantial feature, major redesign, new application, uncommon integration, premium third-party service, or unusually time-intensive request may require a separate quote and one-time charge. That change does not restart or replace the original launch balance. Breauti will explain the boundary, issue a replacement agreement for any material scope or price change, obtain both signatures, and confirm any required one-time payment before the separately charged work begins. When the signed terms say so, ordinary maintenance and updates for the delivered addition then become part of ongoing care; future material expansions can still require a separate quote.

Included requests are scheduled reasonably against scope, urgency, operational risk, and available capacity. The $25 monthly small-site care rate, $50 monthly existing-site maintenance rate, and $65 monthly small-education care rate are introductory startup pricing. As the Studio's client base, capacity, and operating record grow, Breauti may change standard eligibility, limits, scheduling, or pricing for new agreements. A signed client's rate and included care remain unchanged through the current service term. Any proposed price or material care-term change for a later renewal requires advance notice and the client's affirmative acceptance; without acceptance, care ends at the close of the current term under the cancellation, pause, and migration process.

For custom projects outside the straightforward small-site offer, ongoing care may be included, optional, or separately quoted. Larger organizations and more demanding products may require a higher care level. Breauti manages client domains through Cloudflare during active care, including the agreed setup, DNS configuration, and administrative work, and coordinates the handoff if the client migrates. Domain registration, renewal, transfer, premium-name, and registry charges remain separately priced third-party costs. Business email is also separately priced, including any agreed setup and mailbox or provider fees.

Breauti keeps cancellation easy to find. A client may stop future automatic renewal through the clearly labeled Stripe-hosted billing control in the applicable workspace without a retention conversation, or use the workspace service control or support@breauti.com if that control is unavailable. The client can end care at the close of the current paid period or request an immediate end with a prorated refund of the unused recurring-care payment. Build payments, completed work, and separate third-party costs are not part of that care refund except where the signed agreement or non-waivable law says otherwise.

When care ends, Breauti's maintenance, security work, updates, monitoring, revisions, and support end. A Breauti-hosted product may be deactivated under its signed agreement. Cancellation does not by itself disable or delete a client-controlled app listing, cloud project, payment account, repository, or data. For products with active paid transactions, the parties should coordinate safe completion, refunds, or transfer before Breauti stops a component it controls. Breauti will state any deadline for removing only its own inactive working copies, subject to the signed transition terms, required records, and backup cycles.

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.

The signed agreement identifies what is handed off and in what form. The client retains its lawful original assets and data. Under the new continuity agreement, Breauti-built projects receive a client-accessible project-specific source repository and a recovery package, with project-specific code assigned and shared Breauti components licensed for that project at handoff. A maintenance-only engagement does not give Breauti ownership of an existing site's third-party code. Older signed agreements remain unchanged unless both parties sign a replacement.

Standard migration from another platform is included with every launch. Breauti will migrate the accessible client-provided assets, Breauti-created non-code asset files intentionally delivered into the project folder, content, data, and agreed materials identified in the launch scope. Breauti manages the client's domain through Cloudflare during active care and will coordinate DNS, registrar, or account handoff when migration is requested.

When a site or app uses Firebase, the client must maintain a client-controlled Google Cloud Billing account and valid payment method for the production project. Firebase usage charges, if any, are billed separately by the provider. They are not included in the launch or ongoing-care price unless the accepted agreement expressly says otherwise.

When Breauti processes personal information on the client's behalf, the engagement will identify the parties' privacy roles and documented instructions and include any data-processing terms required for the work. Those terms may address confidentiality, security, subprocessors, assistance with individual rights and incidents, international-transfer safeguards, and return or deletion of client data. The client remains responsible for its own lawful collection, notices, permissions, and operational obligations.

Migration and handoff assistance away from Breauti is included when care ends. The client may also request an early continuity handoff under the signed agreement's closure or unavailability conditions. The recovery package describes build, deployment, dependencies, services, data exports, and how the client's authorized account owner can rotate credentials; it does not include live secrets. The client chooses and pays any successor. Independent paid escrow applies only if expressly included in the signed scope. Provider exit charges, paid licenses, and unavailable third-party data remain separate. Breauti may retain records required for taxes, accounting, security, disputes, or legal claims and will handle personal information under the Privacy Policy.

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.