Client Service Agreement

Version 0.9 — Effective July 24, 2026

RooferConversionLab is a service of Rumulla Group LLC. Prior versions of this agreement are archived and available on request.

This agreement is between Rumulla Group LLC, a Minnesota limited liability company (“RCL,” “we,” “us”), and the business that accepts it (“Client,” “you”). RooferConversionLab is the brand name under which RCL provides the services described in this agreement.

How you accept it. You accept this agreement by checking the “I agree to the Terms of Service” box at checkout, by signing it electronically, or by paying an invoice that references it — whichever happens first. Checking the box has the same legal effect as a signature.

Which parts apply to you. This agreement has two layers: the General Terms (Part I), which apply to every Client, and one or more Service Schedules (Part II), each describing a specific service. Only the Schedule(s) for the service you actually purchased apply to you. Which service and plan you purchased is determined by the checkout page, payment link, or order form you completed. There are currently four Schedules: Schedule A — AI Intake Caller, Schedule C — Conversion Page System, Schedule D — Website Redesign (One-Time), and Schedule E — Demo-Built Website (Hosting & Maintenance Plan).

Part I — General Terms

1. Definitions

2. Term, renewal, and cancellation

  1. This agreement starts when you accept it and continues month to month.
  2. Subscriptions renew automatically each billing period until canceled.
  3. You may cancel at any time — by email to rikhil@rooferconversion.com or through your billing portal. Cancellation takes effect at the end of the current billing period. Except where the Guarantee in your Schedule applies, fees already paid are not refunded, and usage-based fees already incurred remain payable.
  4. We may terminate or suspend the Service (a) for non-payment not cured within 7 days of notice, (b) if you materially breach this agreement, or (c) immediately if we reasonably believe your use of the Service violates the law (see Section 4). If we terminate without cause, we will refund the unused portion of any prepaid period.

3. Fees and billing

  1. Fees are as stated on the checkout page or payment link you completed. Plan mechanics are described in your Schedule.
  2. You authorize us to charge your payment method on file for recurring subscription fees and for usage-based fees as they are incurred, via our payment processor (Stripe).
  3. You will keep a valid payment method on file while the Service is active. If a charge fails, we may retry it and may suspend the Service until payment succeeds.
  4. Fees do not include taxes; if any sales or similar tax applies, it will be added.
  5. Fee disputes must be raised within 30 days of the charge, and follow the dispute process in your Schedule where one is defined.

4. Your responsibilities and warranties

  1. Accurate setup information. You will provide accurate business information (service area, hours, calendar access, forwarding configuration, intake preferences) and keep it current. The Service says what you configure it to say; wrong inputs produce wrong outputs.
  2. Inbound Leads only. The Service contacts only Inbound Leads — people who initiated contact with your business and provided their number. You will not ask or configure the Service to call purchased lists, scraped lists, aged lead lists, or any person who has not initiated contact with your business. Requests to do so are outside the scope of the Service and will be declined.
  3. Consent warranty. You represent and warrant that every Lead routed to the Service is an Inbound Lead as defined above, and that your own lead sources (website forms, ads, call lines) are operated lawfully.
  4. Form consent language. If the Service places callbacks to your web-form leads, you will add and keep the following (or substantially similar) disclosure near your form's submit button: “By submitting, you agree to receive a call and/or text at the number provided, which may use automated or AI-assisted technology.” If this language is removed, we may pause form callbacks until it is restored.
  5. Your sales process is yours. The Service captures, qualifies, books, and delivers. What happens after delivery — returning calls, showing up, quoting, selling, performing work — is entirely yours. You are solely responsible for your conduct with your customers and for your compliance with laws applicable to your business (licensing, contracting, insurance practices).

5. Our responsibilities

  1. We will provide the Service described in your Schedule with reasonable skill and care.
  2. AI and recording disclosure. Calls handled by the Service disclose, at the start of the call, that the caller/answerer is an AI assistant and that the call is recorded.
  3. Calling rules. Outbound calls are placed only (a) in immediate response to an inquiry the Lead made within the previous 60 minutes, or (b) between 8:00 a.m. and 9:00 p.m. at the Lead's local time. Callbacks that would otherwise fall outside that window are queued to the start of the next window.
  4. Opt-outs honored. Any Lead who asks not to be called again is logged and suppressed from further outbound contact by the Service.
  5. Records. We keep the Event Log and Recordings so that everything the Service did is countable and auditable — including by you.

