Salesforce for SMBs · edition sizing · first implementation & rescue · governance · certified partner
Most SMB disappointment with Salesforce starts at the quote, not the build. An edition gets picked from a user count and the implementation is shaped for a company four times the size. We size on structure and name who holds it afterwards.
Pressure we surface early
What we find in most orgs: an edition chosen from a user count, an implementation shaped for a much larger company, a field list grown one request at a time, and nobody named to hold any of it.
Headcount is the easiest number to ask for and the one that tells you least. What decides fit is whether Salesforce can model your business, whether anything has to integrate, and whether two teams need the same object to behave differently.
Multi-quarter phases, a steering committee and a workstream for change management, for eleven people. The result launches so complete that nobody can navigate it, and nobody who is left can maintain it.
Nobody is empowered to say no, so the record grows a field every time somebody asks. Two years later the page layout is unusable and half the fields have never been populated once.
Professional Edition has no API by default, and the add-on people order first does not enable it. So the integration that was assumed to be a small piece of work becomes an edition conversation nobody budgeted for.
The person who set it up moved on, the partner finished, and now three people have admin rights and none of them has the job. This is the single strongest predictor of whether we get called back in two years.
An agent reads whatever is in the records. Point one at an org where half the fields are blank and the duplicates were never merged, and it will be confidently wrong in front of a customer.
Find your tier
A small business is trying not to be over-sold. A medium one is trying to control something that already grew. An enterprise is trying to make several orgs behave. Running the wrong engagement is the quickest way to waste a quarter.
You want the thing working next month, not a programme. The risk is being sold an edition and an implementation shaped for a company four times your size, and paying for both.
See the small businesses pageYou have outgrown the setup that got you here. Fields accumulated, nobody owns the org, and the first real integration has just run into an edition question nobody priced.
See the medium businesses pageSeveral orgs from acquisitions, a release process that competes with delivery, and a transformation programme whose real constraint is data ownership rather than technology.
See the large enterprises pageYou have a proposal in front of you and no way to tell whether it is right. We will read it against what you actually need and tell you where it is oversized, for free.
Talk it throughThe three ceilings
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?
One, the modelling ceiling. 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.
Two, the integration ceiling. 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.
Three, the variation ceiling. 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.
Allocations change, so treat this as the shape of the question rather than a price list. Salesforce publishes the current edition comparison, and your account team remains authoritative.
SynconAI sizing ladder for workshops. Read it upward and stop at the first rung that clears all three ceilings; everything above that is capability you are paying for and will not configure this year.
SynconAI sizing ladder
What we actually build
These reflect how owners, operations leads and the person who inherited the org describe the problem, rather than a feature list. Most engagements start with the first two, because an org you have not read is one you cannot safely change.
Your objects, integrations and process variation mapped against the three ceilings, so the edition is decided by structure. It frequently lands lower than the quote.
Fields populated against fields required, automation mapped, duplicates scored. The first release of a rescue usually takes things away, and people notice immediately.
The shortest process that supports how you already sell and serve, with reporting designed on day one rather than bolted on a quarter later.
Flow doing the admin work nobody enjoys, migration off Workflow Rules and Process Builder, and a register so the next person to change one is not guessing.
Matching and duplicate rules, a merge plan for what is already there, and validation that guides at the point of entry rather than blocking at the end of a form.
A named owner, a change request path, and a release rhythm, because at this size that is the difference between an org that stays clean and one we rescue in 2028.
Scope of delivery
From a written sizing review through to run-state support across Salesforce for small business, Sales Cloud, Service Cloud, Flow and Agentforce, scoped with named owners, a measured baseline, and the edition question settled before anything is built.
At this size the constraint is almost never the platform. It is that nobody was given the job of saying no to a new field, and nobody priced the integration that everyone assumed would be easy.
Objects, integrations and variation mapped against the three ceilings; if you already have an org, fields populated against required, automation mapped and duplicates scored. Yours whether or not you engage us.
Sales process and stage design, case model and queues, the shortest record that still supports reporting, and a deliberately small first release.
Spreadsheets or another CRM brought across with cleaning, deduplication and a tested rollback, so the first week after go-live is not spent fixing records.
Finance, marketing and operational systems joined, with the edition consequence stated up front. Larger estates move to MuleSoft integration when point-to-point stops scaling.
A named owner, a request path for new fields, and three Salesforce releases a year absorbed as decisions rather than as projects.
A named team for the run-state backlog and releases, or admin-on-call for a business that has one part-time owner, optionally as managed services.
Switched on after the records are worth grounding on, never as the first thing an SMB buys. See Agentforce services.
The work
Not a phase plan. These are the pieces of work we are asked for, in the order they usually matter. Most engagements are two or three of them, and a first release that does everything below is a first release nobody will adopt.
SynconAI engagement spine for SMB workshops. Agentforce sits after all four, not before, and nothing contractual or financial completes without a named human.
Send us the proposal and the edition on it. We will tell you where it is oversized, where an add-on is genuinely required, and what it does not cover. Free, and it regularly saves more than the engagement costs.
The customer list, the pipeline tab and the shared inbox brought into one place, cleaned and deduplicated on the way in, with a rollback so the first bad week does not become a crisis.
Every required field tested against one question: does answering this help someone do their job, or only help someone report? If it is the second, it becomes optional, derived, or gone.
Overlapping Workflow Rules, Process Builders and Flows firing in an order nobody has mapped. We document what runs, retire the dead, and rebuild the rest so an admin can safely edit it.
Accounting, marketing or an operational system joined to Salesforce, with the edition consequence stated before work starts rather than discovered in week three.
Documentation an admin can maintain, training aimed at the person who will own it, and a change process, so the answer to "who decides?" stops being a shrug.
Governed AI
Useful at small scale, and easy to deploy too early
Your records stay on your data model; Agentforce is how Salesforce surfaces governed assistants on top of them. Small teams benefit because the work an agent absorbs is the work there is nobody spare to do. What none of them should do is commit anything: price, discount, contract terms and entitlement decisions stop at a named approver.
Availability follows your edition and region. Details on our Agentforce services page.
A long email thread or a call condensed into what changed, and a follow-up drafted for someone to approve. This is the work that gets skipped when there is nobody spare, which is most weeks at this size.
Update the record from what actually happened rather than relying on someone remembering on Friday. Better data in turn makes everything else on this page work.
Anything touching price, discount, contract terms or an entitlement decision goes to a named person. That is set in configuration, so it holds when the agent is under pressure to be helpful.
Honest scoping
We are a certified consulting partner rather than a licence reseller, so no margin rides on what you buy. What we bring is the mapping between the work you need and the edition that supports it, which is the part a quote never shows you.
Capability you will not configure for three years is capability you are renting unused. Editions move up more easily than budgets recover, so we size for the work in front of you and flag the trigger that would justify the next rung.
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.
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. We have seen SMBs quoted for capability that was already included in the agreement they signed, unswitched-on, for a year.
If you do not have a Salesforce account executive yet, we will make the introduction. The FAQ covers what we can and cannot do on licensing. Adjacent needs such as Data 360 work share the same change-control ownership so nothing becomes a governance island.
Partnership criteria
Most partners are built for enterprise work and take SMB projects at the edges, which is why the method arrives unchanged and the invoice surprises everyone. We run enterprise programmes too, and that is exactly why we can tell you which parts of one you do not need. Learn more about our Salesforce consulting partner approach.
Structure decides the edition, and it frequently lands a rung below the quote. Saying so costs us margin we never had, because we are a consulting partner rather than a reseller.
Fields populated against required, automation mapped, duplicates scored, or your quote read line by line. You keep the document whether or not you engage us, and it usually shows a smaller job than expected.
The first thing people should notice is that something they used to do by hand has stopped existing. Adoption follows the tool giving time back, not a training calendar.
The same architects who run multi-org enterprise programmes, scoping your work. Knowing what large-company governance looks like is what lets us cut it down to one page for you.
Hubs in Delaware, Sydney and Hyderabad, a named team on your business hours, and travel onsite for discovery, go-lives and executive sessions.
The same people for the run-state backlog, the releases and the awkward questions, or admin-on-call where you have nobody internal to hold it.
Delivery method
Six beats, with transparent gates and no surprise scope. Two of them are unusual for a Salesforce project: sizing happens before anything is signed, and an owner is named before go-live rather than after the project closes. Both are cheap to do at the right moment and expensive to retrofit. Same method as our broader Salesforce consulting practice, scaled down.
The nouns your business genuinely uses, how you sell and serve today including what happens off-system, and what already exists if you have an org. You keep the write-up either way.
The three ceilings answered in writing and the edition chosen from them, with integration priced now rather than discovered later. If you have a quote, it gets read line by line against this.
The shortest process that supports the work, Flow taking the admin nobody enjoys, duplicate rules in from day one, and reporting designed rather than bolted on a quarter later.
One team first, with a measured before-and-after on field completion and response time, and a rollback. It expands when the numbers survive scrutiny, not when the plan says so.
A named person holds the org, with a written path for requesting a new field and a rhythm for the three releases a year. Internal where you have capacity, ours where you do not, never nobody.
Additions on evidence, and an edition move only when a ceiling is genuinely hit. Optionally continue with managed services or ongoing Salesforce administration.
Client reviews
Verbatim reviews from SynconAI Salesforce and Agentforce engagements across the United States, Australia and globally. Anonymised clients are labelled by sector.
Salesforce Select Partner16+ architect certificationsDelivery across USA, Sydney & India
Simply Outstanding
“SynconAI Consulting are Simply the Best in the Business When it comes to Salesforce implementation and AI-powered solutions, SynconAI are in a league of their own. Their expertise, dedication, and ability to deliver results that truly move the needle sets them apart from every other consulting partner we've worked with. What they achieved with our Sales Cloud, Service Cloud, and custom Agentforce agent has completely transformed how we operate streamlining our pipelines and our customer service, and automating tasks that used to consume hours of our team's time. They don't just implement technology they transform businesses. If you want the best, you work with their team.”
“I had a very urgent deadline for our project reporting to be delivered and needed to build the module, dashboard and output reports in Salesforce. SynconAI were very responsive - they met with me online, responded to my emails quickly and took calls - whatever was needed to progress the work quickly. We are thrilled with the outcome and will continue to work with SynconAI in the future to continue to build our Salesforce capability and platform.”
“The team at SynconAI were fantastic, and promptly delivered on each project. They were able to guide us through every stage and made sure we were satisfied with the outcomes on multiple scopes of work.”
“They have been great and helping us transform out business by bringing what I conceptualize to life. Great at translating process/workflow needs into a solution. Been a pleasure work with and they're a critical part of our team and will be instrumental into bringing about my vision.”
“Working with SynconAI was a seamless and highly professional experience from start to finish. They took the time to deeply understand our business processes before designing and implementing a Salesforce solution tailored specifically to our operational needs. The team demonstrated strong technical expertise across Salesforce configuration, automation, integrations, reporting, and user experience design.”
Frequently asked questions
Straight answers about which edition you actually need, what Starter can and cannot hold, the API gap in Professional Edition, how long an SMB build really takes, and when the honest answer is that you do not need Salesforce yet.
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.
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.
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.
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.
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.
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.
Salesforce, Starter Suite, Pro Suite, Salesforce Foundations, Flow and Agentforce are trademarks of Salesforce, Inc. SynconAI is an independent certified Salesforce consulting partner and is not created by, affiliated with, or endorsed by Salesforce, Inc. Editions, allocations, entitlements and pricing are set by Salesforce and change; the edition comparison, the Salesforce Help allocation pages and your account team remain authoritative. Screenshots are reproduced for illustrative purposes.
Free architect conversation
60 seconds to brief us. A certified architect replies within one business day.
Sales Cloud
Service Cloud
Field Service
Experience Cloud
Marketing Cloud Next
Revenue Cloud AdvancedSalesforce CPQ
Data 360
Financial Services Cloud
Nonprofit Cloud
Health Cloud
CRM Analytics & Einstein
Agentforce
