If the Program Architect represents the football coach, then the Solution Architect (SA) represents the quarterback.
The SA is often found in the field, beside the other players, and calling the shots. They decide and are responsible for the solution, from a functional perspective.… Read the rest
I had a great conversation with a student of mine today. We spoke about how junior Salesforce consultants believe senior consultants know everything.
They perceive senior consultants as a large book of knowledge, who can immediately find the right page with a moment’s notice.… Read the rest
One step down, from the Enterprise Architect, in terms of visibility, is the Program Architect (PA).
The main responsibility of the PA is the strategy of the entire program within Salesforce. A program is usually composed of one or more projects.… Read the rest
In the Salesforce ecosystem, the Enterprise Architect (EA) has the widest technical view. They see the complete end-to-end architecture, and are not limited to just the CRM.
This means they understand and are responsible for
They are very technical, are able to discuss approaches with fellow architects, and ensure fellow architects are aligned.… Read the rest
In the realm of Salesforce, there are plenty of hats you can wear.
The responsibilities for some of these hats (or roles) are straightforward. Other roles have multiple names and meanings, and other-others overlap multiple roles (also considered to be a *really* big hat!).… Read the rest
Being an employee at a Salesforce agency, it can be challenging to set your own path. But it is possible!
When you’re just beginning your Salesforce career, it makes sense to accept all kinds of work. The more exposure you have to a wide range of clients and clouds will only make you better.… Read the rest
A handful of years ago, I just returned from a two year round-the-world backpacking trip. The bank account was empty and there weren’t many options, so I was open to work that didn’t involve Salesforce.
I ended up at an insurance company.… Read the rest
Being a Salesforce consultant is much more than just having Salesforce knowledge. It’s also a mindset.
There are several aspects of this mindset, so let’s discuss three big ones.
1. Being positive
One mantra that really speaks to me is, “Success is not an absence of problems.… Read the rest
Today’s email is a little off topic, but it’s a huge accomplishment that I’m proud to share with you. The 100th episode of my podcast was released yesterday!
If you’re unaware, I host a weekly podcast in which I interview everyday superheroes in the nonprofit space.… Read the rest
As an independent Salesforce architect, here are the apps I use on a daily basis.
1. Scheduling Tool
By now, most of you know of Calendly. It’s great, but I’m still waiting for the feature where you can limit the number of meetings per week.… Read the rest
One important element of a fixed price proposal is managing change orders. And when I say, change orders, I mean not having any.
The whole purpose of being fixed price is being fixed. What would be the point if the price kept changing via change orders?… Read the rest
You’ve just submitted a 5 page fixed-price proposal for a Salesforce project. The client is shocked your prices are so high and attempts to negotiate. What do you do?
To start, there are two things to consider:
1. Perhaps you didn’t assess the situation correctly
If your prices are actually too high, it’s possible you misread the situation.… Read the rest
When submitting a proposal for a Salesforce project, there are a number of important sections to include.
1. A situational appraisal
This section, usually the first in the proposal, explains the situation back to the client. It shows you’ve paid attention to their needs and the circumstances.… Read the rest
In yesterday’s example of a mid-project change, some readers commented it was a fairly minor change (switching from Zapier to Make). Some asked what can be done if it’s a larger change during a fixed-priced project. In essence, this is a question about scope creep.… Read the rest
One of my current projects is a Shopify to Salesforce integration. The client had purchased Zapier, and I was OK with it, so it was the chosen connector.
Products and orders needed to be synchronized with Salesforce, one way only.
With Zapier, the order lines were concatenated on a single line.… Read the rest
A while back, I asked you to complete the “Good Enough” questionnaire.
The short survey allows me to see who exactly is my audience. By knowing this, I can tailor my emails so they are more relevant to you, dear reader.… Read the rest
Let’s consolidate the previous two posts about scope and price in a Salesforce project.
The flowchart below allows you to see the steps and process involved in determining scope and pricing method.
This is the exact process I’ve been using for the past two years, so I hope you find it helpful.… Read the rest
Once you’ve an idea of what your client wants and the value of the Salesforce project, it’s time to sit down and determine options for price and scope.
Remember, scope is last, so the next step is deciding your prices.
Here are two popular pricing methods:
1.… Read the rest
One of the most popular questions I’m asked is, when doing fixed pricing, how do you accurately scope a Salesforce project? Don’t you need to add tons of conditions to protect yourself?
Note: This question doesn’t apply when you’re selling a product or a productized service, as the price and scope are already established.… Read the rest
Let’s assume you’re a freelance Salesforce consultant, and are currently billing by the hour.
You’ve heard me speak about fixed pricing before, and the topic interests you. You just don’t know how to switch.
Here are three considerations to help you with this transition:
1.… Read the rest
An earlier project with a challenging client quickly became a vast source of knowledge. Knowledge of what NOT to do. Here’s one example.
This client was challenging to work with, because they wanted everything. They didn’t believe in a MVP, so in their first release of Salesforce, they wanted
How many Salesforce projects should you be working on at the same time?
As a consultant, and especially when you’re good enough, you’ll be in demand. Whether you work in an agency or are a freelancer, the option to work on simultaneous projects is available.… Read the rest
When working with Salesforce flows, you often need to refer to static strings.
For example, let’s say you have a custom text field called `Entity` on the account, which you want to set to “Organization” in a flow.
Option 1: When setting the Account record variable, just set `Entity` = “Organization”
This is definitely the quickest and easiest method, but it’s the hardest to maintain.… Read the rest
When updating or creating records in screen flows or autolaunched flows, you have two main choices for determining how the record is set:
Admittedly, option 1 takes slightly longer to set up.… Read the rest
In Salesforce flows, having a proper and consistent naming convention is important. It helps with readability, understanding, and logic processing.
When working with a single record, it makes sense for the variable to be singular. Similarly, when working with multiple records in a collection, it makes sense for the variable to be plural.… Read the rest
Yesterday’s email sparked some great feedback from readers, so let’s expand the topic of building your Salesforce network.
LinkedIn was mentioned, but it doesn’t really matter which social media platform you participate in. For example, Twitter/X has a vibrant Salesforce community.… Read the rest
Having a strong professional network helps attract clients and projects. Once you are known, you can refer business to others, and they can refer business to you.
So how do you become known?
There are three main ways to build your professional network.… Read the rest
People have various opinions about naming conventions for Salesforce variables in flows. Some draw their opinions from old VB code, others from C or Java.
As a previous C developer, below is my approach, which follow specific design patterns.
1. Keep it simple and concise
If a variable name can be written shorter, then shorten it
E.g.:… Read the rest
There was a recent discussion on LinkedIn about the input variable “recordId”.
Most flow developers know about the special variable “recordId”. (Note: the “I” must be capital, but the “r” can be upper or lower case). In a screen flow, when you set this specific variable as an input and text, it’ll automatically be populated with the Salesforce Id of the current record from where it was called.… Read the rest
Not so long ago, there were only two Salesforce editions, Professional and Enterprise. Then they introduced Developer, Starter, and Unlimited. After that, Essentials was introduced.
Note: If you want to know the differences between these editions, checkout https://help.salesforce.com/s/articleView?id=sf.overview_edition.htm
Last week they announced Unlimited+ (UE+), which is a bundle of services.… Read the rest