Choosing a technology partner is a leap of faith. You’re trusting an outside team with systems your business depends on, and you deserve to know exactly how that partnership will work before it starts.
This guide explains what working with BRIO looks like: how projects begin, who you’ll work with, how we keep you informed, and how we handle decisions and changes along the way.
How it starts
Every engagement begins with a conversation about what you’re trying to solve, not what you want to buy. We’ll ask about your goals, your current systems, your timeline, and the constraints you’re working within.
From there, we recommend an approach and put together a proposal that describes the scope, the team, and the estimated investment. Once it’s approved, we’ll introduce your project manager and start preparing for kickoff, often before the official start date, so we can move quickly when the project begins.
Who’s on your team
The team depends on the work, but most projects include some combination of:
- A project manager, your main point of contact, who keeps the schedule, budget, risks, and communication on track.
- A business analyst, who leads discovery, documents requirements, and makes sure what we build matches how your team works.
- Salesforce or Litify consultants and admins, who configure and automate the platform.
- Developers, who build custom features, integrations, and applications.
- A solution architect, who shapes the overall design and makes sure it will hold up as you grow.
- Data specialists, when your project includes migrating or reporting on data.
You’ll know who everyone is and what they’re responsible for from the start.
How we keep you informed
We believe that transparency is crucial to a project’s success. You should never have to wonder where things stand.
- Kickoff. We align on goals, scope, roles, and how we’ll work together, and send you a written summary afterward.
- Weekly check-ins. Short, regular meetings with your project manager to review progress, upcoming work, and anything that needs a decision.
- Written status reports. A clear summary of what’s done, what’s next, open risks, and decisions needed, updated with notes from each check-in and sent to you afterward.
- Steering committee meetings, if you want them. Brief, high-level updates for executives, typically monthly, to keep leadership informed without pulling them into the details.
How decisions are made
Big decisions are made together and written down. After discovery, we document the design of what we’ll build, and you review and approve it before building begins. That approved design becomes our shared reference for what’s in scope.
Throughout the project, we’ll bring decisions to you with context and a recommendation, so you can make choices quickly and confidently.
How changes are handled
Ideas come up during every project, and that’s a good thing. When a request falls outside the approved scope, we don’t just absorb it or quietly let the schedule slip. We describe the change, estimate its impact on budget and timeline, and ask for your approval before starting. Some changes are worth doing now; others are better saved for a later phase. Either way, you decide with full information.
Testing and launch
Before anything goes live, we test it internally, then your team tests it with real scenarios to confirm it works the way you expect. We plan the launch together, including timing, training, and what support will look like in the first weeks. For Litify projects, our implementation timeline walks through each phase in detail.
After go-live
We don’t disappear after launch. The first weeks include close support while your team settles in. After that, many clients continue with ongoing support, a dedicated admin, or a second phase of improvements, with a team that already knows your systems. Some of our client relationships have lasted a decade and counting.
What we’ll ask of you
- A project lead on your side who can coordinate and make day-to-day decisions.
- Access to the systems and data we need, as early as possible.
- Time from the right people for discovery sessions and testing.
- Quick answers to questions, so work doesn’t wait.
- Candid feedback, early and often. It’s much easier to adjust in week three than in week thirty.
Starting a Litify project? Our guide to preparing for a Litify implementation covers what to gather before kickoff. You can also read more about our approach, or start a conversation with our team.
Frequently asked questions
How often will we hear from BRIO during a project?
Most projects include weekly check-ins with your project manager and a written status report, plus optional monthly steering committee updates for executives.
What happens if we want to change the scope?
We describe the change, estimate its impact on budget and timeline, and ask for your approval before starting. You decide whether to do it now or save it for a later phase.
Does BRIO provide support after go-live?
Yes. Every project includes close support in the first weeks after launch, and many clients continue with ongoing support, a dedicated admin, or additional phases of work.
Who will we work with day to day?
Your project manager is your main point of contact, supported by a team that may include a business analyst, consultants, admins, developers, a solution architect, and data specialists.
