The back-office trap in advisor-tech evaluation

You sit through the demo. Forty minutes. The vendor walks the clause library: eleven document types, two hundred clauses, attorney-reviewed templates, integrations with the major custodians, an audit log per advisor seat. You take notes. None of what was on the screen will ever be seen by the household.

Advisors evaluating estate-planning platforms overweight back-office capability and underweight client-facing translation. The conventional RFP rewards breadth of features the household will never experience. It penalizes attention to the surfaces that decide whether the household wants to log in again. The retuning is the back-office discount, and applying it changes which platform wins the comparison.

The conventional advisor-tech evaluation rubric

The standard RFP for an estate-planning platform runs through a fixed inventory of back-office features. Document types covered. Clause library depth. Whether each template is attorney-reviewed. State coverage. Audit log granularity. Integration list (CRM, custodian, financial planning software). Security posture (SOC 2 status, encryption, MFA). Compliance posture (UPL framework, attorney-review routing, document retention). Onboarding time. Support SLA. Cost per advisor seat. Cost per document. Cost per attorney review.

The list is reasonable. Every line item names a real capability and vendors that built more capability earned more line items. The rubric is also written by evaluators who know enough about estate planning to ask about clause library depth, but who have never sat next to a household running the platform for the first time. The questions are vendor-shaped, not household-shaped.

A different evaluation rubric exists. It asks one question per surface the household actually touches. Most evaluators never see this rubric because the trade press, the consultants, and the vendor sales decks all run on the back-office one. The two rubrics produce different vendor rankings.

What the household actually experiences

You can list everything a household touches in an estate-planning engagement, end to end, in fewer than ten surfaces. The login page. The questionnaire. The advisor-led meeting where the questionnaire runs. The generated documents the household reads. The signing meeting. The funding letters and the dashboard that drives them. The annual review and the maintenance flow that runs between reviews. Transactional emails throughout. A vault for proof-of-filing uploads. A footer that says who the platform belongs to.

That is the full set. Everything else (the clause library, the integrations, the audit log, the admin queue, the compliance dashboard, the SOC 2 control set, the SHA-256 manifest on the template files) operates entirely below the surface. The household never logs into the clause library. The household never inspects the integration list. The household never opens the audit log.

This is not an indictment of the back-office. The back-office is what makes a platform legally functional, structurally compliant, and operationally maintainable. Without it, the client-facing surface has nothing to render. The back-office matters in the same way an air-traffic control center matters to the flight: the passengers never see it, but the flight does not happen without it.

The mistake is treating back-office capability as if it directly creates client value. It does not. Back-office capability becomes client value only when it is rendered to the household through a client-facing surface. A clause that exists in the library but never reaches the document a family reads is back-office capability with zero client value. The translation rate is what determines whether the back-office investment shows up in the household experience.

The back-office discount

Apply the discount this way. For every back-office line item in the RFP, ask one question: how does the household actually experience this capability? Then assign a translation rate between zero and one. Multiply the raw capability score by the translation rate. The product is the capability’s actual contribution to client value.

The framework is not a downvote on back-office investment. It is a re-rank. A vendor that built four document types and shipped a branded portal that the family actually wants to log into can produce more client value than a vendor that built fifteen document types but renders all of them through a generic portal that defaults to the vendor brand. The first vendor’s back-office is smaller and translates fully. The second vendor’s back-office is larger and translates partially.

Twelve times zero is zero.

Five worked examples

The graphic carries the headline numbers; the worked examples below show why each translation rate lands where it does. The pattern repeats across most back-office axes.

