Draft. Not reviewed by a lawyer. Do not show this to a customer.
This was written by the engineer who built the software, by reading the code. It has not been reviewed by anybody qualified to review it. It is published here so that it can be read, checked and corrected — not so that it can be relied on. Nothing in it is an offer, a contract or legal advice, and it must not be linked from a signup flow or signed by anybody until a lawyer has read it.
All three documents · 10 unfilled markers in this document
Terms of Service
Draft — not reviewed by a lawyer
This document was drafted by the engineer who built the software. It has not been reviewed by a lawyer. It must not be put in front of a customer, linked from a signup flow, or signed by anybody until a qualified person has read it. Every [NEEDS ZACH: ...] marker below is a fact only Zach can supply, and a marker that is still showing means this document is unfinished.
1. Who this agreement is between
These terms are between [NEEDS ZACH: the legal entity name — the company that licenses this software, exactly as it is registered], registered at [NEEDS ZACH: the registered business address] ("we", "us"), and the business that licenses the software ("you", "your company").
The software is a business development platform for restoration and adjacent trades, referred to here as "the Platform". You license it. We do not run your business development for you, we do not act as your agent, and we do not contact anybody on your behalf. Everything the Platform sends is sent because one of your people decided to send it.
2. What you are licensing
A right to use the Platform for your own business, for the number of users your plan allows, for as long as you are paid up. Not a copy of the software, not the source code, and not a right to resell it or to run it for anybody else.
The Platform is one codebase serving many companies. Your configuration — branding, field labels, pipeline stages, triggers, email templates, send windows — is yours and is data, not code. We do not write bespoke code for one customer.
3. What we do with your data
Your records are yours. We hold them to run the Platform for you and for nothing else. We do not sell them, we do not use one company's contacts to help another company, and we do not use your data to train a model.
The technical boundary this rests on: every record in the Platform carries the identifier of the company it belongs to, and every read goes through a single function that filters on it. A request for a record belonging to another company is answered as "not found" rather than "not allowed", because telling a stranger that a record exists is itself a disclosure.
The detail of what is collected, where it goes and how long it is kept is in the Privacy Policy. If your company is subject to data protection law that requires a processor agreement, the Data Processing Agreement is part of these terms.
4. What you are responsible for
This is the section that matters most, because the Platform's job is to help you contact people who have not asked to hear from you.
You decide who gets contacted. The Platform finds commercial properties from public map data, watches public weather and news feeds, and drafts messages. It queues them. A person at your company reads each one and approves it. Nothing is sent that nobody approved.
You are responsible for the lawfulness of your own outreach. That includes commercial email rules in every place you send to, honouring an unsubscribe or a request to stop, and not contacting somebody you have been told to leave alone. We give you the tools — a queue, an approval step, a stop switch, a record of what was sent — and we cannot judge whether a particular message to a particular person is lawful. [NEEDS ZACH: ask the lawyer whether this section needs to name specific statutes — CAN-SPAM in the United States, and whichever of CASL, GDPR or PECR applies if you ever sell outside the US — and whether a flat allocation of that responsibility to the customer actually holds.]
You are responsible for the accuracy of what you put in. If you import a contact list, you are telling us you are entitled to hold it.
You are responsible for your own credentials. One account per person. The Platform records every sign-in, every failure and every lockout, and those records are attributed to the account that was used.
5. What we will not do
- We will not send anything your people have not approved, unless you deliberately switch on automatic sending for a specific campaign, which is off by default and is a decision you make in writing in the Platform.
- We will not read your data except to operate the Platform, to investigate a fault you have reported, or where the law requires it.
- We will not contact your contacts ourselves, for any reason.
6. Availability, and what it is honest to promise
The Platform is hosted on Railway. We do not operate the hardware and we do not control the network, so we cannot promise more uptime than our host gives us, and we do not offer a service credit regime.
[NEEDS ZACH: decide whether you want to offer an uptime commitment at all. If you do, it has to be a number you can measure, and nothing in the product measures uptime today. The honest position for a first beta customer is "best effort, no credits", and a lawyer should put that in language that survives somebody's procurement questionnaire.]
What we do commit to, because the product actually does it: your data is backed up, the backups are verified by restoring them into a scratch database and checking the restored data rather than by checking that the backup command exited cleanly, and the backup retention window is recorded in the Privacy Policy.
7. Agents, automation and the things the Platform decides
The Platform runs scheduled jobs on your behalf: it checks weather alerts, reads news feeds, sweeps map data, scores prospects, and writes draft messages. Three things about that are worth stating in a contract rather than in a help page.
A score is advice, not a decision. Lead scrubbing ranks prospects on business size and age, owner versus tenant, whether a decision maker has been verified, and whether a trigger matched. A low score holds a prospect back from the queue. Your people can override it, and the override is recorded.
Public data stays public data. Property records come from OpenStreetMap through the Overpass API, which is open data used under its own licence, and the attribution is displayed in the Platform where those records appear. Weather alerts come from the United States National Weather Service. News items come from feeds you configure yourself.
You choose the news feeds and you own that choice. If you point the Platform at a feed whose terms forbid automated reading, that is your decision. The Platform refuses addresses that are not ordinary public web addresses, which is a security control rather than a licensing one.
8. Money
[NEEDS ZACH: the whole of this section. It needs the price for the Base tier and the VIP tier, whether the charge is flat or per seat or per rep, the seat limits, the trial length and whether a trial takes a card, the billing period, the notice period for cancellation, the refund position, and whether you charge sales tax on software in the states you sell into. This is NEEDS ZACH item 4 in ROADMAP.md and nothing can be drafted here without the numbers.]
What the software already enforces, so that it matches whatever is agreed: a company's plan decides which features answer at all, independently of whether a feature is switched on for them. Switching a feature off is never refused. Downgrading a plan makes a feature stop answering without losing the settings behind it, so an upgrade restores exactly what the company had before.
9. Ending it
[NEEDS ZACH: notice period, whether a term is annual or monthly, and what happens to a part-paid period on cancellation. See item 4.]
What happens to your data when you leave, which is a technical fact and not a commercial one: you can export your contacts and jobs to CSV at any time while your account is open, including after you have given notice. After the account is closed we delete your records on the schedule in the Privacy Policy. The audit trail — who did what, when — is retained separately, and the Privacy Policy says for how long.
10. Liability
[NEEDS ZACH: the cap, the exclusions, and whether you carry errors and omissions insurance and cyber liability insurance. A buyer with an IT department will ask for certificates before they ask about the product, and the answer "none" is a decision rather than an oversight — but it has to be a decision you have made. This is part of NEEDS ZACH item 7.]
[NEEDS ZACH: the governing law and the courts — which state's law applies and where a dispute is heard. Pick the state you are actually in unless the lawyer says otherwise.]
11. Changes to these terms
We will tell you before these terms change in a way that affects you, and we will not change them retroactively. [NEEDS ZACH: how much notice, and whether continued use counts as acceptance. A lawyer will have a view on whether "continued use is acceptance" is enforceable where you sell.]
12. How to reach us
[NEEDS ZACH: the contact address for anything legal — notices, disputes, and the address that appears on an invoice. See also the data-request address in the Privacy Policy, which may or may not be the same mailbox.]
Last revised 8 October 2026. This is a draft. It has not been reviewed by a lawyer.