FOR LARGER OPERATIONS

Enterprise

Same product, run across branches and crews — with the roles, rate books and paper trail a bigger operation needs. What’s live and what’s being built is marked plainly below.

Talk to usRead the security page

What changes at scale

What larger operations get today, and what’s being built for them — tagged honestly, because procurement quotes this page back.

TODAYRoles that fitOwner, admin and member seats — owners control billing, admins manage rates and the team, members create and send. Branch-level roles are being designed.
TODAYThe signature recordEvery signature records the signer, timestamp and the exact version signed, sealed against edits. An org-wide audit export is planned.
IN STAGESAPI and webhooksLead intake and MeloScan uploads are live; documents, webhooks and payments are opening in stages. Your clients, rates and jobs push in; signed paperwork comes back.
PLANNEDSingle sign-onSAML and OIDC against Okta, Entra or Google, with SCIM provisioning so leaving the company ends access. Scoped with early enterprise accounts.
PLANNEDA rate book per regionLabour in Spokane is not labour in Seattle. Each branch will price from its own book, with the company seeing both in one report.
PLANNEDReporting across branchesWin rate, margin, average quote and days to signature, sliced by branch, estimator or trade.

Security

Every row here restates the trust center, which answers the longer questionnaire — nothing on this page goes further than that page does.

EncryptionTLS 1.2 or better on every connection; AES-256 at rest by the managed database and storage services.STANDARD
Tenant isolationEvery workspace is isolated by row-level security at the database — your data is never in another tenant's query path.STANDARD
Card dataCard numbers never touch our servers. Checkout is hosted by Stripe, a PCI DSS Level 1 service provider.VIA STRIPE
SubprocessorsThe full list — who, what for, and where — is published on the trust center.PUBLISHED
Data residencyUnited States, on our managed database and payment providers. Other regions aren't offered yet.US
SOC 2 Type IINot held by MeloDocs yet — the infrastructure underneath us maintains SOC 2 Type II reports, and ours is planned. The trust center will carry the report when it exists.PLANNED

How a rollout runs

Steps, not promises about weeks — the pace is set with you, branch by branch.

STEP 1
Scoping

We look at the documents you send today — the good and the ones you would rather not show us.

STEP 2
Data

Clients, rate books and open jobs come across, from a CSV or through the API as it opens.

STEP 3
Profile

Rules, margins, tax and tone set for the branch, then tested against quotes you have already sent.

STEP 4
Pilot

One branch runs live. Everything is compared against what they would have sent by hand.

STEP 5
Go live

The rest of the company, one branch at a time, with training run for each.

Terms

The self-serve product against an enterprise agreement. Specific commitments — response times, uptime — are written into the contract, not this page.

TERMSBusinessEnterprise
Support responseEmail — a person reads every notePriority, terms agreed in your contract
Named contactNoYes
Uptime commitmentNoneNegotiated in your agreement
OnboardingSelf-serveManaged, branch by branch
Security reviewThe trust centerQuestionnaire and a call
ContractMonthly, self-serveAnnual, invoiced
PricePublishedQuoted per branch

Bring one branch. Keep the rest as they are.

Most companies start with the branch that writes the most paperwork and roll the others in once the numbers reconcile.

Talk to usSee pricing