If you are evaluating AzAd CRM invoices estimates and the rest of the sales stack, start from what actually shipped in Phase 17 — not from a generic CRM brochure.
AzAd CRM is the organization add-on on AzAd Workspace: US$10/month or US$100/year per organization, not per seat. You can begin CRM-only (no mailbox required) at /start/crm/, or add CRM beside mail. Buying guidance: CRM vs email plans. Product overview: /crm/.
Sales documents
Shipped sales flows include:
- Items catalog
- Proposals and estimates (with HTML preview)
- Invoices with line items and payments
- Credit notes
- Convert estimate → draft invoice
Staff can create invoice share links for the client portal. Public token links let clients view invoice HTML without a full CRM login. Staff preview also matches invoices when the session email belongs to a company person.
Projects and tasks
Projects and tasks are first-class. Tasks can link to projects; tickets can link to projects when support work becomes delivery work. Job numbers help ops keep conversations short.
Support and knowledge
- Support tickets with notes
- Knowledge-base articles (HTML body)
- Estimate requests as an intake path
This is practical support for small teams — not a claim of enterprise ITSM parity.
Ops and insights
- Contracts and expenses
- Subscription records in CRM ops
- Dashboard/report style visibility for pipeline, tickets, and projects
What we do not claim
AzAd CRM is not marketed as Salesforce, HubSpot, or Dynamics feature parity. Automation depth, marketplace apps, and enterprise sandboxing are not the pitch. The pitch is: one affordable org CRM next to AzAd Mail on the same platform.
Mail relationship
CRM does not replace mailboxes. When sellers live in inbox and pipeline, buy both. Mail storage is separate (15 GB ≈ US$2.86/mo display USD). See pricing.
A week-one CRM pilot
Day 1: create company + person records for your top five accounts.
Day 2: open one deal and move it across two pipeline stages.
Day 3: draft an estimate with line items; preview HTML; convert to invoice if accepted.
Day 4: record a payment against the invoice; create a portal share link for the client.
Day 5: open a support ticket linked to a project task; publish one knowledge-base article your team already answers repeatedly.
If that week feels natural, CRM is probably the right buy. If nobody updates records, fix process before you pay annually.
Permissions and org shape
CRM sits inside the AzAd organization. Start CRM-only if mail can wait; add mail storage later without recreating companies and invoices. Conversely, mail-first orgs can attach CRM when sellers are ready. See CRM vs email plans so finance understands per-org vs per-mailbox bills.
Honest limits (again)
No claim of Salesforce Flow-style automation depth, AppExchange ecosystems, or multi-org enterprise sandboxes. Reports cover practical pipeline and ops visibility. Client portal focuses on invoice sharing — not a full self-serve commerce suite.
Buyer scenarios
Agency with five sellers: one CRM org at US$10/mo, mailboxes added when @agency.com is ready — estimates and invoices in CRM, threads in mail.
Services firm billing projects: link tickets to projects; convert estimates to invoices when work is approved.
CRM-first startup: /start/crm/ before mail; add 15 GB seats when domain DNS is verified.
Objections
“We already use spreadsheets.” CRM only helps if someone updates deals weekly. Run the week-one pilot; if records stay empty, fix process before paying annually.
“Is this Salesforce?” No — and we do not market it as such. Compare module list on /crm/ to your must-have list.
“CRM should bundle with every mailbox.” Flat org pricing avoids taxing mail-only users. See CRM vs email plans.
Mail + CRM sequencing
Stabilize mail first when deliverability is urgent. Add CRM when pipeline or invoices hurt more than inbox reliability. Same organization means no second identity provider — admin provisions users once.
Reporting expectations
Dashboard-style CRM reports help small teams see pipeline and ticket load — not a replacement for BI warehouses. Export habits (CSV, manual review) still matter for year-end close in many SMBs.
Client portal scope
Invoice share links let clients view HTML invoices without a full CRM login — useful for collections, not a full customer self-service portal. Set expectations with finance before go-live.
Support tickets module
Link tickets to projects when delivery and support blur. Knowledge-base articles reduce repeat questions — publish answers your team already types in email threads.
Estimate → invoice habit
Train sellers to convert accepted estimates to draft invoices inside CRM instead of retyping line items in mail. The mail thread stays conversational; CRM stays authoritative for totals and tax lines.
Next step
Tour modules on the CRM page, compare numbers on pricing, then start CRM-only at /start/crm/ or a full workspace trial at /start/.