Release roadmap · clean start · launch in four to six months, then waves · working title "the platform"

Eight releases. Follow them here.

Click a release to open its checklist. Every tick, note and proposal is shared with everyone who opens this page. The name of the product is decided in parallel and never blocks a release.

Master plan v3 Platform Plan Code github.com/gitngn/lorpex · CI runs Documents docs/proposals/2026-09-14-*.md in the repository Tabs roadmap · what we build · gaps · security & infra · tests · schedule · financial track

Overall

You are Kickoff date connecting…

Releases

Status follows the checklist: nothing started → in progress → done. Mark a release at risk from its panel.

Release

not started in progress done Studio increment

Months
Outcome
Demo gate

Notes for this release (saved when you click away)

Parallel tracks

Run across releases, never on the critical path. The partner owns naming and pricing.

Now · Next · Later

Releases sort themselves by status. Proposals from anyone land in Next until triaged.

Activity

Last 40 changes, newest first.

Gaps we fill

Evidence checked on 2026-09-14. Full text with sources: docs/proposals/2026-09-14-competitor-gap-analysis.md. The v3 column moves with the roadmap.

SalesforceCRM leader · cloud only · no operations

Does well

Pipelines, forecasting, territories, CPQ; the widest ecosystem (AppExchange, MuleSoft, Tableau, Slack); customisation that survives three releases a year; Agentforce AI.

Real gaps

Price and stacking. Sales $25 (Starter, 10 users max), $100, $175, $350, $550 per user per month. Marketing is a second product from $1,250 per month for 10,000 contacts; multi-touch attribution only from the $2,500 tier. Service, Field Service, Loyalty, Revenue Cloud and MuleSoft are separate. 60 users on Sales Enterprise alone: about $10,500 a month.
Three marketing products, three contact models (Account Engagement, Marketing Cloud Engagement, the newer Growth/Advanced editions).
No operations. No inventory, purchasing, POS, ledger, payroll or HR; commissions need Spiff or Xactly.
Arabic is not end to end. Lightning supports Arabic, but Salesforce lists no RTL in Marketing Cloud Engagement, Account Engagement or Commerce Cloud, and none for emails, PDFs, CRM Analytics or the phone app. No Kurdish.
Cloud only. No on-prem, no customer cloud. No strategy execution, no native events, WhatsApp only as a marketing or service add-on.

What we fill

Operations on the same record as the CRM (R0–R3); one marketing model with attribution in the base product (R1, R4); Arabic, Kurdish and French across UI, email and PDF (R0); SaaS, own cloud and on-prem (R0, R7); strategy and events (R1, R4); WhatsApp for documents and approvals (R0–R1); one price list. Match, not beat: pipeline depth and record sharing (R1), customisation quality (Studio R1–R7).

Dynamics 365best identity and BI · four to six licences · two data models

Does well

Entra ID and Microsoft 365 native; Dataverse and Power Platform; Power BI as a first-class layer; real-time journeys with sales-activation nodes; Business Central as a solid SMB ERP; Copilot everywhere.

Real gaps

Licence stacking. Sales $65 or $135; Customer Service $50 or $115; Field Service $105; HR $30 attach; Business Central $80 or $110; Customer Insights – Journeys $1,700 per tenant per month ($1,000 attach). Power BI Pro, Power Apps and Dataverse capacity extra.
Two data models. Customer-engagement apps on Dataverse, Business Central on its own; Dual-write or connectors keep accounts, items and orders in sync.
No payroll. HR integrates with Ceridian Dayforce, ADP and UKG through an API; no partner payroll for Iraq or Mauritania.
On-prem CRM is ending. Customer Engagement on-premises v9 is the last release: mainstream support to 12 Jan 2027, extended to 9 Jan 2029. Only the ERP stays on-prem.
Strategy execution retired. Viva Goals ended 31 Dec 2025 with no replacement from Microsoft.
WhatsApp native only for service (Contact Center on Azure Communication Services, 2025); journeys need Infobip or another partner. Restaurants need LS Central from a partner, 14 to 20 weeks to implement. Regional localisation is partner-led (Saudi, UAE); nothing found for Iraq or Mauritania; no Kurdish.

What we fill

One data model for CRM and operations (R0–R1); payroll with country packs (R2); restaurant chains natively (R3); strategy execution where Viva Goals was (R1–R2); WhatsApp in journeys and for documents (R1, R4); an on-prem future for CRM (R0, R7); Iraq and Mauritania (R2); one price list. Match: Entra ID sign-in and Teams notifications (R0–R1), approvals as a primitive (R0), events (R4), Power BI export via the hub (R5).

Odoobreadth at one price · fragile upgrades · thin BI

Does well

CRM, sales, accounting with localisations, inventory with lots and expiry, purchase, restaurant POS with kitchen display, events, marketing automation, helpdesk, field service, HR with attendances and time off, payroll localisations, eLearning, loyalty and gift cards, native WhatsApp app, Studio, on-prem or Odoo.sh. Middle East list prices from about $9 per user.

