1. Set up the drop
Two to four phrases, separated by commas. Copy them from a real message you already received — this page cannot look up search data.
The schedule uses one posting day per run day, starting tomorrow, so the days always run in a row. Seven days fits one full week. Five days posts on five days in a row and uses five of the seven posting ideas; the plan then names the two ideas it leaves out.
Occasion, platform, product idea and who it is for are enough. Press Build the drop plan — or press Fill an example for a worked run you can edit. If something is missing you get a plain message here; this line goes away once a plan is built.
Not sure what a plan looks like? There are six worked runs below — one for each seasonal window in the occasion list, from New Year and Valentine’s through Easter, summer, back to school and Halloween to Christmas. Press one and it fills the fields with a real-style product, audience and word list, then builds the plan straight away; after that, change any field and press Build again. The buttons themselves are built by this page’s scripts, so if no buttons appear below, those scripts are not running in your browser and nothing on this page can be built — the fields and the Build button above will not work either.
2. Your plan
Nothing here yet. Fill in the product idea and who it is for, then press Build the drop plan. The worked examples above are buttons built by this page’s scripts — if none appear there, those scripts are not running and the Build button cannot make a plan either, and this line stays as the stand-in. Everything here is a template you edit before you post it.
3. Run cost, from your own numbers
Add up what one run costs before you make anything. Numbers only: DropKit does not know your currency, and it saves nothing. Whatever you work out here is also added to the plain-text copy of the plan when you press Build the drop plan, Show plan as text or Select all the text.
Anything you pay once for the run: a die, a batch of boxes, a licence. Leave it blank if you pay nothing extra.
4. The last order date you can advertise
A seasonal run normally ends with a cut-off date, and the one people get wrong is the last day you can take an order and still have it made and posted in time. This works that date out from the run length chosen in section 1 (the schedule posts on that many days in a row, starting tomorrow) and one number from you: how long an order takes to become a parcel. It is date arithmetic only — no carrier data, nothing saved. Work a date out and its lines are also added to the plain-text copy of the plan, next time you press Build the drop plan, Show plan as text or Select all the text.
Your making time plus the days the carrier takes from collection to handover. Leave the box empty to use three days. Whole days only, 0 to 60.
Nothing worked out yet. Leave the box empty to use three days, or type your own number, then press the button.
About
DropKit is a static page built by an AI agent. It does no research of its own: there is no live trend data, no search-volume data, no account, no shop connection, and nothing is saved between visits. Close the tab and the plan is gone.
There is also a caption desk, the second page. It takes one line from your plan, the product and the people it is for, and writes three caption drafts, a first comment that carries a last order date worked out the same way as section 4 above, a reply line and a few plain tags. It does no research either, and it invents no facts: where a real size, a material or an amount belongs it leaves a [bracket] for you to fill in, and the one date it writes is arithmetic on your own numbers, not carrier data.
The scripts, the swap lines, the word list, the schedule, the run-cost sum and the last-order-date helper assume you make the product yourself or already hold stock, and that you know your own making time and the real shipping cut-off date. Treat every line as a starting point, and check anything before you publish it. Never invent a review, a count or a delivery promise.