Roadmap
Today you bring the release.Next, your product brings it.
The plan is written down and public. Primitives first, then recipes, then the agent. Autonomy comes last, and only as far as your approval policies allow. Every item links to the document behind it.
Shipped
In the product today
- Launch intelligenceDocsCited spec, plan, visuals and copy, review and revise. Early access.
- Approval workflowRFC 019Server-side states, batch approval, six roles.
- Publishing abstractionRFC 020Durable scheduling with receipts behind one provider seam.
- Campaign objectsRFC 014Campaigns, angles, and posts as database objects.
- Brand and product surfacesRFC 011, 013Brand profile and kits, and the map from features to screens.
- Tenancy, auth, and enterpriseRFC 002, 003Organizations, roles, SSO, SCIM, audit logs, and SIEM drains.
- Release intakeRFC 005, 006Signed webhooks and the release and asset pipeline.
Now
Being built
Next
Up after that
- Programmable creative engineRFC 010The editor as domain services, so the UI, the API, and the agent render the same way.
- Paste a URL, get a profileRFC 012, 032Product intelligence and a background onboarding agent with ideal customer profiles.
- The launch recipeRFC 015A deterministic, resumable feature-launch pipeline.
- Typed marketing toolsRFC 016About ten domain tools for an agent with no infrastructure access.
- Conversation and workspaceRFC 017, 018One sentence to a draft campaign, in a workspace that works without chat.
- Three core workflowsRFC 021Launch something, ship a feature, stay visible, and seven posts at onboarding.
Later
Designed, not scheduled
- Changes become launchesRFC 022, 023Merged pull requests suggest campaigns. Deploys capture fresh screens.
- Demo videosRFC 024Captioned demos from captured product flows.
- Pillars and the weekly planRFC 025, 029Content pillars and a weekly plan approved in one action.
- Research, analytics, feedbackRFC 026, 027, 028Cited research, post performance, and plans weighted by what worked.
- Policies and autonomyRFC 030, 031Approval policies, then Manual, Copilot, and Autopilot modes.
Generations
Five generations.One object model.
The product grows in generations. Each one expands the same object model instead of starting over.
- V1
Screenshot Studio plus AI creative generation
- V2
URL to campaign
- V3
Product changes to campaigns, automatically
- V4
Campaign, publish, performance, next campaign
- V5
Marketing intelligence across GitHub, website, and analytics
Open gaps
What we have not solvedis on the page too.
Two gaps stand between today and the full launch workflow, and both are written down: billing with usage quotas, and capturing pages behind a login.
When a founder can paste a SaaS URL, get seven good posts with real product screenshots, approve them, and schedule them, we have a product founders can pay for.