Product Launch Announcement Kit

One feature description in, a coordinated launch set out: announcement post, in-app and email copy, three social posts sized per platform, a sales one-liner, and the internal FAQ that stops your team improvising answers.

A Markdown launch kit containing: (1) a 400-600 word announcement post opening on the problem and naming at least one limitation; (2) a changelog note under 60 words; (3) a customer email under 150 words with a subject line and one action; (4) three platform-native social posts (LinkedIn, X, developer community); (5) a one-line sales pitch; (6) an internal FAQ of six to eight questions with answers, using [YOU MUST DECIDE THIS BEFORE LAUNCH] wherever the brief does not settle it.

# Launch kit — Scheduled exports

## 1. Announcement post

### Your export now runs without you

For the last year, the single most common request in our support inbox has been a variation on the same sentence: can this export just run automatically?

It was a reasonable thing to ask. Until today, getting a saved view out of the product meant opening it, clicking export, waiting, downloading a file, and putting it somewhere useful. If you needed that file every Monday, you did that every Monday. If you needed it every morning, someone on your team had a recurring calendar reminder to do a job a computer should be doing.

**Scheduled exports** ship today. Any saved view can now be exported on a schedule — hourly, daily, weekly or monthly — as CSV or Parquet, delivered to Amazon S3, Google Cloud Storage, or an email address. You set it once. It runs.

The practical difference is not the clicking. It is that a scheduled export can be a dependency. A file that reliably lands in your bucket at 06:00 is something a downstream job can be built on: a warehouse load, a finance reconciliation, a weekly report that assembles itself before anyone opens a laptop. A file that arrives when someone remembers cannot be depended on by anything.

Parquet is there for the same reason. If the destination is a warehouse rather than a spreadsheet, CSV is a lossy and slow way to get there, and enough of you were converting it on the other side that shipping the format directly was overdue.

**What it does not do yet.** Exports are capped at five million rows per run — above that, the export fails rather than silently truncating, which we think is the correct behaviour but is still a limit you should plan around. Hourly frequency is Enterprise only; Growth plans schedule daily and slower. And there is no transform step: what you export is the saved view as it is defined, so shape the view before you schedule it.

Scheduled exports are available today on Growth and Enterprise. There is no price change, and no action required if you are happy exporting by hand.

Set your first schedule from any saved view: Export → Schedule.

## 2. Changelog note

**Scheduled exports.** Any saved view can now export automatically to S3, GCS or email as CSV or Parquet, from hourly to monthly. Growth and Enterprise plans. Five million rows per export; hourly is Enterprise only. Find it under Export → Schedule.

_54 words._

## 3. Customer email

**Subject:** your export can run itself now

Hi {{first_name}},

The most-requested thing in our support inbox this year was automatic exports. They are live today.

Any saved view can now export on a schedule — hourly to monthly, CSV or Parquet, straight to S3, GCS or your inbox. Set it once and stop doing it by hand.

Two limits worth knowing: five million rows per export, and hourly scheduling is Enterprise only.

It is included in your plan at no extra cost.

**Set up your first schedule** → [link]

_98 words._

## 4. Social posts

**LinkedIn**
> For a year, our most common support request was one sentence: 'can this export just run automatically?'
>
> Today it can.
>
> Any saved view, on a schedule, as CSV or Parquet, to S3, GCS or email.
>
> The interesting part is not the automation. It is that a file which reliably lands at 06:00 can be a dependency — a warehouse load, a finance close, a report that builds itself. A file that arrives when someone remembers cannot.
>
> Caps: 5M rows per export, hourly on Enterprise.
>
> What is the job in your stack that still runs because a human remembers to run it?

**X**
> Scheduled exports are live. Any saved view → CSV or Parquet → S3, GCS or email, hourly to monthly.
>
> 5M rows per export. Hourly is Enterprise.
>
> Our most-requested feature of the year, shipped.

**Developer community**
> Shipped today: scheduled exports. Saved view out to S3 or GCS as CSV or Parquet, hourly through monthly.
>
> Parquet is the reason this is worth posting — if your destination is a warehouse, you were converting on the other side and now you do not have to.
>
> Hard cap of 5M rows per run. It fails the export rather than truncating, deliberately. If you have a view that regularly exceeds that, we would like to hear what it is.

## 5. Sales one-liner
> Any saved view now exports on a schedule to your bucket in CSV or Parquet, so the data lands where your warehouse expects it without anyone clicking anything.

## 6. Internal FAQ

**Q: Which plans have it?**
Growth and Enterprise. Not Starter. Hourly frequency is Enterprise only; Growth schedules daily and slower.

**Q: Is there an extra charge?**
No price change.

**Q: What happens above five million rows?**
The export fails and the schedule reports an error. It does not truncate. Say this plainly — a customer who discovers a silent truncation in a finance report will not stay one.

**Q: What happens if the destination bucket is unreachable?**
[YOU MUST DECIDE THIS BEFORE LAUNCH] The brief does not state the retry behaviour, and it is the first question support will get after the first failed delivery. Confirm the retry count, the interval, and whether the customer is notified.

**Q: Can a Starter customer upgrade mid-cycle to get this?**
[YOU MUST DECIDE THIS BEFORE LAUNCH] Not covered in the brief. Sales will be asked on day one.

**Q: Does the export contain the view as defined at schedule time, or at run time?**
At run time — the schedule references the saved view, so editing the view changes future exports. Flag this to support: it is the most likely cause of a 'my export changed' ticket.

**Q: Is data encrypted in transit and at rest at the destination?**
[YOU MUST DECIDE THIS BEFORE LAUNCH] Security will be asked this in the first enterprise renewal conversation after launch. Get the written answer from engineering before Tuesday.

**Q: What do we say to the customers who have been asking for a year?**
Email them individually before the general announcement, referencing their original ticket. It is the cheapest goodwill available and it is a one-hour job for support.