moat runs the whole line — lead, deal, estimate, invoice, and the follow-up in between. For construction and creative firms tired of doing the chasing themselves.
Deals sit on a board by stage, with the value, the owner and the close date where you can see them. Every deal carries its own service-level agreement: how long it may go without activity, and how far past its close date it may drift.
Cross either and the card says so. Not a report you have to remember to run — a mark on the deal, on the board you already look at.
Price the work once. An approved estimate converts without re-typing a line, and both print on your letterhead, addressed to a named person rather than to a company that has to work out who it is for.
Payment terms belong to the customer, not to a global default. A client who mandates Net 15 gets Net 15 on every invoice, and changing their terms tomorrow never restates one you issued today.
Net 7 through Net 90, or due on receipt. Plus a grace period, because “due” and “start chasing” are not the same date.
Every CRM can send a reminder sequence. The failure everyone has lived through is the one that keeps sending after the customer has paid — and it is always the same cause: the stop is a setting, and settings get missed.
In moat it is not a setting. Recording a payment cancels the pending step inside the same database transaction that records the money. A message already in flight is refused at the last gate. There is no configuration that turns this off, because it is not configuration.
Describe your business and moat builds the site — pages, copy, and a contact form wired straight into your pipeline. An enquiry does not land in an inbox to be copied somewhere later. It arrives as a lead, with the ad or search that produced it attached.
At the other end, every customer gets a private hub: what they owe, what they have paid, and every estimate you have sent them. One link, revocable, in your branding.