Brandloop public roadmap
The roadmap separates what is available now from what is next. It is meant to help buyers and agents avoid confusing planned automation with shipped product behavior — which cuts both ways: Autopilot has shipped and is listed under Current, not Planned.
Current
Brandloop currently presents the public brand engine, pricing, Brand DNA workflow, Studio generation, approval/calendar positioning, developer API reference, OpenAPI, and machine-readable buyer resources. Autopilot is shipped: it proposes drafts on a cadence and stops at the human approval gate, so nothing it plans publishes unattended.
- Public pages and docs are crawlable without sign-in.
- Pricing and pricing markdown come from the public package catalog.
- API reference and OpenAPI are public; API operations require scoped keys.
- Autopilot proposes on a cadence; every draft waits for a human approval.
Next
Near-term work should focus on provider-verified measurement, public proof collection, docs hardening, support setup evidence, and route-level search readbacks.
- Verify Google Search Console and Bing Webmaster Tools directly.
- Add real third-party profiles only after they exist.
- Record crawler and AI referral evidence from server or analytics logs.
Planned
Broader agent workflows should stay framed as controlled automation over Brandloop contracts, with review and workspace boundaries preserved.
Claim boundaries
- Roadmap items are not commitments, warranties, or shipped-feature claims.
- Future provider integrations must remain clearly separated from current product behavior. Autopilot is not one of them — it ships, and it stops at the human approval gate.
- Measurement and third-party proof require external verification.