Fill-in artifacts engineers and PMs work through and walk away with a populated document. Each one forces the thinking that should have happened before code was written or compliance review was scheduled — and produces an artifact you can attach to a ticket or paste into a deck.
Each worksheet produces a populated document you can attach to a Jira ticket, paste into a Slack channel, or hand to a steering committee.
ROI calculators, sizing computations, and coverage roll-ups recalculate as you type — no submit button.
Half-fill it on a Tuesday, finish it on a Friday — the worksheet remembers everything across sessions on this device.
Take it online, or download the XLSX (live formulas) or PDF (printable) to continue offline.
Compute the minimum archetype count, longitudinal depth, and event-density floor your team needs to ship a defensible wealth-tech feature. Outputs a recommended Wealth Data Set bundle.
Compute the fully-loaded annual cost of building synthetic wealth data in-house vs. licensing WealthSynth. Outputs payback period, three-year NPV, and a sensitivity view. Pairs with the in-house-build comparison.
A grid where the team enumerates code paths down the rows and demographic / account / event slices across the columns, then marks coverage gaps. Output: the specific archetypes that close each gap.
For each recommendation type the firm makes, capture the audit-trail fields, timestamps, and disclosures required to demonstrate Care Obligation compliance. Cross-walks to the Reg BI Audit Data Checklist.
For each FinCEN typology the team monitors (structuring, layering, source-of-funds anomalies, PEP-adjacent), document the synthetic transactions and account patterns required to fire the rule. Pairs with the AML/BSA monitoring data checklist.
Walk through every system, vendor, and data class that touches NPI; produce an inventory mapped to 16 CFR 314 control families. The artifact the FTC examiner asks for first.
Capture the wash-sale, lot-selection, cross-account, and short-vs-long-term cases your TLH engine must handle. Outputs the synthetic households that exercise each case.
For each lifecycle event (risk-tolerance change, retirement transition, large deposit, beneficiary change), capture the data signals required and the synthetic households that produce them.