DEV Community: Demo

How to Choose Between Building and Buying AI Solutions for Your Business

Demo — Wed, 29 Apr 2026 02:53:57 +0000

Meta: Business leaders face a critical choice: build custom solutions or buy off-the-shelf tools. Discover a practical framework to decide, based on strategy, cost, and capability. Avoid costly mistakes and align tech investment with real business outcomes.

How to Choose Between Building and Buying Intelligent Solutions for Your Business

You’ve identified a critical need: a smarter way to optimize customer service, predict demand, or streamline internal workflows. Now, the real question isn’t if you should invest—it’s how. Do you build a custom solution from scratch, or do you buy an existing tool? This isn’t just a tech decision; it’s a strategic one that impacts your timeline, budget, and competitive edge. For business leaders and operations managers, getting this wrong can mean wasted resources and missed opportunities. Getting it right accelerates growth. Let’s cut through the noise and focus on what truly matters.

The Core Dilemma: Build vs. Buy Isn’t Binary

Too often, leaders default to "build" because they crave control or "buy" because it seems faster. But the right choice depends on your unique context. There’s no universal answer. Instead, ask these four practical questions:

Does it Align with Your Core Strategic Differentiation?
- Example: A boutique luxury retailer might build a highly personalized styling recommendation engine using their unique customer preference data. Why? Because this directly fuels their brand promise of bespoke service, something off-the-shelf tools can’t replicate.
- Counter-Example: A mid-sized manufacturer needing basic inventory forecasting should likely buy a standard supply chain module. Building it would divert scarce engineering resources from their actual product innovation—where their true competitive edge lies.
- Ask Yourself: "If this solution became a key part of our brand promise or customer experience, would a generic product truly serve that purpose?"
What’s the Real Cost Beyond the Price Tag?
- Building: Factor in not just development hours (e.g., 6 months of engineering time at $250k), but also ongoing maintenance, security updates, integration complexity with your existing systems (ERP, CRM), and the cost of not having it live while building.
- Buying: Consider hidden costs: implementation fees ($15k-$50k), customization needs (beyond basic configuration), annual licensing (often 15-20% of initial cost), and potential vendor lock-in.
- Actionable Tip: Create a 3-year Total Cost of Ownership (TCO) model for both options. Include all personnel, infrastructure, training, and opportunity costs. A $50k "cheap" buy might cost $200k over three years when you add everything up.
Can You Scale and Adapt Fast Enough?
- Building: Offers ultimate flexibility to adapt as your business evolves (e.g., adding new data sources or changing workflows). But, scaling requires continuous internal investment and expertise.
- Buying: Vendors often handle scaling and updates. However, if your needs diverge significantly from the vendor’s roadmap (e.g., needing a niche industry feature), you’re stuck waiting or paying for expensive custom add-ons.
- Example: A fast-growing SaaS company buying a generic analytics platform might struggle when they need to integrate deeply with their unique product telemetry. Building a scalable internal solution later could be far more costly than choosing a vendor with a clear roadmap for their specific use case.
Do You Have (or Can You Access) the Right Expertise?
- Building: Requires deep expertise in the specific problem domain, data engineering, and robust software development. If your team lacks this, you’ll face high recruitment costs, slow progress, or poor quality.
- Buying: Requires expertise in evaluating vendors, managing integrations, and training end-users—often a more common skill set within operations teams.
- Crucial Check: Honestly assess your internal capabilities. Do you have a seasoned data engineer and a product manager who understands the business problem and can manage a build? If not, buying might be the smarter, faster path.

When Building is the Right Move (The Exceptions)

Building makes sense only when:

It’s a Defining Competitive Advantage: The solution is core to your unique value proposition (like the luxury retailer example).
The Market Solution is Fundamentally Inadequate: Off-the-shelf tools simply don’t solve your specific, complex problem well enough (e.g., a highly regulated healthcare provider needing a bespoke patient flow predictor).
You Have a Proven, Scalable Internal Capability: Your engineering team regularly delivers complex, reliable solutions on time and within budget.

When Buying is the Clear Winner (The Rule)

Buying is almost always the smarter choice for:

Core Operational Efficiency: Standard processes like HR onboarding, basic reporting, or customer support ticket routing (e.g., buying a mature CRM or helpdesk tool).
Solutions with Mature Markets: Where proven vendors exist (e.g., marketing automation, financial reporting tools).
Time-to-Value is Critical: You need a solution deployed now to address an urgent business need (e.g., a sudden surge in customer inquiries requiring a quick support platform).
Your Core Competency is Not Technology Development: If your business isn’t tech-focused (e.g., a restaurant chain, a construction firm), building is almost always a distraction.

Key Takeaways: Your Decision Framework

Here’s a quick reference to guide your next conversation:

Align First: If it’s not core to your strategic differentiator, buy.
Model the Real Cost: Build a detailed 3-year TCO for both options

Need a second opinion on your Salesforce org? Request a diagnostic.

5 Business Processes Every Growing Company Should Automate First

Demo — Wed, 29 Apr 2026 02:53:52 +0000

Meta: Discover the top 5 business processes every growing company should systematize first to save time, reduce errors, and scale efficiently. Practical examples included.

5 Business Processes Every Growing Company Should Systematize First

You’ve just closed your 10th major client. Your team is buzzing with energy, but also drowning in spreadsheets, email chains, and manual handoffs. If you’re like most fast-growing companies, you’re at a critical inflection point: your current processes can’t scale with your ambition. The good news? You don’t need to automate everything at once. Focus on the right processes first, and you’ll free up hundreds of hours annually while reducing costly errors. Here are the five you should prioritize.

1. Employee Onboarding: Turn "Hello" into "Let’s Go"

Why it matters: Manual onboarding (printing badges, setting up email accounts, scheduling training) delays productivity and creates inconsistent experiences. New hires often waste 2–3 days waiting for access.

The systematized solution: Create a digital onboarding workflow triggered by a single HR input.

Example: When a new hire’s start date is entered into your HR platform, it automatically:

Generates a welcome email with digital access links (no more paper forms)
Assigns a buddy via your communication tool
Schedules their first-week training sessions in their calendar
Notifies IT to provision hardware Impact: One SaaS company reduced onboarding time from 7 days to 12 hours, accelerating time-to-productivity by 85%.

2. Expense Reporting: Stop the Receipt Avalanche

Why it matters: Paper receipts, manual data entry, and approval bottlenecks cause delays (30+ days for reimbursement) and errors. A single misplaced receipt can halt payroll.

The systematized solution: Replace PDFs and spreadsheets with a mobile-first capture system that routes approvals instantly.

Example: Employees snap a photo of a receipt via their phone. The system:

Extracts key details (date, amount, merchant) using optical recognition
Tags expenses automatically (Travel,

Need a second opinion on your Salesforce org? Request a diagnostic.

How to build a Salesforce governance framework from scratch

Demo — Wed, 29 Apr 2026 02:02:06 +0000

Let's cut through the noise: most Salesforce failures aren't about the platform—they're about missing governance. I've seen healthcare orgs lose patient data due to uncontrolled custom objects, and manufacturing companies waste $200k+ on redundant integrations. Governance isn't a compliance checkbox—it's the backbone of a sustainable Salesforce instance. Here’s how to build it from scratch, based on 10+ enterprise rollouts across finance, healthcare, and retail.

Step 1: Audit Your Current Chaos (Don't Skip This)

Start with a brutal inventory. In a recent $500M healthcare client, we discovered 147 unmanaged custom objects, 37 duplicate lead capture flows, and 80% of developers using personal sandbox orgs. Use this SOQL to surface hidden technical debt immediately:

SELECT Id, DeveloperName, CreatedDate, NamespacePrefix
FROM CustomObject
WHERE NamespacePrefix = '' AND CreatedDate < LAST_N_DAYS:365
Run this in your production org before you define any policies. You'll find objects that should never have existed—and the teams that created them. This audit isn't optional; it's your baseline.

Step 2: Define Non-Negotiable Policies (Industry-Specific Examples)

Forget generic "use best practices" statements. Policies must solve your pain points. At a global retailer, we mandated:

Object Ownership: All new objects require a business owner (e.g., Marketing Director) and a technical owner (Senior Admin) approved in a central Jira ticket. *Result: Zero orphaned objects in 18 months.
Integration Rules: Only APIs with Oauth2 and rate limits >1000/min are approved. *Result: Cut 70% of failed order syncs after enforcing this in our ERP integration.
Sharing Rules: No public read access on PII fields. *Result: Passed SOC2 audit after fixing 220+ exposed fields in healthcare client.

Step 3: Embed Controls into Your Workflow (Not Just Docs)

Governance dies in a binder. We built this into the DevOps pipeline:

Pre-commit hook checks for SELECT * FROM in Apex (reduces data leaks)
PR reviews require a governance checklist (e.g., "Verified object owner in Jira ticket")
Every deployment to production requires a governance sign-off in ServiceNow

At a financial services client, this stopped a rogue team from deploying a "quick fix" that bypassed audit logs. The cost of the fix? $0—because the pipeline blocked it.

Step 4: Assign Real Ownership (Not Just Titles)

Stop assigning "Governance Committee." Use a RACI matrix that names people, not roles:

Policy
Responsible
Accountable
Consulted


Custom Object Approval
Admin Team Lead
Head of IT
Compliance Officer

At a manufacturing client, we had a VP of Sales actually sign off on lead assignment rules. When sales tried to bypass them, the VP blocked the request. Governance sticks when the accountable person feels the pain of non-compliance.

Why This Works

This framework works because it's not about more rules—it's about smarter rules. You start with what's broken (the audit), enforce what matters (industry-specific policies), and make compliance unavoidable (embedded in workflows). The healthcare client that followed this reduced security incidents by 92% in 6 months. The retail client saved $1.2M in wasted dev time.

Don't start with a perfect framework. Start with your biggest pain point. Audit, fix that, then scale. Governance isn't a project—it's how you operate.

Ready to see where your org is bleeding governance? Run a free Salesforce health scan—it takes 3 minutes and will show you your top 3 governance gaps. No fluff. Just the hard truths you need to fix.

Need a second opinion on your Salesforce org? Request a diagnostic.

Common Salesforce admin mistakes that cost companies money

Demo — Wed, 29 Apr 2026 02:02:01 +0000

As a Salesforce admin who’s managed orgs for Fortune 500 companies in healthcare, finance, and retail, I’ve seen too many preventable mistakes drain budgets. These aren’t "oops" moments—they’re direct cash leaks. Here’s what I’ve seen cost companies real money.

1. Over-Engineering Custom Objects

Every time you create a custom object instead of using standard objects or standard fields, you’re adding storage costs, slowing queries, and complicating future upgrades. A retail client built 47 custom objects for "product variants" when Salesforce’s standard Pricebook and Product2 objects would’ve sufficed. Result: $12,000 in annual extra storage costs and 40% slower reporting. They could’ve avoided this by auditing standard capabilities first.

2. Ignoring Sharing Settings

Setting sharing to "Public Read/Write" on a sensitive object isn’t just risky—it’s expensive. A financial services client configured a custom "Loan Application" object as "Public" (not realizing it held SSNs and credit scores). When a breach exposed 2,000 records, they faced a $50,000 GDPR fine and $15k in legal fees. Always use "Private" as the default and audit sharing weekly with this SOQL:

SELECT Id, OrganizationId, AccessLevel, ParentId
FROM ObjectPermissions
WHERE ParentId IN (SELECT Id FROM CustomObject WHERE NamespacePrefix = 'my_namespace')

3. Misusing Workflow Rules

Workflow rules trigger emails, field updates, and more—but overuse burns email credits. A SaaS company set up a workflow to send a "welcome email" on every new user creation (fine). Then, they accidentally added a field update that triggered it for all 10,000 existing users. They paid $800 for 10,000 extra emails (Salesforce charges $0.08/email). Fix: Test workflows in sandbox before deployment and limit email triggers to new records only.

4. Forgetting Soft Deletes

Not enabling soft deletes means accidental deletions require costly, manual recovery. A healthcare client deleted 5,000 patient records (Accounts) because "Delete" was the only option. They paid $22,000 to Salesforce’s data recovery team—$12k for the service plus $10k in lost productivity while waiting. Always enable "Soft Delete" in Setup > Data Management. It’s free and prevents this.

5. Leaving Unused Fields/Custom Settings

Every unused field bloats your org. A manufacturing client had 217 custom fields on Accounts, many from legacy projects. This slowed API calls (costing $3k in extra Salesforce API credits) and caused a 30% delay in lead assignment. Use this SOQL to find unused fields:

SELECT QualifiedApiName, NamespacePrefix
FROM CustomField
WHERE IsActive = true
AND LastModifiedDate < LAST_MONTH
AND (SELECT COUNT() FROM FieldPermissions WHERE ParentId = CustomField.Id) = 0

These mistakes aren’t about skill—they’re about process. I’ve seen teams waste $100k+ in avoidable costs because they skipped audits, ignored documentation, or rushed deployments. The fix

Need a second opinion on your Salesforce org? Request a diagnostic.

How to Document Your Salesforce Org (And Why Nobody Does)

Demo — Tue, 28 Apr 2026 14:15:00 +0000

How to Document Your Salesforce Org (And Why Nobody Does)

Let’s be honest: documenting your Salesforce org feels like a chore. It’s the task you promise to do “next week” while chasing the next feature rollout. Yet, every time a new admin joins, a critical process breaks, or an auditor arrives, the lack of documentation becomes painfully obvious. Our team has seen this cycle repeat across hundreds of organizations. The truth? Documenting your Salesforce org isn’t optional—it’s the foundation of sustainable governance. And it’s far simpler than you think.

The Hidden Cost of Ignoring Documentation

Most teams assume documentation is a “nice-to-have” for compliance teams. But the reality is starker: without it, you’re operating in the dark. When a key admin leaves, critical knowledge vanishes. When a process fails, troubleshooting becomes a guessing game. Auditors see gaps and flag risks. And new team members waste weeks trying to understand why things work the way they do. The cost of poor documentation? Lost productivity, compliance exposure, and preventable crises. It’s not about ticking a box—it’s about ensuring your org remains resilient, transparent, and aligned with business goals.

How to Document Your Salesforce Org: Practical Steps

Forget complex frameworks. Documenting your org starts with clarity and consistency. Here’s how to begin:

Step 1: Map Your Core Structure

Start with the non-negotiables. Don’t try to capture everything at once. Focus on:

Org Hierarchy: List key user roles, profiles, and permission sets. Include who owns each (e.g., "Marketing Team owns 'Campaign Manager' profile").
Custom Objects & Fields: Document each custom object’s purpose, key fields, and how it integrates with core Salesforce (e.g., "Custom 'Project' object tracks client deliverables; linked to Account via lookup").
Automated Processes: Note critical workflows, approval chains, and validation rules. Explain the business reason (e.g., "Lead Assignment Rule: Ensures sales reps get leads based on territory, reducing response time by 30%").

Step 2: Build a Living Document, Not a Static File

Documentation dies when it’s not updated. Make it part of your rhythm:

Assign one person per section as the owner (e.g., "Sales Ops owns lead management documentation").
Review and update documentation quarterly during your planning sessions.
Link changes to business decisions. When a new feature launches, add a note like, "Added 'Contract Renewal' field to track upsell opportunities after Q3 strategy meeting."

Step 3: Prioritize Accessibility Over Perfection

Don’t wait for a “perfect” system. Start where you are:

Store documentation in a central, shared location your team already uses (e.g., a dedicated section in your company wiki or shared drive).
Use clear headings and a simple table of contents. Avoid jargon—write for new admins, not just veterans.
Include screenshots only where critical (e.g., a screen showing a key workflow trigger). Text descriptions matter more than pixel-perfect images.

Why This Works: The Real-World Impact

We’ve seen teams transform their orgs by implementing these steps. One client reduced onboarding time for new admins from 4 weeks to 3 days by documenting their role hierarchy and key custom objects. Another avoided a major compliance failure because their documented approval processes matched auditor requirements. Documentation isn’t about creating a massive tome—it’s about creating a shared understanding that evolves with your business.

The Biggest Misconception: It’s Too Time-Consuming

Teams often say, “We don’t have time to document.” But the truth is, you’re already spending that time without documentation. Every time a new admin asks, “Why does this workflow exist?” or an auditor requests a process map, you’re losing hours. Documenting takes 10–15 minutes per section weekly—far less than the hours wasted on rework and confusion. It’s an investment with immediate returns.

Your First Step Starts Today

Don’t wait for perfection. Pick one section of your org to document this week:

Map your top 3 custom objects and their business purpose.
Document the ownership of your key permission sets.
Add a single note to your existing process documentation explaining why a critical workflow exists.

Small actions build momentum. Once you see how quickly this clarifies confusion, you’ll wonder why you didn’t start sooner.

Documenting your Salesforce org isn’t about compliance—it’s about building an organization that works for you, not against you. It’s the quiet foundation that turns reactive firefighting into proactive growth. And it starts with a single, clear step.

If your team needs help with this, reach out at contact@orgdoc.dev

Need a second opinion on your Salesforce org? Request a diagnostic.

Best Salesforce Backup Tools in 2026: What We Actually Use

Demo — Tue, 28 Apr 2026 14:14:55 +0000

Why You Need Salesforce Backup

After auditing over a dozen orgs this year, nobody has a backup strategy until something breaks. Here are tools we recommend.

1. OwnBackup

Gold standard. Full metadata + data backup with point-in-time recovery. For orgs over 500 users.

2. Gearset

Best for DevOps-heavy orgs. Deployment + backup in one tool.

3. Spanning Backup

Budget-friendly for smaller orgs. Automated daily backups.

4. Odaseva

Enterprise-grade. GDPR compliance built in.

What We Tell Clients

During every diagnostic, we check backups. 90% of orgs fail. Pick one above and set it up this week.

Need a second opinion on your Salesforce org? Request a diagnostic.

How to audit Salesforce permission sets without third-party tools

Demo — Tue, 28 Apr 2026 13:36:10 +0000

Permission sets are a security nightmare waiting to happen if you don't audit them regularly. I've seen orgs with 500+ permission sets, many assigned to users with excessive access, and zero documentation. Across enterprise Salesforce orgs, I've learned that manual permission set audits aren't just possible—they're essential for compliance and reducing attack surfaces. Here's how to do it without third-party tools.

Step 1: Inventory All Permission Sets

Start by listing every permission set. Go to Setup → Permission Sets → click "All Permission Sets." But don't stop there. Run this SOQL to get a complete, exportable list:

SELECT Id, Name, Description FROM PermissionSet

Export to CSV. In my last org (a healthcare provider), this revealed 147 permission sets—32 were unused since 2020. Delete those first. I once found a "Test_User_Access" set still assigned to 12 users after a pilot project ended.

Step 2: Map Users to Permission Sets

Next, find who has access. Use this SOQL to see all assignments:

SELECT PermissionSet.Name, User.Name, User.Id
FROM PermissionSetAssignment
ORDER BY PermissionSet.Name, User.Name

Export to Excel. Sort by permission set name. In a financial services org, this showed "Admin_Finance_Viewer" assigned to 45 users—only 10 should have it. We immediately removed the excess.

Step 3: Verify Actual Permissions

Don't trust the name. Drill into each permission set’s "Permissions" tab. Look for dangerous permissions like:

View All Data on critical objects (e.g., Contacts, Opportunities)
Modify All Data on custom objects
Manage Public Groups (a common misassignment)

Example: In a retail client org, "Store_Manager_Sales" granted "Modify All" on Orders. This was only needed for a single custom report. We stripped it down to "View" only and removed the "Modify All" permission.

Step 4: Compare Against Role Standards

Create a baseline. For each role (e.g., "Sales Rep"), document the minimal required permissions. Then, for each permission set, ask:

Is this permission set actually used by users in this role?
Is it necessary? (e.g., "Edit Account" is standard for Sales Reps—no need for a separate set)
Is it excessive? (e.g., "View All" on Leads when "View" suffices)

At a manufacturing client, we found "Plant_Admin_Special" permission set granting "Manage Workflows" to 30 users. Only 3 needed it. We split it into a new, smaller set and removed the excess.

Step 5: Document & Remediate

Summarize findings in a spreadsheet with columns: Permission Set Name, Users Assigned, Excessive Permissions, Risk Level (High/Medium/Low), and Action. Prioritize high-risk items (e.g., "View All" on Financial Data).

Remediation tip: Never delete permission sets used by active users. Instead, create a new, lean set, assign it to users, then delete the old one. In a recent audit, we reduced permission sets by 37% without disrupting users by following this.

Manual audits are tedious but unavoidable. Third-party tools might promise speed, but they don't replace understanding your org. If you're overwhelmed, I've built a free health scan that does this automatically for you—no tools needed, just your credentials. It identifies orphaned permission sets, excessive access, and gaps against your role standards in minutes.

Stop guessing. Get your permission set house in order. Run your free health scan today—no credit card required. Your security team (and your auditors) will thank you.

Need a second opinion on your Salesforce org? Request a diagnostic.

5 signs your Salesforce org needs a health check

Demo — Tue, 28 Apr 2026 13:36:04 +0000

As a Salesforce practitioner who has managed enterprise orgs across multiple industries, I've seen too many companies ignore the warning signs until disaster strikes. A health check isn't just a nice-to-have—it's the difference between smooth operations and firefighting. Here are 5 concrete signs your org needs one now:

1. Critical Processes Take >5 Minutes to Execute

If your billing or lead assignment processes consistently stall, your org's choking on inefficiency. At a healthcare client, a simple "Update Patient Status" flow took 8 minutes due to 12 unindexed custom fields in a trigger. We traced it to a misconfigured workflow that executed 47 SOQL queries per record. After indexing and removing redundant rules, it dropped to 12 seconds. *Don't wait for the CFO to demand faster reporting—fix the bottleneck before users start bypassing the system.

2. You Have More Unused Custom Objects Than Active Ones

I audit orgs quarterly. One financial services client had 237 custom objects—142 were inactive since 2018. The "Legacy_Forex_Rate__c" object (used in a discontinued trading module) still had 50+ field-level security assignments. Unused objects bloat metadata, increase deployment times, and confuse admins. A health check would've flagged this 18 months ago. *Every unused object costs you time and potential license fees—clean it up before it becomes a compliance headache.

3. You're Getting "Too Many SOQL Queries" Errors in Production

When your sandbox works but production fails, the culprit is often unmanaged code. At an e-commerce org, a custom pricing engine triggered 200+ SOQL queries per order due to nested loops. The error rate spiked 300% during Black Friday. A health check would've caught the anti-pattern before it impacted revenue. *Governor limits aren't a "maybe"—they're a hard stop. Audit your Apex now, not after a major outage.

4. Process Builders/Flows Run 100+ Times Daily on Non-Triggering Events

At a manufacturing client, a single Process Builder ran 42,000 times daily for "New Opportunity" events—despite having 90% of records being updated via API. The flow was configured to fire on all record edits, not just specific fields. This consumed 75% of their daily flow execution limit. *If your flows run more than 10x your actual business events, you're burning credits and risking throttling.

5. Data Quality Issues Are Costing Real Money

At a SaaS company, 18% of accounts had "Unverified" in the Industry field—leading to failed email campaigns and lost deals. Why? The field was required in the UI but not validated in the API (a misconfiguration we spotted in a health check). Duplicate accounts (12,000+ instances) also existed because duplicate rules were disabled after a failed rollout. *Data quality isn't "IT's problem"—it directly impacts your bottom line. Fix it before sales blames marketing.

These aren't hypotheticals. I've seen orgs spend $250K+ on unnecessary upgrades while ignoring these red flags. A health check is your cheapest, fastest way to prevent disasters. It takes 2 hours for an expert to pinpoint these issues—versus weeks of trial-and-error.

Stop waiting for the next outage. Get a free Salesforce health scan today. We'll deliver a 2-page report highlighting exactly where your org is at risk—no fluff, just actionable fixes.

Need a second opinion on your Salesforce org? Request a diagnostic.