Public roadmap
What we are working toward.
A directional view of AgentHub.ai. It shows active commitments and informed bets, not every idea in the private backlog.
This roadmap is directional. It contains no promised delivery dates and will change based on live customer usage.
Direction, not a contract.
Building now means the work is active. Next candidates are the ordered queue behind the active work. Exploring means the problem is real enough to investigate but the solution is not committed. Shipped means it is part of the product today. No item here carries a promised delivery date, and the order changes as live customer usage produces better evidence.
Building now
00Next candidates
00Exploring
08Pre-change recovery evidence
Capture the state a workflow was in before an implementation so a rollback decision has evidence behind it.
Under consideration; no delivery date is committed. Evidence only. AgentHub would not perform a rollback.Email request intake
Forward selected client emails into the same review-first intake process as Slack.
Selected read-only client access
Let a client see approved records and briefs without exposing the agency's full operating workspace.
Narrow n8n and HubSpot auto-refresh
Keep workflow inventory and client context current without widening what those connections can read or write.
Controlled Slack approvals and assignments
Evaluate controlled actions from Slack after selected-channel intake proves useful and false-positive behavior is understood.
Explicit AI-enabled workflow marking
Let an agency mark which client workflows contain AI steps so review and verification can account for them.
Salesforce business-system context
Evaluate Salesforce as a source of client, owner, and business context after live usage identifies the actual demand.
Read-only GitHub evidence sync
Evaluate a scoped GitHub App that can attach selected pull request, commit, CI, and deployment metadata after manual evidence use proves the recurring need.
No broad personal token, source-code ingestion, automatic verification, merge, or deployment control.
Shipped
17Approval names and dates in client briefs
Include recorded approval attribution in new brief drafts, distinguish client-link responses from outside approvals recorded by the team, and show missing approval explicitly.
Private approval emails and response notes stay out of briefs. Existing frozen briefs are unchanged.Workspace and mobile usability improvements
Refresh the workspace and sign-in design, preserve first-change form details after a failed save, and clarify the handoff from completed work to a client brief.
Standing client request link
Give each client a secure, reusable link for submitting change requests without creating an AgentHub account.
Submissions arrive as drafts for the consultant to review and confirm. They never approve scope, start work, or change the workflow automatically. The link can be shared through email, Slack, WhatsApp, or another messaging tool without building separate channel integrations.No-account client approval
Freeze the exact requested scope in a secure 14-day link so a client can approve it or request changes once without an AgentHub account.
AgentHub creates but does not send the link. The record shows when the approval page was first opened successfully, not who opened it. Approval stops at Approved and never starts work. The record is not an electronic signature or authenticated identity proof.Scope reconciliation at closure
Require the operator to record whether the verified implementation matches the approved scope before a passed change can close.
The operator records a match, cites revised approval, or closes with a visible unresolved scope difference. AgentHub does not infer the result.Unified client change fast path
Start with the request, select an existing client and workflow or create only the missing records inline, and open one formal Requested change in a single transaction.
Existing owners are preserved. No connector is required, and nothing is sent, approved, implemented, verified, or published automatically.Code-backed workflow references and implementation evidence
Choose where a client workflow actually runs, optionally link its repository and deployment, and attach reviewed pull request, commit, test, and deployment references to the client change.
References are private by default and never replace human verification.Scheduled client brief preparation and delivery
Prepare private client brief drafts on an agency-controlled schedule, then let the consultant review, publish, and explicitly email the frozen link.
Nothing is published or emailed automatically.Meaningful workflow version diff
After a forward-only baseline is captured, compare supported workflow versions and show safe structural differences on the linked change record.
Detection is not approval and does not change a live workflow.Targeted re-verification after a workflow change
Turn the recorded request and available safe structural difference into a focused, editable verification plan on the change record.
The consultant still records the verification outcome.Client operations workspace
Manage clients, live workflows, ownership, requests, incidents, commitments, and evidence in one workspace.
Request, ownership, approval, implementation, verification, and closure lifecycle
Carry a client request through every accountable step on one record instead of across tools and memory.
Frozen client briefs and share links
Produce a client-facing brief from the operating record and share it as a fixed account of the work.
Selected-channel Slack monitoring and review inbox
Watch only the Slack channels an agency explicitly selects and place likely requests in a review inbox before any record is created.
Human confirmation remains required.Task-based Help Center and Ask AgentHub
Follow current guides for the first client change, setup, connected tools, approvals, verification, and briefs, or ask product and workspace questions from the same surface.
Help answers link to current guides. Workspace answers cite stored records. Unsupported or unrelated questions are not guessed.Workspace-level automation connections and scoped client assignment
Connect n8n or Make once, then assign only selected workflows or scenarios to clients. Zapier alert intake stays client-scoped, while HubSpot supplies client context.
Unassigned n8n and Make resources are not imported.Public API v1 and developer documentation
Workspace API keys, narrow client, workflow, and change-request endpoints, and published documentation of the supported boundary.
See the record on your own client work.
One managed client, unlimited changes, no credit card, and no deadline.
Request onboarding