Engagement, Auth & Cost
How we build, who logs in (and how), and why your monthly stack costs almost nothing.
How we'd execute
Step 1 is me sitting in on your day, not a Gantt chart. We don't write code until we've watched the work.
A focused working session (or two) with Meridian leads to walk the live workflow, the workbook edits, the side conversations, and the email chains. We agree on scope and priorities. No code yet.
Translate your workbooks into typed schemas (deal, party, document, cell, signoff). Round-trip a single Meridian deal end-to-end in the model before any UI is built.
Build the views from this pitch one at a time, with you reviewing each before moving on. Iteration is cheap because the model is already right.
Runbook, admin training, model docs, and the audit story for your buyers/lenders.
Third-party stack · the bill stays small
Every third-party we add is a recurring bill, a security review, and a vendor risk question on every sale. Default is: build it ourselves on the MLL stack. The rare exception below has a clear ROI story.
- No analytics SaaS (we self-host)
- No third-party data-room vendor (we are the data room)
- No third-party CRM tie-in (your CRM exports CSV, we ingest)
- No usage-based AI billing exposed to your clients
Auth tiers · three levels, one user store
Each user is at a tier. Buyers and partners on Staunch. Most operators on Medium. Outside reviewers and assistants on Magic-link, scoped tight.
- Method
- Email + password + TOTP 2FA (Authy / Google Authenticator). Hardware key (WebAuthn) optional.
- Session
- 8h sliding, IP+device fingerprint
- Audit
- Every login, every action, signed
- Method
- OAuth (Google Workspace / Microsoft 365) OR local strong password (≥14 chars, breach-checked)
- Session
- 8h sliding, no IP pin
- Audit
- Every signoff, file open, comment
- Method
- Emailed temporary magic link, scoped to a single folder or document, expires in 24h–7d
- Session
- Per-link, no persistent account
- Audit
- Link issued, link redeemed, doc opened
Client consolidation + org hierarchy
You said 'Buyer / Seller / Meridian' — we both know it's actually six layers deep. The platform takes that as a feature, not a problem: client consolidation + a proper hierarchy is where this stops being a single workbook and starts being your repeatable product.
- Partners
- VPs / Directors
- Diligence associates
- Assistants
- Buyer principal
- Buyer team
- Buyer counsel
- Buyer's assistant
- Seller principal
- Seller controller
- Seller counsel
- Lender
- Tax advisor
- QofE reviewer
- Consolidation — one login, every deal a user has ever touched at Meridian is in one place.
- Hierarchy — partners see firm-wide; associates see their deals; assistants see what they're delegated.
- Recurring revenue — once a buyer/seller is in the system, they re-engage on the next deal without re-onboarding.
- Audit — every action carries the org + role of the actor, forever.
Add to scope
Check items to build your estimate. Totals update live in the cart.
-
Working session with Meridian leads, annotated workflow doc, agreed scope.
-
Typed schemas: deal, party, document, cell, signoff. Round-trip one Meridian deal.
-
TOTP enrollment, optional WebAuthn, IP+device fingerprint, audit log.
-
Google/Microsoft OAuth, local strong-password with breach check.
-
Email magic links with scope + expiry, single-folder grants, audit trail.
-
Firm / client / external orgs with parent-child roles; permissions inherit.
-
One login → every deal that user has touched, across buyers/sellers/counsel.