6. Data, recordings, and privacy

  1. Your leads are yours. Lead contact details, lead sheets, bookings, and the Recordings of your calls belong to Client. We claim no ownership of your customer relationships.
  2. Our license to operate. You grant us the right to process this data to provide the Service: to record, transcribe, log, analyze, and deliver it, and to use it internally to monitor and improve Service quality.
  3. Subprocessors. We use industry-standard providers to deliver the Service — currently including voice-AI infrastructure (Retell AI), telephony and SMS carriers, Google Workspace (logs, sheets, calendar), and Stripe (billing). A current list is available on request.
  4. No resale. We do not sell your lead data and do not share it with anyone except the subprocessors above, you, and destinations you designate.
  5. Recording consent. You consent to the recording of calls handled by the Service and acknowledge Recordings are made available to you. Recordings and the Event Log are retained for at least 4 years for compliance purposes, after which they may be deleted.
  6. On written request after termination, we will provide an export of your lead sheets and Recordings within 30 days.

7. What we do not promise

  1. No outcome guarantees. We report and, where stated in your Schedule, guarantee things the Service itself does — calls answered, details captured, inspections booked. We make no promise of jobs won, contracts signed, or revenue earned, and no representation about the quality or intent of any individual Lead.
  2. AI limitations. The Service uses artificial-intelligence systems. AI can mishear, misunderstand, or answer imperfectly. We work continuously to improve it, and the Guarantee in your Schedule is your remedy if it underperforms — but the Service is provided “as is” and we disclaim all implied warranties, including merchantability and fitness for a particular purpose.
  3. No guaranteed capture. Telephony, carriers, and networks fail sometimes. We do not warrant that every call will be answered or every callback completed.
  4. The Service provides intake and scheduling only. It does not provide quotes or pricing commitments beyond what you configure, and it does not provide legal, insurance, or claims advice to Leads.

8. Indemnification

  1. By Client. You will defend and indemnify RCL against third-party claims, damages, fines, and reasonable attorneys' fees arising from: (a) Leads you routed to the Service who were not Inbound Leads or otherwise lacked consent to be contacted; (b) your breach of Section 4; (c) your products, services, or conduct toward your customers.
  2. By RCL. We will defend and indemnify you against third-party claims arising from our material violation of the calling rules in Section 5 with respect to Leads you properly routed to us as Inbound Leads.
  3. The indemnified party must give prompt notice and reasonable cooperation; the indemnifying party controls the defense.

9. Limitation of liability

  1. Neither party is liable for indirect, incidental, consequential, or punitive damages, or for lost profits or lost business, even if advised of the possibility.
  2. Each party's total aggregate liability under this agreement is capped at the fees Client paid to RCL in the 12 months before the event giving rise to the claim.
  3. The exclusions and cap above do not apply to: a party's indemnification obligations under Section 8, Client's obligation to pay fees owed, or either party's fraud or willful misconduct.

10. General

  1. Independent contractor. RCL is an independent contractor, not your employee, agent for general purposes, partner, or joint venturer. You authorize RCL to answer and place calls on your behalf solely as described in your Schedule.
  2. Governing law and venue. This agreement is governed by the laws of the State of Minnesota, and disputes will be brought in the state or federal courts located in Minnesota. Before filing, both parties agree to try in good faith to resolve any dispute informally for 30 days.
  3. Entire agreement; amendments. This agreement (General Terms + your Schedule(s) + your checkout selections) is the entire agreement and replaces prior discussions. We may update these terms for future billing periods by posting a new version with a new version number and effective date and notifying you by email at least 14 days before it takes effect; if you don't agree to an update, your remedy is to cancel before it takes effect. The version you accepted remains archived and available on request.
  4. Assignment. Neither party may assign this agreement without the other's consent, except RCL may assign it to an affiliate or successor entity in connection with a reorganization, merger, acquisition, or sale of the business, provided the Service and its terms continue unchanged.
  5. Notices. Notices go to rikhil@rooferconversion.com for RCL and to the email you provided at checkout for Client.
  6. Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control (carrier outages, natural disasters, acts of government).
  7. Severability. If any provision is unenforceable, the rest of the agreement stands.
  8. Electronic contracting. Both parties agree this agreement may be formed and signed electronically, including by checkbox acceptance at checkout.

Part II — Service Schedules

Schedule A — AI Intake Caller (“Never miss a roof lead again”)

A1. The Service

