Custom plans for restaurant brands and agencies with 10+ accounts.
Whether you operate twelve locations under one brand or twenty-five restaurant accounts inside an agency, the enterprise plan adds the contract, security, and reporting layer your team's procurement already requires.
Three things every enterprise procurement team asks for on day one.
The self-serve plans cover product. Enterprise is where the operational layer kicks in — the things your security and finance teams need before they sign.
Security review process
We answer your security questionnaire (SIG, CAIQ, custom) and walk your InfoSec team through our data handling. SOC 2 Type II in progress; happy to share our current attestations and roadmap.
Custom DPA + DSA
Mutual data processing addendum and a brand-specific data sharing agreement covering the diner-facing tracking. Procurement-ready, redlines welcome, signed before any production data flows.
Quarterly business review
A dedicated success manager runs a quarterly review on Match Quality, cost-per-attributed-order, platform mix, and any open product requests. Roadmap commitments in writing where it matters.
The product is the same. The contract, the security posture, and the people who pick up the phone are what enterprise actually pays for.
The enterprise-specific layer, in detail.
Every item below is included in an enterprise contract by default. Anything not listed, ask and we will scope it.
Service-level agreement
99.95% uptime on the diner-facing smart links, 99.9% on the admin dashboard, credits for any breach. Monthly status report.
SSO + SCIM provisioning
Okta, Azure AD, Google Workspace. Group-based role assignments for agency operators, restaurant owners, and read-only stakeholders.
Custom MSA + procurement
We sign through your procurement portal. Mutual NDA, custom invoicing terms, net-30 or net-60 supported, security questionnaire in week one.
Data sharing agreement
DSA covering Meta CAPI, Google Ads conversion uploads, GA4 Measurement Protocol, TikTok Events API. Co-signed once, blanket-covers every restaurant in your enterprise.
Dedicated infrastructure
Optional dedicated Postgres + edge worker pool, isolated from multi-tenant compute. Required for some EU and healthcare-adjacent restaurant brands.
Read-only Postgres replica
Optional live replica into your warehouse account, or hourly Parquet drops to S3/GCS. Schema documented and versioned.
What you get inside the contract.
The product surface is identical. The contractual and operational surface is where Enterprise earns its keep.
| Self-serve plans | Enterprise | |
|---|---|---|
| Contracts | ||
| Terms of service | Standard ToS | Custom MSA + redlines |
| Data processing addendum | Standard DPA | Mutual custom DPA |
| Data sharing agreement | Self-signed online | Co-signed brand-specific DSA |
| Net terms | Stripe monthly | Net-30 or net-60, PO-based |
| Security | ||
| SSO | — | |
| SCIM provisioning | — | |
| Custom security review | — | |
| Dedicated infrastructure (optional) | — | |
| Operations | ||
| SLA | — | 99.95% / 99.9% |
| Named account team | Agency only | Always |
| Quarterly business review | — | |
| Scope | ||
| Locations or client accounts | Up to 10 each | Unlimited |
| Tracked events / month | Per-tier caps | Custom pooled cap |
| Webhook + data export | CSV + webhook | Full schema, replica optional |
No self-serve sign-up. Talk to a human.
Enterprise pricing is quoted against scope. Tell us how many locations or client accounts are in play, your monthly ad spend, and your procurement timeline.
- Unlimited locations or client accounts
- Service-level agreement (SLA)
- SSO + SCIM provisioning
- Custom contract, MSA, DSA
- Dedicated infrastructure available
- Quarterly business review
What to expect from the first call
- 30 minutes. Scope, security must-haves, procurement timeline.
- 48 hours. Indicative quote and a draft MSA + DPA in your inbox.
- 2 — 4 weeks. Security review, redlines, signature.
- Day 1 of contract. Account team paired, kickoff scheduled, migration runbook drafted.
Prefer email? sales@dineroute.com
Things procurement and security ask first.
What does procurement look like?
First call covers scope, MSA, DPA, security questionnaire, and pricing model. Most procurement cycles close in 4-6 weeks for restaurant brands and 2-4 weeks for agencies, depending on legal review on your side.
How does enterprise pricing work?
Two anchors: (1) total locations or client accounts in scope, (2) tracked events per month pooled across the org. We quote a flat annual fee on a 1-year or 3-year term. Most enterprise contracts land between $40K and $250K annually.
Do you support custom contract terms — termination, IP, liability?
Yes. Our standard MSA covers the common asks. Mutual termination for convenience, IP carve-outs for derivative restaurant brand assets, mutual indemnity, and an aggregate liability cap pegged to the annual contract value. We redline rather than dig in.
Where does the data sit and who can access it?
US-East primary, US-West warm standby on multi-tenant. Dedicated infrastructure customers can pick US, EU, or APAC regions. Production access is restricted to on-call engineering with audit logging. We can route around any third-party processors your DSA prohibits.
Can you integrate with our existing data warehouse?
Yes. We offer hourly Parquet drops to S3 or GCS, a Snowflake/BigQuery share, or a read-only Postgres replica. Schema is documented, versioned, and tested against the open-source dbt models we ship.
What does the security review process look like?
Week one: kick-off, NDA, exchange of SOC reports, our completed CAIQ. Week two: your questionnaire (SIG-Lite, CAIQ, or custom). Week three: live walkthrough with our engineering lead. Most reviews close in three weeks; we have done one in a week when contracts pressured it.
Scope your enterprise rollout in one call.
30 minutes, no slides. We will tell you what we can and cannot do for your scope — and what the rough timeline and pricing look like.
No procurement obligation. Conversation only.