Weekend launch checklist for a prepaid AI chat

You can launch a prepaid AI chat in a weekend if you refuse three temptations: unlimited seats, an unbounded API key, and a six-agent graph. Bix is the reference implementation — Atlas, Scout, Quill, a snack jar, magic-link sign-in, Stripe packs, a hard stop at zero. This checklist is what we would hand a friend who wants the same shape on their own domain, or who simply wants to use Bix without wandering.

Bookmark usebix.com, the blog, and the credit calculator. When you need a human door, sign in.

Friday night — decide the fuse

Write the stop condition in the README. “When credits are zero, the models stay quiet.” If you cannot say that in public, you are building a seat.

Pick prepaid, not a trial that becomes a card. Bix gives 150 starter snacks, then $10 / $25 / $50 packs on #pricing. Copy the shape even if you copy nothing else. People understand jars.

Name at most three agents. Planner, researcher, writer is enough. Bix calls them Atlas, Scout, and Quill. Read the field guide before you invent a fourth personality named Omni.

Do not provision ChatGPT Team “just for the weekend.” If you need a comparison, use prepaid vs seats and then close the tab.

Measure before you theme. Open the calculator. Put in a guess: messages/day, average tokens, dollars per million. If the monthly API line scares you, shrink the product, not the font.

Saturday morning — the door and the jar

Ship magic-link sign-in, not a password novel. Bix uses a one-time hello link. Users should land on the desk, not a settings maze. If you are *using* Bix, this step is: click Say hi, open your mail, arrive at `/desk`.

Show the balance. A wallet that only exists in a database is an API key with extra steps. The jar has to be visible on every thread.

Reserve snacks before the call. Do not start a completion you cannot afford. Bix’s hard stop is a product promise, not a CSS badge.

Put Stripe on a pack, not a subscription. Webhook refills the jar. That is the only refill. If you add “courtesy overage,” you have rebuilt unlimited and called it kindness.

Keep legal in the footer. Company name, copyright, done. Do not brand the mascot as the LLC. Bix is Bix.

Saturday afternoon — the desk

Human routing. Three links or three buttons. No orchestrator agent. The budget essay explains why fan-out is a trap.

One shared wallet. Threads can be many. The jar is one. That is how a crew stays cheaper than three seats.

Write the empty state. When snacks run out, say so like a person. “Bix sat down. Feed the jar or write it yourself.” Then link billing.

Ban live-browse theater. If the researcher cannot see the web, they must say so. Invented citations are how weekend launches become Monday apologies.

Do a real loop: Atlas plans a launch post, Scout marks unknowns, Quill drafts once. Ship the draft. Do not regenerate it into sludge.

Saturday evening — the public internet

Ship indexable pages. A prepaid chat that only exists behind login will not grow. Bix ships `/blog`, `/tools`, and the calculator on purpose. You should too: a sitemap, robots.txt that allows the public pages, Open Graph that does not say “Welcome to my app.”

Link the tool from the article. Arithmetic belongs in a client-side calculator. The essay belongs at tokens → $ → packs. Cross-link them. Search engines are allowed to watch.

Internal links that a human would click: sign-in, packs, pals, blog index, tools. If a link exists only for a crawler, rewrite the sentence.

Analytics that do not require a speech. Page views and speed are enough for a weekend. Bix already mounts Vercel Analytics and Speed Insights in the root layout. Do not add a second tag manager “for growth.”

Sunday morning — the first strangers

Send five people the magic link, not a deck. Watch where they stall. If they stall on pricing, your packs are unclear. If they stall on the desk, your pals sound the same. If they stall on email, your from-address is creepy. Bix sends from a named product, not a no-reply fog.

Sit with the hard stop. Ask someone to spend the 150 snacks on purpose. Confirm the models go quiet. If they do not, you shipped a leak.

Buy a pack as a customer. Starter is $10. Feel the webhook. If you do not trust it, neither will anyone else.

Write down snacks per shipped artifact. “Homepage hero: 18 snacks.” That number belongs next to the calculator, not in a vibes channel.

Sunday afternoon — what you refuse to add

Refuse a fourth agent. Refuse a waitlist that promises agents. Refuse a usage-based invoice you cannot explain. Refuse “unlimited for influencers.” Refuse to hide Record of Sale anywhere except the footer if you are Bix; refuse to hide your own legal name if you are not.

Refuse to call it multi-agent if a human cannot name the jobs. Atlas, Scout, Quill is a sentence. “Our autonomous workforce” is an invoice.

Sunday night — publish the checklist you actually used

Turn your notes into a page. We turned ours into this one. Then link the other four essays so a stranger can self-serve:

• Prepaid AI credits vs unlimited ChatGPT seats
• Multi-agent desk without burning your API budget
• AI credit cost calculator explainer
• Meet Atlas, Scout, and Quill
• How prepaid AI credits stop bill shock
• Plan your monthly token spend
• Cartoon mascot AI brand without cringe

If you only publish a landing page, you will buy ads. If you publish the manual, people who search for prepaid AI credits can try Bix without a sales call.

Copy-paste checklist

Friday

1. Write the hard stop in public.
2. Cap the crew at three jobs.
3. Run the calculator with ugly numbers.

Saturday

1. Magic link to the desk.
2. Visible jar, reserve-before-call.
3. Stripe packs only — see pricing.
4. Human routing between pals.
5. Honest empty state.
6. Sitemap + OG + a tool page.

Sunday

1. Five real humans.
2. Force the empty jar once.
3. Buy Starter as a customer.
4. Record snacks per artifact.
5. Publish the manual and go outside.

If you are launching *on* Bix, not a clone

Skip the infrastructure. Sign in. Talk to Atlas about the launch. Let Scout list what you have not verified. Let Quill write the tweet. Buy a pack if the jar looks sad. Stop when it is empty.

That is the whole weekend product: prepaid snacks, named pals, no buffet. The rest is essays so the internet can find the jar.

After the weekend — a two-week hold

Do not add agents in week two. Do not add a second analytics script. Do not add a community Discord you will not moderate. Do answer five emails like a pal would: short, named, and willing to say the jar is empty.

Re-run the calculator with last week’s real sends. If Plus would have been cheaper than your sloppy Starter refills, buy Plus once and stop nibbling. If you did not send enough to matter, keep the leftover snacks and write by hand. Prepaid is allowed to look unused. Unused seats look like waste. Unused snacks look like a fuse you did not burn.

On Friday the 14th, reread Meet Atlas, Scout, and Quill and delete any prompt that asks one pal to do all three jobs. That is the only recurring meeting a prepaid desk needs.

If the weekend slips

Slip is normal. Do not “catch up” by buying a seat or wiring five agents. Resume at the last unfinished checkbox. If sign-in works and the jar is visible, you are still in the game. If only the landing page exists, you have a poster. Posters do not need Pro packs. They need Atlas and one honest sentence about the hard stop. Finish the fuse before you finish the gradient. Then publish one essay that teaches the fuse. That essay will outlive the gradient, and it will send the right people to sign-in instead of a seat comparison chart you do not own. If you cannot think of an essay, start with how the jar empties. Everyone who has been burned by an API key will recognize themselves by the second paragraph. Write that paragraph, publish it, and go to bed.