An AI operator that:

  1. Answers your inbound calls when your team doesn't — after hours, on overflow, or by configuration — typically by the second or third ring;
  2. Calls back your web-form leads promptly (targeting under 60 seconds) after they submit your website form, 24/7;
  3. Runs a roofing intake — the same questions your office manager would ask: name, address, roof problem, insurance or cash, urgency, and where relevant, storm date, carrier, and claim status;
  4. Delivers the result to your team as a complete lead sheet (text/email/sheet, per your configuration) and/or books an inspection directly onto your calendar for the call types you designate;
  5. Records and logs everything — every call, capture, and booking appears in the Event Log with its Recording, and you receive a monthly report of calls answered and inspections booked.

Configuration. You choose, per call type, whether the Service captures-and-hands-off (your team calls back holding the lead sheet) or books directly onto your calendar. Defaults at onboarding: business-hours calls → capture and hand off; after-hours, overflow, and web-form callbacks → direct booking where a time is agreed.

A2. What the Service is not

A3. Plans and fees

You selected one of the following at checkout (the checkout page controls which):

  1. Standard plan — flat monthly fee (the amount stated at your checkout; no setup fee; month to month; cancel anytime). Founding-rate lock: if your checkout stated a founding rate, that rate is yours for as long as your subscription remains continuously active.
  2. Performance plan — $0/month, plus a per-Booked-Inspection fee (the amount stated at your checkout, currently $40) for each Booked Inspection the Service delivers, as defined in Section A4 — booked onto your calendar or delivered with a confirmed date and time on your lead sheet. Usage fees are billed monthly in arrears to your card on file. A valid payment method on file is required before Go-Live.

You may switch plans for a future billing period by written request.

A4. “Booked Inspection” — definition and disputes

A “Booked Inspection” is a call or callback handled by the Service in which:

  1. the Lead agrees to a specific date and time for an inspection, estimate, or on-site visit; and
  2. the Service creates the corresponding calendar event or delivers the confirmed date and time on the lead sheet; and
  3. both of the above are evidenced by the Recording and the Event Log.

Counted once: the same Lead (same phone number) booking for the same property within 30 days counts as one Booked Inspection, regardless of reschedules.

Not billable: bookings created from calls that the Recording shows to be spam, solicitors, wrong numbers, or tests; bookings the Lead cancels on the same call.

Still billable: no-shows and later cancellations. The Service's job ends when the appointment is booked with the Lead's agreement and delivered to you (calendar event or lead sheet); show rate belongs to your follow-up process.

Disputes: you may dispute any billed Booked Inspection within 7 days of the invoice by identifying the entry. The test is the Recording: if it does not show a date and time agreed, we credit the fee. No other evidence is argued.

A5. The 30-Day Guarantee

Try it for 30 days from your Go-Live Date. If, after listening to the Recordings of the calls it answered and the inspections it booked, you do not feel the Service was clearly worth it, tell us in writing within that 30-day window and we will:

  1. refund what you paid for the period — on Standard, your first month's fee; on Performance, the per-Booked-Inspection fees incurred during the window — and
  2. turn the Service off.

That's the whole process. We may invite you to review the Recordings together first, but the refund is not conditioned on our agreement. The Guarantee is judged on what the Service provably did — calls answered and inspections booked, as shown in the Recordings and Event Log — and is available once per Client, on your first subscription only.

A6. Onboarding requirements

Go-Live requires, with our guided help: (1) call forwarding or number configuration from your side; (2) for form callbacks, webhook or notification access to your web form and the consent language in General Terms Section 4.4; (3) your business profile (service area, hours, calendar access, intake preferences); (4) a valid payment method on file. Setup is typically days, not weeks; delay caused by missing items on this list does not extend billing periods, but the Guarantee window always runs from Go-Live, not from checkout.

A7. Numbers and offboarding

Any tracking or service phone number we provision remains ours; your own business numbers are never ported or controlled by us — forwarding is configured on your side and reverts the moment you remove it. On termination we deliver final lead sheets and, on request, the export in General Terms Section 6.6.

Schedule C — Conversion Page System (“head-to-head pilot”)

C1. The Pilot

A free, time-boxed, head-to-head test of RCL's conversion page system against Client's existing landing page, on Client's own live Google Ads traffic:

  1. RCL builds and hosts intent-matched landing pages for Client's paid search traffic (emergency, storm/insurance, replacement, repair, financing), each with a lead-capture form, on a subdomain RCL controls;
  2. Traffic is split 50/50 between RCL's pages (the “System arm”) and Client's existing page (the “Control arm”), via Google Ads experiments or an RCL-operated click router;
  3. Both arms are measured identically (see C2) — a lightweight tracking snippet on both sides, and one call-tracking number per arm, both instantly forwarding to Client's own phone line;
  4. Every captured lead is delivered to Client (CRM or spreadsheet, per configuration) as it arrives — pilot leads are Client's to work, immediately;
  5. A live dashboard shows both arms' clicks, contacts, and rates throughout — the same numbers RCL is judged on.

