Matthew Bagley

For a company running on EOS—the management system built around Level 10 meetings, Rocks, and Quarterly Conversations—the answer is not a separate IT process but a translation into the vocabulary the team already uses.

• A technology roadmap becomes an owner-tagged issues list, ready for the same identify-discuss-solve treatment as other business problems.
• A 90-day technology review becomes the quarterly conversation that sets the next IT priorities.
• When technology follows the same rhythm as the rest of the business, it stops hijacking traction.
• Bagley says the Visionary can focus on growth, the Integrator can keep operations moving, and the “accidental IT person” can get their day job back.

The post maps three EOS tools to IT equivalents: a prioritized, owner-tagged IT Issues List; a 90-day “Quarterly Conversation” for technology, paired with quarterly planning to choose the coming quarter’s IT Rocks; and a named IT Prosperity Process for turning tech chaos into measurable momentum. Prosper IT runs EOS itself, making the vocabulary part of the company’s operating method, not a marketing gloss.

Read original

Citing an average hit to small and midsize businesses of $120,000 to $1.2 million once downtime, recovery, and lost business are counted, they frame resilience as something to fund and insure, not a checkbox to tick.

• Basic file backup does not cover this risk: the money needs to go toward full business continuity, including offsite or offline copies that ransomware cannot encrypt and recovery playbooks that have been tested, not just written.
• The comparison to insurance makes the case: many small firms could not survive an extended outage, so preparedness belongs alongside routine, unglamorous spending such as a policy premium.

The post opens with the line “Got $120,000 up to $1.2 million to waste?”

• It then names what the spending should cover—offline backups, tested recovery playbooks, and employee training—before offering to run scam tests on staff or review a reader’s existing backup and recovery plans.
• The dollar range is presented as an industry average without a cited source or date, so buyers should ask for its source before using it as a benchmark.

Read original

Once ChatGPT and AI-driven analytics are in everyday use, a small business faces the same questions as a large one: how to use AI responsibly, ethically, and legally.

• The answer is to write down a few decisions, not hire a compliance department.
• Those decisions include whether employees may paste confidential data into a chatbot, how to use AI-generated content without infringing copyright, whether customer data reaches external AI services, whether a recommendation can be explained, and whether AI used in hiring or lending could discriminate.
• Without guardrails, a small firm risks a regulatory breach or a loss of customer trust from a single careless use.
• Bagley’s prescription is deliberately modest: a simple plan endorsed by leadership and updated as the law changes.

The post lists policy questions a small business can answer, such as whether employees can enter confidential data into an AI chatbot and what guidelines should govern AI-generated content and copyright.

• It also sketches areas a framework should cover: data privacy, decision transparency, and avoiding discrimination when AI informs hiring or lending.
• Buyers who need a template or jurisdiction-specific legal guidance should ask for it.

Read original

Start here for the signature move: translating a familiar business framework into decisions about systems, priorities, and vendors.

The post translates three things.

• A technology roadmap becomes a prioritized, owner-tagged IT issues list, ready for the same identify-discuss-solve treatment as other business issues.
• A strategic business review becomes a 90-day “quarterly conversation” about tech: what is working, what is not, and which IT rocks to take on next.
• The third translation is the named IT Prosperity Process, a path from tech chaos to measurable momentum.
• Prosper IT says it runs EOS itself, making the language an expression of the company’s own operating method.
• The stated outcome: visionaries stay focused on growth, integrators keep the gears turning, and the “accidental IT person” gets their day job back.

For brands planning a campaign

A useful fit for a managed IT services company targeting founder-led or EOS-run SMBs.

• The post offers a ready-made collaboration angle: translating an operating framework into an IT plan.
• Its “accidental IT person” framing names a specific buyer pain the collaboration could address.

Start here for the dollar framing and the concrete list of what a recovery plan should contain.

The post opens with a cost range: an average cyberattack costs an SMB roughly $120,000 to $1.2 million once downtime, recovery, and lost business are counted.

• It argues that file backup alone is not enough; business continuity planning should include offsite or offline backups that ransomware cannot encrypt and tested recovery playbooks.
• Many small firms, it adds, would struggle to survive an extended outage, making ransomware resilience—from employee training to backup infrastructure—an essential counterpart to insurance.
• The post closes by inviting readers to message for help testing whether staff will fall for scams or for another set of eyes on backup and recovery plans.

For brands planning a campaign

Gives a managed IT services brand a cost-anchored hook for a collaboration on resilience. The post names decision points—offline backups, tested playbooks, phishing training, and the insurance comparison—so a follow-up can explore one in depth rather than repeat the warning.

Start here to see the same governance mindset applied to a newer technology risk.

The post argues that AI governance is no longer only a large-company concern, as tools such as ChatGPT and AI-driven analytics enter everyday small-business work.

• It outlines questions SMBs must answer about using AI responsibly, ethically, and legally, with concrete examples: whether employees may put confidential data into a chatbot, and how to use AI-generated content without infringing copyright.
• The framework should cover data privacy, decision transparency, and avoiding discrimination when AI informs hiring or lending.
• The recommendation: a simple governance plan endorsed by leadership and updated as laws change.

For brands planning a campaign

Offers a managed IT services collaborator a policy-level angle rather than a product pitch. A joint piece could turn the outline into a starter AI-use policy for SMBs, fitting a brief on SMB technology strategy and giving the partner something practical to co-sign.

They argue that technology planning should follow the same rhythm: a technology roadmap works like a prioritized, owner-tagged IT Issues List ready for the IDS step, while a 90-day strategic business review works like a Quarterly Conversation for tech, deciding which IT Rocks to take on next.