• Branded client portal. The household logs into the portal on every session. The branding, typography, color palette, and footer attribution are visible every time. Investment here compounds across roughly 100 to 150 sessions per household over the life of the relationship. Translation rate is near 100 percent and the compounding is what produces the wealth-transfer payoff described in the brand-interruption piece.
• Document quality and readability. The family reads the will at signing. The family reads the trust at funding. The family reads the powers of attorney during incapacity. The format, the language, the structure are all visible. Vendors who invest in document polish (typography, plain-language headers, structural clarity) translate that investment to the family at full rate. Vendors who ship documents that read like 1990s WordPerfect output translate the same back-office "deep clause library" claim at zero.
• Clause library depth. A 200-clause library matters only to the share of households whose fact patterns require the depth. A typical household needs perhaps 30 clauses; a complex household with closely-held interests, special-needs beneficiaries, and multi-state property may need 80. Beyond that, additional clause coverage is back-office surface area with diminishing translation. The right evaluation question is not "how many clauses?" but "what share of clauses are reached by the typical fact pattern, and how do you handle the rest?"
• CRM and custodian integrations. The advisor benefits from integration; the household does not. Integration value is real but it belongs on a separate axis of the evaluation (advisor-time savings rather than client-value creation). Treating integration count as client value inflates the score of vendors who built advisor-side automation and discounts the portal experience the family will actually see.
• Audit log and admin dashboards. Compliance posture matters for the regulatory side of the practice. The household never opens the audit log. Audit-log depth belongs on the compliance-posture axis rather than the client-value axis. A vendor with an excellent audit log and a mediocre client portal scores high on one axis and low on the other; counting both as the same dimension produces the wrong rank.

The five examples cover the most common back-office line items. The pattern repeats: take the back-office capability, ask how the household experiences it, assign the translation rate, multiply.

The retuned evaluation criteria

The retuned RFP keeps the back-office checklist but adds a client-facing checklist beside it. The two lists run in parallel; the platform’s overall score is the weighted combination of both.

Client-facing line items to add to any platform RFP: login URL and domain ownership, browser tab title across every page, email From-address and SPF/DKIM/DMARC alignment, password-reset email body, portal footer attribution, privacy and terms pages, document file names and PDF metadata, payment receipts and statement descriptors, 404 and error pages, and the visual coherence of the document set the household reads. Score each item zero, one, or two. The platform that scores well on both checklists is the platform that produces back-office capability AND translates it to the household; the platform that scores well only on the back-office checklist is the one most advisors would currently pick by default.

If you are running a real platform evaluation, the cleanest version of the retuned rubric is in our four-tell diagnostic and the five-tier white-label spectrum. Both posts cover the client-facing axis with specific questions to ask the vendor in the demo and after.

How Bancroft invests in client-facing surfaces

Bancroft’s engineering investment runs heavily on the client-facing axis. The Firm tier ships full white-label end to end: custom domain (yourfirm.com or any subdomain) with multi-tenant DNS automation and per-tenant SSL provisioning; branded portal with the firm’s colors, typography, logo, and favicon; brand resolution at the middleware layer that runs on every authenticated request so every page renders with the firm’s identity rather than a generic shell.

On the document layer, the platform generates documents from attorney-reviewed templates that licensed attorneys in the supported state reviewed. The output is the format the family reads at signing and at every life event; the structure, language, and rendering are the surface the household evaluates. On the workflow layer, the funding letter system generates branded packets the household downloads, the Digital Safe vault stores encrypted proof of filing under the firm’s brand, and the daily reminder cron drives follow-through on a schedule the household experiences as firm-led rather than vendor-driven.

The platform fee structure (Advisor $299 a month, Growth $499 a month, Firm $799 a month plus $249 a month per additional seat) covers the platform. Whatever the advisor charges the household for any service running on top of the platform is set by the practice, invoiced from the practice, and kept by the practice. The mechanics of attorney review are covered in our piece on attorney-reviewed vs attorney-prepared.

The bottom line

Two platforms with the same back-office checklist score can produce very different client experiences. The difference is the translation rate. Back-office capability that never reaches the household is overhead. Back-office capability that translates fully through a client-facing surface is client value. Vendors who optimize for the first checklist score high in vendor sales decks; vendors who optimize for the second score high with households over the life of the relationship.

Run both checklists in parallel on your next platform evaluation. The vendor that wins both is the one that built infrastructure and translated it. The vendor that wins only the back-office one is the one the firm replaces in two years when a household asks whose portal it is logging into.