For founders running the whole company
Not backed by Y Combinator
Launch the whole thing from one conversation.
Boardbox already knows your company. Describe what you’re launching, and one Initiative designs the screens, builds the code, prepares the sales outreach, writes the email and cuts the video. Then it keeps deciding where the next hour and the next dollar should go.
- Design
- Build
- Product
- Sales
- Growth
- Video
- Operations
All in one workspace, running on the Claude Code or Codex plan you already pay for.
You’d never run a company where nobody talks to each other. Your AI tools already do.
When design, engineering, marketing, sales and support each work alone, a launch gets pulled in five directions. A stack of single-purpose AI tools works the same way, with a separate subscription for each one.
Six tools, six islands
Six subscriptionsDraws a dashboard with a location switcher.
Doesn’t know: Engineering scoped permissions differently yesterday.
Builds location access from a spec in a chat that has since closed.
Doesn’t know: The design changed twice.
Renders the launch video from last week’s screens.
Doesn’t know: The dashboard was redesigned on Tuesday.
Raises the Meta budget because click-through is up 18%.
Doesn’t know: Sales is booked solid through Friday.
Pitches group billing to 40 restaurant groups.
Doesn’t know: Group billing slipped to next sprint.
Hears about the launch from a confused location manager.
Doesn’t know: There was a launch.
You are the only thing connecting them: re-explaining the company, re-stating the tone, and carrying files from one tool to the next.
One Initiative
Your Claude Code or Codex planOne plan, one memory of the company, and every capability working toward the same result.
One Initiative, start to finish
Watch Tablebird launch for restaurant groups.*
Tablebird makes scheduling software for restaurants. This is one launch, from the first message to the numbers two weeks later, and it never leaves the Initiative.
Click through it yourself, from idea to growth →*Drastically simplified for privacy and brevity.
- Initiatives1 of 11
It starts as one conversation.
Ava describes the launch once: restaurant groups, one dashboard across every location, 15 paying groups by the end of November. The Initiative asks what it needs to, then drafts the plan for every part of the company, with that outcome written into it.
- Library2 of 11
The company is already explained.
The Initiative already knows who Tablebird sells to, how it writes and what it has decided, and so does every capability it calls after this.
- Design3 of 11
The screens come back into the conversation.
Design Studio draws the group dashboard from Tablebird’s own components, checked against the rule that managers only see their own locations. Ava approves one exact version, and that version is the one that gets built.
- Build4 of 11
Built from the version she approved.
A coding session on Ava’s own Claude Code or Codex plan builds it in the real repo, and stops when a decision is hers, like who should be allowed to export payroll.
- Product5 of 11
The roadmap updates itself.
Every task the launch creates, from the invite flow to the launch email, lands on the backlog under the Initiative. The rest of the company can see what is being built, and why.
- Sales6 of 11
The funnel runs alongside the build.
The Initiative builds the restaurant-group audience, researches 20 new groups every morning, and prepares every conversation with what the launch actually includes, so each pitch matches what shipped.
- Growth7 of 11
One launch, told the same way everywhere.
The website page, the email to existing customers, the social posts and the ads come from the same plan in the same voice, and go out the day the product does.
- Video8 of 11
The launch video, cut from the real screens.
Scripted from the approved design and generated scene by scene on Tablebird’s own video key, in the same workspace as the rest of the launch.
- Automations9 of 11
It keeps working after launch day.
The Initiative sets up its own agents. One finds the next groups to call at 6:00. Another reads every signup, demo and support case and has a report on Ava’s desk by 7:00.
- Observe10 of 11
Every channel judged against the same goal.
Groups on paid plans, demos by source, cost per demo, all measured against the 15 groups in the plan. When referrals beat paid ads, it proposes where the budget should go next.
- Operations11 of 11
Support already knows about the launch.
When a location manager asks why they can’t see another location, the reply explains the permission design, because support works from the same Initiative that designed it.
Day 14 of the launch
An Initiative judges every channel against the outcome you asked for.
It planned the sales funnel, the content and the ads together. Some weeks that means spending more on ads, and some weeks organic is doing the job and the budget should come home.
What the ad tool sees
Performance is improving. Increase the Meta budget by 40%.
It’s right about the ads. It has never heard of the sales calendar, the referrals or the goal.
What the Initiative sees
6 of 15 groups on paid plansReferrals and organic are carrying the launch, and sales is booked through Friday. Meta is buying demos at $412 that nobody can take this week. Proposed: pause Meta, move the launch video into organic, and ask the six paying groups for owner referrals.
Every capability reads the same company.
When you correct a fact, every Initiative and every capability it calls works from the correction.
- 1
Your company
Who you sell to, what you offer, and the decisions you have already made.
- 2
Your voice
How you write, so every page, email, post and support reply sounds like you.
- 3
Your design system
The tokens, assets and fonts in your code, so new screens look like your product.
- 4
Your codebase
The working folders you pick on your Mac, read before anything is designed or built.
- 5
Your customers
Support conversations, sales records and what each group has been promised.
- 6
Your numbers
The metrics you connect, with the definitions and dates behind them.
Every capability an Initiative can call
Each one also works on its own, with the same knowledge of your company.
- Command center
- CIC
Each morning, the decisions waiting on you across every Initiative.
- Insights
Your metrics, captured with their definitions and the dates they cover.
The questions an Initiative keeps checking long after launch.
One conversation that plans and runs work across the whole company.
Agents on a schedule or a trigger that report back into the workspace.
- Capabilities
- Product
The backlog and roadmap every Initiative writes to, so everyone sees what's next.
Coding sessions in your own repo, on your Claude Code or Codex plan.
Screens drawn from your design system, approved one exact version at a time.
Your website, email, organic posts and ads, judged against the outcome.
Support cases investigated against your code, your data and your launches.
- Memory
Who you serve, how you sound and what you've decided, read first by every capability.
One monthly price per company
Solo founder or a very small company.
A small team using Boardbox across functions.
A larger team running more than one company.
Larger organizations with their own requirements.
- Design, build, sales, growth, video and support in every plan
- Runs on the Claude Code or Codex plan you already pay for
- The same bill in a busy launch month as a quiet one
Early access · macOS
Run your next launch from one conversation.
We’re onboarding a few founders and small teams each week, one at a time, starting with the launch you’re planning next.
We email you once, when your seat is ready.