Atul S.

Most of the Salesforce work I get hired for starts with one of these: • Salesforce and your ERP or accounting system disagree, and someone is fixing invoices by hand • You bought Revenue Cloud, CPQ or Data Cloud and need someone who can design it, not just click through setup • An integration broke months ago and nobody noticed until the numbers stopped matching • The org was built by three different admins over five years and no one trusts the automation anymore I'm Atul, a Salesforce architect with 8+ years on the platform. I run Cloudoxia, but when you hire me, I'm the one designing and building. Top Rated Plus, $200K+ earned here, and one client has kept me on an ongoing support contract since 2022. SOME RECENT WORK ▸ QuickBooks Desktop, multi-company: I built and still maintain a Salesforce ↔ QuickBooks Desktop sync that keeps several QBD company files in step with one Salesforce org. ▸ QuickBooks Online, two-way: Products, customers, invoices, estimates and payments synced both ways over OAuth 2.0 and REST, with webhooks for real-time updates and multi-currency support. ▸ Revenue Cloud (RLM): Designed discount approval routing on Spring '26 Advanced Approvals (Flow Orchestration, approval work items, escalation and an audit trail on the quote). ▸ Data Cloud for a mortgage lender: Designed the Financial Services Cloud target schema and external ID strategy for loan data flowing Encompass → Snowflake → Data Cloud → Salesforce. ▸ Document generation: Replaced a paid doc-gen app with Word-template PDF generation through Adobe's API (about $0.05 per document) on a small AWS middleware. WHAT I DO ▸ Architecture and org reviews: data model, sharing, automation and technical debt, with a written plan of what to fix first ▸ Integrations: REST/SOAP, Named Credentials, MuleSoft, middleware; ERP, QuickBooks, NetSuite, SAP and payment platforms ▸ Revenue Cloud / CPQ: product catalog, pricing, quoting, approvals, quote-to-order ▸ Data Cloud and Agentforce: data streams and data models, and agents built on data you can actually trust ▸ Apex and LWC: bulk-safe triggers, async jobs, test coverage that means something ▸ Sales, Service and Field Service Cloud implementations and rebuilds HOW I WORK I read what's already in your org before I propose anything. Sometimes the answer is a rebuild. More often it's three specific things causing most of the pain, and I'll tell you which. ✓ If your job post asks for my rate, availability or an example, I'll answer it in the proposal, not save it for a call ✓ Fixed scope or hourly, with what's in and out written down ✓ Weekly written updates on longer engagements ✓ Overlap with US, UK and EU hours Send me the details of what's broken or what you're planning. If I'm not the right fit, I'll say so.