C2. How the test is counted

(These definitions decide the pilot, so they are fixed before it starts and are never changed afterward.)

  1. A “Tracked Contact” is exactly one of: (a) a form submission that passes validation (working phone and email) on either arm's page; or (b) an engaged call to that arm's tracking number — inbound, connected, and lasting 60 seconds or more. Nothing else counts — no tel-link taps, no pageviews, no self-reported inquiries.
  2. One person counts once. Contacts are deduplicated by phone number: the same number calling and submitting, or contacting twice, is one Tracked Contact, credited to its first event.
  3. An “Eligible Click” is a paid Google Ads click that lands on either arm and is recorded in the Event Log, excluding RCL's own labeled test traffic.
  4. Each arm's contact rate = its unique Tracked Contacts ÷ its Eligible Clicks.
  5. Both arms are counted by the same rules, the same systems, and the same definitions. Calls are counted through two numbers of the same type, one per arm, both forwarding straight to Client's line; call tracking during the pilot is count-and-forward only — no AI participates in pilot calls and RCL does not record them.

C3. Evaluation and outcomes

  1. The pilot runs up to 30 days and is evaluated only once all three gates are met: at least 14 days elapsed, at least 150 total Eligible Clicks, and at least 20 total Tracked Contacts.
  2. Win: the System arm's contact rate exceeds the Control arm's at evaluation. Client may then continue under C4 — or not; continuing is Client's choice.
  3. No win: the System arm does not beat the Control arm. RCL turns the system off, restores Client's original setup, and Client owes nothing.
  4. Inconclusive: if the gates are not met by day 30 (slow traffic, storm lull), the pilot extends automatically up to a maximum of 45 total days. If the gates are still unmet at day 45, the pilot ends as a no-win: system off, nothing owed, either party may propose a re-run later.
  5. Results are reported as transparent head-to-head counts — every click, contact, and rate on the dashboard, both arms, same rules. RCL does not dress small samples up as statistical proof, and no individual pilot is presented as one.
  6. If Client's ad campaigns stop entirely during the pilot, the pilot clock pauses with them and resumes when traffic does.

C4. Fees

  1. The pilot is $0. No setup fee, no month-one fee, no obligation to continue after a win.
  2. Continuation (only after a win, only if Client chooses): a flat monthly subscription at the fee stated on your checkout page or order form — month to month, cancel anytime, under the General Terms. Founding-rate lock: a founding rate stated at checkout is yours for as long as the subscription remains continuously active.
  3. Continuation covers: the winning pages staying live and maintained, ongoing tracking and lead delivery, the dashboard, and iterative improvement of the pages.

C5. Your responsibilities

  1. Keep the ads running. Client keeps operating its Google Ads account and spend as usual; the pilot needs live traffic to measure. RCL never touches bids, keywords, budgets, or targeting (see C6).
  2. Test plumbing access: whatever the split requires from Client's side — Google Ads access sufficient to run the experiment or update the ad's final URL, and permission to place the tracking snippet and the call-number snippet on the Control page. Control-arm measurement is a hard prerequisite: without the snippet and call number on Client's page, there is no head-to-head test, and the pilot does not start.
  3. Work the leads. Captured leads are delivered to Client in real time; calling them back, quoting, and selling remain Client's job (General Terms Section 4.5).
  4. The Control-page call number is installed as a dynamic snippet (never hard-coded), so Client's published business number — and its local-listing consistency — is untouched and reverts the moment the snippet is removed.

C6. What the pilot is not

C7. Ownership and offboarding

  1. The system is RCL's; the leads are yours. Landing pages, router, tracking snippet, dashboards, and call-tracking numbers remain RCL's property and stay with RCL if the engagement ends. Lead data captured for Client belongs to Client (General Terms Section 6), delivered continuously during the pilot and exportable afterward (Section 6.6).
  2. On pilot end or termination: traffic reverts to Client's original page, the Control-page snippets are removed, the tracking numbers are released or reassigned by RCL, and any number forwarding to Client's line stops. Client's own phone numbers and website are never controlled by RCL at any point.

Schedule D — Website Redesign (One-Time) (“Full Website Redesign” · “Mobile Conversion Fix”)

D1. The Service — two one-time service levels

A one-time website project — a project, not a subscription. Schedule D covers two service levels; which one Client purchased is determined by the checkout page, payment link, or invoice completed (General Terms, Section 3.1). Both are for Client's roofing business, and both include the Conversion Elements in D1.3 at no separate charge.

