How is this different from hiring a Salesforce partner?

Most Salesforce partners work on time-and-materials, which means:

• Open-ended scope

• Long timelines

• Unpredictable cost

These packages are fixed-scope and fixed-price.
You know exactly what’s included, what’s excluded, and when it’s done.

If you need enterprise-scale customization, a large partner may be a better fit.
If you want Salesforce set up correctly and predictably, these packages are designed for that.

What kinds of companies are a good fit?

These packages are ideal for:

• Small to mid-sized teams

• First-time Salesforce implementations

• Organizations moving off spreadsheets or legacy tools

• Teams that want a clean foundation they can grow into

They are not a good fit for:

• Enterprises with heavy integrations

• Highly regulated environments requiring formal compliance consulting

• Teams expecting unlimited changes or ongoing support

Do these packages include standard Salesforce objects?

Yes.
Both packages include configuration for standard Salesforce objects such as:

• Accounts

• Contacts

• Activities (Tasks & Events)

The Growth Foundation may also include:

• Leads

• Opportunities

Standard objects are configured alongside custom objects to ensure Salesforce works as a complete system, not just a collection of custom data.

Are permissions and security included?

Yes — this is always included.

Each package includes:

• Permission sets and permission set groups

• Object and field-level security

• Public groups (where appropriate)

• A basic role hierarchy, if needed

Advanced or highly customized sharing models are intentionally excluded to keep the project predictable and maintainable.

Will you customize Salesforce to match our processes exactly?

These packages focus on best-practice configuration, not recreating every edge case.

Where possible:

• Processes are simplified

• Automation is standardized

• Complexity is reduced

If your process requires heavy customization or advanced logic, that is typically addressed as a Phase 2 after go-live.

Do you build integrations with other systems?

No — integrations are intentionally excluded from these packages.

This includes:

• Real-time syncs

• Middleware configuration

• Custom APIs

If integrations are needed, they can be scoped separately after the core system is in place.

Do you write custom Apex code?

Only in the Growth Foundation — and only when Flow is not sufficient.

These packages prioritize:

• Declarative automation (Flows)

• Maintainability

• Admin ownership

Heavy custom code and complex trigger frameworks are outside the scope of these offerings.

What about data migration?

Each package includes limited data migration:

• Starter Foundation: one object

• Growth Foundation: up to three objects

Data is imported using Salesforce’s standard tools.
Large-scale data cleanup, transformation, or deduplication is not included.

How long does the implementation take?

• Starter Foundation: 4–8 weeks

• Growth Foundation: 8–12 weeks

Timelines assume:

• Timely client feedback

• Clear data inputs

• One project at a time

Delays in feedback or data delivery may extend timelines.

When are you available to work on the project?

Work is delivered primarily outside standard business hours, making this ideal for teams that don’t want daily disruption.

Meetings are:

• Scheduled in advance

• Limited in frequency

• Focused on decisions, not status updates

This structure helps keep projects efficient and on track.

What happens if we need changes?

Each package includes two revision cycles per phase.

Requests outside the defined scope are:

• Clearly identified

• Quoted separately

• Never added without approval

This avoids surprises on both sides.

Do you offer ongoing support after go-live?

Ongoing support is not included by default.

After delivery, you may choose to:

• Engage for occasional advisory work

• Scope a Phase 2 enhancement

• Transition to another admin or partner

There is no long-term contract or retainer requirement.

What does the discovery process look like?

Before any project begins:

• We confirm the package is a good fit

• We validate scope assumptions

• We align on timeline and expectations

Discovery is short, focused, and designed to protect both sides.

How does payment work?

Projects are billed in milestones:

• A portion upfront

• A midpoint payment

• A final payment upon delivery

Details are outlined clearly before work begins.

What if Salesforce isn’t the right solution for us?

We’ll tell you.

If Salesforce is not a good fit for your size, budget, or goals, we’ll say so during discovery — before any commitment is made.

These packages are intentionally designed to favor clarity over customization.
If that approach resonates with you, we’ll work well together.