Planning your pilot

Last updated:

|Edit this page

We want you to love using PostHog.

We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.

Here's how to get the most out of a pilot test with your team.

Ask for help if you want it

For companies sized 25 and up, we’ve got a team who can answer questions and help you make a plan.

But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and trouble. They can also help you map PostHog features to your business goals, developing a useful mental model for using all our products.

But we’re not going to get in your way, either, because...

We want you to play around

The most important job is getting familiar with PostHog in whatever way makes you most comfortable.

The most basic integration takes 5 minutes and we’ve got loads of documentation to support you exploring on your own.

First two weeks: get data in, then look at it

Job one is making sure PostHog is reliably ingesting your data and reporting the basics in a dashboard. Once this is working, take a break, order a pizza1.

Invite everyone who cares about user behavior

It doesn't matter what their role is. We charge by how successful your product is, not how many people have a login. We're building a product everyone will find useful.

So it's all upside when you invite everyone who cares about user behavior. As your integration comes online, think about who else should have access. You'll have the option to invite them during setup, and any time after that.

Key metrics and event tracking

With the basics in place, you have a few decisions to make to build a strong foundation for your reporting and data collection.

Enhance your integration

From here, you can get more sophisticated:

Check in with your teammates

After two weeks to explore, check in with your teammates. See if there’s anything they want but aren't getting. If you can get them excited with you, you'll have a better chance of making this pilot turn into a full-on switch.

Assess costs

After a couple weeks, you should have a decent picture of how much activity PostHog is tracking, and you can use that to understand your costs.

From here there’s no sneaky stuff. All our pricing is posted publicly, and you can see your projected costs in your billing settings.

Want to lower your bill? Check out our guides on cutting costs for product analytics, session replay, and feature flags.

We guarantee your safe pilot

You don't need to worry about a surprise billing spike as you're getting started. If something unexpected happens, just get in touch. We’ll work it out with you. We need your trust and enthusiasm way more than we need a month of charges you weren't expecting.

We’re in this for the long-haul. If you want more time to evaluate, and our generous free tier isn’t going to cover your volume of usage, just tell us about it. We can offer you a longer no-cost trial so you can be completely confident in switching over.

It means a lot to us that you want to make this switch. We've got your back.

Migration planning

Once you’re clear on the path forward, we’ve got you covered on historical data as well.

Let's talk about everything you need to plan a migration.


  1. Pineapple or not is up to you.

Questions? Ask Max AI.

It's easier than reading through 626 docs articles.

Community questions

Was this page useful?

Next article

What to expect as you migrate

With your team onboarded and a successful pilot completed, you can turn your attention to planning your migration . Technical planning PostHog provides tools and guides to support you making this switch. Check out our migration docs for details on moving from Amplitude , Mixpanel , LaunchDarkly and others. Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our onboarding team will reach out to help. If…

Read next article