D1.1 Full Website Redesign. RCL designs and builds a complete replacement for Client's existing website on RCL's build system:

  1. Client's existing website content carried over and reorganized into a new structure of up to fifteen (15) pages — typically 8 to 15 (for example: home, services, individual service pages, service area, reviews, about, contact) — assembled from Client's existing website content and the materials Client supplies (D9). Every page of Client's existing public website is accounted for: carried into the new structure, consolidated into it (for example, individual testimonial pages consolidated into one reviews page), or redirected (item 6). How existing pages consolidate into the new structure is RCL's editorial call, and Client reviews the whole result at staging (D3.3). Light editing and reorganization of existing content is included; open-ended new copywriting is not;
  2. mobile-first layout and navigation on every delivered page;
  3. a performance-oriented build, served per the hosting election in D3.7 — RCL runs before-and-after mobile speed tests (Google Lighthouse) on the old and new sites and shares both results with Client at delivery;
  4. the Conversion Elements (D1.3) on every appropriate page;
  5. deployment to Client's own domain after Staging Approval (D3.5–D3.6), replacing the prior site at that domain;
  6. redirects: prior-site URLs that do not carry forward into the new structure are redirected to their closest new page at cutover, so existing links to Client's website keep working (standard redirects, as the hosting arrangement under D3.7 permits).

D1.2 Mobile Conversion Fix. A narrower project: RCL edits Client's existing website in place — the platform, hosting, design system, and all other pages stay as they are:

  1. scope = Client's homepage plus up to three (3) additional existing pages chosen together at order (typically the main service and contact pages);
  2. on those pages: mobile-usability repairs (layout, header/navigation behavior, text size, tap targets, horizontal overflow, and removal of obvious mobile obstructions RCL and Client agree on) and installation of the Conversion Elements (D1.3);
  3. expressly not included: load-time / speed work. The Fix does not modify Client's hosting, theme engine, or platform-level code that controls how fast the site loads, and no load-time improvement is promised or implied (D8). Making the site fast is what the Full Website Redesign is for;
  4. eligibility: the Fix is offered subject to the platform check in D2.4.

D1.3 Conversion Elements (included in both levels). As fits each page: tap-to-call buttons and a sticky mobile call bar; lead-capture forms; and — where suited to the pages and chosen together at order — interactive lead-capture widgets, in these variants:

Required on-page disclaimers. The widgets ship with, and the pages must keep displaying while these elements are in use: (a) a non-binding-estimate disclaimer on the calculator (estimates are informational, not a quote or a contract); (b) an eligibility disclaimer on the checker (informational only; coverage decisions belong to the insurance company); and (c) contact-consent microcopy on every form, substantially like: “By continuing you're okay with {Client company} contacting you about your roof.” If Client later edits the pages and removes these, Client is solely responsible for the consequences (General Terms, Sections 4.5 and 8.1). Widgets run in the visitor's browser and store no payment or card data.

D1.4 Lead delivery and logging. Form and widget submissions are sent to Client and logged to a Google Sheet shared with Client, so both parties see the same submission count. This logging is part of every delivery and is disclosed here so it never surprises anyone.

D1.5 One revision round is included (per project): Client reviews the staging build (Full Redesign) or the edited pages (Fix), requests changes once, as one consolidated list, and RCL applies them. Further rounds may be declined or quoted separately as new work.

D2. Client's existing site — access, backups, and eligibility

  1. Access. Client authorizes RCL to access and modify Client's website and related accounts to the extent needed for the purchased scope, and will provide the needed access (for example a CMS login, hosting or DNS access, or the contact who has it). Client warrants it has the right to grant this access.
  2. Backups before edits (Fix). Before editing any page, RCL saves a copy of that page as it stood. At Client's request during the project or the D6 fix window, RCL will restore any edited page to its saved copy.
  3. Prior-site archive (Full Redesign). Before the new site replaces the old one, RCL archives the prior site's publicly reachable pages. RCL also recommends Client keep its prior hosting active through the transition — rollback is then just pointing the domain back.
  4. Platform eligibility (Fix). The Fix depends on Client's platform allowing the D1.2 edits. RCL runs a short platform check before or immediately after order; if the platform does not reasonably permit the scoped work (for example a locked theme, a proprietary builder without code access, or access that cannot be obtained), RCL declines or cancels the order and refunds 100% — including if this is only discovered after work begins.
  5. Pre-existing problems stay pre-existing. RCL is not responsible for issues that predate its work, or for Client's platform, hosting, theme, or plugins failing for reasons independent of RCL's edits.

