What problem does it solve?
Customer information becomes fragmented when commerce, operations, scheduling and finance each maintain separate relationship context.
Part of HalNora One · Independent product
In developmentCustomer relationships
Customer context without collapsing the suite into one database.
HalNora CRM is being developed as a standalone customer-relationship product for customer records, pipeline, quotes, tasks, reminders, interactions, reporting and privacy-aware administration.
Designed around
- Customer 360
- Contacts and addresses
- Leads and opportunities
- Quotes and follow-up
- Tasks and reminders
- Reporting and manager visibility
Current status
146 tests pass with TypeScript clean. Linking safeguards, search/contact-preview fixes and short-lived signed-authority protections have advanced; full PostgreSQL rehearsal and live cross-product identity acceptance remain open.
Live development statusActive development
Current focusThree-proof account linking, signed short-lived authority, PostgreSQL rehearsal, authenticated cross-product testing and production-readiness hardening.
Last updatedOctober 12, 2026
The live status feed is temporarily unavailable. Showing the last published snapshot.
Investor view
Problem, capability, connection and current stage.
HalNora separates demonstrated development progress from future product direction so scope can be understood without treating roadmap items as commitments.
What is it being built to do?
Customer 360, contacts, leads, opportunities, quotes, tasks, reminders, interaction history, reporting and privacy-aware controls.
How does it connect?
Receives approved customer/business events from HalNora products without taking ownership of Dispatch work, Marketplace orders, Booking appointments or Accounting ledgers.
Where is it today?
Active development. 146 tests pass with TypeScript clean; PostgreSQL rehearsal and live cross-product identity/MFA acceptance remain open.
HalNora One integration
Shared-profile planning is validated; live SSO is not.
CRM now has a validated shared-profile contract and onboarding planner for future HalNora One integration. The standalone CRM remains unpublished, live cross-product account linking is not enabled, and live CRM email remains disabled pending verified sender configuration and release acceptance.
Current direction
What this product is being built to do.
Public descriptions reflect current development direction and do not imply general availability or production certification.
Customer 360
Bring contacts, addresses, leads, opportunities, quotes, tasks and interactions into a focused customer view.
Lead & opportunity pipeline
Track prospect progression without changing records owned by Booking, Dispatch or Marketplace.
Quotes & follow-up
Manage sales quotes and follow-up tasks without turning quote acceptance into an automatic invoice, payment or fulfillment event.
Tasks & reminders
Use scheduled reminders and notification/inbox patterns for CRM work.
Activity timeline
Maintain customer interactions and activity history as CRM-owned context.
Reports & exports
Support time-window reporting, rep performance, activity trends and controlled CSV export.
Internal automation
Use duplicate-safe internal follow-up automation while keeping high-impact workflows disabled until approved.
Team & permission controls
Continue role, invitation, privacy and administrative control hardening for multi-user organizations.
Realtime security
Use short-lived protected realtime authorization and reauthentication rather than broad long-lived access.
Integration boundaries
Dispatch, Marketplace, POS, Booking, Accounting, Inventory, Payroll and Pharmacy remain disconnected until explicit mappings and contracts are approved.
Product boundary
CRM owns customer relationships.
CRM owns relationship and pipeline context. Operational, commerce, finance and regulated products remain authoritative for their own records; integration uses explicit mappings and events instead of shared tables.
HALNORA ONE ARCHITECTURE
Connected, not coupled.
Cross-product workflows use explicit contracts, authenticated events and clear authority so one product does not silently take over another product’s records.
How the HalNora platform works →Security & privacy hardening
Customer data protection is being built into the workflow.
Recent CRM work goes beyond pipeline features into privacy-aware administration, short-lived authorization and auditable data access.
Protected imports
Administrative import workflows are permission-scoped and designed to preserve tenant boundaries.
Privacy-aware search
Private/restricted data paths are treated differently from ordinary customer lookup.
Audited exports
Restricted exports are protected and auditable rather than treated as an unrestricted download.
Short-lived realtime access
Protected realtime authorization uses short validity windows and reauthorization rather than long-lived implicit access.
Invitation lifecycle
Invitations expire and reinvitation follows a controlled security path.
Account security signals
Password-failure counts and lockout warnings are tenant-scoped to help administrators see account-risk signals.
What comes next
Development priorities.
HalNora prioritizes reliability, security, recoverability and real-world validation over feature count alone.
Search themes: CRM software, customer 360 software, sales pipeline CRM, quote follow-up software, service business CRM, privacy-aware CRM.
Product inquiry
Interested in CRM?
Talk with HalNora about product direction, commercial use cases, partnerships or investment.