• The payoff is role-specific — Visionaries stay focused on growth, Integrators keep operations moving, and the "accidental IT person" gets their day job back.
• The post points to a one-page summary hosted on Prosper IT's site and ends by asking whether technology is fueling a company's traction.

Translates an established management framework the reader already uses into a technology plan, mapping each EOS term to an IT equivalent.

The advice presumes the reader runs EOS; it addresses that audience rather than small businesses choosing a planning system from scratch.

For brands planning a campaign

A good fit for collaborations aimed at EOS-run or similar operating-system-run companies — tooling, managed services, or software that plugs into quarterly planning and issue-tracking routines. Content works best when it uses the reader's own vocabulary rather than generic IT advice.

Examples: Source 1

They predict that SMBs will increasingly invest in backup and disaster recovery.

• Their argument: basic file backups are not enough — businesses need full continuity, including offsite or offline backups that ransomware cannot encrypt and recovery playbooks that have actually been tested.
• They compare that spending to buying insurance, noting that many small firms could not survive an extended outage, and offer employee scam-testing training and a review of existing backup and recovery plans to readers who message them.

Opens with a cost figure and a provocative question, defines the risk in business terms, names specific measures, and offers a concrete next step.

Before using the $120,000-to-$1.2 million range as a statistic, ask for its source and date.

For brands planning a campaign

Suited to security, backup, or continuity vendors whose message centers on prevention and preparedness rather than product features. The dollar framing and tested-recovery angle offer reusable hooks for SMB-facing security content.

Examples: Source 1

They list the questions SMBs face — how to use AI responsibly, ethically, and legally — and point to concrete policy decisions, such as whether employees may put confidential data into a chatbot or how to use AI-generated content without infringing copyright.

• In their account, a framework should cover data privacy, decision transparency, and avoiding discrimination in hiring or lending decisions.
• They warn that without guardrails, SMBs risk regulatory breaches or lost customer trust, and recommend a simple plan endorsed by leadership and updated as laws change.

Reframes an enterprise topic for SMBs, then lists practical policy questions a small business can answer.

For campaigns that need implementation detail, ask for a template, checklist, or jurisdiction-specific legal guidance.

For brands planning a campaign

Useful for legal, compliance, or AI-platform partners targeting SMB decision-makers who need a plain-language starting point. Content can build on the post by supplying templates and policy examples.

Examples: Source 1

The post links to a one-page Prosper IT resource and invites readers to comment or send a direct message. Bagley speaks as part of the business but does not specify their role; ask whether they own, work for, or otherwise work with Prosper IT.

Original disclosure

At Prosper IT, we also run EOS.

View example

The posts present EOS as a method they use and adapt, not as a client or sponsor.

View example

Sandra Roberts frames quantum readiness and CISO priorities as board-level concerns, comparable to Bagley's SMB focus on cybersecurity and AI governance.

Sandra Roberts's material centers on enterprise CISO and board strategy and emerging quantum threats; Bagley's focuses on SMB owners and managed IT, using EOS planning language.

Read original · Original 2

Jurga's pay-or-not post parallels Bagley's continuity argument.

Jurga focuses on software supply chain and DevOps risk for an enterprise C-suite audience; Bagley writes for SMBs and ties recommendations to the EOS operating rhythm.

Read original · Original 2

Abtar's lists for pharmaceutical and IoT security and for financial services follow a comparable educational format.

Abtar organizes broad threat catalogs by regulated sector, with a legal and data-protection angle; Bagley writes shorter, SMB-focused posts that turn topics into planning, budgeting, or policy decisions.

Read original · Original 2

One post explains how a compromised package can reach CI/CD systems and expose deployment secrets, then points to controls such as version pinning, least-privilege access, credential rotation, and immutable backups.

• Another frames ransomware payment as a board-level decision and discusses isolated backups and tested recovery.
• These examples offer a more technical, DevOps-centered campaign than Matthew Bagley’s broader SMB technology-planning material.

The posts focus on software delivery security and ransomware, not on fitting technology decisions into an SMB’s operating rhythm.

• Bagley is the closer fit for an EOS-to-IT planning collaboration; Jurga is the sharper choice for a security-and-recovery campaign.
• Ask for audience reach and commercial terms.

Examples: Source 1 · Source 2

A post on CISO priorities connects security spending to business goals, reputation, privacy, AI, workforce awareness, and compliance.

• Another argues that boards and executive leaders should sustain quantum-readiness roadmaps across CISO turnover.
• That material may suit an executive-facing cybersecurity campaign better than Bagley’s practical SMB technology-planning examples.

Roberts’s posts focus on CISOs, boards, and enterprise security priorities, rather than Bagley’s specific SMB and EOS-to-technology-planning angle. Choose Roberts for leadership-level cybersecurity messaging, not as a like-for-like substitute for an SMB operating-process collaboration.

Examples: Source 1 · Source 2

The posts list risks and mitigations involving clinical-trial data, connected medical devices, financial-services cloud risk, account takeovers, and supply-chain attacks. Those examples offer more industry-specific subject matter than Bagley’s general SMB technology-planning posts.

Abtar’s posts offer broad lists of sector risks and suggested controls, rather than Bagley’s EOS-aligned planning framework or a comparable approach to SMB operating rhythms. Choose Abtar when industry threat coverage is central, and Bagley when the collaboration is about integrating technology decisions into SMB planning.

Examples: Source 1 · Source 2