project_mlp_pilot_pitch_2026_04_28

Tuesday 28 April 2026 — Rich + Charis prepared a 13-page partner-pitch leave-behind for Jane Hunter at MLP, to be emailed before an in-person meeting later the same day. MLP is being invited as lead partner firm for the MyFamilyInherits.com pilot — free six-month pilot covering MFI consumer leads + InheritWills.com conversion + IAS authoring for E&W secular wills.

Why: MLP is a Manchester-area (Altrincham, “0 mi” in the comparison-engine mockup) firm Rich and Charis have been working with. MFI mockups were already MLP-branded (“In association with MLP Law” / MLP listed as recommended firm at £320 in the comparison engine) BEFORE this pitch was prepared, suggesting prior groundwork. Faith-tradition wills (Islamic, Jewish in particular) flagged in §5 as longer-term opportunity NOT pilot scope; Rich’s read is MLP doesn’t currently do faith-tradition wills but may want to develop the capability.

How to apply:

• The doc lives at outreach/mlp-jane-hunter-pilot-invitation.md v1.3 (git commit b9f879f, pushed to origin/main)
• The PDF in Rich’s Downloads folder (MLP-pilot-invitation.pdf) is what gets emailed to Jane
• Mockup screenshots live in outreach/mlp-mockups/ — re-captured with three firm-specific renames applied to /tmp working copies (MLP Law → MLP / MFI BackOffice → IAS / idrlaw → mlp). The code-mfi/ source HTML was NOT updated; the renames live only in the screenshot PNGs that went into the PDF.
• After the meeting, Rich may update the doc with what worked / what didn’t — bump to v1.4+ with a new CHANGELOG entry.
• Outcome is unknown at time of writing this memory — if a future session needs to know what happened in the meeting, ask Rich directly rather than assume from later commits.
• Open follow-up question (parked, not actioned): should the renames in /tmp be propagated back to the canonical mockups in code-mfi/mockups/public/*.html? Rich said “save everything” but did not explicitly authorise editing code-mfi. Confirm before propagating.

Pattern recipe is at: feedback_partner_pitch_doc_pattern.md — reusable for next firm pitch.

One vocabulary fact established this session (Rich confirmed 2026-04-28): IAS expands to InheritKit Authoring Studio, NOT “Inherit Advisory System” (that was my v1.4 guess). The brand-architecture.md does not currently document this expansion. The doc reached v1.5 at commit 82c5844 with the corrected expansion in two locations (closed-loop diagram + §4 heading + §4 first sentence).

---

UPDATE — meeting outcome (Tuesday 28 April 2026, evening)

The meeting went POSITIVE. Rich met Jane Hunter in person at MLP Altrincham. Jane was impressed with both documents (the pitch invitation Rich emailed beforehand + the technical & integrity supplement Rich brought with him).

Board-sign-off route opened. Jane committed to bring the proposal to the MLP LLP board, which is led by Stephen Attree (managing partner). Two new dates locked:

• Monday 11 May 2026 — joint call: Rich + Jane Hunter + Stephen Attree, to discuss the combined proposal in detail.
• Tuesday 19 May 2026 — MLP board meeting with potential sign-off on a proposal to work with Testate Technologies.

Two new documents produced for the Stephen / board path (both committed at parallel-session commit 2cf917f after my explicit 3aeae26 for v1.0 of the combined proposal):

• outreach/mlp-stephen-attree-combined-proposal.md v1.1 — 17-page prose-only board paper. Combines pitch invitation + technical supplement; Lasting Powers of Attorney added to pilot scope; bidirectional Clio Draft integration committed as priority InheritWills.com target; faith-tradition reduced to single paragraph (per Jane’s signals, see below); MLP’s in-house Digital Assets log deliberately omitted (Jane’s pet project — not Stephen-board territory yet). PDF at /mnt/c/Users/Richard/Downloads/MLP-board-proposal.pdf.
• outreach/mlp-stephen-attree-mockups.md v1.0 — 7-page visual companion document, six interface mockups one per page. PDF at /mnt/c/Users/Richard/Downloads/MLP-mockups.pdf. Stephen reads each at his own cadence.

Intelligence captured during the meeting:

• MLP’s software stack: Clio Manage (case management) + Clio Grow (CRM) + Clio Draft (drafting) + Lexis Protégé AI (“very good” per Jane). This is the first concrete signal we have on a partner firm’s full stack. Clio Draft is now the first build target for the InheritWills.com importer/exporter path — bidirectional, so MLP keeps Clio Draft as their drafting workspace and INHERIT adds the structured-data + audit layer alongside.
• Faith-tradition reality at MLP: Jane reported Jewish work is limited (“funerals not included”) and Muslim work is “not high end.” Rich suggested MLP may not get much Muslim work because they don’t try; Jane appeared disinterested in the suggestion. Implication: faith-tradition framing did NOT land as a hook for MLP. Soft-pedalled to a single paragraph in the Stephen combined proposal.
• Power of Attorney: MLP do POA work in roughly equal measure to wills. Rich added LPAs to pilot scope in the combined proposal (was previously parked as roadmap).
• MLP’s in-house Digital Assets log: Rich’s read is Jane may want to monetise this in the near future. Deliberately omitted from the Stephen combined proposal (Jane’s pet project; not Stephen-board territory at this stage).

Pipeline state (per ~/testatetech/docs-admin/partner-pipeline/per-firm/mlp-law/contact-log.md v0.2 commit b3b76ef): advancing P-β → P-γ. MLP Law is candidate-1 for Phase-1 closure gate B and is now the most-advanced firm in the partner pipeline by 24+ months ahead of dev-plan expectation. Pipeline diversification is now the most important risk: if MLP signs but no second firm exists, MLP has implicit leverage on terms; if MLP doesn’t sign, gate B fires red with no fallback.

Three new richard-tasks added at ~/davieshq/docs-personal/richard-tasks-tt.md v1.3 commit 8637e0c: task 179 (combine docs for Stephen — done same day), task 180 (Mon 11 May joint call), task 181 (Tue 19 May MLP board meeting).

Open follow-ups (not yet actioned):

• Draft NDA template ready for 11 May call (in case MLP requests).
• Sample anonymised Clio Draft export — explicit ask in the combined proposal §13 — would let us scope the bidirectional integration before 19 May board.
• If MLP signs: pilot Statement of Work needs drafting for board review.
• If MLP signs: pipeline diversification urgent — advance 2-3 more firms to P-β over next month so MLP isn’t structurally leveraged.