> ## Documentation Index
> Fetch the complete documentation index at: https://www.flypllc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboarding with Flyp: What to Expect in the First Weeks

> Learn what happens after you engage Flyp LLC — from the kickoff call to full onboarding, asset inventory, and setting up ongoing support.

Onboarding with Flyp is designed to be straightforward, low-friction, and fast. From the moment you sign on, Flyp takes the lead on gathering what's needed, understanding your environment, and getting up to speed — so you spend as little time as possible hand-holding and as much time as possible seeing results. The goal is simple: get Flyp fully equipped to support your business with confidence, starting in weeks, not months.

***

## What to Expect: The Onboarding Steps

<Steps>
  <Step title="Kickoff Call">
    Your engagement begins with a kickoff call between your team and your Flyp point of contact. This session covers introductions, a confirmation of the project scope or managed services agreement, and answers to any open questions you have before work begins. You'll also agree on communication cadence — how often you'll check in, which channels to use, and who the primary contacts are on both sides.
  </Step>

  <Step title="Asset Discovery">
    Flyp conducts a structured discovery of your IT environment. This includes an inventory of your devices, servers, cloud accounts, software subscriptions, and any third-party vendors or service providers currently supporting your business. You don't need a perfect list to get started — Flyp will help build or validate that inventory as part of this step.
  </Step>

  <Step title="Access & Credentials">
    To begin work effectively, Flyp will need access to certain administrative systems and vendor accounts. You'll be guided through exactly what's needed and how to share it securely. Flyp uses dedicated credential management tools for this purpose — no credentials are ever transmitted over email or chat.

    <Info>
      Flyp uses secure credential management practices — you will never be asked to share passwords over email.
    </Info>
  </Step>

  <Step title="Baseline & Review">
    With discovery complete and access in place, Flyp reviews your environment in full. For managed IT clients, this includes a baseline assessment of your systems' health, security posture, and any immediate gaps that need attention. For project clients, this is where scoped analysis begins in earnest. Flyp shares initial findings with you and aligns on priorities before moving into active work.
  </Step>

  <Step title="Ongoing Cadence">
    Once the baseline is established, you and Flyp agree on the rhythm going forward: how often you'll receive reports or check-in calls, what the escalation path looks like for urgent issues, and how to request changes or additions to the scope of support. For managed IT clients, this cadence becomes the backbone of your working relationship with Flyp.
  </Step>
</Steps>

***

## What You'll Need to Provide

To make onboarding go as smoothly as possible, gather the following before your kickoff call. Don't worry if some of this isn't available yet — Flyp can help you track it down.

* **Current IT vendor and contact information** — ISPs, hardware vendors, software providers, and any existing IT support contacts
* **Administrative credentials** — to be shared securely through Flyp's credential management process, not over email
* **Network and device inventory** — a list of servers, workstations, laptops, and network equipment, if available
* **Key business systems** — your email platform (e.g., Microsoft 365, Google Workspace), ERP, accounting software, and any line-of-business applications your team relies on
* **Escalation contacts** — the people on your side who should be looped in for urgent issues or major decisions

***

## Timeline

Onboarding timelines vary depending on the size and complexity of your environment, but here are typical ranges:

### Project Engagements

Project onboarding typically takes **one to two weeks**. During this period, Flyp completes discovery, confirms scope, and establishes access. Active project delivery begins once onboarding is complete.

### Managed IT Engagements

Full managed IT onboarding typically takes **two to four weeks**. Flyp works through discovery, baseline assessment, and tooling deployment during this window. Light support is available from day one, but full coverage — including proactive monitoring, alerting, and helpdesk — activates once onboarding is complete and the baseline is established.

***

## After Onboarding

Once onboarding wraps up, the relationship shifts into its steady state. For managed IT clients, that means Flyp is actively monitoring, patching, and supporting your team as part of the regular engagement. For project clients, it means active delivery is underway with clear milestones ahead.

Either way, your Flyp contact is available throughout — and onboarding sets the foundation for everything that follows.

<CardGroup cols={2}>
  <Card title="Getting Support from Flyp" icon="headset" href="/working-with-flyp/support">
    Learn how to reach Flyp when something comes up and what to expect from the support experience.
  </Card>

  <Card title="Frequently Asked Questions" icon="circle-question" href="/faq">
    Find answers to common questions about how Flyp works, what's included, and more.
  </Card>
</CardGroup>