Results
What the content did for the business.
Built content operations, an AEO/GEO strategy and weekly AI visibility reporting. Share of voice grew 37% week over week.
Launched an executive byline series in Entrepreneur, a resource library of customer stories and a nurture that hit a 33% open rate across 3,000 leads.
Wrote hundreds of stories on Apple's business, products and culture, including scoops, for an award-winning newsroom.
AI in my workflow
How I use AI to write, publish and measure content faster without losing the voice.
Set the AEO/GEO strategy and a distribution playbook for every launch, then reported weekly on brand visibility and share of voice in AI answers.
Used AI-assisted workflows to move from subject-matter interviews to SEO- and AEO-ready drafts, then edit for accuracy and voice.
Generated and tested variants of ads, landing pages and emails, and produced video with AI tools.
Customer stories
Case studies built from customer interviews, written for sales to use.
- Chalk · Why a fintech's ML team bought an AI infrastructure platform instead of building one
- Google Maps · How a grocery delivery startup sped up dispatch with Google Maps APIs (archived copy)
- Google for Work · Customer story for the Google Cloud blog
- Chalk · What AI agent teams asked us at the AI Conference
Executive thought leadership
Bylines I ghostwrote and placed for founders, CEOs and investors.
- Adweek · Ghostwritten for Peter Reinhardt, CEO, Segment
- TechCrunch · Ghostwritten for Chet Kapoor, CEO, Apigee
- TechCrunch · Ghostwritten for Andy Vitus, Scale Venture Partners
- Fast Company · Ghostwritten for Andre Durand, CEO, Ping Identity
- Fortune · Ghostwritten for Alex Bard, CEO, Campaign Monitor
- Forbes · Ghostwritten for Justin Shriber, LinkedIn
- Fortune · Ghostwritten for Amy Errett, CEO, Madison Reed
- Fortune · Ghostwritten for Rodney Rogers, CEO, Virtustream
- TechCrunch · Ghostwritten for Claire Hough, Udemy
- Ad Age · Ghostwritten for Rich Mintz, Blue State Digital
- Adweek · Ghostwritten for Penry Price, LinkedIn
- How I Overcame First-Time Founder AnxietyEntrepreneur · Ghostwritten for Kristel Kruustük, CEO, Testlio. Picked up by Inc.
Security and compliance writing
Click a title to read the full piece.
Why CrowdStrike Insurance Claims Are Under Intense ScrutinyRead sample
Written for Koop, an insurance and SOC 2 platform, within days of the CrowdStrike outage.
Companies are still reeling from CrowdStrike's errant software patch that caused millions of Windows systems to crash. Thankfully most affected organizations are back online as attention turns to mitigating the costs of extended downtime.
Many teams will try to lean on their cyber liability insurance to cover claims and costs from this incident. There's surface-level logic. CrowdStrike is a cybersecurity company, so one could argue that any claims resulting from its mistakes are in effect cybersecurity claims. There's an important wrinkle in this story, though, that underscores why businesses need a comprehensive suite of insurance coverage instead of over-relying on a single policy.
Understanding cyber liability limits
Plenty of technology SMEs should consider cyber liability insurance, but fewer know its coverage limits and definitions. Cyber liability coverage is most applicable when companies face an external cyberattack (a denial of service attack, for example) or when external parties access secured customer data. These attacks are common and underscore the need for tech companies to adopt robust security postures and achieve standardized certifications like SOC 2 Type I.
The challenge is that CrowdStrike has said this incident was not the result of a cyberattack, but rather a software update that contained a bug. In practice this means insurers are likely to deny a large swath of cybersecurity claims stemming from CrowdStrike's update because no cybersecurity incident actually took place. Instead, companies with errors & omissions and especially business interruption insurance will see the most benefit from covered claims.
Beating business interruption
Business interruption insurance, which is more agnostic to the cause of damages than cyber liability, will provide the most coverage for those affected. Commonly covered scenarios include natural disasters, utility outages, equipment breakdown, government-mandated closures and supply chain disruptions.
While obviously not a natural disaster, many teams will receive claims benefits from interruption insurance with clauses for utility outages, equipment breakdown, or supply chain disruptions.
Mitigating future outages
If the CrowdStrike debacle tells us anything, it's that companies need the right suite of coverage policies as opposed to the right single policy. General liability and even cyber liability policies will come up short in scenarios like this one, where the incident was caused by error rather than a third-party attack.
The Justice Department Just Sued Georgia Tech for Alleged Compliance FailuresRead sample
Written for Koop to tie a federal compliance lawsuit to SOC 2 risk for startups.
Compliance gets a bad rap as a cost center, but a leading public research university might now be wishing it had made the investment anyway.
The Georgia Institute of Technology (which we Atlantans call Georgia Tech, or just "Tech") is being sued by the U.S. Department of Justice for misrepresenting its compliance controls.
Misrepresenting endpoints and controls
As a Department of Defense contract awardee, Georgia Tech was required to adhere to NIST 800-171 cybersecurity standards. Adherence to additional cybersecurity rules is extremely common for organizations, public or private, that work with Uncle Sam.
The DoJ essentially makes two claims: that Georgia Tech misrepresented its endpoints (read: potential vulnerabilities), and that it failed to implement required security controls, including fairly basic ones like installing anti-malware software on its systems.
Beyond public sector risk
The risk of litigation is just as real for private companies that skip compliance and business insurance as it is for public research universities. When customers include compliance controls as a prerequisite to doing business, they're not suggestions; they're requirements for the partnership. Often those requirements are as straightforward as carrying comprehensive business insurance and adhering to SOC 2 Type I controls.
The IAM Product Checklist: 5 Things Cloud Security Engineers Need to Look ForRead sample
Unpublished spec sample for a cloud identity and access startup.
We've all been there as developers: stuck troubleshooting an on-call incident, or just trying to do our jobs without the permissions we need. Managing cloud entitlements is a frustrating problem that feels like it should have been solved by now.
Despite advances in cloud security tooling, costly breaches like Uber's and T-Mobile's underscore the growing attack surface companies face. That's why choosing the right identity and access management (IAM) partner has become a P0 initiative for developers. Here are five preventative capabilities cloud security engineers should look for in an IAM product.
- Role-based access control. Define permissions by role so users only have what they need to do their jobs.
- Least privilege. Grant only the permissions a job requires, reducing the risk of unauthorized access to sensitive data.
- Auditing. Track user activity in the cloud so engineers can see who has access to what, and what they're doing with it.
- Automated provisioning and deprovisioning. Create and remove accounts and permissions automatically, so access exists only when it's needed.
- Centralized management. Manage IAM policies from one place instead of logging into several tools.
Ease of use and scalability are critical to long-term adoption, and the best IAM tools integrate with the rest of the security stack. A well-integrated solution reduces complexity, improves visibility, automates provisioning and supports certifications like SOC 2.