D3. Delivery, timeline, staging, and DNS

  1. Payment first, then intake, then the clock. Work begins when payment (or the deposit under D4.3) clears and Client completes the intake checklist (D9). Delivery timelines run from intake completion, not from payment.
  2. Intake window and stalls. Intake materials are due within 5 business days of order. If RCL is waiting on Client for 5 business days at any point, the schedule pauses. After 30 consecutive days waiting on Client, the project is archived and resumes in the next available production slot when Client re-engages; if a project stays archived for 90 days, RCL may close it by refunding any unearned portion of what Client paid (work already performed is earned — D5.2).
  3. Staging (Full Redesign). The new site is built at a private staging URL and shared with Client for review — typically within about 7 business days of intake completion. The revision round (D1.5) runs against staging.
  4. Review (Fix). Edited pages are reviewed with Client as the platform permits — on a preview or staging copy where the platform supports one, otherwise live with the D2.2 restore right. Typically complete within about 5 business days of intake completion and access.
  5. “Staging Approval” is Client's approval of the staging site (Full Redesign) or the edited pages (Fix). Approval given in writing (email or text) counts on its date; approval given verbally is confirmed back by RCL in writing the same day, and that confirmation's date is the Staging Approval date.
  6. Launch / cutover (Full Redesign). The new site replaces Client's live site only after Staging Approval and payment in full (D4.3). Cutover is done via DNS changes Client (or Client's web/domain person) makes with RCL's step-by-step instructions, or that RCL makes with Client's authorization; RCL's changes are limited to the records needed to point the domain at the new site, and RCL is not responsible for unrelated DNS records (for example email/MX records) beyond following that instruction set. If DNS access is delayed on Client's side, delivery, approval, the revision round, and the D6 fix window all proceed on the staging URL — payment obligations never wait on DNS.
  7. Hosting election (Full Redesign). Staging is served from hosting RCL configures. For the live site, Client elects one of two paths, no later than Staging Approval: (a) the optional care plan (D6.4) — RCL hosts and maintains the delivered site for as long as the plan is active; or (b) the migration handoff (D3.8) — the delivered site is deployed to hosting Client owns, and RCL's serving role ends at launch. No monthly fee is ever required to receive or own the delivered work — the care plan is the only recurring charge under this Schedule, and only if Client chooses it (D4.1). Outside an active care plan, RCL does not serve Client's production site except during the D3.8 handoff itself.
  8. Migration handoff (Full Redesign — included, one time). Where Client elects (or later moves to) its own hosting: Client creates and owns an account with any standard hosting service capable of serving the exported site (most mainstream hosts are — this means hosting the delivered site as built, not rebuilding it inside a proprietary site-builder platform), and RCL, as part of the project fee, deploys the site there, transfers the form endpoint and the D1.4 lead-log Sheet to Client's accounts, provides the export (D7), and points DNS per D3.6 with Client's authorization. After handoff, RCL's hosting and serving obligations end; the D6 fix window still applies to the delivered work, and Client may subscribe to the care plan later (RCL then resumes hosting as part of it). If Client elects its own hosting but the account is not ready by cutover time, the D3.2 delay mechanics apply — or Client may start the care plan to launch immediately and take the handoff later.

D4. Fees and payment

  1. All Schedule D fees are one-time, flat fees — not subscriptions. The amounts are as stated on the checkout page, payment link, or invoice you completed (General Terms, Section 3.1). No recurring fee is required for the delivered work; the optional care plan in D6.3 is the only recurring fee under this Schedule, and only if Client chooses it.
  2. Default: payment in full at order. The full fee is due at checkout via our payment processor (Stripe); accepting this agreement there (the Terms-of-Service checkbox) and paying are what start the engagement (see “How you accept it,” above). No work begins before payment.
  3. Split schedule (where RCL offers it and Client selects it). For some orders RCL may offer a two-part schedule, stated at checkout or on the invoice: 50% of the project fee as a deposit, which reserves Client's production slot and starts the project, and the remaining 50% due at the earliest of (a) Staging Approval (D3.5); (b) completion of the included revision round (D1.5); or (c) 5 business days after the staging site or edited pages are delivered for review without a written list of material deviations from the D1 scope. The balance must be paid in full before DNS cutover, site transfer, or public launch (D3.6). The deposit reserves production capacity and is applied to the total project fee; its refund treatment is D5.
  4. Fee disputes follow General Terms, Section 3.5.

D5. Refunds and the approval gate

