Beta addendum

Version 1.0 · Effective September 1, 2026

You are one of a small number of contractors running ACE Platforms before it is generally available. That is genuinely valuable to us and it is why the commercial terms are what they are. It also means you are running your business on software that is newer than the software you would otherwise buy, and this document is the honest version of what that means.

This addendum modifies the Terms of service for the beta period. Everything in the terms still applies except where this says otherwise. Where the two conflict, this wins.

1. The beta period

The beta runs from September 1, 2026 until November 1, 2026— about sixty days. We may extend it, and if we do we will tell you in writing rather than let it drift. Either of us can also end it earlier on fifteen days’ notice; section 9 covers that.

At the end of it, this addendum stops applying and the standard terms take over in full, at standard pricing. Section 10 covers how that transition works and what your choices are.

2. What you pay

Your fee for the beta period is the amount in your Order Form, or if there is no Order Form, the amount we agreed in writing when your account was created. It is a beta price and it is not the price after November 1, 2026.

AI usage is included up to your plan’s monthly limit. When you reach that limit the AI features stop working until the next monthly cycle — they do not keep running and bill you afterwards, and you will never receive a surprise charge for going over. We email you as you approach the limit, not after you pass it.

If you want more than your limit allows, ask us and we will raise it for an agreed amount, in writing, before it takes effect. Everything else in the product is unmetered during the beta.

Payment processing fees charged by Stripe on money you collect from homeowners are unaffected by any of this. They are Stripe’s fees, at Stripe’s rates, and they apply from day one.

3. What we are not promising

Plainly, so there is no room for a misunderstanding later:

• No uptime commitment. There is no guaranteed availability, no service credits and no maintenance window we are bound to. We will not take the platform down carelessly during your working day, but we are not promising we will not have to.
• No support response time. In practice you have a direct line to the person who wrote the software, which is better than a ticket queue. It is still not a contractual commitment.
• Features may change or be removed. Beta is when we find out that something we built is wrong. If we remove something you depend on we will tell you first, but the thirty days notice in section 19 of the terms does not apply during the beta.
• Bugs are expected. Some of them will be found by you, in front of a customer. That is the deal, and it is why section 5 asks you to keep your own records of anything you cannot afford to lose.

4. You are running a real business on this

We are not asking you to test with fake data. The whole point is real jobs, real homeowners and real money — that is the only way either of us learns anything. But it means the ordinary responsibilities in the terms are live from the first day, not suspended because the label says beta:

• the estimates, contracts and invoices you send are yours, and you check them before they go out — including anything a measurement takeoff or an AI feature produced (section 8 of the terms);
• your obligations to homeowners under your own contracts are unaffected by anything that happens to our software;
• refunds, disputes and chargebacks remain yours (section 6 of the terms).

If the platform is unavailable when you need to send a contract, you still owe the customer a contract. Have a way to do that.

5. Your data during the beta

Your data is yours, exactly as in section 4 of the terms, and you can export it at any time. We take backups. We are not planning to lose anything.

That said: during the beta we may need to migrate, restructure or in a genuine emergency reset data. We would tell you before doing it and we would work with you to avoid it. We are putting it in writing because it is a real possibility during a beta and you should decide what to run on the platform knowing that, rather than find out afterwards.

The practical advice, which we would give a friend: for the first few months, keep your own copy of anything you could not reconstruct — signed contracts especially. Export regularly. If that turns out to have been unnecessary, good.

6. Liability during the beta

The limitation of liability in section 16 of the terms applies in full, including the cap at twelve months of fees. Given that beta fees are low, that cap is low. That is deliberate and it is the trade for the price.

What that cap does not cover, and what we are not trying to disclaim: fraud, wilful misconduct and gross negligence on our part. If we do something genuinely reckless with your business, a beta label is not a defence and we would not want it to be.

7. Feedback, and what we do with it

Telling us what is broken, what is missing and what is annoying is the substance of what you are giving us. Section 13 of the terms means we can act on it freely and without owing you anything — which is the point: no one should have to think about ownership before saying that a screen is confusing.

We may also ask you for things beyond bug reports: a call about how your estimating actually works, a look at how your crews use the mobile app, a question about your numbers. All of it is optional. Your business data stays confidential under section 14 of the terms regardless.

Naming you. We would like to be able to say publicly that your company is one of our first customers, and to use your logo. You agree we may — but tell us at any time and we will stop and remove it. We will not quote you, publish your numbers or use anything that identifies your customers without asking first, every time.

8. Known limitations at the start of the beta

These are the things we already know will be awkward. We would rather you read them here than meet them mid-appointment.

• Connecting your Gmail shows an “unverified app” warning. Google’s verification review takes weeks and is under way. Until it finishes, every user who connects a mailbox must be added by us as an approved tester and will see a warning screen they have to click past. The connection is safe and asks only for permission to send — but the screen looks alarming and we are telling you so it does not surprise you.
• The iPhone app is not distributable yet. Apple developer enrolment is in progress and outside our control. The Android app is available now.
• No contractual uptime or support commitment, as set out in section 3.

We will keep this list current as things land, and it is not exhaustive — it is what we know today.

9. Ending it early

Either of us can end the beta arrangement on fifteen days written notice, for any reason and without penalty. If you walk away, nothing is owed beyond fees for the period you used, and you get the thirty-day export window in section 18 of the terms.

We would obviously rather hear what went wrong than watch you leave quietly.

10. What happens on November 1, 2026

At least thirty days beforehand we will tell you what standard pricing looks like for your business. Then:

• if you continue, the standard Terms of service apply in full at the new price, and this addendum falls away;
• if you do not, you can leave at the end of the beta with the usual thirty days to export your data, owing nothing further.

You will not be rolled onto a higher price by silence. Continuing past the end date is a choice you make after seeing the number.

11. Contact

Anything about this addendum, or anything at all during the beta: hello@aceplatforms.com