Amanda DiCicco Stilman works on enterprise AI products and content focused on governance, compliance, and practical deployment in regulated industries. Their posts discuss AISquared products and frameworks for AI controls, data governance, and automating proposal work.
They are most useful for enterprise AI governance, compliance, and deployment content for regulated-industry buyers.
Best for
A regulated enterprise software brand wanting governance and compliance-ready AI deployment content for security, GRC, procurement buyers.
Not for
Short-form video reach or product demos for a large practitioner audience.
Key takeaways
A seven-layer AI controls framework names evidence to request from vendors.
Weak data lineage can make an accurate AI answer indefensible.
Bolt Instruct routes routine work to smaller models and adds guardrails.
Check first: Confirm audience demographics and recent results on comparable governance and compliance content.
Main ideas
Governance is what you can prove, not what you were promised · When AI gives a bad answer, look at the data layer, not the model · Open models as a procurement requirement, not a technical preference
Amanda DiCicco Stilman writes about enterprise AI, especially the governance and data controls needed to deploy it in regulated industries.
The posts connect practical implementation questions—where data comes from, how models are selected, and what safeguards are in place—to the evidence procurement teams, auditors and security leaders may need.
One lays out a seven-layer AI controls framework; another argues that weak data lineage can make an AI answer indefensible even when it is accurate.
The posts also cover AI product architecture and proposal automation, offering a practical starting point for readers interested in how enterprise AI moves from promise to deployable systems.
These posts turn broad claims about responsible or reliable AI into concrete questions buyers can investigate.
A governance guide names seven control layers and specifies what evidence to request from vendors.
A post on systems of record traces a bad AI answer to data lineage, access and conflicts between authoritative sources, rather than stopping at model performance.
A post about Bolt Instruct applies that deployment focus to product architecture: routing routine work to smaller models, adding input and output guardrails, and using open-model documentation to support traceability.
A shorter post on Sparx Proposal Intelligence shifts from governance analysis to a concise product explanation for bid teams.
Together, these examples offer specific ways to assess enterprise AI controls and deployment claims, while showing the posts extend beyond governance.
Amanda DiCicco Stilman writes about enterprise AI as something that has to survive regulated buying and review processes, not just perform well in a demo.
Read more
Their recurring positions: governance should be judged by evidence a reviewer can check rather than vendor assurances; bad AI output usually traces back to ungoverned source data; open models can be a procurement requirement rather than a technical preference; and the same problem-first, framework-led writing is applied to operational work such as bid and proposal response.
Governance is what you can prove, not what you were promised
The most detailed post argues that buyers — examiners, auditors, underwriters — will ask what an organisation can demonstrate about its AI, not what a vendor assured it.
Read more
The response is a seven-layer AI controls framework covering systems of record; connectivity and access control; data processing and context; workflow orchestration; policy and governance; delivery and embedding; and observability and continuous improvement.
For each layer, the guide sets out questions to put to a vendor, documentation to request, and answers that should make a buyer walk away.
The post argues that a governance platform proves its value by producing artefacts such as scoped credentials, tamper-evident logs, versioned policies and drift dashboards.
It presents the framework as vendor-neutral: something to apply to any vendor, including the author's own company.
The post connects the framework to concrete external standards and pressures: ISO/IEC 42001 readiness, what cyber insurers now ask about agentic AI, and where a control plane fits under the Federal Reserve's SR 26-2 model risk guidance. It ends with a vendor checklist for procurement or renewal calls.
When AI gives a bad answer, look at the data layer, not the model
A recurring argument: when a model produces a wrong output, the instinct is to blame the model, but the real problem usually sits one layer down, in the systems of record an enterprise has already decided to trust — ERP, CRM, HRIS, case management and data warehouses.
Read more
The post describes these as years of accumulated organisational truth that the business already runs on.
In regulated settings, the standard shifts from accuracy to provenance: an auditor wants to know where an answer came from.
If the AI draws on an ungoverned pipeline, the answer cannot be defended, so the deployment fails on defensibility rather than performance.
The stated remedy has three parts: documented lineage from output back to source, governed access designed in from the start, and a clear hierarchy for when systems disagree.
'An auditor doesn't just want an accurate answer. They want to know where it came from' — followed by three requirements a team can act on.
Open models as a procurement requirement, not a technical preference
In a product-architecture post aimed at regulated industries, the argument is that enterprises cannot deploy AI there without first clearing procurement, legal and compliance review, and that model openness is part of passing that review.
Read more
The product described, Bolt Instruct, is positioned as an orchestration layer that routes requests to the right model, enforces guardrails on inputs and outputs, detects PII and jailbreak attempts, and produces structured outputs for high-volume work such as retrieval-augmented generation.
Routine tasks go to smaller purpose-built models, with frontier models reserved for work that needs them.
Because Ai2 publishes Olmo's training data, code and architecture, the post argues that customers can trace what they are building on through compliance review.
The post claims the move cut the company's own infrastructure hosting costs by roughly half, with customers seeing similar savings. The performance-and-cost claim concerns the author's own employer's platform.
Applying the same logic to unglamorous operational work: bids and proposals
A shorter, more conversational post applies the same problem-first approach to revenue and bid teams rather than security leaders.
Read more
It describes responding to RFPs and ITBs as time-consuming, fragmented and reactive: teams miss relevant bids, chase low-probability opportunities and spend days drafting proposals from scratch.
The post presents Sparx Proposal Intelligence as covering bid discovery, win-probability scoring and proposal generation, so teams can focus on opportunities most likely to convert.
It closes by asking readers how they handle bids today.
The argument is compressed into a few sentences, followed by a direct question to the reader — a noticeably different register and audience from the governance posts.
A consistent method — and a tension between neutral guidance and product promotion
Across the posts, the structure repeats: a short problem statement, then a framework, list or architecture carrying the substance, followed by a link to a guide or product page and often a question to the reader.
Read more
The vocabulary stays rooted in enterprise buyers, compliance review and procurement. One post offers a framework to use on vendors including the author's own company, while others describe that company's products with concrete performance, cost and efficiency claims.
The governance guide is explicitly framed as vendor-neutral, with questions and evidence requests to apply to 'any AI governance vendor (including us)'. The platform and proposal posts, by contrast, read as product advocacy with numbers attached.
Start here to see the framework behind most of the creator's other posts and judge whether the compliance case rests on specifics or slogans.
Read more
This post introduces a guide built around a seven-layer AI controls framework: systems of record; connectivity and access control; data processing and context; workflow orchestration; policy and governance; delivery and embedding; and observability and continuous improvement.
For each layer, it promises questions to ask a vendor, evidence to request, and answers that should make a buyer walk away, plus a checklist for a procurement or renewal call.
It connects AI controls to ISO/IEC 42001 readiness, what cyber insurers now ask about agentic AI, and the Fed's SR 26-2 model risk guidance.
Its central argument: a governance platform proves its value with evidence — scoped credentials, tamper-evident logs, versioned policies, drift dashboards — not claims that AI is safe.
For brands planning a campaign
A governance, GRC, or AI assurance vendor could commission a decision framework buyers can take into a procurement conversation, applying the same layer-by-layer scrutiny to the vendor's platform. It suits content that must stand up to an auditor's or examiner's questions, not just make a marketing-page claim.
Shows whether the creator can explain how AI systems are assembled and run, not just how they are governed on paper.
Read more
A product-architecture post for enterprises in regulated industries, where AI must clear procurement, legal, and compliance review before deployment.
Bolt Instruct is described as the orchestration layer inside UNIFI, an enterprise AI platform: it routes requests to the right model, enforces guardrails on inputs and outputs, detects PII and jailbreak attempts, and generates structured outputs for high-volume workflows such as RAG and document processing.
Routine tasks go to smaller purpose-built models, while frontier models are reserved for work that needs them.
It was built on Ai2's Olmo open models because the post frames model openness as a procurement requirement in regulated industries: published training data, code, and architecture let customers trace what they are running.
The post claims the migration cut the author's own infrastructure hosting costs by roughly 50%, with customers seeing similar savings.
For brands planning a campaign
Useful for infrastructure, model-provider, or platform brands seeking an architecture and cost walkthrough rather than a policy essay. The cost claim and routing logic give a sponsored piece concrete numbers and trade-offs to test; the openness angle suits vendors whose buying case rests on compliance traceability.
Read this for the recurring 'defensibility, not performance' argument and to see how the post makes a technical claim specific enough to act on.
Read more
The clearest statement of the data argument.
When a model produces a bad output, the instinct is to blame the model, the post says, but the problem usually sits a layer down: nobody solved how to get clean, current, authoritative data from the systems that hold it.
It names those systems of record — ERP, CRM, HRIS, case management, data warehouses — and describes them as years of accumulated organisational truth the business already runs on.
In regulated environments, the bar shifts from accuracy to provenance: an auditor wants to know where an answer came from; if AI is pulling from an ungoverned pipeline, that answer does not exist.
Three requirements follow: documented data lineage from output back to source, governed access built in from the start, and a clear hierarchy for when systems disagree.
For brands planning a campaign
Directly useful for data lineage, master data management, data catalog, or integration vendors: the post gives buyers a reason to put governance work before model choice. It also offers a strong angle for reframing a failed AI pilot as a data problem rather than a model problem.
Open this one to see the creator's range: they write compact, practical automation posts for operational audiences as well as argumentative governance pieces.
Read more
The shortest and most product-specific post in the set, aimed at teams answering RFPs and ITBs.
It describes the work as time-consuming, fragmented, and reactive: teams miss relevant bids, chase low-probability opportunities, and spend days drafting proposals from scratch.
AISquared's Sparx Proposal Intelligence is presented as automating the whole chain — bid discovery, win probability scoring, and proposal generation — so teams can focus on the opportunities most likely to convert.
It closes by asking readers how they handle bids today.
For brands planning a campaign
Suits procurement technology, bid-management, or sales-automation brands. It uses a shorter, more conversational register than the governance posts and addresses a different audience — revenue and bid teams rather than security and GRC leaders — a useful distinction when matching a creator to a brief aimed at non-technical buyers.
Compliance-ready deployment and open models as procurement requirements1
Automating RFP and bid response work1
AI governance as evidence an auditor can check
The longest post introduces The CISO's AI Governance Guide and a seven-layer AI Controls Framework for security and GRC leaders: systems of record; connectivity and access control; data processing and context; workflow orchestration; policy and governance; delivery and embedding; observability and continuous improvement.
Read more
For each layer, the guide lists questions to ask a vendor, information to request and answers that should make a buyer walk away.
The post presents the framework as vendor-neutral, saying it can also be applied to their own employer.
It argues that a governance platform proves itself by producing scoped credentials, tamper-evident logs, versioned policies and drift dashboards—not by claiming AI is safe.
It also ties the material to ISO/IEC 42001 readiness, what cyber insurers now ask about agentic AI, and where a control plane fits under the Federal Reserve's SR 26-2 model risk guidance.
A vendor checklist is available for procurement or renewal calls.
Publishes a numbered, layered framework with questions and evidence requests for each layer, then connects it to named external standards and a downloadable guide.
For brands planning a campaign
A regulated enterprise software company can build an engagement around a checklist, framework explainer or procurement-question series rather than a product pitch. The questions-to-ask and evidence-to-request framing helps a brand serve GRC and security buyers, while Amanda DiCicco Stilman’s posts show they can turn a framework into a downloadable asset with a call to action.
A recurring argument in the corpus: when a model produces a bad answer, the instinct is to blame the model, but the problem usually sits one layer down in Systems of Record—the authoritative sources an enterprise already trusts, such as ERP, CRM, HRIS, case management and data warehouses.
Read more
In regulated environments, the post argues, the standard is stricter: auditors want to know where an answer came from, so an ungoverned pipeline makes a deployment fail on defensibility rather than performance. The proposed fix has three parts: documented data lineage from output back to source, governed access designed in from the start, and a clear hierarchy for when systems disagree.
Opens with a familiar complaint about AI quality, redirects attention to the data layer, then offers three concrete requirements buyers can act on.
The same text appears in two of the five posts, so the theme rests on one piece of writing, not two independent statements.
For brands planning a campaign
This is a strong opening for a data-governance, integration, ERP/CRM or master-data vendor. The claim that deployments fail on defensibility, not performance, gives a brand a way to discuss governance and lineage with buyers disappointed by model-led pitches.
Compliance-ready deployment and open models as procurement requirements
A product post describes Bolt Instruct, an orchestration layer inside the UNIFI enterprise AI platform, as routing requests to the right model, enforcing guardrails on inputs and outputs, detecting PII and jailbreak attempts, and producing structured outputs for high-volume work such as retrieval-augmented generation and document processing.
Read more
The architecture sends routine tasks to smaller, purpose-built models and reserves larger frontier models for work that needs them.
The post says Bolt Instruct was built on Olmo, the Ai2 family of fully open language models, arguing that openness is a procurement requirement in regulated industries, not a technical preference: published training data, code and architecture let customers trace what they are building on through compliance review.
It also claims the migration cut the company's own infrastructure hosting costs by roughly half, with customers seeing similar savings.
For brands planning a campaign
A model provider, infrastructure vendor or platform in a regulated sector can co-create content on open-model traceability, procurement review and model-routing cost control. Amanda DiCicco Stilman pairs architectural explanations with concrete cost or compliance outcomes, a format a brand can support with real numbers.
A post describes RFP and ITB responses as time-consuming, fragmented and reactive: teams miss relevant bids, pursue low-probability opportunities and spend days drafting from scratch.
Read more
It presents AISquared's Sparx Proposal Intelligence as covering bid discovery, win-probability scoring and proposal generation, freeing teams to focus on opportunities most likely to convert. The post closes by asking readers how they handle bids today.
For brands planning a campaign
Suited to procurement, legal-operations, proposal-management or sales-tech brands. The closing question offers a ready-made engagement hook, and the problem-first framing could anchor a sponsored discussion about bid qualification or proposal quality.
Across the posts, the pattern is consistent: a short problem statement opens; a framework, list or architecture carries the substance; and a guide or product link and a question to the reader close it.
Read more
The writing uses the vocabulary of enterprise buyers, compliance review and procurement rather than creator commentary. The same argument can recur across posts in near-identical wording.
For brands planning a campaign
Expect an educational, framework-led treatment anchored to a named asset, not a personality-driven or anecdotal collaboration. The most useful briefing includes a real problem statement, a concrete framework or checklist, and one defensible number or standard.
Amanda DiCicco Stilman posts as part of AISquared, the enterprise AI company behind the UNIFI platform.
Read more
Their posts promote AISquared's governance, data, and proposal-automation products rather than outside sponsorships: the CISO's AI Governance Guide and AI Controls Framework, the UNIFI platform with its Bolt Instruct orchestration layer, and Sparx Proposal Intelligence.
The only other company named in a working relationship is Ai2, whose open Olmo language models AISquared builds on.
Ask for their specific job title.
AISquared
Employment
Posts speak from inside the company — “our enterprise AI platform,” “our own infrastructure hosting costs,” “we wrote The CISO's AI Governance Guide” — and describe its products: UNIFI (enterprise AI platform), Bolt Instruct (orchestration layer routing requests, enforcing guardrails, detecting PII and jailbreak attempts), the AI Controls Framework, and Sparx Proposal Intelligence for bid discovery, win-probability scoring, and proposal generation.
Bolt Instruct was built on Olmo, Ai2's family of fully open language models.
Read more
Ai2 publishes the full model flow, including training data, code, and architectural blueprints — presented as a procurement and compliance-review advantage for regulated industries.
Amanda DiCicco Stilman’s writing is a useful starting point if you work in a regulated enterprise and need a way to discuss AI that can withstand procurement, legal and audit review.
Read more
Start with the long governance post, which sets out a seven-layer controls framework and the questions and evidence to request from any vendor; it’s the clearest example of how they structure an argument.
Then follow the thread through the shorter piece on systems of record, which argues that a bad AI answer usually traces back to ungoverned source data rather than the model, and the post on an enterprise AI orchestration layer built on fully open models, which treats model openness as a procurement requirement.
The RFP and bid-automation post applies the same problem-first method to less glamorous operational work and a different buying audience.
Read the posts as a set for the through-line—evidence over assurances, data before models—and expect a framework, checklist or architecture rather than personal commentary.
Both make the same core argument from different seats: enterprise AI fails without clean, governed data underneath it, and integration holds the stack together.
Read more
They write for enterprise architects and IT leaders in the vocabulary of platforms, metadata, lineage and audit-ready decisions, and explain a vendor stack layer by layer.
Where Amanda DiCicco Stilman offers a vendor-neutral framework auditors can apply, Akhilesh Perla writes from inside a Salesforce and MuleSoft practice, reading platform news and acquisitions through the lens of an AI operating system and closing with a direct commercial call to action. Their reference points are vendor roadmaps and integration layers, rather than control questions and evidence requests.
Both take a compliance process founders find opaque and explain it plainly: what the review consists of, what evidence must exist before someone signs off, and why an audit validates work already done rather than replacing it.
Read more
They write problem-first, use concrete counts and examples, and treat defensibility—not passing the exercise—as the point.
Jacob Riff focuses on SOC 2 attestation for small teams, covering policies, controls, penetration tests and observation windows.
He is candid about when a platform is unnecessary.
Amanda DiCicco Stilman focuses on AI governance and deployment inside larger regulated enterprises, addressing security and GRC leaders rather than startup founders, with AI controls—not security controls—as the unit of analysis.
Both argue that orchestration and governance—not model quality—are the real bottlenecks once AI reaches production, and identify the same hard problems: permissions, governance, observability and recovery.
Read more
They use a layered stack diagram to explain where value sits and write for enterprise operators.
Gaurav Bhattacharya targets go-to-market and revenue operations, arguing that AI has commoditised outbound execution and that trust and distribution now decide who wins.
His frame is the agentic digital worker stack.
Amanda DiCicco Stilman focuses on regulated-industry procurement and audit evidence, addressing compliance and security reviewers rather than sales and growth teams.
The strongest fit is subject matter: posts cover AI governance, an AI controls framework, enterprise data readiness, and proposal automation for regulated industries—the same territory as a campaign on compliance-ready AI deployment.
Read more
The only measured audience figure is a LinkedIn follower count of 1,630, observed on 9 October 2026.
Treat a first placement as a test of topic credibility, with reach measured after publication, rather than as a targeted reach buy.
The posts read as vendor communication: a CISO-facing AI governance guide, a seven-layer AI controls framework, and product explainers for Bolt Instruct and Sparx Proposal Intelligence.
That suggests an audience following a company’s governance point of view, rather than an independent commentator’s—a distinction that matters when buying a point of view, not just a follower number.
Before booking, ask for recent results on comparable governance and compliance deployment content, including impressions, engagement, and any click or conversion data.
Also ask for audience survey results or documented demographic data on job function, seniority, industry, and geography.
Without those, audience composition remains unverified, so set expectations around subject-matter reach rather than verified practitioner reach.
The posts do not say that Amanda DiCicco Stilman offers creator partnerships or sponsorships.
Read more
All five promote employer-side enterprise AI products and frameworks: Bolt Instruct inside the UNIFI platform, the seven-layer AI Controls Framework and The CISO's AI Governance Guide, and Sparx Proposal Intelligence.
They include no sponsored-content disclosure, rate card, deliverable or format specification, audience or performance figures, or terms of engagement.
Brands planning an AI-governance and compliance-ready deployment campaign should treat this as an employee-advocacy and thought-leadership channel, not a standing paid-creator inventory, and expect commercial conversations to go through the employer organization rather than an independent creator deal.
Ask the employer whether it offers an official partnership route; the posts provide no inquiry link, and the general homepage is not a substitute.
Need A: a regulated enterprise software company wants to commission a content engagement on AI governance and compliance-ready AI deployment, aimed at security, GRC, and procurement buyers.
Read more
This is a strong fit, for specific reasons.
The subject matter matches the posts post for post.
The CISO's AI Governance Guide supplies a seven-layer AI controls framework, with questions to ask a vendor, proof to request, and answers that should make a buyer walk away at each layer.
It connects the framework to ISO/IEC 42001 readiness, what cyber insurers now ask about agentic AI, and where a control plane fits under the Federal Reserve's SR 26-2 model risk guidance.
The Systems of Record post makes the defensibility argument compliance buyers need: an auditor wants to know where an answer came from, and an ungoverned pipeline cannot produce that answer.
The Bolt Instruct post covers the deployment side, including model routing, input and output guardrails, PII and jailbreak detection, and structured outputs for high-volume work.
It also claims that migrating cut infrastructure hosting costs by roughly half.
The format fits, too.
Posts open with a short problem statement, develop the substance through a framework, list, or architecture, then close with a link to a guide or product page and a question.
A brand seeking a checklist, framework explainer, or procurement-question series rather than a personality-led pitch can commission that format.
The posts also anchor claims to named external standards, a register suited to regulated buyers.
Three constraints belong in the campaign plan.
The posts do not describe a sponsorship offer, rate card, deliverable specification, or sponsorship disclosure, and no partnership inquiry route is published.
They read as employer-side enterprise AI marketing, so expect the commercial conversation to go through the employer organization and plan for an employee-advocacy or co-authored arrangement rather than an independent creator placement.
The only measured audience figure is 1,630 LinkedIn followers, observed on 9 October 2026; demographic, engagement, and click data are not published.
Scope the placement as subject-matter reach, not a targeted buy, and ask for post-level performance on comparable governance and compliance topics before committing.
When to choose a specialist
Need B: a developer-tools or B2B software brand wants short-form video reach, commissioning two or three short videos that demonstrate a product, with a target of verifiable reach into a large practitioner audience.
Read more
This is a poor fit based on the available posts.
They are written LinkedIn posts only, with no video, transcript, or other format to assess, so they offer no basis for committing to a visual or on-camera deliverable.
Nor do the audience figures support a reach target: 1,630 LinkedIn followers, no engagement breakdown, no geography, no job function or seniority data, and no platform demographic data.
Those figures cannot verify measurable reach into a large practitioner audience; follower count is the only measured figure available.
The writing also offers a narrow base for a multi-post campaign.
The structure repeats closely: problem statement, framework, product link, closing question.
Two of the five posts carry identical body text, leaving four distinct pieces of writing.
The tone is an enterprise-vendor argument for security, GRC, and procurement readers, rather than the demonstration-and-personality register short-form video usually needs.
There is no published commercial format to price or schedule a video commission against: the posts provide no rate card, deliverable specification, sponsor policy, or inquiry route.
Before reconsidering, ask for actual video or on-camera work, engagement and audience-composition data for the channels in question, and a sponsorship policy or format list.
A worked campaign example
A worked angle for the campaign aimed at security, GRC, and procurement buyers.
Campaign: "Questions that survive the audit" — a three-post LinkedIn series plus one downloadable checklist, built on the layer-by-layer structure of the CISO governance post.
Post 1 turns the seven layers — systems of record; connectivity and access control; data processing and context; workflow orchestration; policy and governance; delivery and embedding; observability and continuous improvement — into questions a buyer can ask any vendor, including the sponsoring brand, with proof to request beside each one. Its payload is the walk-away answer for each layer, making it useful in a real procurement call rather than just a marketing read.
Post 2 takes one layer and traces an answer to its source, following the data-lineage argument: where the number came from, who governs access to it, and what happens when two systems of record disagree. It demonstrates provenance rather than simply asserting accuracy, which gives it relevance to compliance buyers.
Post 3 covers architecture and cost: routing routine work to smaller models and reserving frontier capacity for the rest, guardrails on inputs and outputs, and how open-model provenance helps a buyer clear compliance review.
It needs one real number from the sponsor's own deployment, as the posts do when citing a roughly 50% hosting-cost reduction.
The sponsor must be willing to defend that number publicly.
The downloadable asset is the checklist, formatted for a procurement or renewal conversation and designed to be completed against two vendors side by side.
The brand must supply a named accountable author or reviewer, one honest deployment number, the named standards that actually apply to its own controls, and a truthful answer to the walk-away questions in post 1. A sponsor unwilling to answer its own checklist should expect the audience to notice.
Success means a security or GRC lead runs the checklist against the sponsor and one competing vendor, then can explain the choice from the information collected. Test that reader task before publication.
Before agreeing on scope, confirm the commercial route through the employer organization, since no partnership offer or inquiry path is published. Request post-level performance on comparable governance topics and any audience-composition data.
Akhilesh Perla is the stronger choice for a campaign about the data-governance layer underneath AI deployment, rather than a framework layered on top.
Read more
Both posts argue that the problem is the data, not the model: fragmented systems, untrusted or poorly governed data, and AI that works in demos but collapses in real workflows.
The work gets concrete about the stack—MuleSoft for integration, Informatica for data quality and governance, Agentforce for execution—and what buyers get from it: trusted data by default, metadata and lineage across the enterprise, and agents that start workflows and enforce policy as they act.
A sponsor commissioning content on lineage, master data, and controlled access inside its own platform will find more architectural detail here than in a vendor-neutral controls checklist.
Published 19 November 2025 and 23 June 2026.
The reasoning centers on one vendor stack—Salesforce with MuleSoft and Informatica—and the later post closes with a practice pitch and direct-message invitation rather than a checklist readers can use.
A brief that needs named external standards, auditor-facing evidence, or questions buyers can put to any vendor, including the sponsor, should ask for those explicitly.
The subject-matter fit is genuine, but the lens is platform integration, not compliance or procurement.
Jacob Riff is the better pick for a campaign about compliance readiness for a small team trying to get through an audit, rather than a large regulated enterprise buying an AI platform.
Read more
The two posts do what the Amanda DiCicco Stilman corpus does not: walk through a process end to end.
One covers the SOC 2 path in working detail—around twenty policies, roughly 100 to 150 controls, vendor due diligence, risk assessment, penetration testing, and the difference between a Type I report covering a single day and a Type II run over a three-to-six-month observation window.
The other meets the strongest objection head-on—that a compliance platform is a waste of money—and concedes that a spreadsheet and a shared drive can get an attestation.
Published 20 August 2026 and 6 August 2026.
These are security-compliance posts about SOC 2 evidence and audit mechanics, not AI governance: neither names AI controls, model-risk guidance, or the questions insurers now ask about agentic AI.
The voice is a founder writing about a product in the same category, so a sponsor would be buying practitioner candor rather than neutral AI-governance analysis.
That willingness to concede the counterargument also makes the posts useful as content.
Gaurav Bhattacharya fits a campaign focused on deploying AI inside production workflows rather than governing it for an audit.
Read more
The stronger post names the hard problems directly—orchestration, reliability, memory, permissions, governance, recovery systems, observability, and trust—and argues that enterprise workflows are limited by orchestration, not intelligence, before sketching a signals-to-reasoning-to-action-to-human-oversight stack.
The other makes a distribution argument about AI commoditizing execution.
For a sponsor seeking content on what actually breaks when agents run in production, that operational framing sits closer to engineering reality than a controls framework.
Published 18 May 2026 and 22 May 2026.
Governance appears as one item in a longer operational list, with no named standards, auditor evidence, or procurement-facing detail.
The primary frame is go-to-market and revenue operations rather than regulated-industry compliance, and one post ends by pointing readers to a whitepaper, giving the thought leadership a funnel behind it.
Buyers who need material a security, GRC, or procurement reader can take into a review call should ask for it explicitly; the AI-governance angle of the Amanda DiCicco Stilman posts offers more usable content.
This page draws on five LinkedIn posts published by Amanda DiCicco Stilman's account, read in full.
Two carry identical body text, so four distinct pieces of writing inform it: a seven-layer AI controls framework with a CISO guide, a post on enterprise data and systems of record, a post on an enterprise AI orchestration layer built on open models, and a post on RFP and bid automation.
The posts have no publication dates, so they cannot be placed in sequence and no change over time is established.
The posts also included one follower count observed on 9 October 2026.
Claims about employers, products, and external standards come from the posts' own text; statements about Stilman's role, credentials, or commercial terms were not verified beyond that writing and are not asserted here.
The similar-creators section compares LinkedIn posts from three other creators against the same subject matter.
Gaps left open rather than filled: a stated job title, post-level engagement or audience-composition data, and any sponsorship, rate card, or partnership inquiry route.
None appeared in the posts here, and none of them should be assumed from this page.