# How implementation works *** **The honest version** Most CS platforms treat implementation as a billable project. Months of scoping, professional services fees, data mapping sessions, and a go-live date that keeps moving. By the time you're live, the team that bought it has half-forgotten why. Startdeliver works differently. The platform is genuinely fast to set up — most integrations take under an hour, the basics can be configured in a day, and a motivated admin can have their team working in the platform within 24 hours of signing. But fast setup isn't the goal. Good CS is. So alongside the platform, you get a partner who helps you get there — at no extra cost. *** **What's included** Every Startdeliver customer gets expert guidance as part of the relationship. Not a ticketing system. Not a knowledge base and good luck. A person on our side who knows the platform and knows CS, working with you to make sure you get value — not just a working configuration. Depending on what you need, that looks like one of two things: *** **Two tracks** **Tech track — move fast with a Solutions Expert** You work directly with a Startdeliver Solutions Expert. They know the platform inside out and will get you configured correctly from day one — integrations connected, health model set up, data flowing. This track suits teams with technical stakeholders who want to move quickly and get the setup right without trial and error. Each working session ends with something done, not a list of things to do. **CS track — build your CS motion with a CSM** You work directly with a Startdeliver CSM. They bring platform knowledge and CS best practice together — helping you not just configure Startdeliver but think through how your team should actually use it. This track suits CS leaders who want to build their motion and their tooling at the same time. The platform gets configured as a byproduct of getting your CS thinking right. You leave with both. *** **Self-serve is also a real option** Startdeliver is fully self-serve. Everything you need to configure is in Settings. Everything you need to understand it is in these docs. Our support team is available when you get stuck. If you want to spin it up yourself and bring in a partner later — that works too. *** **What getting live actually involves** Regardless of track, implementation covers the same ground. Here's what it looks like in practice: **Connect your stack** Your CRM, billing tool, support tool, feedback tool, and mail. Most integrations take 30 to 90 minutes to connect and configure. You don't need all of them on day one — start with the ones that bring in your customer records and the data your team needs most. → \[Integrations & Your Stack] **Import your customers** If your customers aren't coming in via a CRM integration, import them via CSV. Either way, getting your customer list in is typically the first thing that happens. **Configure your health model** Define what good usage looks like for your products. Set your feedback window and support SLA threshold. Start with your most important product and one goal type. The AI starts working with whatever signals are flowing in — you refine from there. → \[Product usage health] · \[Experience health] · \[Support health] **Set up your workspace** Invite your team, assign customers, configure your customer profile, create your first project templates. Admin setup typically takes a few hours spread across your first week. → \[For Admins: Set up your platform] **Connect mail & calendar** Each team member connects their own Gmail or Outlook. Two minutes per person. Every email and meeting with a customer contact is tracked automatically from that point. → \[Google mail & calendar] · \[MS365 mail & calendar] **Onboard your team** Your CSMs log in, see their portfolio, connect their email, and start working. The platform is designed to be intuitive — CSMs don't need a training day, they need a first week. → \[For Users: Your first week] *** **What you don't need before going live** * Map every field from your CRM — start with the ones your team actually uses * Configure every integration — connect what matters most first * Build every project template — one onboarding template is enough to start * Perfect your health model — refine it as you see the data * Train your whole team at once — CSMs can onboard gradually *** **What the first 30 days look like** **Week 1** — Stack connected. Customers imported. Team invited. Mail synced. Basic health model configured. The AI starts assessing customers. **Week 2** — CSMs working in the platform day to day. First project templates live. Health signals flowing on every customer profile. **Week 3–4** — First insights from the AI assessment. Health model refined. Automations configured for the highest-value workflows. Shared Space live for your first customers. **Day 30** — Your team has a live, working CS platform. The AI has 30 days of signal and is producing accurate, actionable assessments. You know what to build next. *** **Ready to get started?** [Sign up here.](https://www.startdeliver.com/get-a-demo) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.startdeliver.io/getting-started/how-implementation-works.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.