(For General Terms purposes — for example Section 2.3 — this section is Schedule D's “Guarantee.”)

  1. Before work begins: Client may cancel for a 100% refund at any time before RCL begins work. Work begins when discovery, setup, or production starts after payment (or the deposit) clears — D3.1.
  2. Once work begins, fees paid (including any deposit) are non-refundable, except to the extent RCL fails to perform the purchased scope: if RCL cannot or does not deliver the D1 scope, RCL refunds the unperformed portion — 100% if nothing usable was delivered. Client delay, failure to supply materials or access (D9), or cancellation for reasons other than RCL's non-performance do not create refund rights.
  3. Platform ineligibility (Fix) refunds 100% per D2.4, whenever discovered.
  4. The approval gate: nothing replaces Client's live website without Staging Approval (D3.6), and Fix edits carry the restore right (D2.2). RCL never leaves Client's live site worse off than before the project.
  5. If RCL terminates without cause before delivery (General Terms, Section 2.4), Client receives a refund per D5.2 as if RCL had failed to perform the undelivered scope.

D6. After delivery — the 30-day fix window

  1. For 30 days after Staging Approval (or after cutover, if later), fixes and tweaks to the delivered work are included at no extra cost: copy corrections, phone/hours/photo swaps, layout and bug fixes, widget adjustments and price-table updates, and reasonable small adjustments that keep the work as scoped in D1.
  2. The fix window is included labor, not a refund right, and it does not include new pages, new sections, or new features — those are new orders.
  3. After the window: further changes — including updates to the widget's price table (the price bands or verdict thresholds Client controls) — are quoted in writing before any work, or covered by the optional care plan (D6.4). Neither is required; the delivered work keeps working without them.
  4. The optional care plan (month to month, cancel anytime, General Terms Section 2; at the rate stated on its payment link) covers, while active: hosting and serving the delivered site (D3.7(a)), SSL, monitoring, repair of bugs and errors in the delivered work, and small content changes — up to two (2) requests per month, each up to about thirty (30) minutes of work (for example: copy corrections, photo/hours/staff swaps, widget price-table updates). New pages, new sections, new features, and larger changes are quoted separately as new work; unused requests do not roll over. For Fix clients — whose site stays on their own platform — the plan is maintenance-only: the same change-request allowance and repair of RCL's delivered edits, with no hosting component.
  5. Care-plan cancellation: RCL serves the site through the end of the paid period, then the migration handoff (D3.8) applies — the export plus the one-time deployment to Client's own hosting, if not already used. Cancelling the plan never affects Client's ownership of the delivered work (D7).

D7. Ownership and export

  1. The delivered work is Client's. On payment in full: for the Full Redesign, ownership of the delivered site — its copy, its layout as assembled for Client, and Client's own materials on it — transfers to Client, and an export is provided on request at any time (a complete copy Client can host anywhere, hand to any web person, or modify freely). For the Fix, the edits become part of Client's own site and are Client's from the moment they are made, subject to payment in full.
  2. RCL's underlying tools stay RCL's. The reusable template system, code components, and widget engine remain RCL's property; Client has a perpetual, non-exclusive license to them as embedded in Client's delivered work. Plainly: Client can use, host, edit, and keep the work forever — and RCL can keep building from the same system for others.
  3. If a refund is made under D5 for unperformed work, the transfer in D7.1 reverses for that unperformed work: Client stops using its drafts or previews, and any staging URL comes down. Delivered, paid-for work is unaffected.
  4. Client is responsible for the accuracy and truthfulness of materials Client supplies and of existing-site content RCL migrates at Client's direction (reviews, license numbers, photos, statements about Client's business); RCL places them in good faith as provided (General Terms, Sections 4.5 and 8.1).

D8. What this Service is not

D9. Client cooperation

The D3 timelines assume Client promptly: (1) supplies brand and content materials — logo, photos, reviews or permission to pull them, license number, service area, and the phone number the pages should ring; (2) provides the access in D2.1 (and, for the Full Redesign, reasonable DNS cooperation from Client or Client's web/domain person, with RCL's step-by-step instructions); and (3) attends the review step and returns the consolidated revision list (D1.5). Delay on these breaches nothing — it moves dates and runs the D3.2 pause/archive mechanics, and the staging rule (D3.6) keeps delivery moving regardless of DNS.

D10. Term and termination for this Schedule

  1. This Schedule is project-based: it starts at checkout and its active obligations end when the D6 fix window ends — except that the hosting election and handoff (D3.7–D3.8), the export right (D7.1), and the care plan (if chosen, D6.4–D6.5) continue per their terms.
  2. Client cancellation: any time before work begins for the 100% refund (D5.1); after work begins, per D5.2. After Staging Approval, the fee is earned and not refunded (General Terms, Section 2.3), and the D6 fix window still runs.
  3. RCL may terminate per General Terms, Section 2.4; if RCL terminates without cause before delivery, D5.5 applies.

