Contents

1. 1. Executive summary
2. 2. Product
3. 3. Market analysis (Morocco)
4. 4. Offer and deployment options
5. 5. Pricing
6. 6. Financial projections (5 years)
7. 7. Go-to-market
8. 8. Regulatory compliance (Morocco)
9. 9. Operations and organisation
10. 10. Roadmap
11. 11. Risks and mitigation
12. 12. Conclusion and next steps

1. Executive summary

DentalPro Maroc is complete management software for dental practices, built for the Moroccan market. It covers patients, the agenda, treatments, quotes and invoices, CNSS/AMO forms, imaging, labo, inventory, orthodontics, aesthetics, WhatsApp reminders, a mobile app, and AI-assisted cephalometry. It runs in production today on a cloud VPS with its own domain name and an API for the mobile app.

This plan turns the application into a commercial product sold in two ways, built from one codebase:

• DentalPro Cloud (SaaS): the main offer, a monthly subscription hosted by us, accessible anywhere.
• DentalPro Cabinet (on-site): installed on the practice's own computer with no public domain or static IP. Mobile access goes through our relay, which gives each practice a fixed address.

Funding need: about 1 M MAD to reach break-even, expected in year 3 to 4 (around 300–350 paying practices). Gross margin on the cloud service is about 85–90%.

2. Product

2.1 Functional scope (existing)

2.2 Competitive advantages

• Built for Morocco: CNSS/AMO, NGAP codes, ICE/IF on invoices, MAD, French (Arabic planned).
• WhatsApp reminders, which reduce missed appointments, the most visible pain point for practices.
• AI cephalometry for orthodontists: our own ONNX model, trained with the CephTrainer tool, runs in about 0.1 s on an ordinary CPU. Rare in this price range.
• Cloud or on-site choice, which answers the data-sovereignty objection that many local dentists raise.
• Complete scope in one tool: practices otherwise combine Excel, paper agendas and separate invoicing software.

2.3 Prerequisites before sale

The fixes from the third technical review (REPORT_v3_2026-10-31) are assumed to be applied. In particular:

• The TLS key has been revoked and reissued.
• The SQL injection and XSS are fixed.
• The notifications endpoint and schema migrations are fixed.
• The web root has been cleaned up.
• The regression checklist passes.

3. Market analysis (Morocco)

3.1 Market size

Serviceable market: at 600 MAD/month, 4,500 practices represent about 32 M MAD of recurring revenue per year. Capturing 10–15% in five years is the target in this plan.

3.2 Competition

3.3 Customer needs (to confirm in interviews)

• Fewer missed appointments (WhatsApp reminders).
• Faster invoicing and CNSS/AMO forms with no errors.
• Access to the agenda and patient files from a phone.
• Data safety: backups, confidentiality, data staying in Morocco.
• Simple pricing, local support in French/Darija, help migrating existing data.

4. Offer and deployment options

4.1 Option A: DentalPro Cloud (SaaS)

This is the current architecture (VPS, domain name, API for the mobile app), made multi-practice.

• One database per practice (already supported by tenant_db and the saas_* tables). Needs: automatic sign-up that creates the practice database, one subdomain per practice, limits per plan.
• Billing: card subscription through CMI, plus bank transfer with manual approval.
• Practice identity: logo, ICE, INPE, invoice numbering, WhatsApp number.
• Operations: automatic backups per practice with restore tests, monitoring and a status page, support tooling, data migration tool.

4.2 Option B: DentalPro Cabinet (on-site, no public domain, no static IP)

The application is installed on one computer in the practice (Apache, PHP, MariaDB as Windows services, built from the existing Dist/ installer). The difficulty is mobile access, which needs a fixed address.

How each feature works in option B2

• Mobile app: always uses https://cabinet-x.dentalpro.ma; the relay provides the certificate. Phones are paired by scanning a QR code shown in the desktop app.
• Cephalometry: the ONNX int8 model runs on the practice PC. Minimum 4 CPU threads and 8 GB RAM (0.1–0.3 s per X-ray). The installer checks the CPU; weaker PCs use the paid Ceph Cloud service, which sends only the image and returns only the points.
• WhatsApp reminders: one central gateway on our VPS serves all practices through the relay, or the WhatsApp Business API with one account per practice.
• Backups: encrypted automatic backup to our cloud. This is the biggest risk of an on-site install, so it is strongly recommended.
• Updates: signed automatic updates; database migrations run automatically (migrate.php).
• Licence: signed licence file tied to the PC, check-in every 30 days, 30 days of offline grace before features are restricted.

Keeping one product

• One setting DEPLOY_PROFILE=cloud|onprem and one feature list per profile and per plan.
• Same code, same migrations, same regression checklist; every release is tested in both profiles.
• The mobile app only knows one base URL (the practice subdomain), so it behaves the same in cloud or on-site mode.
• The same ONNX cephalometry model in both modes.

5. Pricing

5.1 Cloud plans (MAD excluding tax)

Annual payment gives 2 months free. A 30-day free trial and a demo instance are offered. Students and new graduates get a free or reduced plan for their first year.

5.2 On-site plans

5.3 Add-ons

6. Financial projections (5 years)

6.1 Customers

6.2 Profit and loss (thousand MAD)

Funding need: about 1 M MAD (lowest cumulative point −0.9 M MAD in year 3), from own funds, partners, or Moroccan startup programmes (for example Innov Invest / Tamwilcom instruments, incubators).

Lean scenario: with a team of 3 (≈ 450 k MAD per year), break-even is reached at about 70–100 practices. The plan above chooses faster growth with a larger team from year 2.

6.3 Key indicators to track

• Monthly recurring revenue (MRR) and number of paying practices.
• Trial to paid conversion (target ≥ 30%).
• Monthly churn (target ≤ 1.5%).
• Customer acquisition cost vs lifetime value (target LTV/CAC ≥ 3).
• Support tickets per practice per month, and time to resolve.
• Missed-appointment rate in practices using reminders (sales argument).

7. Go-to-market

7.1 Channels

7.2 Sales process

1. Lead from a channel → 30-minute online demo.
2. 30-day trial with data import of a sample.
3. On-site or remote training (1–2 hours).
4. Follow-up call at day 7 and day 25; conversion to paid.
5. Satisfaction call at month 3; referral request.

8. Regulatory compliance (Morocco)

9. Operations and organisation

9.1 Team

9.2 Infrastructure

• Cloud: VPS in Morocco or EU (with CNDP approval), one database per practice, nightly encrypted backups off-site, monitoring and status page.
• Relay server for on-site practices (frp/WireGuard), with a wildcard certificate for *.dentalpro.ma.
• Ceph Cloud: ONNX service (serve_onnx.py) on CPU, scaled as needed.
• Support: ticket tool, WhatsApp support line, knowledge base, video tutorials.

9.3 Service levels

• Cloud availability target 99.5% per month.
• Support response: same working day (standard), 2 hours (premium).
• Backup: daily, 30-day retention, restore test every month.

10. Roadmap

11. Risks and mitigation

12. Conclusion and next steps

DentalPro Maroc already has the functional depth of a commercial product. The main work is to make it safe, multi-practice and easy to buy, and to add an on-site version that keeps the mobile app working through a relay. With realistic adoption (15% of practices in five years), the product can reach about 5 M MAD of yearly revenue with good margins.

1. Apply and verify the audit fixes (month 1).
2. Decide hosting: Morocco data centre or CNDP transfer approval.
3. Recruit 10 pilot practices, including 2–3 orthodontists.
4. Sign one or two dental supplier partnerships.
5. Validate the regulatory analysis with a lawyer and file the CNDP pack.