Complex Salesforce, taught simply.

I'm Mustafa Aksu, and I'm a Salesforce ISV Partner: I build Configra, my own AppExchange product that lets sales reps create deal-specific product configurations directly on a quote — without polluting the Revenue Cloud catalog. It came straight out of real Revenue Cloud work and is currently going through AppExchange Security Review.

Day to day, most of my work sits where AI meets the platform: a live, deployed Agentforce agent that answers grounded in Data 360 and takes real action (it identifies the customer, explains a consumption anomaly, and logs the support Case), custom Apex exposed to Claude as MCP tools over Salesforce Hosted MCP Servers, and an agent loop that built an entire Salesforce org — seven objects, triggers, tests — verified by its own test runs. Underneath all of it sits the part people forget: Quote-to-Cash, end to end — CPQ, contracts, billing, payments, and accounting, integrated with SAP, DocuSign, and Stripe. An agent is only as good as the org and the data underneath it.

And because an agent that takes real action has to be trusted, I built the proof around it too — the whole Agent Development Lifecycle, the part almost nobody publishes. PreFlight scans a customer's real case history and scores whether the data can carry an agent at all — before a single build hour. Prüfstand attacks the live agent with a pre-registered German red-team corpus and grades it with a deterministic verifier the model never controls. Agent Blast Radius computes what an agent's code can actually reach and caught a GDPR-labelled field slipping past the running user's permissions — with a real org, not me, as the judge. Nabz watches the live agent's pulse and, when quality drops, correlates it with the org's change stream to name the why — with an evidence grade, never a guess. And Aktenlage turns an agent's operational traces into an EU AI Act Article 26 evidence pack. Trust is something you engineer, not something you claim.

But I didn't start in tech. I spent around twenty years in education, including six as a guidance counselor at an international college. That's not a detour from what I do now — it's the engine behind it. Teaching for two decades makes you good at one specific thing: taking something genuinely complex, structuring it clearly, and explaining it to someone who's never seen it before. This whole site is that skill pointed at Salesforce.

I care about code quality and user adoption in equal measure — clean architecture nobody uses is a failure, and so is a popular feature built on sand. Playing bağlama, ney, and piano taught me that a single character, condition, or line of code can change how a whole system behaves. I try to stay calm under pressure, listen before I build, and justify every decision I make.

I build in public and I give back to the community. I founded and moderate the Salesforce Revenue Cloud | Germany LinkedIn group, and you can see all ten of my builds — PreFlight (the pre-install evidence scan), HanseWatt (the live agent), Agent Blast Radius, Prüfstand, Nabz and Aktenlage (the trust layer around it, closing the Agent Development Lifecycle), Urla Shoes (AI document classification over MCP), Hospital Org (an org built by an agent loop), Configra (my AppExchange product), and TechnoStore (Quote-to-Cash across ten external systems) — on my Projects page, each linking to its full case study. Everything I write here comes from work I've actually shipped, not theory I read somewhere.