Clear expectations for using ProBuilder OS.

Agreement and eligibility

These terms apply when you create or use a ProBuilder OS workspace, client portal, or mobile application. You must be at least 18, be authorized to act for the company named on the account, and be able to enter a binding business agreement. If a separate written agreement applies, that agreement controls where it conflicts with these terms.

Your account

Keep account credentials confidential, provide accurate information, and promptly remove access that a teammate no longer needs. You are responsible for activity under accounts you authorize and for assigning roles appropriate to each person's work.

Trial, plans, and service changes

A new company workspace currently begins with a 14-day Pro trial and does not require a payment card. Creating a trial does not authorize a charge. Published plan prices and limits may change before paid activation; any paid purchase will show the price and billing interval before the company owner confirms it. Features may evolve, and roadmap items labeled coming soon are not part of the current service commitment.

Company data

You retain rights in information you submit. You authorize us and our service providers to process that information only as needed to operate, secure, support, and improve the service. Do not submit regulated, highly sensitive, or unrelated personal information unless a written agreement explicitly places it in scope. See the Privacy Notice and Security page for current service boundaries.

Acceptable use

You may not use the service to:

• Access another company's workspace or data without authorization
• Probe, disrupt, reverse engineer, or bypass security or access controls
• Upload malicious code, unlawful material, or content you lack rights to use
• Misrepresent identity, authority, licenses, estimates, or project information
• Resell or provide the service to third parties without written permission

Business decisions and estimates

ProBuilder OS supports construction operations but does not replace professional, financial, legal, code, licensing, insurance, engineering, or safety judgment. You are responsible for reviewing estimates, schedules, documents, calculations, and project decisions before relying on or sharing them.

Project cost ledgers and earnings views are operational reports derived from records entered or maintained by workspace users, including budgets, costs, paid amounts, contract values, approved changes, invoices, and payments. Their accuracy depends on the completeness and timing of those records. They are not audited financial statements, accounting or tax records, payroll calculations, accounts-payable services, bank reconciliation, or accounting, tax, payroll, or financial advice. You are responsible for checking entries, source documents, exports, and results against the company's professional and formal financial systems before relying on them.

A customer payment receipt in ProBuilder OS records an authorized user's statement that funds were received outside the service. It does not mean ProBuilder OS charged a payment method, transferred funds, verified a deposit, or reconciled a bank account. Users must verify the amount, date, method, and any correction against their source and accounting records. A void removes the entry from active collection totals but retains the original receipt and void evidence.

A project cost-ledger CSV is an operational export, not an accounting-system synchronization. ProBuilder OS does not currently connect or reconcile the cost ledger with QuickBooks, a bank, a payroll provider, or another accounting platform.

Cost-record changes use version checks to reduce accidental overwrites. Voiding a cost removes it from active totals but retains the original record and void evidence in the workspace's server-side audit history. You remain responsible for reviewing corrections and maintaining any source documents or formal records required by your business or law.

Owners and administrators may archive a completed project cost ledger to make its cost and budget records read-only while preserving an aggregate integrity checkpoint, archive events, active records, and void history. Reopening the ledger creates another retained event; it does not erase prior archive evidence. Archive status is an operational workflow control, not an accounting close, tax determination, records-destruction instruction, or substitute for your company's formal retention policy. You remain responsible for retaining source records and exported copies for any period required by law or business policy.

AI-assisted scope content is generated from limited project information and may be incomplete or incorrect. It is never professional, legal, engineering, code, safety, or pricing advice. The contractor remains responsible for checking every generated detail, correcting assumptions, and approving the final proposal before it is issued.

AI-assisted plan analysis and takeoff count suggestions may omit, duplicate, or misidentify plan items. They are review aids, not engineering, architectural, code, safety, material-ordering, or pricing advice. The contractor must verify every result against the correct source-plan revision, drawing region, scale, notes, schedules, and actual site conditions before relying on it or using it in an estimate.

AI-assisted proposal scope drafting is optional and currently in a controlled rollout for selected eligible Pro and Business workspaces. Other AI capabilities described as coming soon are not part of the current service commitment. The drafting interface identifies generated material as AI-assisted and preserves generation and review provenance. The final proposal may not carry a separate AI label, so the contractor remains responsible for any disclosure or recordkeeping required when generated or edited content is shared.

Electronic records and proposal acceptance

A client may choose to review and accept an issued proposal electronically. Before signing, the client is shown the exact proposed scope, inclusions, exclusions, clarifications, total price, payment schedule, and electronic-record consent. An electronic acceptance records the client's intent to accept that proposal and request preparation of a separate construction agreement. It does not authorize construction, require payment by itself, or replace the separate written construction agreement required before work begins.

A client is not required to use electronic records and may request a paper copy or paper-based review from the contractor. Proposal receipts are designed to remain accessible and reproducible. Before accepting, a client may leave the electronic process and ask the contractor to continue on paper. Consent shown in this workflow applies to the identified proposal acceptance and receipt; it is not a blanket consent to every future company or project record.

Electronic review requires internet access, a current web browser or supported mobile app, an email-linked verified client account, and the ability to view or download a PDF. Clients who cannot access those formats should contact the contractor before accepting. ProBuilder OS provides record, consent, signature, and receipt tools; it does not promise that using those tools alone satisfies every jurisdiction's electronic-record, consumer-disclosure, contract, notice, cancellation, or signature requirement. Contractors remain responsible for any additional disclosures, withdrawal process, paper-copy terms, fees, and construction-agreement requirements that apply to their transaction.

Suspension and ending access

You may stop using the service, and a company owner may request account assistance by contacting us. We may suspend or limit access to protect users, data, infrastructure, legal compliance, or the integrity of the service. Data return, retention, and deletion requests are handled through the support process and applicable written agreements.

Warranty and liability boundary

The service is provided on an as-available basis, without promises that it will be uninterrupted or error-free. To the extent permitted by law, neither party is responsible for indirect, incidental, special, or consequential losses arising from use of the service. Any additional warranty, indemnity, or liability terms must be stated in a separate written agreement.

Changes and contact

We may update these terms as the service changes. Material changes will be communicated through the service or to the account contact when appropriate. Questions can be sent to info@terrabuildr.com.