Aura CRM — a project by Ahsan Mahmood
A voice-first client operations engine for independent professionals who spend hours on post-session admin.
The interesting hour of a client session is the one after it ends.
A coach, a consultant, a therapist, an advisor: each finishes an appointment and then owes a set of small obligations.
Notes while the detail is fresh. A task or two. A follow-up message that sounds like them. Sometimes an invoice for the part that ran over.
None of that happens in the room, and most of it happens badly.
It gets done hours later from memory, or in a batch on a Sunday, or not at all. The record degrades quietly, and nobody notices until the moment they need to remember what was agreed in March.
Aura CRM's proposal is that speaking is the write path.
Finish the session, say a short update out loud, and let the system transcribe it, update the record, raise the tasks, draft the follow-up in a matching style, queue anything billable and refresh a private progress view for the client. The write happens while the detail is still in your head rather than after it has gone.
That is the concept, and here is the part that matters more than the concept.
It is not running. The record calls it documented roadmap rather than shipped functionality, and the honest description of what exists today is a polished landing page sitting on a production-grade foundation. Saying anything else would be describing an intention as a product, which on a page like this is simply a false claim with better adjectives.
What is real is the foundation and the positioning.
The stack is React with Tailwind on a Supabase backend carrying Postgres, vector search, authentication and edge functions. A Capacitor shell is configured for web and Android, and there is no iOS release behind any of it. There is a runtime theme customiser with accent presets, dark mode, a high-contrast option and a reduce-motion setting, and a brand mark whose gradient binds to the live theme variables rather than being a fixed image.
The architecture anticipates a requirement that cannot be retrofitted.
Row-level security in the database and awareness of business-associate agreements when routing to AI services are decisions made before there is data, because a system that will one day hold therapy notes cannot acquire those properties later. That is architectural readiness. It is not a certification and nothing here claims one.
The positioning is deliberately narrow, and that was the risk worth testing first.
Five specific kinds of practitioner rather than businesses in general. Narrow positioning either resonates immediately or fails immediately, and finding out which costs a landing page rather than a voice pipeline.
There is a service layer underneath all of it, centralised rather than scattered.
Logging, errors, analytics, storage and data access each sit behind one place instead of being called directly from wherever they were needed. That sounds like housekeeping. It is the difference between swapping a provider in an afternoon and hunting forty call sites. On a product whose eventual shape depends on services nobody has chosen yet, it is the cheapest decision available.
What it cost is honesty.
An entry like this is easy to write as though the concept were the product, and no reader could tell from the outside. The alternative is a page admitting the interesting half is not built, which is less impressive and is the only version worth putting a name on.
What it does, and what that costs to build
- Voice-first capture concept where a spoken update is the primary write path into the CRM
- Audience-specific positioning for five practitioner segments
- Polished responsive marketing landing with hero, segments, pricing, FAQ, and waitlist
- Runtime theme customizer with accent presets, dark mode, high-contrast, and reduce-motion
- Theme-adaptive brand mark whose gradient binds to live CSS variables
- HIPAA-ready Supabase architecture with row-level security and BAA-aware AI routing
- Centralized service layer for logging, errors, analytics, storage, and data
- Capacitor mobile shell configured for web, Android, and iOS
Built with
- React 19
- TypeScript
- Vite
- Tailwind CSS v4
- shadcn/ui
- Radix UI
- TanStack Query
- TanStack Router
- Zustand
- Supabase
- pgvector
- Capacitor
Worth knowing
- crm
- voice-first
- saas
- supabase
- react
- capacitor
- vertical-saas
- client-operations
What actually exists of Aura CRM today?
A marketing landing page on a production-grade foundation, and the record says so in those words. The positioning, the theme system, the service layer and the mobile shell are built. The voice pipeline that the whole concept rests on is documented roadmap rather than shipped functionality. That is an unusual thing for a portfolio entry to lead with, and leading with it is the only way the rest of the page is worth reading.
What is the voice-first idea meant to solve?
The admin that follows a client session rather than the session itself. A coach, consultant or advisor finishes an appointment and then owes notes, tasks, a follow-up message and sometimes an invoice, and that work happens hours later from memory or does not happen. The concept is that speaking a short update immediately afterwards becomes the write path into the record, instead of typing one later. That concept is designed and documented; it is not running.
Why build the landing page before the product?
Because the positioning was the risky part. This targets five specific practitioner types rather than businesses in general, and whether that framing lands is a question worth answering before building a voice pipeline underneath it. A landing page is a cheap way to put the argument in front of people. It is also the honest reason this entry exists at Phase 0 rather than being held back until there is more.
What does HIPAA-ready mean here, and what does it not mean?
It describes how the backend is arranged, not a certification anybody has granted. The record names row-level security in the database and awareness of business-associate agreements when routing to AI services, which are architectural choices made in advance because retrofitting them into a system holding therapy notes is not realistic. Nothing here claims a compliance audit, a signed agreement or a legal status. The architecture anticipates the requirement, and that is the whole of the claim.
Does Aura CRM work on iPhone?
There is no iOS release. The record lists a Capacitor shell configured for web, Android and iOS, which describes how the project is set up rather than what has been published, and no store listing exists on either platform. There is no Apple Developer account here and nothing I build has shipped to the App Store. The landing page opens in a phone browser like any other web page, which is what there is to open today.
https://aoneahsan.com/projects/com.aoneahsan.auracrm