Framewyre Beta / No-Fault Policy

1. Framewyre is in beta. Read this before you depend on it.

Framewyre is in active beta. It is real, working software that real contractors are using to run real jobs — and it is also still being built. Features are added, changed and removed. Bugs exist that nobody has found yet. There will be downtime.

This policy is part of the Terms of Service and applies for as long as your workspace is marked as being in the beta programme. Where this policy and the Terms of Service conflict, this policy controls during the beta period.

2. What “beta” means in practice

• The product will change. Screens, workflows, field names, calculations, exports and defaults can change, sometimes with little notice. A feature you rely on today may be reworked or withdrawn.
• There will be downtime. We deploy frequently. Planned maintenance and unplanned outages both happen, and we do not promise any uptime percentage during beta.
• There will be bugs. Totals, tax figures, schedules, reports, AI-generated text and automated messages can be wrong. Check anything before you send it to a client, a subcontractor or a tax authority.
• Automated communications can misfire. Call handling, SMS, voicemail and email automations depend on third-party carriers and providers and may be delayed, duplicated, or not delivered at all. Do not rely on them for anything time-critical or safety-critical.
• Data loss is possible. We take reasonable care and keep backups, but during beta you should assume a defect or a failed migration could corrupt or lose records.
• No service levels. No SLA, no guaranteed support response time, and no service credits apply during beta unless we have signed a separate written agreement with you.

3. Keep your own records and backups

You must keep your own independent records. Framewyre is not your only copy and must not be treated as your system of record during beta.

• Export your important data regularly using the export features in the product, and keep those exports somewhere you control.
• Keep your own copies of anything legally or financially significant: signed contracts and change orders, invoices and payment records, lien and permit paperwork, insurance certificates, payroll and timesheet records, and client correspondence.
• Keep your accounting in whatever system your bookkeeper or accountant already uses. Figures shown in Framewyre are not accounting, tax or legal advice and are not a substitute for professional review.
• Before accepting a large change or a migration we announce, take a fresh export first.

We recommend a full export at least [RECOMMENDED EXPORT FREQUENCY]. If you cannot export something you need, tell us at [SUPPORT EMAIL] and we will help.

4. No warranty during beta

The beta Service is provided “as is”, “as available” and “with all faults”. To the fullest extent permitted by law we disclaim all warranties, express, implied or statutory, including any implied warranty of merchantability, fitness for a particular purpose, accuracy, non-infringement, quiet enjoyment, and any warranty arising from course of dealing or trade usage.

In particular, we make no warranty of fitness for your business: we do not warrant that Framewyre is suitable for your trade, your jurisdiction, your contract forms, your licensing or permit obligations, your tax treatment, or your record-keeping duties. Deciding whether it fits your business is your call, and you should keep the systems you already trust running alongside it during beta.

We also do not warrant that the beta Service will be available, uninterrupted, secure or error-free, that defects will be corrected, or that any particular feature will ever ship or continue to exist.

5. No-fault: no liability for business losses during beta

This is the core bargain of the beta programme: you get early access at beta pricing, and in exchange you accept that using unfinished software carries risk you bear yourself.

To the maximum extent permitted by law, we are not liable for any business loss arising out of or relating to your use of Framewyre during the beta period, including but not limited to:

• lost profits, lost revenue, lost bids, lost contracts or lost clients;
• project delays, missed deadlines, schedule overruns, or liquidated damages you owe a third party;
• missed calls, missed leads, undelivered or mistimed SMS, voicemail or email;
• incorrect estimates, invoices, totals, tax figures, reports or AI-generated content, and anything sent to a client in reliance on them;
• missed lien, permit, insurance, warranty or statutory deadlines;
• loss, corruption or unavailability of data, or the cost of recreating it;
• cost of substitute software or services, or staff time spent working around a fault;
• damage to reputation or goodwill.

This applies regardless of the legal theory (contract, tort, negligence, strict liability or otherwise) and even if we were told such loss was possible.

Cap. Where liability cannot be excluded entirely, our total aggregate liability for all claims relating to the beta Service is limited to the subscription fees you actually paid us in the three months immediately before the event giving rise to the claim.

Nothing here excludes liability that cannot lawfully be excluded, such as liability for fraud, wilful misconduct, or death or personal injury caused by negligence. Some jurisdictions do not allow certain exclusions, so parts of this section may not apply to you; the rest still does.

6. What we commit to during beta

The limits above are real, but they are not an excuse to be careless. During beta we will:

• keep your workspace isolated from other customers’ workspaces;
• take regular backups of the production database;
• keep export features working so you can get your data out at any time;
• give notice of planned maintenance we expect to be disruptive, at [MAINTENANCE NOTICE CHANNEL], where we reasonably can;
• tell affected customers about incidents that caused data loss or exposure;
• handle personal information as described in the Privacy Policy;
• let you cancel at any time under the cancellation terms in the Terms of Service if beta is not working for you.

7. How to report a problem

Reporting bugs is the most valuable thing a beta customer can do. Please tell us even about small things.

• Email: [SUPPORT EMAIL]
• Urgent issues (data loss, data visible that should not be, billing errors, the product is down): [URGENT CONTACT METHOD]
• Security issues: [SECURITY CONTACT EMAIL] — please report privately and give us a reasonable chance to fix before disclosing.
• Other feedback and feature requests: [FEEDBACK CHANNEL]

Please include

1. Your business name and the email you sign in with.
2. What you were doing, step by step, and what you expected to happen.
3. What actually happened, with the exact wording of any error message.
4. The date and time (with time zone) and roughly how often it happens.
5. A screenshot or screen recording if you can, with client details covered if sensitive.
6. The device and browser you were using.

We aim to acknowledge reports within [SUPPORT ACKNOWLEDGEMENT TARGET]. That is a target, not a contractual service level. If a bug has cost you money or put a job at risk, say so clearly in the first line — we will prioritise it.

8. When beta ends

We will tell you before Framewyre leaves beta, at least [END OF BETA NOTICE PERIOD] in advance, together with any change to pricing or terms. When beta ends this policy stops applying to your workspace and the general Terms of Service govern on their own. If you do not accept the post-beta terms or pricing, you may cancel before they take effect and export your data.

9. Contact

[COMPANY LEGAL NAME]
[MAILING ADDRESS]
[SUPPORT EMAIL]