Customization Options in SaaS

In the last two weeks, two customers escalated the same issue. "Your product is showing all the wrong data." I panicked. We dug in and then we realized the problem: 💡 Their way of working was so custom, so specific, that no "out-of-the-box" solution could ever do it justice. 1. Customer 1 sells to SMBs. Their CRM tracks: → Subscription Type (Monthly vs. Annual) →Opportunity Amount (Either MRR or ARR, depending on Subscription Type) So even a basic revenue calculation needs a custom formula: If (Subscription Type = Monthly), then Revenue = Opportunity Amount * 12. Else, Opportunity Amount. Now imagine trying to compute ACVs, win rates, or pipeline health—everything breaks unless the tool can adapt. 2. Customer 2 sells to enterprises with million-dollar deals. Their CRM needs to handle complex global deal structures. For example, a Japanese conglomerate deal where multiple AEs across regions collaborate. → AE 1 (Japan) owns the deal and logs the full $1M in CRM. → AE 2 (US) co-owns the deal and logs 50% ($500K). → AE 1 then logs a negative $500K entry to adjust for commission tracking. All three opportunities are marked Closed Won, which means: 1.⁠ ⁠The CRM sees 3 deals instead of 1 2.⁠ ⁠The ACV looks like $333K instead of $1M An analytics product that doesn’t account for this kind of real-world messiness is useless. No SaaS product can work out-of-the-box in environments this complex. The Future of SaaS = Configurability + Services + Automation SaaS needs to evolve. The days of "take my software and self-serve your way to success" are dying. Here’s where we’re headed: 1.⁠ ⁠A Configurable Base Platform – Purpose-built for personas (in our case, B2B marketers), but flexible enough to fit different workflows. 2.⁠ ⁠Automated Agents – To handle repetitive tasks and adapt to evolving processes. 3.⁠ ⁠Expert Services – Not "customer success" as we know it, but real domain experts who help configure, customize, and optimize. At Factors.ai, we’re betting on this model. Instead of forcing self-serve customization, we’re introducing Premium Support Services. We work closely with customers to configure reports, set up workflows, and ensure your CRM quirks don’t break your analytics. This is where SaaS is headed. Not just software. But software + intelligence + expertise. What do you think? How do you see SaaS evolving over the next 5 years? #SaaS #GoToMarket #SalesOps #RevOps #Analytics #FutureOfSaaS

If you're evaluating an off-the-shelf solution right now, there's one question you 𝘵𝘩𝘪𝘯𝘬 you might have asked, but probably haven't fully explored: "How will we handle customizations down the road?" Yes, you asked the vendor all the right questions: → Can it connect to our existing tools? → Can we customize the workflow to fit how we operate? → Can we automate this part of the process? And you might hear: → Yes, we have an API. → Yes, we support integrations. → Yes, you can configure workflows. The answer is almost always “yes.” But the truth is... – The integration will need separate scoping – The custom workflow will impact their roadmap – The automation will depend on your existing APIs and your current tech stack So, "yes" just means possible. Here’s why: Most SaaS platforms are designed to scale. That means building for the 80% - the common workflows, and not the edge cases. Custom work is still doable. But it requires: – Dedicated resources – Extra time – Careful prioritization And for product-led companies, those things are intentionally limited. Not because they don’t care. But because they’re focused on keeping their platform easy to maintain and scale for everyone. So when you need to customize the existing solution, you’ve got 3 options with pros and cons to each: 1. Work with the SaaS vendor to build it + deep product knowledge + easy access to internal components/APIs + everything stays with one team - you’re one of many customers in their backlog - longer timelines because of backlog - higher rates because the work is usually outsourced (quality varies) 2. Bring in a third-party integration partner + teams are more agile and focused + they have broader experience across systems + they provide faster delivery and usually higher quality - it does require strong collaboration with the SaaS provider - they need access to APIs and documentation - results might vary - a partner who understands both your operations and the tech is wins here 3. Build it in-house + you have full control + fast feedback loops (requires a strong technology leader to manage teams effectively) + keeps everything internal - most internal teams lack the specific experience - you risk of building quick fixes that don’t scale - it steals devs valuable time from maintaining your core products or ops priorities ________ TL; DR: → The bigger the company, the more unique the workflow. → The more unique the workflow, the more customization needed. → And the more complex the system, the more critical it is to get it right So if you’re in the middle of evaluating SaaS platforms right now... Don’t just ask if it can be customized. Ask who will do the work, how long it will take, and what happens when priorities shift. That’s where the real risk (or opportunity) lives. Anything you want to add? #enterprisedevelopment #customsolutions

A $10 billion VC firm CFO inbounded Hanover Park. 5 minutes into our first call, it was obvious he only cared about 2 things: 1) Infinite Customizability Every single VC firm is different. Everyone has nuances. Everyone runs their investment process differently. So why do you think someone will fit nicely into your SaaS tool? It’s why firm go back to Airtable and Excel. This CFO wanted every piece of the product to be customizable… from multiple layers of tags on journal entries to portfolio attributes and custom dashboards for reporting. The bigger you are, the more customizability you need. 2) Speed He fired his previous fund admin because they were too slow. Capital calls took days. Distributions took forever. Financial reporting got jammed in manual processes filled with errors. He was sick of legacy fund admins with disjoined workflows, stale data, and manual processes. So he cut his fund admin and moved everything in-house. Because he believed it was the only way to get real-time data access and transparency without waiting for humans. … until now.

