Do you provide training or handover support?

Yes. Every LaunchPad tier includes launch training and documentation, so your team can run the product from day one. At launch, every account moves into your name, whoever held it during the build.

Handover has two halves: the people and the paperwork. Both matter.

What each tier includes

The higher the tier, the more of the launch we do with you rather than for you. Exactly what’s covered is agreed in Discovery, alongside the rest of the scope. The full feature lines are on the pricing page.

Training your team

A product only works if the people running it know how. We train the people who’ll run it day to day, in plain English.

That covers three things:

• Content. How to edit pages, add images and publish changes in your CMS.
• Operations. How to use the admin tools your team relies on, like managing users or exporting reports.
• Measurement. How to read your analytics, so you can see what people actually do.

We walk you through it, and record the walkthroughs so new starters can watch them later. People leave, and the knowledge shouldn’t leave with them.

Being easy to pick up was part of the brief at Sea Turtles Jamaica. Their app replaced a complex paper system, partly so new volunteers could start quickly. A product that only its builders understand isn’t finished.

If you’re worried about running something technical, can I build an app if I’m not technical? is written for you.

The documentation

You get documentation covering how the product is built, how to run and deploy it, and how to use the CMS and admin tools. It’s written so another engineer could pick it up without calling us.

Because your infrastructure is defined in code with Terraform, much of the setup documents itself. The rest we write down, so it’s not held in one person’s head.

Moving the accounts

Wherever the accounts sat during the build, handover is the day they become yours. The GitHub repository, the AWS account and the app store listings all move into your name. Do I own the code and IP? explains how each one transfers.

Handover is a checklist, not a ceremony. What you can see before launch is covered in do I get access to the code, CMS and analytics?

Our guide to who owns your code includes a handover checklist. It’s worth using with any supplier, us included.

After handover

Handover doesn’t have to mean goodbye, and it doesn’t have to mean we stay.

Some founders take everything in-house, or bring in their own team. Everything you need to do that is already yours.

Others would rather keep us on to look after it, so nobody on their side has to learn what a DNS record is. Do you offer ongoing maintenance and updates? explains that option.