Frequently Asked Questions
-
We help organizations modernize Salesforce, connect data and systems, build practical AI and automation, and design digital tools around the people using them. Our work spans strategy and architecture, Salesforce implementation and improvement, digital products, and ongoing technical stewardship. You can bring us a defined project or a problem that still needs to be understood.
-
Yes. We work with inherited Salesforce environments that have become difficult to maintain or no longer fit the organization. We review the architecture, data, integrations, automation, permissions, and day-to-day workflows, then identify what to retain, improve, or retire. The goal is a clear, prioritized plan and a system your team can use and support with confidence.
-
We start with an operating problem and a clear definition of success. We assess the data, permissions, workflows, and human oversight needed before recommending AI, Agentforce, or another form of automation. Where there is a useful fit, we develop a focused use case, test it with your team, and plan how it will be monitored and maintained.
-
Tell us about your organization, what you want to accomplish, what is difficult today, and the tools you use. Share your timing and approximate budget; “not sure” is welcome. We review your inquiry, discuss the goal, and recommend a suitable next step. When the need is clear, we prepare a scoped proposal. When important questions remain, we may recommend a paid Project Blueprint or focused investigation that produces useful findings you own. Package selections are a starting point; the team confirms final scope, price, and availability.
-
Before the engagement begins, we confirm the deliverables, scope limits, exclusions, client responsibilities, milestones, fee, and payment schedule. We account for access, licenses, data, decisions, and other dependencies when planning. The signed agreement defines the work. If a new request changes the scope, we explain its effect on price and timing and obtain approval before proceeding.
-
We agree on requirements, acceptance criteria, and milestones before building. Your team reviews the work at agreed checkpoints and tests realistic scenarios with clear guidance. Before launch, we test the solution, confirm readiness, and plan deployment and recovery steps. You receive the documentation and training included in your engagement, ownership information, and instructions for requesting help. At closeout, we confirm deliverables, final payment, and the agreed defect correction-window dates. Ongoing support and new enhancements can be scoped separately.
-
After the agreement and required initial payment are confirmed, we send a readiness checklist and schedule kickoff. We reuse information you have already shared. Choose one decision-maker to consolidate approvals and feedback, a process owner, realistic-scenario testers, and a system contact for access and licenses. One person can fill several roles. Gather relevant content, sample data, and system information. Any outstanding items will have an owner and a due date.
-
Your project manager coordinates the work, communicates progress, and keeps next steps clear. Your business analyst clarifies requirements and supports testing. Your solution architect guides the design, and developers build, test, and release the solution. At kickoff, we agree on your main contact, update schedule, communication channel, review dates, and client responsibilities. Important decisions and approvals are recorded in the shared project record.
-
We agree on acceptance criteria: the checks used to confirm the work meets the approved requirements. North Shore tests the solution internally, including errors, permissions, and exceptions. Your testers then check realistic scenarios during user acceptance testing (UAT). We explain what is ready, what to test, and when feedback is needed. Your designated approver provides consolidated feedback. We distinguish defects, included revisions, and new requests, and record any agreed exceptions before acceptance.
-
We review new ideas and information against the agreed scope. If a request changes the work, we explain the effect on cost and timing and obtain your approval before starting the additional work. Access, information, decisions, and other dependencies can affect progress. If feedback or materials arrive late, your project manager explains any impact on the schedule and agrees on next steps.
-
Your proposal and signed agreement confirm the package deliverables, allowances, exclusions, review rounds, training, handover, and defect correction terms. Package and add-on selections help us identify a starting point; the team confirms requirements, dependencies, final scope, price, and availability before the engagement begins. For Project Blueprint, the outcome is findings, recommendations, and a roadmap; implementation is a separate next step.
-
The agreed defect correction window is the period for correcting delivered work that does not meet the approved requirements. At handover, we confirm its dates, how to report a problem, who owns the solution, and where documentation lives. Changes to requirements, new features, and ongoing support are separate from defect correction and can be scoped separately.
-
Scope: the work included in the agreement and its limits.
Deliverables: the specific things we will provide.
Milestones: the main project checkpoints.
Requirements: what the solution needs to do.
Acceptance criteria: the agreed checks that confirm the work is complete.
Dependencies: access, information, decisions, or other work needed before we can proceed.
UAT (user acceptance testing): your team tests realistic scenarios against the agreed requirements.
Change request: a proposed change to the agreed work, with its price and schedule impact reviewed before proceeding.
Handover: the documentation, training, and ownership information you need to run the solution.
Defect correction window: the agreed period for correcting delivered work that does not meet the approved requirements.