One of the biggest strengths of #Salesforce is how flexible it is. You can customize almost anything: fields, workflows, automations, integrations. And that’s exactly why so many businesses fall into a trap, because not every customization is good. Some of them are just crutches. Here’s what I mean: 📌 A customization is something that makes your Salesforce instance align better with how your business actually works. It removes friction, saves time, and creates clarity. It’s designed with intention, and it makes your system simpler in the long run. 📌 A crutch, on the other hand, is when we bend Salesforce to fit around a broken process. It’s the extra field that exists only because no one agreed on a standard definition. It’s the custom object created to patch over poor communication between two teams. Crutches don’t fix problems; they just make it easier to limp along with them. And the more you lean on them, the harder it becomes to walk without them. I’ve seen orgs so weighed down by years of “quick fixes” that even simple changes feel impossible. When we work with clients at Peeklogic, one of the first things I look at is whether a customization is truly adding value, or if it’s just a crutch keeping a deeper issue in place. That’s not always the easiest conversation to have. But in my experience, it’s the one that separates a Salesforce org that grows with the business from one that eventually collapses under its own weight. 📌 So here’s the rule I live by: if a customization simplifies the system and empowers the team, it’s worth it. If it complicates the system just to avoid a hard conversation, it’s a crutch. And in the long run, no business should be built on crutches.

🎄Happy Holidays! We're celebrating 24 days of (CRM+GTM) product integrations at Ampersand🎄 We're launching the newest iteration of our Salesforce connector that enables you to build and scale a deep bi-directional SFDC integration for your SaaS product/AI Agent. Here are some details: 1️⃣ 𝗙𝗨𝗟𝗟 𝗖𝗥𝗠 𝗦𝗬𝗡𝗖 Build a comprehensive CRM sync in days, not months. 1.1 Sync all key objects from your customers' Salesforce—including Account, Contact, Opportunity, Case, Task, Event, etc. 1.2 Sync any custom object. 1.3 Sync any custom field on a standard object (example: Customer_Tier__c, a custom field on the Account object used by one of your customers). 2️⃣ 𝗦𝗨𝗣𝗣𝗢𝗥𝗧 𝗘𝗩𝗘𝗥𝗬 𝗖𝗨𝗦𝗧𝗢𝗠𝗜𝗭𝗔𝗧𝗜𝗢𝗡 No two Salesforce setups are alike. Ampersand lets you handle custom objects, fields, and relationships, adapting to each customer’s unique configuration. 2.1 Dynamic mappings of objects and fields Example: A customer can map your system’s “Customer Segment” field to their custom field “Market_Type__c” on the Account object. 2.2 Fine-grained control Example: Your customer might choose to sync only Accounts with specific fields (e.g., Annual Revenue > $1M) or only Leads with a specific Status (e.g., “Qualified”). 2.3 Adapting to schema changes Example: If a customer adds a new field “Customer_Lifecycle__c” to the Account object, your integration can include it in future syncs without requiring significant engineering effort. 3️⃣ 𝗦𝗨𝗣𝗣𝗢𝗥𝗧 𝗔𝗦𝗦𝗢𝗖𝗜𝗔𝗧𝗜𝗢𝗡𝗦 Ampersand preserves associations during syncs — ensuring data relationships remain intact. 3.1 Respecting parent-child relationships Example: If an Opportunity is linked to an Account, the integration ensures that the Opportunity remains tied to the correct Account after syncing. 3.2 Preserving referential integrity Example: If a Lead is converted to an Opportunity with an associated Contact and Account, the integration retains all these links — the data always remains meaningful. 3.3 Dynamic mapping for custom associations A custom object like “Subscription” might be associated with an Account and an Opportunity. 4️⃣ 𝗚𝗥𝗔𝗡𝗨𝗟𝗔𝗥 𝗖𝗨𝗦𝗧𝗢𝗠𝗘𝗥 𝗖𝗢𝗡𝗧𝗥𝗢𝗟 Your customers can choose which objects, fields, and records to sync between Salesforce and your platform. 4.1 Field-level control and permissions Customers might sync only key fields like Name, Email, and Phone for Contacts, leaving out less critical fields (e.g., Fax). 4.2 Control over writebacks Customers might only allow Closed-Won Opportunities from your platform to update their Salesforce instance to a specific custom object. 4.3 Custom mappings of fields and relationships A custom field in Salesforce like "Customer_Lifecycle__c" can be mapped to a field in your product, ensuring data flows where it’s most relevant. TO BE CONTINUED TOMORROW! 🎁 Want to learn more about customizations to your Salesforce integration? Check out our docs, or DM me! --