Build an operations workspace around the work you actually do
Ops Hub gives one consistent workflow for managing people, opportunities, and research sources. Pick a hub, capture the information that matters, qualify each record, move it through a pipeline, and create contextual outreach without switching tools.
Start with a hub
Ops Hub currently includes three ready-to-use configurations:
- Sales Hub for leads, qualification, deal stages, estimated value, and outreach.
- Recruiting Hub for candidates, role fit, interview progress, and follow-up.
- Research Hub for sources, citations, findings, and research status.
Use the hub switcher in the workspace header. Each hub changes labels, fields, stages, scoring criteria, and AI context while keeping the same operating model.
The operating loop
1. Capture a record
Open Entities and select Add. Add enough context for useful filtering and qualification. Notes, tags, company details, role information, and hub-specific fields all improve later decisions.
2. Find and organize work
The entity workspace supports broad text search, status and stage filters, card or list layouts, and sorting by quality, recency, value, or name. Your view and sort choices stay in the browser.
Use / to jump to search. Export the visible result set to CSV when you need a portable snapshot.
3. Qualify what matters
Open an entity and run qualification. Ops Hub combines configured criteria with the available record context, then stores the resulting score and explanation with the entity.
Treat AI output as decision support. Review the evidence, correct weak inputs, and keep human judgment in the loop for consequential decisions.
4. Move the pipeline forward
Update stages as the work progresses. The Dashboard summarizes record volume, high-priority items, active pipeline value, messages, and stage distribution. Each metric and stage is interactive, so it can take you directly to the relevant filtered records.
5. Create contextual outreach
Open AI Writer, choose an active entity and channel, then generate a draft. Review the subject, body, reasoning, and recommendations before copying or sending the content through your preferred system.
Data and access model
The browser workspace can operate with local persisted data and synchronize with the Bun + SQLite API when the backend is available. The profile screen is a local workspace convenience; it is not an authentication boundary.
For a sensitive or multi-user deployment:
- enforce identity and authorization in the backend;
- protect API routes independently of the frontend;
- separate tenant data at the storage layer;
- audit write operations and AI-triggered actions;
- keep secrets and provider credentials server-side.
Run locally
The frontend starts on http://localhost:4321.
Run the API separately when SQLite persistence is needed:
The default local API starts on http://localhost:3001.
Quality checks
The check command runs formatting and lint validation, TypeScript, unit tests, and a production Rspress build.
Deploy directly
Ops Hub is configured for Cloudflare Pages and intentionally does not rely on a repository CI workflow:
The generated site is written to doc_build/.
Ready to work? Open the Dashboard or add a record in Entities.