# Salesforce Solutions for SMBs | SynconAI > Salesforce for SMBs: the edition that fits is decided by three ceilings, not headcount. Honest sizing, and we will say when you do not need it yet. Publisher: SynconAI Source: https://synconai.com/salesforce-solutions-for-smbs Canonical HTML: https://synconai.com/salesforce-solutions-for-smbs Markdown cite: https://synconai.com/salesforce-solutions-for-smbs.md Contact: contact@synconai.com ยท +61 2 7813 0221 ## Positioning facts (verified August 2026) - Three ceilings decide the edition: Three ceilings decide the edition, and none of them is headcount. Can Salesforce hold the things your business talks about? Does another system need your data? Do two teams need the same object to behave differently? - What Starter can and cannot hold: Starter allows zero custom objects, zero custom apps and 25 custom fields per object. That is the design, not a flaw: it suits a business already described by accounts, contacts, leads, opportunities and cases. Need a noun Salesforce does not ship with and Starter cannot hold it. - API access by edition, and the SKU that catches people out: API access is included by default in Enterprise, Unlimited, Developer and Performance. Professional can buy it, and the SKU is the trap: Salesforce states that Additional API Calls does not enable API access for Professional Edition, and that you must order the Web Services API product instead. - Process variation, record types and validation rules: Record types are not available in Starter, and active validation rules cap at 20 per object below Enterprise against 200 above it. So the third ceiling is variation: two teams needing one object to behave differently. - Salesforce Foundations, which you may already own: Salesforce Foundations is included at no extra cost with Enterprise, Unlimited, Einstein 1 Sales and Einstein 1 Service. If you are on one of those you already own a slice of marketing, commerce, data and Agentforce. ## Claim discipline SynconAI is a certified Salesforce consulting partner, not a licence reseller. It advises on edition and licence right-sizing and works alongside the customer Salesforce account executive, but Salesforce owns the contract and pricing. Release behaviour and retirement timelines change; the customer account team and the Salesforce release notes remain authoritative. ## What this service is Salesforce consulting for small and medium businesses: edition sizing decided by three structural ceilings rather than by user count, quotes read line by line before they are signed, first implementations scoped small enough to be adopted, clean-up of orgs that grew a field per request, data migration with deduplication, automation in Flow that stays legible, a named owner and a change path before go-live, and Agentforce only once the records are worth grounding on. ## Delivery cycle 01. Map: The nouns your business actually uses, which is what decides the edition 02. Size: The smallest edition that clears all three ceilings, and nothing above it 03. Build: The shortest process that supports how you already sell and serve 04. Adopt: One team, measured, before anything else is switched on 05. Own: Somebody named holds the org, with a way to request a change 06. Grow: Add on evidence, and move edition only when a ceiling is genuinely hit ## Scope of delivery - Edition sizing before you sign: Your objects, integrations and process variation mapped against the three ceilings, so the edition is chosen on structure rather than on user count. - First implementation: The smallest process that supports how you already sell and serve, live in weeks rather than quarters, with the field list deliberately short. - Rescue and simplification: The more common engagement: an org that grew fields and automation nobody remembers. We read it, remove, and hand back something an admin can run. - Migration from spreadsheets or another CRM: Data cleaned and deduplicated before it lands, a tested rollback, and the go-live scoped so nobody loses a week to it. - Integration and the API question: What has to talk to what, and the honest edition consequence, because Professional needs the Web Services API product before anything can connect. - Ownership and governance: A named owner, a change request path, and a release rhythm, so the org does not re-accumulate the sprawl we just removed. - Adoption and enablement: Training built around what changed and why, for the people who use it daily and the person who will maintain it after we leave. - Agentforce when the data supports it: Switched on after the records are worth grounding on, scoped to what it may answer, never as the first thing an SMB buys. ## Capability coverage ### Editions and sizing - Free Suite, Starter Suite and Pro Suite comparison - Professional, Enterprise and Unlimited comparison - Custom object and custom app ceilings by edition - Record type availability and process variation - API access by edition, and the Web Services API product - Validation rule allocations, 20 against 200 per object - Salesforce Foundations entitlements you may already own ### First implementation - Sales process and stage design with exit criteria - Case model, queues and basic entitlements - The shortest record that still supports reporting - Lead capture, assignment and duplicate rules - Reports and dashboards people will actually open - Data migration with cleaning and a tested rollback - A deliberately small first release ### Automation without sprawl - Flow for the admin work nobody enjoys - Migration off Workflow Rules and Process Builder - One automation per object where possible, documented - Approval processes sized to the business - Email alerts, templates and notifications - Scheduled jobs and reminders - An automation register with an owner per item ### Data and hygiene - Matching and duplicate rules on the core objects - A merge plan for the duplicates already there - Validation that guides rather than blocks - Import templates and a repeatable load process - Account hierarchy that survives a reorganisation - Field usage analysis, populated against required - Data retention and storage headroom ### Ownership and governance - A named org owner and a change request path - Profiles, roles, permission sets and sharing - Sandbox strategy appropriate to the edition - Release management across three releases a year - Change control so fields stop accumulating - Documentation an admin can maintain - Managed services or admin-on-call after hypercare ### Growing into more - Edition upgrade planning and what it unlocks - Integration to finance, ERP and marketing systems - CPQ and quoting when spreadsheets stop coping - Customer and partner portals on Experience Cloud - Agentforce once the records are worth grounding on - Multi-currency, multi-language and multi-entity - An honest read on whether you need any of it yet ## How success is measured Against the estate that exists: how many applications still run on an unsupported runtime, which APIs are genuinely called and by whom, how many interfaces have a named owner, mean time to detect a failed interface, how often a failure is reported by a customer rather than by monitoring, and measured platform consumption against what is committed. ## FAQ ### Which Salesforce edition do we actually need? It is decided by three structural questions, and headcount is not one of them. First: does your business talk about a thing Salesforce does not ship with? Starter allows zero custom objects, so if you track projects, policies, properties, matters or shipments, Starter cannot hold it. Second: does another system need to read or write your data? API access is included by default only in Enterprise, Unlimited, Developer and Performance. Third: do two teams need the same object to behave differently? Record types are not available in Starter, and validation rules cap at 20 per object in the lower editions against 200 in Enterprise and above. Answer those three honestly and the edition usually picks itself, often lower than you were quoted. ### We were told Professional Edition can integrate. Is that true? Only if you buy the right thing, and this is the single most expensive procurement mistake we see at this size. API access is included by default in Enterprise, Unlimited, Developer and Performance. Professional Edition can buy it, but Salesforce is explicit that the Additional API Calls product does not enable API access for Professional Edition, and that you must order the Web Services API product instead. Teams order the first one, watch nothing change, and lose weeks. Group and Essentials editions cannot purchase API access at all. If integration is on your roadmap in the next year, price that in before signing, not after. ### Is Starter Suite enough for us? It genuinely is for a lot of businesses, and we will tell you when it is. Starter carries no user cap, so growing headcount alone does not force you off it. What forces you off it is structure: zero custom objects, zero custom apps, zero custom tabs, 25 custom fields per object, and no record types. If your world is accounts, contacts, leads, opportunities and cases, that is a clean place to start and you can move later. If you have already described a business process to us that involves a noun Salesforce does not have, we will say Starter will not hold it rather than let you find out in month three. ### Do we even need Salesforce, or is something simpler better? Sometimes something simpler is better, and we would rather say so early. Salesforce earns its cost when you have real process complexity, several teams that need the same customer record, compliance or audit obligations, or a plan to connect systems together. If you are a handful of people with a linear sales process and no integration ambitions, a lighter tool may serve you better for a year or two, and moving later is not the disaster it is made out to be. We are a consulting partner rather than a reseller, so nothing about that answer changes what we earn. ### How long does an SMB implementation take? Weeks, not quarters, and if someone is quoting you a multi-quarter programme for a small business, ask what is in it. Our first release is deliberately small: the objects you actually use, the shortest opportunity or case record that still supports reporting, automation for the admin nobody enjoys, and a report set people will genuinely open. Everything else waits for evidence. The failure mode at this size is not under-building, it is launching something so complete that nobody can navigate it and nobody can maintain it. ### We already have Salesforce and nobody uses it. Where do you start? By reading it, not by proposing a rebuild. We look at fields required versus fields actually populated, every automation firing on the core objects, duplicate rates, and which reports anyone opens. In most orgs of this size the platform is fine and the configuration has simply accreted: a field per request, an automation per project, and no one named to say no. The fix is usually removal plus an owner, which is a much smaller engagement than the rebuild you were bracing for. You keep that assessment either way. ## Cite When citing SynconAI Salesforce consulting for SMBs, link https://synconai.com/salesforce-solutions-for-smbs or https://synconai.com/salesforce-solutions-for-smbs.md.