Your first 15 minutes
Create your workspace, verify your email, then follow the onboarding wizard. The fastest path to value: add a business in the Business Finder → convert it to a lead → run a digital audit → the audit becomes your sales argument.
Create your workspace, verify your email, then follow the onboarding wizard. The fastest path to value: add a business in the Business Finder → convert it to a lead → run a digital audit → the audit becomes your sales argument.
Roles: OWNER > ADMIN > MANAGER > SALES > STAFF (read-mostly). Add teammates in Settings → Team. If you belong to several workspaces, switch with the workspace name in the top bar — each workspace's data is fully isolated.
Switch your interface language (FR/AR/EN) from the top bar. Arabic flips the whole interface right-to-left. Documents (proposals, invoices, receipts) follow each client's preferred language, including Arabic PDFs.
Search real businesses via the official Google Places API (Settings → Integrations shows whether it's configured). Results are normalized and deduplicated by provider id, domain, phone, and name+city — importing twice never creates duplicates.
An audit scores a business 0–100 across website, SEO, mobile, local presence, social, branding and marketing. Scores come from real checks — a business with no website scores honestly low. Use the findings as your outreach angle.
Leads are scored HOT/WARM/COLD from audit results, opportunity value and engagement, with a factor-by-factor breakdown on the lead page. Scores update when new information arrives.
Group prospects by campaign to track the funnel (contacted → replied → meeting → proposal → won) and ROI. Record campaign costs to get honest ROI — the platform never invents cost data.
ROI is computed only from recorded costs and real revenue (booked vs collected shown separately). No costs recorded → the ROI shows as not available instead of a made-up number.
Settings → Email: SMTP for sending, IMAP for automatic reply detection. Passwords are encrypted and write-only. For deliverability configure SPF, DKIM and DMARC on your domain — see the production guide.
Generated emails always go through DRAFT → review → APPROVE before sending. Unsubscribes and bounces are enforced server-side: a suppressed address can never be emailed again, whatever the UI shows.
With IMAP configured, replies are matched by mail headers (precise) or sender address, recorded on the lead, and automatically cancel pending follow-ups. Unmatched emails appear in Replies → Unmatched for manual linking — the system never guesses.
Audit summaries, multi-language outreach drafts (FR/EN/AR/Tunisian), reply intent analysis, proposal drafting from your catalog prices, and the Sales Copilot. Every generation is logged. Without an API key configured, AI features refuse honestly instead of faking output.
AI generations count against your plan's monthly quota (Settings → Billing shows usage). Drafts are never auto-sent and prices in AI proposals always come from your service catalog.
Proposals are priced from your catalog, exported as PDF, and signable online in the client portal. Accepting creates an immutable evidence record (signer, timestamp, SHA-256 document hash) and wins the lead automatically.
Revising a sent proposal creates v2, v3… — history is never overwritten. Clients see only the current version.
Invoices are generated from accepted-proposal snapshots (never re-priced), numbered atomically (INV-YYYY-NNNN), and immutable once issued — corrections go through void/cancel. Partial payments reconcile safely; overpayments are rejected.
These three never mix: booked = accepted proposals, invoiced = issued invoices, collected = confirmed payments. Cash ROI uses collected only.
Opt-in per project. A database constraint guarantees exactly one invoice per client+service+period, even if the scheduler runs twice.
Invite from the client page. Clients sign in with single-use magic links — no passwords. They see proposals, invoices, payments, projects, shared documents and support — never your internal notes, scores or costs.
Documents are internal by default; sharing with the client is an explicit, audited action. Versions are immutable and files are only reachable through authorized downloads.
Settings → Portal: brand name, colors, footer. On eligible plans, claim a custom domain and verify it with the DNS TXT record shown. TLS must be terminated by your infrastructure.
Clients open tickets from their portal; your team answers from Support. Configure SLA targets in Settings → Portal to get breach alerts — without configuration the system shows 'SLA NOT CONFIGURED' instead of inventing deadlines.
Settings → Developer. Keys are shown once, scoped least-privilege, and rate-limited. Full reference at /developers and /openapi.json.
Subscribe endpoints to events (client.created, invoice.paid…). Deliveries are HMAC-signed with retries and dead-lettering; event IDs stay identical across retries so you can deduplicate.
Settings → Billing shows your plan, trial end, usage against limits and invoices. Hitting a limit returns a clear 'plan limit reached' — reads are never blocked. Upgrading unlocks immediately.
A failed payment moves you to PAST_DUE with a grace period and reminders. After grace the workspace is suspended read-only — nothing is ever deleted, and paying restores full access.
Owners can export all workspace data as a ZIP (secrets excluded) and schedule deletion with a 14-day cooldown, cancellable any time. Platform accounting records are retained as required.