Akhilesh Perla writes about Salesforce and MuleSoft integration, enterprise AI, and AI governance. Their posts describe work at NexGen Architects and the Hapie AI project.
Akhilesh Perla is most useful for practitioner content on Salesforce and MuleSoft integration, enterprise AI, and AI governance.
Best for
A B2B enterprise software consultancy or integration platform vendor targeting enterprise architects and IT leaders.
Not for
Broad consumer campaigns or standalone AI copilot vendors seeking neutral product reviews and guaranteed placement.
Key takeaways
Enterprise AI is decided by the layers underneath it, not by the assistant on top.
Salesforce's buying spree is an architecture map, not a CRM feature list.
Governance means answering for the decision, not passing a compliance check.
Check first: Confirm follower demographics and which topics generated engagement from people with buying influence.
Main ideas
Enterprise AI is decided by the layers underneath it, not by the assistant on top · Salesforce's buying spree is an architecture map, not a CRM feature list · Integration is the constraint that decides whether any of the rest works
Akhilesh Perla writes about Salesforce’s evolution beyond CRM: connecting systems and governed data to AI that can act inside business workflows.
The posts link that architecture discussion to AI accountability, including a public-sector example involving HMRC and Hapie AI.
Follow them for a practitioner’s perspective on enterprise integration, Salesforce’s evolving platform, and the controls needed when AI takes action.
Across three posts, Perla connects product and business changes to practical architecture questions.
One maps MuleSoft, Informatica, and Agentforce to integration, data governance, and AI execution; another explains why enterprise architects may need to rethink Salesforce’s role as its platform expands.
The HMRC post shifts from capability to accountability, describing named approval gates, an append-only record, and customer-controlled audit trails as safeguards for high-stakes AI.
Together, the posts help readers assess how enterprise AI could operate—and who should answer for its decisions.
Akhilesh Perla writes for enterprise architects and IT leaders, with one argument running through their work: enterprise AI is decided by the layers underneath it.
Read more
Integration, governed data and accountable execution have to work as one system before AI can safely act inside a business.
They apply that frame to Salesforce, reading the company's acquisitions as the construction of an AI operating system rather than a CRM feature list, and repeatedly land on the same conclusion: the integration layer makes or breaks the rest.
Their governance position follows from the same starting point: at the scale of a national tax authority, the question is who answers for an automated decision.
Enterprise AI is decided by the layers underneath it, not by the assistant on top
Perla's central argument is that companies have been buying AI without fixing the hard problems underneath it.
Read more
Most organisations, in their account, struggle with fragmented systems, untrusted or poorly governed data, and AI that works in demonstrations but collapses in real workflows.
They keep returning to the stack: integration, data governance and quality, and autonomous execution, working as one system rather than as separate tools.
Their distinction is that real enterprise AI is not chatbots or copilots, but AI that can reason, act and take responsibility across business processes safely.
One post maps the responsibilities directly: MuleSoft for integration, Informatica for data governance and quality, and Agentforce for autonomous execution. It then lists the consequences for a 2026 roadmap: every event, signal, record and workflow becomes machine-readable and immediately actionable; governance, lineage, MDM and observability are applied before AI touches the data; agents can start workflows, update systems, trigger transactions and enforce policy as they act; and a single metadata layer spans APIs, data lineage, relationships, rules and identity.
Salesforce's buying spree is an architecture map, not a CRM feature list
Perla reads Salesforce's acquisitions as evidence that the company has been rebuilding itself underneath the CRM label.
Read more
They assign each deal a job in the stack rather than treating it as a product announcement, and conclude that none are CRM features — each is a layer of an AI operating system. Their method is to analyse public company announcements and work out what the spending implies for the people who have to integrate and govern the result.
One post puts the tally past $11 billion: Informatica ($8B), because AI is useless without clean, governed, enterprise-scale data, so the data layer came first; Fin ($3.6B), because autonomous customer service resolution is the flagship Agentforce use case; Contentful, because AI-assembled content experiences need a headless content layer rather than a CRM; and m3ter, because once every agent call, API hit and workflow run becomes a billable interaction, the platform needs native metering and billing. Perla concludes that all of these have to be connected, making the integration layer that holds them together more important than ever.
Integration is the constraint that decides whether any of the rest works
Perla's most consistent argument, which aligns with the MuleSoft and Salesforce practice they say they run at NexGen Architects, is that integration is the practical bottleneck.
Read more
Clean data, governed agent access, billing infrastructure and content delivery are valuable only when wired together; separately, they are just more systems to reconcile. Perla warns against "integration spaghetti" and fragile automation, treating connectivity as the precondition for everything else on the roadmap rather than a later implementation detail.
In the Informatica post, the unified stack is presented as removing stitching and fragile automation so that every event and workflow becomes immediately actionable.
In the acquisition post, Perla makes the same point directly: the integration layer holding all of the acquisitions together is more important than ever.
The post closes by naming their practice and inviting enterprise architects to make contact, aligning the editorial argument with the commercial position.
Across the posts, the emphasis shifts but the claim does not: early framing presents integration as one of three layers, while later framing presents it as the layer that determines whether the other two deliver.
Governance means answering for the decision, not passing a compliance check
Perla's governance position starts from scale and consequence rather than regulation.
Read more
When an automated system handles a person's money, identity or case across tens of millions of people, the meaningful question is who answers for the decision.
The design answers they describe are a named human approval gate before any high-stakes action and an append-only record that keeps failures alongside wins.
They distinguish this from checkbox compliance, echoing their earlier claim that applying governance before AI touches data produces audit-ready decisions instead of hallucinations.
The HMRC post reports that Salesforce won a £2.4 billion, ten-year deal with the UK's tax office, potentially extending to 2041 if every extension is used, beating Pegasystems in a decision where quality counted for seventy percent and price for ten percent.
From the contract terms — taxpayer records and cases, calls, messages, portals and campaigns, built-in analytics and AI — Perla draws practical implications: every call involves a real taxpayer's money, identity or case; automated decisions run far beyond one customer at a time; and someone will eventually have to answer for them.
They then describe the approach behind Hapie AI, which they say NexGen Architects builds around that question.
The governance argument develops from a general claim in the Informatica post — governance before AI touches data — into a concrete product position in the HMRC post.
That post moves from market analysis into a pitch for Hapie AI; the deal figures and the quality-versus-price weighting come from Perla's own post.
Buyers should ask for independent support for those figures and weightings.
Written for architects whose platform changed underneath them
Perla writes for enterprise architects and IT leaders who feel their implementation no longer matches what the vendor is selling.
Read more
Rather than opening with a product claim, the posts remove the pressure to have answers already — what a new product replaces or how it fits an existing contract.
The recurring format pairs a hook that contradicts the prevailing read with a numbered breakdown, a closing position and a next step.
The vocabulary assumes familiarity with Salesforce, MuleSoft and Agentforce rather than explaining them from scratch.
One post tells architects they do not need a clear answer on what Agentforce replaces in their stack, know how Fin fits existing service contracts, or pretend the platform they implemented two years ago still looks like what Salesforce sells today. It then explains what has happened to the platform and closes with a direct invitation to get in touch.
Shows how Akhilesh Perla frames Salesforce's AI stack: not as chatbots or copilots, but as integration, governed data, and autonomous execution working as one layer.
Read more
Start here for the core architecture argument that runs through the other posts.
Akhilesh Perla argues that enterprise AI efforts often fail because systems are fragmented, data is untrusted or poorly governed, and AI that works in demos breaks down in real workflows.
The post maps three layers: MuleSoft for integration, Informatica for data governance and quality, and Agentforce for autonomous execution.
It then outlines what this unlocks: a unified digital nervous system, trusted data before AI touches it, agents that can start workflows and update systems, a single metadata layer for explainable AI, and a composable enterprise.
The closing argument: this is not about CRM, integration, or analytics, but the architecture for autonomous enterprises.
For brands planning a campaign
A ready-made thought-leadership sample for a Salesforce or MuleSoft consultancy, this post turns a product acquisition into an enterprise architecture argument.
Its clear point of view could anchor a webinar, sponsored explainer, or partner briefing.
It also shows the vocabulary Akhilesh Perla uses — integration layer, governed data, metadata, autonomous execution — which a campaign should reuse rather than replace with generic AI language.
Shows why Akhilesh Perla thinks Salesforce's identity has outgrown CRM.
Read more
It is the clearest example of the commercial practice behind the commentary: they name NexGen Architects and invite enterprise architects and IT leaders to adapt.
The post opens by arguing that Salesforce stopped being a CRM a long time ago, though the label was never updated.
Akhilesh Perla addresses enterprise architects and IT leaders who feel their implementations are falling behind, telling them they do not need a ready answer for what Agentforce replaces or how Fin fits into existing service contracts.
They list more than $11 billion in acquisitions: Informatica ($8B), Fin ($3.6B), Contentful, and m3ter.
Each is framed as a layer of an AI operating system rather than a CRM feature: data governance, autonomous customer service, headless content, and metering and billing.
The post closes with their MuleSoft and Salesforce practice and an invitation to direct-message NexGen Architects.
For brands planning a campaign
The strongest commercial-fit piece in the set, it identifies a specific buyer — the enterprise architect or IT leader managing a platform that no longer matches its original label — and pairs the argument with a direct call to action for NexGen Architects. A partner campaign could use it as a template for practice-led content: name the buyer's discomfort, explain the acquisitions as one architectural shift, and offer a practical path rather than a product pitch.
Shows how Akhilesh Perla connects a major public-sector technology contract to AI governance.
Read more
Through Hapie AI, it highlights the accountability side of their work, not just Salesforce integration.
Akhilesh Perla reports that Salesforce won a £2.4 billion, ten-year deal with the UK's tax office, HMRC, with possible extensions to 2041.
The post says HMRC is buying one CRM platform for taxpayer records and cases, one system for calls, messages, portals, and campaigns, and built-in analytics and AI, while retaining the choice of where fraud checks and identity verification come from.
It notes that Salesforce beat Pegasystems and that quality counted for 70% of the decision, compared with 10% for price.
The post then turns to governance: every call handles a real taxpayer's money, identity, or case; automated decisions run at the scale of tens of millions of people; and someone has to answer for AI-driven decisions.
Akhilesh Perla says NexGen Architects builds Hapie AI around that question, with a named approval gate before high-stakes actions, an append-only record that includes failures and wins, and the customer's environment, data, and audit trail from day one.
For brands planning a campaign
This post offers a public-sector and AI-governance angle distinct from the Salesforce stack posts.
A campaign could use it to reach government, tax, or regulated-industry buyers who care less about agent hype and more about auditability.
It also features a concrete product, Hapie AI, and a governance framework — approval gate, append-only record, customer-owned audit trail — that could anchor a sponsored research piece or event session.
Salesforce as an enterprise AI operating system, not a CRM
Perla's core argument is that Salesforce has outgrown the CRM label and should be evaluated as an enterprise AI stack.
Read more
In one post, they divide the platform into three layers — MuleSoft for integration, Informatica for data governance and quality, and Agentforce for autonomous execution — and argue that serious enterprise AI depends on all three operating as one system rather than on chatbots or copilots. They then spell out five consequences for enterprise roadmaps: events, signals and workflows becoming machine-readable and immediately actionable; governance, lineage, MDM and observability applied before AI touches data; agents that start workflows, update systems, trigger transactions and enforce policy as they act; a single metadata layer spanning APIs, lineage, relationships, rules and identity; and a move toward AI that orchestrates processes across applications rather than a collection of apps.
For brands planning a campaign
A vendor selling any single layer of the enterprise AI stack — integration, data quality, agent tooling — can brief Perla on the consolidation argument and expect the piece to position its product inside a larger architecture rather than as a standalone tool. The angle that fits is "what this layer makes possible once the rest of the stack is in place."
Reading Salesforce's acquisition spree as an architecture map
Perla's posts frame Salesforce's roughly $11 billion-plus in recent acquisitions as a platform rebuild.
Read more
Each deal gets a functional role: Informatica ($8B) as the data layer AI needs before it can be useful, Fin ($3.6B) as autonomous service resolution, Contentful as a headless content layer for AI-assembled experiences, and m3ter as native metering and billing once agent calls and workflow runs become billable interactions. The conclusion: none of these are CRM features; each is a layer of an AI operating system.
Perla works from publicly announced deals, assigns each one a job in the stack, and reasons about what the pattern implies for the people who have to govern and integrate those systems. This is pattern analysis based on company announcements, not hands-on product testing.
For brands planning a campaign
This format suits a partner or reseller positioning around a shifting vendor platform: the creator supplies the interpretive frame, and the brand supplies the implementation detail. A brand can also extend the map with hands-on customer evidence; ask for that evidence if it is central to the campaign.
Integration as the layer that decides whether any of it works
Across the posts, Perla returns to integration as the practical constraint.
Read more
The Informatica post warns against "integration spaghetti" and fragile automation, arguing that clean data, governed agent access, billing infrastructure and content delivery only work when they are connected.
The acquisition post puts it more directly: the integration layer holding all of this together matters more than ever.
This is the argument they repeat most consistently, and it aligns with the MuleSoft and Salesforce practice they say they run at NexGen Architects.
For brands planning a campaign
This is the strongest fit for a campaign about integration platforms, because the creator's stated specialization and editorial argument point the same way. Expect work aimed at enterprise architects and IT leaders making platform decisions, not a general technology audience; include the implementation specifics the creator will want to reference.
AI governance framed as accountability, not compliance checkboxes
Perla's governance argument starts with a concrete case: Salesforce winning a £2.4 billion, ten-year deal with HMRC, potentially extending to 2041, beating Pegasystems in a decision where quality counted for seventy percent and price ten percent.
Read more
From there, they turn to the question they say matters at that scale — who answers for the decision when AI touches a taxpayer's money, identity or case.
They describe the approach behind Hapie AI as a named approval gate before high-stakes actions and an append-only record that includes failures alongside wins.
The same theme appears earlier in their claim that governance applied before AI touches data produces audit-ready decisions instead of hallucinations.
The deal figures and the quality-versus-price weighting come from Perla's own post and are not independently corroborated in the material reviewed here. The HMRC post also moves from market analysis into a direct pitch for Hapie AI, so a brand engaging on governance should expect the creator to have a product position of their own in the same space.
For brands planning a campaign
For a governance, audit or compliance vendor, the usable angle is decision accountability at scale — approval gates, audit trails and records that hold up years later — not a checkbox compliance pitch. The creator's position at Hapie AI means they are not a neutral commentator on governance tooling; a collaborating brand should complement that position or expect it to appear in the work.
Writing directly to architects and IT leaders who feel behind
One post opens by telling enterprise architects and IT leaders they do not need to apologize for a Salesforce implementation that feels behind the platform: they do not need a clear answer about what Agentforce replaces or how Fin fits existing service contracts, and they are not wrong to feel they are governing something that has fundamentally changed underneath them.
Read more
The post closes by naming the creator's practice and inviting readers to make contact. The format is consistent across all three posts: a hook that contradicts the prevailing read, followed by numbered or bulleted breakdowns, then a closing position and next step.
Contrarian framing followed by structured enumeration, ending with a stated point of view and an explicit business-development close. The explanations target practitioners who already know the products, so the vocabulary assumes familiarity with Salesforce, MuleSoft and Agentforce.
For brands planning a campaign
A brand hiring Perla gets analysis that ends in a business-development ask rather than neutral commentary, so frame the engagement as co-authored or sponsored practitioner content rather than an independent review. The direct-to-architect register also means the campaign should specify how technical the piece can be; material written for a general marketing audience will need adjustment.
The posts tie Akhilesh Perla to one business: NexGen Architects, where they say they run a MuleSoft and Salesforce practice.
Read more
A later post promotes Hapie AI, an AI governance product built at the firm, and links to hapie.ai.
The remaining posts cover Salesforce strategy and its MuleSoft, Informatica, and Agentforce layers, and describe their own practice as built on Salesforce and MuleSoft.
Ask about any sponsor, affiliate, client, or investment relationship.
NexGen Architects
Employment
In a post arguing that Salesforce has outgrown the CRM label, Akhilesh Perla writes, “I run a MuleSoft and Salesforce practice” and “This is what we do at NexGen Architects.”
Read more
A later post about the UK tax office deal adds, “At NexGen Architects, we build Hapie AI.” The posts describe the practice they run and the firm’s work, but don’t say whether they own the firm.
Original disclosure
I run a MuleSoft and Salesforce practice.
DM me if you're trying to get ahead and change with Salesforce instead of staying in the past.
Akhilesh Perla promotes Hapie AI as a product “we build” at NexGen Architects.
Read more
They describe an approval gate before high-stakes automated actions and an append-only record of what happened, and link to hapie.ai. Ask about their role in the product and any ownership stake.
All three posts cover Salesforce as a vendor they follow and build on: its Informatica acquisition and the integration, data-governance, and agent stack it creates; the £2.4 billion HMRC contract win over Pegasystems; and the argument that Salesforce is no longer just a CRM.
Read more
They also describe their own practice as a Salesforce practice.
MuleSoft features as the integration layer in their breakdown of the Salesforce stack and as half of the practice they say they run at NexGen Architects.
Akhilesh Perla writes about the layers beneath enterprise AI: integration, governed data, and accountable execution.
Read more
Start with the post pairing Salesforce with Informatica, which lays out a three-layer stack—MuleSoft for integration, Informatica for data governance and quality, and Agentforce for autonomous execution—then lists what that means for a 2026 roadmap: machine-readable workflows, governance applied before AI touches data, agents that can start processes and enforce policy, and a single metadata layer.
Next, read the post that treats Salesforce's acquisitions (Informatica, Fin, Contentful, m3ter) as an architecture map rather than a feature list; it argues that the integration layer holds the rest together.
For the governance thread, the HMRC post moves from a £2.4bn tax-office contract to who answers when automated decisions touch a person's money, identity, or case, and describes a named approval gate plus an append-only record.
Expect practitioner-level Salesforce and MuleSoft vocabulary, written analysis, and a practice-owner perspective throughout.
Both treat AI failures in large organisations as foundation problems, not model problems.
Read more
Bidgood argues that consumer-goods companies cannot deploy agents safely until commercial, supply-chain, and finance teams agree on shared definitions of customer, product, promotion, and margin. Perla makes the parallel case that integration and governed data must be in place before agents act inside a business.
Bidgood writes from the consumer-goods commercial and supply-chain side, using trade spend, forecasting, and retail-media examples to ask readers where their own definition gaps lie. Perla writes from the Salesforce platform side, using vendor acquisitions and integration tools such as MuleSoft, Informatica, and Agentforce to address enterprise architects and IT leaders.
Both argue that agentic AI changes the commercial shape of enterprise work, putting context, governance, and human oversight ahead of model choice.
Read more
Murali's argument for outcome-based consulting turns on who owns the workflow and whether the firm can influence the outcome. Perla asks who answers for an automated decision, calling for a named approval gate and an append-only record.
Murali centres on consulting contracts and delivery models—time-and-materials versus outcome-based pricing, and Intelligence-as-a-Service—and builds interview conversations with data-platform leaders. Perla focuses on the Salesforce integration and data-governance stack, publishing written platform analysis rather than interviews.
Both read Salesforce's product and acquisition moves as strategic architecture, not feature announcements.
Read more
Keenan treats ServiceNow's acquisition of Sweep and the AIforce launch as signals about metadata, agent governance, and delivery tooling. Perla reads Salesforce's Informatica, Fin, Contentful, and m3ter deals as layers of an AI operating system.
Keenan covers Salesforce DevOps and release and change management in a news-analysis style that tracks announcements and timelines. Perla covers integration and data governance inside the platform, from the perspective of a MuleSoft and Salesforce practice owner.
For a campaign aimed at CFOs in Salesforce and MuleSoft integration and AI governance, Akhilesh Perla’s posts support a placement on a LinkedIn personal profile with a stated 16,779 followers as of 11 October 2026.
Read more
The three posts reviewed target practitioner and buyer segments: one addresses enterprise architects and IT leaders on governance of a changing Salesforce estate; one closes with the MuleSoft Community hashtag and a MuleSoft and Salesforce practice; and one frames public-sector AI decisions at HMRC scale around audit trails and approval gates.
These topics show who the writing is pitched at, not who follows or reads it.
Ask for a LinkedIn follower demographics export covering seniority, industry, company size, function and location, plus an audience survey or existing first-party data on employers, occupations and budget-holding roles.
Also ask which of the three topics—platform convergence, integration architecture or public-sector AI governance—generated engagement from people with buying influence in the past twelve months, at comparable depth and format, rather than lifetime view totals.
LinkedIn followers
16,779
LinkedIn profile at linkedin.com/in/theakhi, as recorded in the account data with this review · 2026-10-11
The posts set out a consultancy route: Akhilesh Perla says they run a MuleSoft and Salesforce practice and invite IT leaders and enterprise architects to make direct contact when their Salesforce implementation is falling behind the platform.
Read more
A second route is Hapie AI, the AI governance product they describe building at NexGen Architects, for organisations where an automated decision is high-stakes enough that someone has to answer for it years later.
Both are engagement-shaped rather than media-shaped, so brands should plan for a scoped project or advisory relationship with negotiated terms, not a sponsored slot with published deliverables.
The MuleSoft Community tag and #HapieAI hashtag are topical signals only, and none of the three posts discloses a paid placement.
Ask directly whether paid placements are available and what terms apply.
Consultancy engagement through Akhilesh Perla’s MuleSoft and Salesforce practice
Buyer requirement
Come with a concrete implementation or integration problem rather than a general awareness goal: an Agentforce rollout to plan, an Informatica data-governance decision to make, or an integration layer that needs consolidating.
The posts direct prospective clients to message Akhilesh Perla.
Scope, fees, and start dates are not published; agree them in conversation before costing the plan.
AI governance advisory or deployment around Hapie AI
Buyer requirement
The posts describe a fit for workflows where automated decisions carry real weight and someone must be able to account for them later.
Akhilesh Perla presents three requirements as part of the offer: a named approval gate before any high-stakes action runs, an append-only record that includes failures alongside successes, and the buyer keeping their own environment, data, and audit trail from day one.
Buyers need a live system and data set they control, plus an internal owner who can sign off on the approval gate and accept the audit record.
Strong fit for a B2B enterprise software consultancy evaluating Akhilesh Perla for Salesforce and MuleSoft integration and AI governance thought leadership.
Read more
Campaign need: a MuleSoft and Salesforce integration platform vendor, or a consultancy selling into the same stack, wants partner content for enterprise architects and IT leaders at large organisations.
The buyer needs material explaining why integration and governed data must be in place before Agentforce-style automation, and a practitioner who can speak to teams governing a Salesforce estate that no longer matches its original CRM label.
Decision: choose Perla for a campaign aimed at enterprise architects and IT leaders, subject to negotiated terms.
Reasons: the posts consistently argue that the integration layer determines whether AI works.
The Informatica post warns against integration spaghetti and fragile automation; the acquisition post says the integration layer holding everything together matters more than ever.
The work is already written for the target buyer.
The acquisition post addresses enterprise architects and IT leaders who feel their implementation is falling behind, tells them they do not need a ready answer for what Agentforce replaces, and maps more than $11 billion in acquisitions to functional layers.
That offers a template for partner content: name the buyer's discomfort, explain the architectural shift, and offer a practical path.
The creator's stated specialisation matches the campaign need.
They say they run a MuleSoft and Salesforce practice at NexGen Architects, making this a practice-led rather than media-led engagement.
The governance material also suits regulated and public-sector campaigns: the HMRC post reports a GBP 2.4 billion, ten-year deal and asks who answers for automated decisions, supporting a governance, audit, or public-sector angle.
Planning: no rate card, media kit, deliverable list, timeline, or sponsorship policy is published; the only stated contact route is a direct message.
Audience information is limited to 16,779 LinkedIn followers as of 11 October 2026, with no breakdown by demographics, job titles, seniority, or employers, and no past campaign metrics.
The work analyses public company announcements rather than hands-on product testing, so the vendor should supply implementation specifics and technical review.
Agree scope, fees, timeline, review rights, and paid-partnership disclosure in writing before the campaign starts.
When to choose a specialist
Poor fit for a broad consumer or general-audience campaign, or for a standalone AI copilot or chatbot vendor seeking a neutral, independent product review and guaranteed sponsored placement.
Read more
Campaign need: a B2C app or broad technology brand wants a sponsored awareness post with verified audience demographics, a published rate card, and a neutral product review.
Decision: reject Perla for a campaign aimed at a broad consumer or general audience.
Reasons: the posts target practitioners, using terms such as MuleSoft, Informatica, Agentforce, metadata, lineage, MDM, and autonomous execution.
One explicitly addresses enterprise architects and IT leaders.
They show no consumer reach, general-interest topics, or track record of independent product testing.
The commercial route is also a mismatch: no post carries a payment disclosure, and there is no sponsor policy, media kit, rate card, or published partnership page.
The only stated route is a direct message, with scope, fees, and start dates left to conversation.
A guaranteed sponsored slot with published deliverables is therefore unverified.
The creator also has a position in AI governance through Hapie AI, whose product addresses the same question as governance-tooling vendors seeking neutral commentary.
The posts reason from publicly announced deals and platform acquisitions, not hands-on testing, so they cannot support an independent product review.
Audience information is insufficient to guarantee reach: the only measured figure is 16,779 LinkedIn followers as of 11 October 2026, with no breakdown by seniority, industry, company size, function, or location, and no past campaign engagement data.
The available work covers three posts, with no transcripts, longer articles, video, or lifetime archive.
For a campaign requiring verified decision-maker reach, neutral review, or a consumer audience, this creator is not the right fit.
A worked campaign example
Campaign angle for enterprise architects and IT leaders: The integration layer is the AI layer.
Goal: reach enterprise architects and IT leaders evaluating Agentforce, Informatica, and MuleSoft together, and give them a practical way to sequence integration and governance before automation.
Creator contribution: a long-form practitioner explainer built around Perla's existing architecture argument.
The posts support its central points: enterprise AI often fails because systems are fragmented, data is untrusted or poorly governed, and demos collapse in real workflows; MuleSoft brings integration, Informatica brings governed data, and Agentforce brings autonomous execution; the integration layer makes those parts work together.
A second piece can develop the governance angle from the HMRC post, asking who answers for an automated decision and using the approval gate, append-only record, and customer-owned audit trail as its discussion frame.
Brand contribution: the vendor supplies implementation specifics the creator does not have, such as a real integration pattern, a customer story with permission, benchmark or delivery data, and a technical reviewer. If the vendor sells a competing governance product, define boundaries with Hapie AI up front.
Deliverables: one sponsored long-form explainer, one practitioner webinar or recorded session with the creator and a vendor architect, and one short follow-up post pointing to a downloadable checklist for approval gates and audit trails. Publish the architecture explainer first, run the session second, and use the follow-up to answer questions raised.
Measurement: qualified conversations or demo requests from enterprise architects and IT leaders, session attendance and question quality, engagement from named target accounts, and follow-up content performance. Do not judge success by follower count alone.
Negotiation: no rate card, deliverable list, timeline, or sponsorship policy is published.
Agree scope, fees, dates, review rights, disclosure language, and asset ownership in writing before work begins.
Keep the creator's vocabulary rather than replacing it with generic AI language, and flag any vendor claim they cannot support from the posts.
Choose Mark Bidgood when the campaign focuses on consumer goods or CPG: trade promotion, retail media, or getting commercial, supply chain, and finance teams to agree on what product, customer, and margin mean before AI agents act on them.
Read more
The posts argue that AI does not remove fragmented definitions but scales them, and that the fix is a unified definition and a governed architecture across retail, supply chain, ERP, CRM, and trade systems. That suits a campaign aimed at CPG data and commercial leaders, or a buyer whose pilot lives in trade spend and forecasts rather than platform architecture.
The posts sit above the integration layer and do not cover MuleSoft, Informatica, or Salesforce architecture specifics.
For a campaign about sequencing integration and governed data inside a Salesforce estate, Akhilesh Perla's platform-level argument is more directly reusable.
Bidgood's advantage is the business-definition and CPG framing; the tradeoff is less depth on the tools named here.
Ask for examples of an integration practice if that capability is central to the campaign.
Choose Arvind Murali when the campaign is about how consulting and services work gets priced and contracted for agentic AI: outcome-based versus time-and-materials, hybrid commercial models, shared-risk managed services, and governance as an enabler of production AI.
Read more
The posts also use a conversational format: a shortcast interview with a named data-platform executive on context, governance, people, and purpose.
That suits a partner content piece built around a guest.
It fits a consultancy selling AI transformation services, or a campaign aimed at consulting and delivery leaders, better than one about platform architecture.
The posts focus on consulting economics and data-context foundations rather than Salesforce, MuleSoft, or Informatica integration mechanics.
The interview format also brings a third-party employer and guest into the asset, which affects sponsor boundaries.
For a buyer who needs the integration-layer argument aimed at enterprise architects, Akhilesh Perla's posts address that task more directly.
Ask for examples of integration work if that practice is central to the campaign.
Choose Vernon Keenan when the campaign focuses on Salesforce DevOps, release governance, or competitive positioning against ServiceNow: metadata visibility, dependency-resolved models of a Salesforce org, and news-style analysis of platform moves such as AIforce and Salesforce's interface shift.
Read more
The posts show an analyst who reads acquisitions and releases for their control-layer implications, which suits a vendor selling DevOps, release, or governance tooling, or a buyer who wants timely commentary on platform direction.
The emphasis is on tooling, metadata, and interface control rather than MuleSoft and Informatica integration practice.
The analysis also takes a clear competitive view of ServiceNow and Salesforce, which can constrain a neutral sponsored placement.
For a brief about sequencing integration and governed data before Agentforce-style automation, Akhilesh Perla's integration-layer argument is closer to the buyer's task.
Ask for examples of integration practice if that capability is central to the brief.
This page is built from the full text of three LinkedIn posts by Akhilesh Perla: one on Salesforce and Informatica as an enterprise AI stack, one reading Salesforce's acquisitions as an architecture map and describing the MuleSoft and Salesforce practice at NexGen Architects, and one on the HMRC contract win and the Hapie AI governance position.
The posts do not give publication dates, so they are not placed in sequence and no claim is made about how the arguments developed or which are oldest.
Perla's posts do not include articles, talks, transcripts, biography, employer records, or audience breakdowns, beyond a stated LinkedIn follower count of 16,779 as of 11 October 2026.
The similar-creator comparisons draw on two dated posts each from Mark Bidgood, Arvind Murali, and Vernon Keenan.
A wider body of work would be needed to confirm which themes recur across Perla's writing rather than appearing in these three pieces.