Project intelligence
OmniCRM
Multi-site content management for service businesses
Manage client presentation websites from one scoped workspace: edit content, preview changes, publish reviewed versions and recover history. Built for agencies and service businesses with direct-contact sites.
Latest signal
Nov 15, 2026
Synced Nov 16, 2026
14
Commits · 365 days
15
Pull requests · 365 days
0
Issues · 365 days
0
Code reviews · 365 days
Public summary
Public summary
What it is
OmniCRM is a content-management workspace for agencies and service businesses that maintain presentation websites. It separates the protected editing environment from the public website, with a focus on scoped access, reviewed publishing and recoverable content history.
The problem and business value
Updating a price, service description or image should not require losing track of which version is live or who can edit each client site. OmniCRM provides a structured operational path for those changes. It is a candidate foundation for a managed website service, with pilot acceptance still required before promising a complete industry solution.
What it does today
- Separates client website administration from hostname-based public rendering.
- Provides workspace and site access controls, with English-first administration and Romanian localization.
- Supports structured content, catalogs, media and bounded spreadsheet import/export paths.
- Implements preview approval, publication preparation and activation, version history and restore operations.
- Includes account security and team-delegation controls.
- Provides release-readback machinery to check the version served on verified domains.
An implemented schema or renderer does not establish that every editor, import and industry pack is complete.
Integrations and data flow
Authorized editors prepare structured content in the admin workspace. Validation, previews and publication operations control the path to a public release. The public renderer resolves the site's verified hostname and serves published content. Supabase supports authentication and scoped persistence; provider configuration and each customer's domain setup need separate verification.
AI or automation workflow
Publishing and readback use explicit operational states. This is not an autonomous AI website generator, and editing a draft does not publish it automatically.
Lead, email, notification or collaboration flow
Public sites support direct telephone, email and WhatsApp contact. Team members can work within delegated client scopes. V1 and V2 exclude payments, carts, transactional bookings, public lead forms, ERP/POS and LMS workflows.
Security and privacy boundaries
Draft and private content must stay out of the public renderer. Membership and site scope are enforced in server and database paths. The public rendering application must not receive privileged database credentials. Onboarding includes access, domain and publishing checks.
What is coming next
Finish the integrated pilot, including media, import, editor, publish and restore acceptance. Additional industry packs and client approval features follow their own validation gates; they are not presented as completed products.
Current activity and evidence
Reviewed in November 2026 against the maintained product brief, delivery roadmap, site operation routes, content contracts and public renderer. This brief makes no customer, uptime, performance or complete-industry-pack claim.
Discuss your use case
Managing several service-business websites or planning a controlled content-editing workflow? Share the sites, editors and content types involved to discuss a pilot and its acceptance criteria.
Contribution graph
The work behind the work.
Commits, PRs, issues and reviews
29 recorded activities in the selected range.
All available activity
Monthly activity totals
| Month | Activities |
|---|---|
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 17 |
| 2026-10 | 4 |
| 2026-11 | 8 |
Recent activity
What is moving now.
- [CRM-023] Add source-backed sales portfolio briefPull request - merged · Nov 15, 2026↗
- [CRM-023] Add source-backed sales portfolio briefCommit · Nov 15, 2026↗
- [CRM-022] Upgrade current CLI and library contractsPull request - merged · Nov 14, 2026↗
- [CRM-022] Upgrade current CLI and library contractsCommit · Nov 14, 2026↗
- [CRM-021] ci: signal automatic main deployments on the VPSPull request - merged · Nov 14, 2026↗
- [CRM-021] ci: signal automatic main deployments on the VPS (#13)Commit · Nov 14, 2026↗
- [CRM-020] Upgrade the runtime and compatible workspace dependenciesPull request - merged · Nov 14, 2026↗
- [CRM-020] Upgrade the runtime and compatible workspace dependenciesCommit · Nov 14, 2026↗
- [CRM-019] Add verified authenticator removalPull request - merged · Oct 19, 2026↗
- [CRM-019] Add verified authenticator removal and recovery guidance (#11)Commit · Oct 19, 2026↗
- [CRM-018] Bound tenant dashboard reads and patch release dependenciesPull request - merged · Oct 13, 2026↗
- [CRM-018] Bound tenant dashboard reads and patch release dependenciesCommit · Oct 13, 2026↗
- [CRM-017] Record verified production branding configurationPull request - merged · Sep 30, 2026↗
- [CRM-017] Record live pages and saved Google Branding (#9)Commit · Sep 30, 2026↗
- [CRM-017] Add public application information for Google BrandingPull request - merged · Sep 30, 2026↗
- [CRM-017] Add public application and privacy pages (#8)Commit · Sep 30, 2026↗
- [CRM-016] Reconcile delivery documentation and preserve task draftsPull request - merged · Sep 30, 2026↗
- [CRM-016] Reconcile delivery documentation and preserve task drafts (#7)Commit · Sep 30, 2026↗
- [CRM-015] Record Google owner sign-in and MFA verificationPull request - merged · Sep 30, 2026↗
- [CRM-015] Record verified Google owner login and MFA (#6)Commit · Sep 30, 2026↗
Published roadmap
What is shipped and what comes next
Delivered
- [done] Separate protected content administration from public website rendering
- [done] Implement scoped editing, preview, import, publishing and restoration contracts
Operationally pending
- [in-progress] Complete pilot acceptance across editors, imports, public readback and restore
Coming soon
- [planned] Expand validated industry packs and client approval workflows
Reviewed in November 2026. Roadmap items describe product direction, not a customer delivery commitment. A tailored implementation requires agreed scope and acceptance criteria.