The operating cockpit for small SaaS portfolios
Know what your SaaS needs next.
Turn each product's lifecycle stage into a clear view of what to solve, what to track, and the quickest worthwhile move—then carry that move into a real focus queue.
Invited participants get everything currently available for 14 days. Public signup and billing are not enabled.Illustrative workspaceBuild
Next move · your product
Prove the core workflow end to end
- Activation blockers
- Build and release health
- User feedback
Guidance changes as the product changes
01Idea02Validate03Build04Launch05Grow06Maintain07Paused
How it works
From scattered context to one useful next move.
Name the product and its stage
Start with the smallest truthful picture. No giant setup project required.
See what matters now
Launchpad frames the problem, the signals worth watching, and a concrete quick win.
Move it into focus
Turn guidance into an owned queue and keep the wider product context close by.
Built for portfolio builders
Your products can be different. Your operating rhythm shouldn't be chaotic.
See today clearly
One command view shows the work that deserves attention across products.
Guidance fits the stage
An idea should not be managed like a mature product. The cockpit adapts.
Turn advice into action
Useful guidance becomes a focus item instead of another forgotten note.
Keep the status honest
Saved workspace data, manual prompts, and planned connections are labelled for what they actually are.
Available now
A working foundation, not an integration theatre.
- Secure email account access and workspace membership
- Products with lifecycle stages and stage-aware guidance
- A real focus queue with quick-win history
- 14-day access to everything currently shipped
Building next
Tools, operating signals, and remembered access.
We are adding truthful links and manual checks first, then narrowly scoped read-only connections where they make the cockpit meaningfully better.
GitHubVercelHostingerSupabaseSentryPostHogStripeCodex
Security by honest boundaries
Access belongs to the workspace. Claims belong to the evidence.
Membership protected. Workspace data is isolated by database access rules, not browser convention.
Credentials are not accepted yet. The planned locker will arrive with explicit security boundaries; today, Launchpad never asks for your API keys or passwords.
Connection status stays literal. A provider link is a link. A manual check is labelled manual. Read-only access will be named and scoped.
Common questions
Before you bring the portfolio in.
Is this a project manager?
No. Launchpad is the operating layer that helps you decide what deserves work, then keeps the supporting context close.
Are the developer tools connected?
Not yet. The planned first integrations use explicit links and manual status checks. Read-only access will follow provider by provider.
What happens after 14 days?
The whole application is planned to require a paid subscription. The access policy reserves security and recovery after expiry; self-service billing, export, and deletion controls are still being built.
Can I store secrets?
Not in the current alpha. A workspace-wide credential locker is planned, but Launchpad does not currently accept or store real credentials.
One portfolio. One calmer rhythm.