Schedule E — Demo-Built Website (“Hosting & Maintenance Plan”)

E1. What this Schedule covers

RCL built a demonstration website for Client's business at no charge, hosted at an RCL-controlled URL and labeled as a concept demonstration. This Schedule governs converting that demonstration website into Client's live website and operating it on an ongoing subscription — the “Hosting & Maintenance Plan.”

E2. Production setup (included — no build fee)

Upon subscription start, RCL will:

  1. remove all demonstration labels, ribbons, and search-engine exclusions;
  2. connect the website to Client's domain name (in Client's registrar account; see E7);
  3. make the contact form and chat assistant deliver for real, to the delivery destination Client designates (email and/or spreadsheet);
  4. set the estimate calculator's figures to ranges Client approves in writing (until approved, the calculator displays no figures or remains disabled);
  5. make reasonable corrections to names, phone numbers, service lists, and similar facts Client identifies during review.

Target timeline: production setup completed within seven (7) days of subscription start, subject to Client providing domain access and approvals. Setup is complete when the website is serving on Client's domain with working delivery (“Go-Live”).

E3. The monthly plan — $250/month

The subscription includes:

  1. hosting, SSL, and serving of the website;
  2. keeping the website operational and fast (performance maintained by RCL's build standards; no specific score is warranted);
  3. up to two (2) change requests per calendar month, each up to approximately thirty (30) minutes of work (text edits, photo swaps, service-list changes, hours, and similar). Unused change requests do not roll over. Larger work — new pages, redesigns, integrations, photography, copywriting projects — is quoted separately;
  4. operation of the website's widgets (estimate calculator, checker, contact form) and the chat assistant as configured at Go-Live;
  5. delivery of form and chat submissions to Client's designated destination.

E4. Billing

$250 per month via Stripe subscription, card on file, auto-renewing monthly. Seven (7) day free trial: card collected at checkout, first charge on day 7. Failed payments: RCL may pause the website after fourteen (14) days of non-payment following notice; restoring service after payment resumes the plan. Prices may change only with thirty (30) days' written notice, effective at the next renewal.

E5. Term and cancellation

Month-to-month; Client may cancel at any time, effective at the end of the current billing period (General Terms, Section 2.2). Early-cancellation handoff fee: if Client cancels before completing three (3) paid months, a one-time handoff fee of $500 applies, covering the production setup performed without a build fee (E2). After three (3) paid months, no handoff fee applies — cancellation is free, and the handoff in E6 still applies.

E6. Handoff — Client is never locked in

Upon any cancellation (and payment of any E5 fee then due), RCL will within fourteen (14) days deliver a complete static export of the website's files to Client and reasonably cooperate with pointing Client's domain wherever Client directs. Client keeps: the domain (always Client's — E7), all business content and facts, and all leads and submissions already delivered. What RCL retains: the hosting infrastructure, delivery integrations, widget/chat backend configurations, and RCL's build tooling. The exported files are static and functional as a website; live form and chat delivery requires Client's own replacement services.

E7. Domain

Client's domain remains registered to Client at all times. RCL never takes ownership of, or registers, Client's domain in RCL's name. If Client has no domain, RCL will assist Client in registering one in Client's own account.

E8. Content and accuracy

The website was prepared from Client's public business information. Client is responsible for reviewing and approving the website's factual claims (services, credentials, service areas, review figures) at Go-Live and thereafter; RCL will promptly correct any item Client identifies. RCL does not publish figures for Client's pricing without Client's written approval (E2.4).

E9. No performance promises

RCL makes no promise of leads, calls, jobs, revenue, search rankings, or any business outcome (General Terms, Section 7). The plan's deliverables are the website, its operation, and the maintenance described in E3.

E10. Chat assistant scope

The included chat assistant answers general roofing questions and takes messages; it does not make appointments, quotes, or commitments on Client's behalf, and its conversations are processed by RCL's chat vendor. A custom-configured assistant (Client-specific answers, integrations) is available as separately quoted work.

E11. Order of documents

This Schedule is subject to the General Terms. If this Schedule conflicts with the General Terms, this Schedule controls for the services it covers.

Questions

Email rikhil@rooferconversion.com, call (612) 346-7325, or use the contact form.

RooferConversionLab is a service of Rumulla Group LLC · © 2026 Roofer Conversion Lab. All rights reserved.