New: Privacy Analytics — measure your site without cookies or a consent banner. Start free →

Research

Original analysis and frameworks for small business AI adoption and operational maturity.

Research BriefFree

AI Model Data Practices: What Business Users Need to Know

The data practices of AI tool providers vary significantly and are frequently misunderstood by business users. The key distinctions that matter operationally are: whether the provider uses user inputs to train or improve their models, whether there is an opt-out available, what data the provider shares with third parties, and what retention policies apply to user inputs and outputs. Enterprise agreements for major AI providers typically include provisions that prevent training on customer data, but these provisions are often not the default for free or low-cost tiers. Small businesses that use free or consumer-tier AI tools may be subject to data practices that would not be acceptable under their own privacy policies or under the terms of their contracts with clients. The secondary issue is sub-processor chains: AI tools that process data frequently use sub-processors for infrastructure, model serving, or other components. Understanding who those sub-processors are and where they are located matters for businesses with customers in privacy-sensitive jurisdictions.

Read →
Research BriefFree

The Business Case for Process Standardization Before Scaling

Growth amplifies both the strengths and weaknesses of existing operational processes. Organizations that scale with undocumented, person-dependent processes find that inconsistency — which was manageable at small scale — becomes a significant quality and customer experience problem at larger scale. The research on this is consistent across industries: the window for process standardization is before rapid growth, not during it. During rapid growth, the urgency of operational demand crowds out the time needed for documentation and standardization. The cost of retroactive standardization — re-documenting processes while simultaneously running them — is substantially higher than proactive standardization. The most effective standardization approach is incremental: start with the processes that most directly affect customer outcomes or revenue, establish documentation and review practices, and expand systematically. Attempting to document everything simultaneously produces documentation that no one owns and no one maintains.

Read →
Research BriefFree

Data Breach Disclosure Patterns and SMB Preparedness

Analysis of data breach disclosure trends reveals that small businesses face a different risk profile than enterprises, both in the nature of incidents and in preparedness to respond. The most common incident types affecting small businesses are credential compromise, phishing-driven account takeover, and third-party vendor incidents — not the sophisticated intrusions that dominate enterprise incident narratives. This matters for preparation: the controls that address small business risk are primarily operational (access management, employee training, vendor vetting) rather than technical (advanced threat detection, security operations centers). Preparedness surveys consistently show that the majority of small businesses do not have a documented incident response process, have not tested their backup and recovery capabilities, and do not have a clear understanding of their disclosure obligations in the event of a breach. The gap is not technical sophistication — it is the absence of basic documented practices.

Read →
Research BriefFree

AI Tool Adoption in Small and Medium Businesses: Patterns and Gaps

Surveys of AI tool adoption in small and medium businesses consistently reveal a pattern: adoption is faster than governance. Individual employees and departments adopt AI tools based on productivity benefits, while organizational policies, vendor vetting, and data handling practices lag significantly. The gap creates operational exposure that organizations typically become aware of reactively — through a vendor policy change, a security incident, or a customer inquiry — rather than through proactive assessment. The tools most frequently adopted without formal approval are writing assistants, code completion tools, and data summarization tools — all of which regularly interact with business-sensitive or customer-sensitive information. The risk is not inherent to the tools themselves but to the absence of clear guidance on what information is appropriate to share with them.

Read →
Research BriefFree

Privacy-Preserving Analytics: Accuracy Trade-offs and Business Value

The assumption that privacy-preserving analytics necessarily sacrifices measurement accuracy has been substantially revised by both academic research and practitioner experience. Cookieless and server-side measurement approaches, when implemented correctly, often produce more accurate data than cookie-based alternatives — particularly as browser-based cookie blocking has become widespread among higher-value audience segments. Research suggests that privacy-conscious users who block traditional trackers tend to be more engaged and have higher purchasing intent than the average visitor, meaning that analytics approaches that cannot measure them systematically undercount the most valuable part of the audience. The trade-off is real but narrower than commonly assumed: privacy-preserving analytics typically loses individual session continuity while retaining aggregate behavioral signals that are sufficient for most operational decisions. For small businesses making content, product, and acquisition decisions, aggregate signals are usually the relevant level of analysis.

Read →
Research BriefFree

The Hidden Cost of Undocumented Business Processes

Research on organizational knowledge management consistently shows that undocumented processes create compounding costs beyond the obvious disruption of staff turnover. When critical process knowledge exists only in people's heads, organizations incur costs from inconsistent execution, onboarding delays, error rates that increase over time, and reduced capacity to delegate or scale. The problem is self-reinforcing: the more dependent an organization becomes on individual knowledge holders, the more disruptive their absence becomes, which creates pressure to keep those individuals rather than systematically documenting what they know. The intervention is well-established: structured process documentation with explicit ownership, regular review cycles, and a format that captures decision logic rather than just task sequences. Organizations that establish this practice before they need it — before a key departure, before rapid growth — incur significantly lower transition costs than those that attempt to reconstruct knowledge after the fact.

Read →
Do Not Sell My Data