[101]Foundational
Inmon (1992)
Inmon, W. H. (1992). Building the Data Warehouse. New York: John Wiley & Sons.
Origin of the corporate data-warehouse concept and the case for a single subject-oriented integrated data store.
Read sourceData architecture
Data architecture: warehouses, lakehouses, and the integration tax
The Single Data Backbone is Weaver's answer to a thirty-year academic conversation about how to give business applications a single, consistent, real-time view of their data — without the integration tax. The references below trace that argument from Inmon's 1992 corporate-warehouse manifesto through the 2021 lakehouse paper from the Databricks team.
[102]Foundational
Kimball & Ross (2013)
Kimball, R. & Ross, M. (2013). The Data Warehouse Toolkit: The Definitive Guide to Dimensional Modeling (3rd ed.). Wiley.
Canonical reference on dimensional modeling and the case against silos of analytical data.
Read source[103]Academic
Armbrust et al. (2021)
Armbrust, M., Ghodsi, A., Xin, R., & Zaharia, M. (2021). Lakehouse: A new generation of open platforms that unify data warehousing and advanced analytics. In Proceedings of the 11th Conference on Innovative Data Systems Research (CIDR '21).
The Databricks "lakehouse" paper — the architectural argument for unifying warehouse and lake into one platform that supports both analytics and applications.
Read source[104]Academic
Halevy et al. (2006)
Halevy, A., Rajaraman, A., & Ordille, J. (2006). Data integration: The teenage years. In Proceedings of the 32nd VLDB Conference, 9–16.
Survey of why enterprise data integration is structurally hard and why "every new application means another integration project."
Read source[105]Academic
Stonebraker & Hellerstein (2005)
Stonebraker, M. & Hellerstein, J. M. (2005). What goes around comes around. In Readings in Database Systems (4th ed.), MIT Press.
Historical/critical overview of how database architectures cycle, useful when arguing against fragmented stacks.
Read source[106]Academic
Stonebraker (2010)
Stonebraker, M. (2010). SQL databases v. NoSQL databases. Communications of the ACM, 53(4), 10–11.
On ACID, consistency, and the cost of giving them up — supports the SDB ACID claim.
Read sourceAI governance
AI governance: agents under human control
Every AI claim on Weaver — agentic marketing in Growth Engine, AI policy enforcement in QuickExpense, AI insights in ERP — is paired with an explicit human-control posture. That posture is grounded in the NIST AI Risk Management Framework, the OECD AI Principles, the EU AI Act, and the academic literature on responsible ML in production.
[110]Standard
NIST AI RMF (2023)
National Institute of Standards and Technology (2023). Artificial Intelligence Risk Management Framework (AI RMF 1.0). NIST AI 100-1.
US voluntary standard for managing AI risk — anchors the "AI with human control" claim with a recognised governance framework.
Read source[111]Standard
OECD AI Principles (2019, updated 2024)
OECD (2019, updated 2024). Recommendation of the Council on Artificial Intelligence. OECD/LEGAL/0449.
International AI principles adopted by 47+ countries; backs accountability and transparency claims.
Read source[112]Standard
EU AI Act (2024)
European Parliament & Council (2024). Regulation (EU) 2024/1689 of 13 June 2024 laying down harmonised rules on artificial intelligence (Artificial Intelligence Act).
EU legal framework on AI risk classes, transparency, and human oversight — directly relevant to enterprise compliance.
Read source[113]Academic
Bommasani et al. (2021)
Bommasani, R., Hudson, D. A., Adeli, E., Altman, R., et al. (2021). On the opportunities and risks of foundation models. Stanford CRFM, arXiv:2108.07258.
Foundational survey from Stanford CRFM on capabilities, risks, and governance of large foundation models.
Read source[114]Academic
Amershi et al. (2019)
Amershi, S., Begel, A., Bird, C., DeLine, R., Gall, H., Kamar, E., Nagappan, N., Nushi, B., & Zimmermann, T. (2019). Software engineering for machine learning: A case study. In Proceedings of ICSE-SEIP 2019, 291–300.
Microsoft Research study showing why ML in production needs human-in-the-loop checkpoints and explicit governance.
Read source[115]Academic
Mitchell et al. (2019)
Mitchell, M., Wu, S., Zaldivar, A., Barnes, P., Vasserman, L., Hutchinson, B., Spitzer, E., Raji, I. D., & Gebru, T. (2019). Model cards for model reporting. In Proceedings of FAT* 2019, 220–229.
Origin of the "model card" — supports the explainability/auditability claim in our AI-with-human-control message.
Read source[150]Academic
Wirtz et al. (2018)
Wirtz, J., Patterson, P. G., Kunz, W. H., Gruber, T., Lu, V. N., Paluch, S., & Martins, A. (2018). Brave new world: Service robots in the frontline. Journal of Service Management, 29(5), 907–931.
Frequently-cited framework for thinking about autonomous service agents and where humans stay in the loop.
Read sourceAccounting
Algebraic accounting: from Pacioli to type-safe ledgers
Weaver's Financial Ops is built on a research-grade accounting model. The lineage starts with Pacioli's 1494 codification of double-entry bookkeeping, runs through Ellerman's 1985 reformulation in group-theoretic terms, and culminates in the K3 Labs paper on type-safe algebraic accounting that backs Weaver's ledger.
[120]Foundational
Pacioli (1494)
Pacioli, L. (1494). Summa de arithmetica, geometria, proportioni et proportionalità. Particularis de computis et scripturis. Venice.
The 1494 publication that codified double-entry bookkeeping — the historical anchor for any algebraic-accounting claim.
Read source[121]Academic
Ellerman (1985)
Ellerman, D. P. (1985). The mathematics of double entry bookkeeping. Mathematics Magazine, 58(4), 226–233.
Reformulation of double-entry as group theory over additive abelian groups — basis for algebraic accounting.
Read source[122]Academic
Ellerman (2014)
Ellerman, D. P. (2014). On double-entry bookkeeping: The mathematical treatment. Accounting Education: An International Journal, 23(5), 483–501.
Modern restatement of the algebraic foundation of accounting; cited by the K3 Labs algebraic-accounting paper.
Read source[123]Academic
K3 Labs — Algebraic Accounting
K3 Labs (2024). Algebraic Accounting: A Type-Safe Mathematical Foundation for Computational Accounting.
Weaver/K3 Labs in-house paper; the technical depth proof point behind Financial Ops.
Read source[130]Industry
ACFE (2024) — Report to the Nations
Association of Certified Fraud Examiners (2024). Occupational Fraud 2024: A Report to the Nations.
ACFE biennial study; widely-cited 5% of revenue lost to fraud and expense-reimbursement scheme statistics.
Read source[131]Standard
COSO (2013)
Committee of Sponsoring Organizations of the Treadway Commission (2013). Internal Control — Integrated Framework.
The COSO internal control framework — references for control-design and SOX compliance arguments.
Read sourceExpense & fraud
Expense fraud and internal control
QuickExpense's real-time fraud detection is anchored in the ACFE's biennial Report to the Nations and the COSO Internal Control framework — the two most widely-cited authorities on occupational fraud and the controls that catch it.
[130]Industry
ACFE (2024) — Report to the Nations
Association of Certified Fraud Examiners (2024). Occupational Fraud 2024: A Report to the Nations.
ACFE biennial study; widely-cited 5% of revenue lost to fraud and expense-reimbursement scheme statistics.
Read source[131]Standard
COSO (2013)
Committee of Sponsoring Organizations of the Treadway Commission (2013). Internal Control — Integrated Framework.
The COSO internal control framework — references for control-design and SOX compliance arguments.
Read sourceERP
ERP failure rates and TCO
The "you don't have to rip out QuickBooks to grow up" argument on the comparison page is grounded in two decades of well-documented ERP implementation outcomes — from the Standish CHAOS reports to McKinsey's analysis of large IT projects to Panorama Consulting's annual ERP study.
[140]Industry
Standish Group — CHAOS Report
Standish Group International (annual). CHAOS Report. The Standish Group, West Yarmouth, MA.
Long-running study of project success/failure rates across IT projects — anchor for "implementation risk" claims.
Read source[141]Industry
McKinsey — IT projects (2012)
Bloch, M., Blumberg, S., & Laartz, J. (2012). Delivering large-scale IT projects on time, on budget, and on value. McKinsey Quarterly.
17% of large IT projects go so badly they threaten the company; canonical citation for ERP implementation risk.
Read source[142]Industry
Panorama Consulting — ERP Report
Panorama Consulting Group (annual). The ERP Report. Denver, CO.
Annual ERP implementation outcomes survey — cost overruns, schedule slippage, benefit shortfalls.
Read sourceCRM
CRM as process, not as a tool
The CRM Graveyard campaign rests on academic CRM research showing that customer-relationship management succeeds as a process embedded in operations, not as a standalone tool. References include Reinartz's empirical CRM study and the Payne & Frow strategic framework, complementing the industry data already cited on /crm-graveyard.
[170]Academic
Reinartz, Krafft & Hoyer (2004)
Reinartz, W., Krafft, M., & Hoyer, W. D. (2004). The customer relationship management process: Its measurement and impact on performance. Journal of Marketing Research, 41(3), 293–305.
Foundational empirical CRM study — operationalises CRM as a process and measures its actual impact on firm performance.
Read source[171]Academic
Payne & Frow (2005)
Payne, A. & Frow, P. (2005). A strategic framework for customer relationship management. Journal of Marketing, 69(4), 167–176.
Strategic CRM framework — supports the argument that CRM lives in a broader operations context, not as a standalone tool.
Read sourceAgentic marketing
Agentic marketing and service automation
Growth Engine — Weaver's deep marketing agent — sits inside an emerging academic literature on autonomous service agents and the boundary between machine and human work. References include Stanford CRFM's foundation-models survey and the leading service-research framework on AI in customer-facing roles.
[113]Academic
Bommasani et al. (2021)
Bommasani, R., Hudson, D. A., Adeli, E., Altman, R., et al. (2021). On the opportunities and risks of foundation models. Stanford CRFM, arXiv:2108.07258.
Foundational survey from Stanford CRFM on capabilities, risks, and governance of large foundation models.
Read source[150]Academic
Wirtz et al. (2018)
Wirtz, J., Patterson, P. G., Kunz, W. H., Gruber, T., Lu, V. N., Paluch, S., & Martins, A. (2018). Brave new world: Service robots in the frontline. Journal of Service Management, 29(5), 907–931.
Frequently-cited framework for thinking about autonomous service agents and where humans stay in the loop.
Read source[151]Academic
Huang & Rust (2018)
Huang, M.-H. & Rust, R. T. (2018). Artificial intelligence in service. Journal of Service Research, 21(2), 155–172.
Four-stage model of AI in service (mechanical → analytical → intuitive → empathetic) — useful frame for the marketing-agent pitch.
Read sourceLow-code / extensibility
Low-code, citizen developers, and Build Your Own
Build Your Own — Weaver's extensibility model — is positioned within the broader low-code research showing that platforms which let domain experts build alongside engineers ship faster and accumulate less integration debt.
Applied on/build-your-own
[160]Academic
Sahay et al. (2020)
Sahay, A., Indamutsa, A., Di Ruscio, D., & Pierantonio, A. (2020). Supporting the understanding and comparison of low-code development platforms. In Proceedings of SEAA 2020, 171–178.
Comparative academic analysis of low-code platforms; supports Build Your Own positioning.
Read source[161]Industry
Forrester — Low-Code Wave
Forrester Research (annual). The Forrester Wave: Low-Code Development Platforms. Cambridge, MA.
Industry analyst coverage of low-code platforms.
Read source