Mainframe Launch Plan

+⋮⋮ The plan, in one page

+⋮⋮ We launch Mainframe on Monday, April 28. @Marcus Chen owns the landing push, @Jordan Vale owns the module catalog, and I’m on the keynote + pricing page. The thesis is simple: per-call < per-seat. We’re not another wiki tool — we’re a toll road on top of every API your team already hits. Read the teardown of Notion’s pricing model if you want the long version.

+⋮⋮ Pre-launch checklist

+⋮⋮ Launch workstreams

Each workstream is a row in the database below. Same source, rendered as a table here, as a Kanban on the Sprint Board, and as a calendar on the Launch Timeline. One database, three views — change the row once, update everywhere.

+⋮⋮ Sample: call a module from the launch page

The landing page wires three MeterCall modules: pricing-calc, module-catalog, and launch-waitlist. Each one is a single per-call billed endpoint — render it, pay for it, done.

// render the launch pricing widget -- one call, $0.0004
import { render } from "@metercall/sdk";

const widget = await render({
  module: "pricing-calc",
  inputs: { seats: 140, avgCalls: 8400 },
  theme: "rose-gold"
});

document.getElementById("calc").innerHTML = widget.html;
// cost per render: $0.0004 -- no seat fees, no flat minimum

+⋮⋮ Open questions

Three things I still want to decide before Friday. Read the linked thread and drop a comment if you have a strong opinion. Default is: we go with whatever Pat types last.