If your organization is considering Kibu, there's a good chance some version of the same question has crossed your mind: what happens to our documentation in the meantime?

It's a fair concern. Any time you introduce new software into an organization - especially one running on a legacy system, or pen and paper - the fear of disruption is real. What about compliance? What about continuity? What if staff push back on something new?

To answer those questions head-on, I sat down with Conor McNichols, Kibu's Head of Customer Success, and the person responsible for guiding organizations through implementation from day one. What he shared might surprise you.

📲 It Starts Before Anyone Opens the App

The Kibu onboarding process doesn't begin with a login link and a "good luck." It begins with a scoping call and a deep dive into how your organization actually operates. What does a typical day look like in your program? How do your DSPs typically record notes? What compliance standards are you working within?

From there, the Kibu team handles the bulk of the data import work themselves.

"Our goal isn't just to set it up for you and leave…The process moves into weekly calls, and the focus is less on ‘here's how to use the software’ and more on understanding Kibu specifically as it applies to your organization.” Rather than handing organizations a generic manual, the team builds each customer's knowledge around what they actually do.

By the time a go-live date arrives, staff have already been in the system: exploring, creating records, getting comfortable. "We set up a version of Kibu that acts like a sandbox environment. In it, DSPs and managers are playing around, getting comfortable, following along with an organization-specific onboarding materials that are available to them 24/7." Conor said.

Plus, those training materials don't expire. When new staff come on months down the line, the most up to date resources are still there.

📣 On Disruption: The Answer is Direct

One of the most common concerns Conor hears is whether switching systems will interrupt documentation workflows - particularly for DSPs who are submitting service notes in the field on a regular basis.

His answer is clear: "There really isn't an interruption in documentation because we guarantee staff are fully trained. We work directly with organizations to thoughtfully plan out when the switch will happen."

The go-live date is established well in advance. In the weeks leading up to it, managers communicate clearly with their teams: on this date, you'll log into Kibu - not your old system, not a paper notepad. By the time that date arrives, it isn't a surprise to anyone. When working with organizations coming from pen and paper, the transition is even more straightforward.

For organizations migrating from a legacy digital platform, the change is planned with the same care. The week leading up to go-live, the Kibu team makes sure DSPs and managers are already in the system, and already comfortable. Managers communicate directly with their staff so that when the switch happens, it's a date everyone has been preparing for - instead of a disruption dropped on them without warning.

👋 Customer Success Won't Disappear

This is one that tends to catch organizations off guard in the best way.

"Customer success does not disappear from Kibu. You're not just left in the dark when you have questions, because staff in organizations will always have questions during times of transition. We understand that, and we’re always here for you - on your timeline."

That ongoing support extends to how customers reach the team day-to-day. Kibu sets up direct Slack communication with customers and encourages them to drop the formalities.

"Just text us. No need to be formal about it. We've worked together for a while now," is the basic, but jovial message Conor gives once an organization is up and running. And if something does come up, the average response time is under 10 minutes from a real person. You’re texting Conor, not a robot, if you ever need a hand. 

🤔 What about existing data?

For organizations migrating off a previous platform, the question of historical data is top of mind. Can records be preserved? What if the old system makes it difficult to export?

Conor's team takes a segmented approach. Rather than asking organizations to hand over everything at once, they work through it in structured phases. Member information first, then staff information, and so on.

"We can't just share you a folder in Google Drive and say ‘give us all of your data right now'... that's just not going to work," Conor explained. The phased approach keeps things manageable for organizations while avoiding the chaos of trying to organize a data dump after the fact.

In the vast majority of cases, this goes smoothly. The one notable exception Conor recalled involved a legacy system that refused to produce an organization's data - a limitation entirely outside Kibu's control. Even then, the organization eventually worked through it and got their information transferred successfully with help from the Kibu team.

And when it comes to getting your data out of Kibu - for an audit, a backup, or any other reason - you don't need to ask permission or contact anyone.

"You can produce any data at any time on your own. There's no need to send us an email or try to export or get someone on the Kibu side of things to do it."

(But remember - you can always text Conor if you still need some assistance 😉)

🤏 A Shorter Implementation Timeline

Organizations coming from legacy software often brace for a long implementation. In some cases, that expectation is shaped by bad prior experience. We’ve heard of previous platforms that can take almost a year to get up and running… and never quite worked right.

"I think people definitely overestimate the time it takes… especially people coming from older software. It ends up being (at most) three months."

For many organizations, it's even faster.

"The average time is probably two months right now."

Smaller, single-program organizations have gone live in as little as a month. Complexity scales with the number of programs and service types. For example, a 1,500-person organization with 20 different service offerings will naturally need more runway - but the baseline is significantly lower than most people expect across organizations of all sizes.

The reason it moves quickly comes down to how the process is designed. The Kibu team handles the data work. Training is tailored, not generic. Because organizations reach their go-live date already familiar with the platform, there's no steep learning curve waiting on the other side. Just an intuitive, easy-to-use platform, and a team to help if you need it.

🎉 When It ACTUALLY Clicks

Every onboarding has an “aha!” moment for the movers and shakers of the organization. According to Conor, it almost always happens in the second meeting.

The first meeting is mostly introductions and overview of the platform. The second is where an organization sees Kibu set up with their data. Their staff roster. Their program structure. 

"This is your documentation and this is what a DSP's experience looks like. And that's where it clicks for them... 'Wow, this is really easy.'"

DSPs, in particular, often become some of the most enthusiastic early adopters. The moment they realize they can speak their session notes into their phone instead of filling out paperwork after a shift, the question tends to shift from “Will my staff accept this?” to “When can we start?”

🏗 Built on Something MORE than Process

When asked what the secret sauce behind Kibu's implementation success actually is, Conor didn't point to a methodology or a checklist.

"I think the secret sauce is everyone working internally at Kibu. We all want each customer to succeed just as much as the other. I think that kind of backing as a company is what drives such high satisfaction from providers - both during onboarding and years later."

That culture shows up in small ways: customer success taking feature ideas directly to engineering, turnaround times that feel more like texting a colleague than submitting a support ticket, and an ongoing relationship that doesn't end at go-live.

Anyone can use Kibu. You don't need to be tech-savvy. You don't need a large IT team. You need leadership that's willing to bring their staff along for the ride, and a partner who'll be there to help every step of the way.

Ready to see what it looks like for your organization?
Let’s get a 30 minute conversation on the calendar. You’ll be glad you did!