Terms of service

1. Who operates Precedent

The website operator is Francisco Gutierrez, North Dakota, United States. “Precedent Systems” is the business brand used on this website. It is not represented here as an LLC or corporation, and no trade-name registration is claimed.

2. When a service agreement begins

Browsing, requesting information, or booking a discovery call does not purchase services or authorize recurring charges. Before work begins, Francisco Gutierrez and the client must approve a written project agreement. These proposed terms and the refund policy apply only if supplied with and expressly incorporated into that agreement.

The agreement must identify the parties and authorized signers, scope and exclusions, deliverables, acceptance criteria, timetable, fees, billing dates, support, ownership, and cancellation arrangements. Applicable law takes priority; otherwise, expressly agreed project terms take priority over these general terms. Website updates do not change an existing signed contract.

3. Scope, approvals, and client cooperation

Additional features, integrations, revisions, or support require written agreement on fees and timing before that work proceeds. The client supplies accurate information, content they are entitled to use, and appropriate access to required accounts. Access should be limited to what is needed; do not send passwords through a discovery-call form.

If missing access, information, or approvals cause a delay, the parties should document the impact and revised timetable. A delay does not by itself authorize extra charges. The project agreement must specify a review and correction process. Silence is not treated as acceptance under these proposed terms.

4. Prices, payment, and recurring services

The website shows indicative package prices. The project agreement must confirm currency, applicable taxes, setup and recurring fees, payment dates, usage limits, and third-party charges before purchase. The first-year comparison is setup plus twelve monthly payments, without an assumed discount; it does not create a twelve-month commitment.

Recurring billing requires advance disclosure of the amount or calculation, frequency, duration, renewal conditions, and cancellation method, plus the client’s express authorization and a copy they can keep. A calendar booking is not that authorization. Price changes must be communicated before taking effect; no retroactive increases are proposed. See Refunds & cancellation.

5. Ownership and handover

Each party retains its pre-existing rights. Client content remains the client’s or its licensor’s. The project agreement must identify which custom deliverables are assigned or licensed, when those rights begin, and whether source files, documentation, domains, and administrator access are included. This website itself transfers no intellectual property.

Third-party software, fonts, assets, and open-source components remain subject to their licenses. Retained reusable tools must be identified, with the client’s rights to use them set out clearly. Using a client’s name, logo, testimonial, or results for promotion requires separate permission.

6. Confidentiality and customer data

Confidential project information should be used only for the agreed work, shared only with authorized people and approved providers who need it, and protected with appropriate safeguards. The project agreement must address permitted disclosures, account access, incident handling, and return or deletion at the end of the project.

Before handling a client’s lead or customer information, the parties must document processing instructions, approved tools and recipients, retention, security responsibilities, and assistance with privacy requests. A separate data-processing agreement may be needed. The website privacy notice does not replace those arrangements.

7. Automated messages and outside providers

Before live messaging or recording begins, the parties must identify applicable consent, notice, opt-out, suppression, and provider requirements and assign responsibilities in writing. An inquiry is not blanket permission for every promotional message.

Scheduling, CRM, messaging, hosting, and other providers have their own terms, fees, and limits. The project agreement must identify required subscriptions and who controls and pays for them. Provider outages or changes may affect the system; they do not remove remedies required by law or promised in the agreement.

8. Demonstrations, support, and results

Sample leads, messages, timing, and scenarios are illustrations, not customer results or performance commitments. No specific revenue, lead volume, conversion rate, uninterrupted availability, or response time is guaranteed here. Support commitments and any guarantee must be defined in writing with coverage, exclusions, duration, and remedy. These proposed terms do not create a general 60-day money-back guarantee.

9. Ending work and resolving problems

Cancellation and prepaid balances follow the refund policy incorporated into the agreement. The agreement should define an orderly handover of paid-for deliverables, permitted data exports, accounts, and credentials, with any transition fee agreed in advance.

Please report problems using the contact in your agreement. Contacting Precedent first is not a condition for exercising legal rights, raising a payment dispute, or making a regulator complaint. These proposed terms impose no mandatory arbitration, class-action waiver, or blanket liability release. Jurisdiction-specific liability and dispute provisions need legal review. Nothing excludes rights or responsibilities that applicable law does not allow to be excluded.

10. Website use and contact

Do not interfere with the site, attempt unauthorized access, introduce malicious code, impersonate others, or submit information you have no right to share. Website content may be protected by its owners’ or licensors’ rights. Access does not transfer those rights or restrict uses allowed by law.

Operator: Francisco Gutierrez, North Dakota, USA.
Business email: awaiting confirmation before public launch. Existing clients should use the contact in their signed agreement or invoice. A working, monitored contact must be provided before new service agreements are accepted.