Running a launch, hour by hour

Launch Desk is a working handbook for teams launching a token on a bonding-curve launchpad. It covers the preparation nobody enjoys, the running order for the first hours, the arithmetic behind a curve budget, and the week that starts when trading moves to a pool.

Independent, and not affiliated with Pump.fun or any other launchpad. Nothing here predicts an outcome: we write down the parts of a launch you control and name the parts you do not.

The launch in four phases

PHASE 01
Preparation. Metadata, wallet policy, budget, comms and the sign-off sheet. Ends when the mint is signed.
PHASE 02
Launch day. The first hours in public, run from a call sheet with named owners and deadlines.
PHASE 03
The curve. Buying moves along the bonding curve. Budget, distribution and triage all live here.
PHASE 04
After graduation. If the curve completes, trading moves to a pool and the work changes shape.

Featured handbook entries

Four pages that carry most of the weight: the full operating plan, the launch day call sheet, the budget arithmetic, and the week after migration.

01Operating plan

Pump.fun launch strategy

The whole launch as one document: four phases, the decisions each phase owns, and the parts of the outcome nobody running the launch can control.

Open the entry

02Schedule

The launch day timeline

A running order for the first six hours, written as a call sheet: who is on the desk, what is published when, and which decisions have deadlines.

Open the entry

03Budget

Budgeting the curve

Where money goes during a curve launch, how to write a budget in SOL that survives a bad hour, and the arithmetic behind every line of it.

Open the entry

04Week one

The week after migration

A seven-day operating plan for a token that now trades in a pool: liquidity questions, reporting rhythm, and the difference between quiet and dead.

Open the entry

The short version of the preparation sheet

The full sign-off sheet lives in the pre-launch checklist, grouped by owner and by deadline. These are the lines teams most often reach launch day without.

  • A written answer to what "done" means for this launch, agreed before anyone mints.
  • A ticker and name you have searched for, in the places buyers will search.
  • An image that still reads at the size a feed will show it.
  • Every link in the metadata opened once, from a device that is not yours.
  • A wallet policy in writing: which wallets are team, who holds keys, what is disclosed.
  • A budget in SOL with a reserve line that is not allowed to be spent on hour one.
  • A named person awake for each slot of the first six hours, including the dull ones.
  • A first message written in advance, and a second one for the case where nobody comes.
  • Abort conditions written down while you are calm, not decided while you are not.
  • A place to log the day, so the review afterwards is possible at all.

Where tooling fits in a launch plan

Somewhere in most launch plans there is a line for tooling: dashboards, alerting, explorer tabs, and often some form of automated market activity. It belongs in the preparation phase, decided and budgeted before launch day, because choosing a service while a curve is live is how teams end up handing wallet access to whoever answers first.

Be precise about what that class of tool does. It routes trades and produces recorded on-chain activity. It does not create demand, it does not decide whether a curve completes, and it does not oblige anybody to buy. Activity is a record of transactions, not evidence of interest, and readers can tell the difference on chain. If you use one, budget it as a cost with no expected return, and never present its output as organic demand.

The questions worth asking a provider are the boring ones: what custody model does it use, what does it charge and on what basis, what does it report, and what happens to your funds if it stops working. Those are covered in the budget entry and in the triage entry, where the temptation to spend during a quiet hour is at its strongest.

How this desk works, and what it refuses to promise

Launch Desk is written by The Launch Desk, an editorial desk rather than a named personality. Here is the method, the sourcing, and the line we will not cross.

Method

Every page is an operating procedure: what to do, when, and who owns it. Protocol behaviour is described from public documentation. Anything arithmetical is worked through in the open and labelled illustrative, so you can substitute your own figures.

Sourcing

We do not publish launchpad thresholds, fees or market figures as if they were fixed. Those are platform decisions that change, and the platform is the place to read them. Where a claim needs a source, the source is linked and named in the editorial policy.

What we refuse

No predictions, no success rates, no invented case studies, no testimonials, and no advice that depends on misleading a buyer. Who turns up, when attention arrives and whether a curve completes are outside everyone's control, including ours. About the desk sets out the rest.