Real gaps

Upgrades break customisation. Yearly major versions; custom modules and Studio changes need review and often a rewrite; on-prem upgrade fixes are paid support; unsupported versions carry a 25% surcharge from April 2026. Studio changes are database records, harder to analyse and migrate.
Support scores 3.9 of 5 across 1,200+ reviews, below the product itself.
Pricing mechanics. About $24.90 rising to $31.10 (Standard) and $49 rising to $61 (Custom) after the 12-month introductory rate; Studio, multi-company, API and on-prem need Custom; a warehouse picker costs the same seat as a controller.
Payroll localisations cover Saudi, UAE, Egypt, Jordan, Morocco, US and more, but not Iraq, Mauritania or Sweden.
Arabic RTL is fragile (rtlcss dependency; recurring direction, dashboard and report issues). BI is Dashboards and Spreadsheet only. No strategy execution, no meetings module, no Account 360 with compliance and credit, no territories or attribution, no biometric attendance without extra hardware modules, no integration hub with an on-prem bridge.

What we fill

Upgrade-safe, no-code customisation with packs (Studio R1–R7, upgrade test in the definition of done); strategy and meetings (R1–R2); Account 360 with compliance and credit (R1); territories, forecasting, attribution (R1, R4); Qlik-class BI and budgets (R6); biometric attendance (R2); payroll packs for Iraq and Mauritania (R2); RTL quality (R0); Integration Hub and Bridge (R5). Match: restaurant POS (R3), events, field service, LMS (R4), loyalty (R3), WhatsApp app (R0–R1), and the Middle East price point (pricing track).

Stratsysstrategy execution done right · nothing else · Nordic

Does well

Plans per org unit with inheritance, yearly plan versions, goal hierarchies, status sets with counters, timetable, KPI reporting periods with comments, reports to Word, PDF and web, meetings with decisions to actions, do-board, forms; sibling modules for quality, risk and control, information security, ESG and due diligence; SAML, OpenID Connect, Microsoft 365 sign-in, user sync from LDAP, Entra ID and SCIM; built-in AI assistant. Meetings from $30 a month.

Real gaps

Not a system of record. No CRM, ERP, POS, HR or payroll; KPI values arrive by hand or through the API; a plan cannot drill into an invoice or a payroll run.
Languages: Swedish, English, Norwegian. No Arabic, French or Kurdish.
Cloud only, EU hosted; no on-prem or customer cloud.
Nordic integrations (Power BI, Qlik, Jira, Visma, Unit4, Kolada, Swedish municipal systems); nothing for Salesforce, Odoo, Dynamics, WhatsApp or POS.
Work management is a do-board; approvals are plan and report sign-off; reviews mention slowness in document handling.

What we fill

Match their core in R1–R2 (inheritance, versions, statuses, timetable, KPI periods, Word/PDF/web reports, meetings, forms, SSO and SCIM, Power BI and Qlik export via the hub). Beat by putting the plan on top of the transactions (drill from a KPI to the invoice), by languages, by on-prem, and by owning the rest of the business. If Swedish public sector ever matters, their municipal integrations are the moat to respect.

Capability area	Salesforce	Dynamics 365	Odoo	Stratsys	v2 today	v3 (live)

full native and complete in the base productpartial shallow, partner-delivered, or a separately licensed productnone not offereddelivered all linked roadmap items done

Commercial snapshot, list prices September 2026

Suite	To cover our scope you buy	Indicative monthly cost, 60 users	Note
Salesforce	Sales Enterprise $175 per user + Account Engagement from $1,250 + Service, Field Service, Loyalty, MuleSoft + a separate ERP and HR	≈ $11,750 before service, ERP, HR	Attribution behind the $2,500 tier
Dynamics 365	Sales Enterprise $135 + Customer Insights – Journeys $1,700 per tenant + Business Central Premium $110 + Field Service $105 + HR $30 attach + Power BI Pro $14 + partner payroll	≈ $17,000 to $23,000	Two data models to keep in sync
Odoo	Custom plan, about $49 promotional and $61 at renewal, all apps; Middle East prices far lower	≈ $2,900 to $3,700 (US list)	Plus partner implementation and paid upgrade fixes
Stratsys	Platform on quote; Meetings $30 to $450 per month	not comparable	No operations; SSO and SCIM included
v3 (target)	Seats × module bundles with a value band by revenue; one list; on-prem licence on request	set by the pricing track before R1	Odoo's regional price is the benchmark to respect

Sources checked on 2026-09-14

Eight releases. Follow them here.

Releases

Release

Parallel tracks

Now · Next · Later

Activity

What we achieve, release by release

The platform, module by module

Gaps we fill

Does well

Real gaps

What we fill

Does well

Real gaps

What we fill

Does well

Real gaps

What we fill

Does well

Real gaps

What we fill

Commercial snapshot, list prices September 2026

Security and infrastructure gates

Automated tests (CI on main)

Acceptance tests per release

Financial track

Levers

Risks by phase

Spend by month

Tenant economics, years one to five

Schedule