Skip to main content
DILACODE

DilaCode is a Canadian software company. We build our own business software and develop products for clients.
Legal entityDILACODE INC.
JurisdictionOntario, Canada
Corporation no.1000959255
Registered officeBradford, ON
The problem

Most business software was built for somewhere else

Many CRM, ERP and point-of-sale systems assume one language, one currency and reliable internet. Businesses in Kurdistan and nearby markets often have to work around those assumptions with spreadsheets and chat messages. We build software around the way those teams actually work.

Our approach

Software that fits the operation

Our systems support Kurdish, Arabic and English, cope with unreliable connections and follow the real workflow of the business. We use the same practical approach in our own products and in software we build for clients.

  • 01

    Built for three languages

    Interfaces, content and AI replies support Kurdish, Arabic and English, including proper right-to-left layouts.

  • 02

    AI with human control

    AI can draft, classify and route work. Administrators decide what can be sent automatically and what needs approval.

  • 03

    Works through weak connections

    Offline support and queued updates help staff continue working when the internet drops.

  • 04

    Direct access to the team

    Clients work with the people who design and build the product, from planning through release.

Owned software

Software we build and operate

DilaCRM, DilaERP and dila.menu are active products with their own release cycles. Use the links below to see each one.

01

DilaCRM

One AI inbox across WhatsApp, Instagram, Messenger, Telegram, TikTok and email, with a CRM, campaigns and an approval gate in front of every automated reply.

  • Sales24 is the same platform under its enterprise brand, at sales24.io
  • AI replies drafted in Kurdish, Arabic and English
  • Administrators set what an assistant may send without a human
02

DilaERP

Sales, inventory, accounting, HR and payroll, POS and reporting in one system — a full ERP that works in Kurdish.

  • Fifteen modules across three languages, right-to-left included
  • Self-hosted deployment, so the operating data stays with the business
  • Branded document output and an in-product assistant
03

dila.menu

Trilingual QR menus, dine-in and messaging-based ordering, and dila RMS — the restaurant management system underneath, with kitchen routing and local payment handling.

  • Menu, ordering, reservations and analytics in one platform
  • Kitchen and bar routing with offline tolerance on the floor
  • Built for local payment behaviour, not card-only assumptions

Search and AI discovery

Help customers find and understand your business

We structure websites and product information so search engines and AI assistants can understand what a business does, where it operates and who it serves.

Clear service pages, verified company details, structured data and fast pages give those systems better information to work with. Rankings and recommendations cannot be guaranteed, but the business becomes easier to identify and cite.

OWNED SAASAI SYSTEMSMOBILEPLATFORMSIN PRODUCTIONOWNED SAASAI SYSTEMSMOBILEPLATFORMSIN PRODUCTION
RESEARCH01BUILD02SHIP03COMMERCIALIZE04EXPORT05RESEARCH01BUILD02SHIP03COMMERCIALIZE04EXPORT05
Multi App Interface

Loading projects...

How we build

Research and development

Engineering problems we work on

These are practical problems we have encountered while building the products: language quality, safe automation, reliable answers and software that keeps working on weak infrastructure.

R1

Low-resource language quality

Kurdish (Sorani) and Iraqi Arabic have a fraction of the training data English does. Getting an assistant to write a usable business reply — correct register, correct script direction, correct numerals — is an open engineering problem, and it is the one our products stand on.

R2

Bounded autonomy

Where an AI system may act alone and where it must stop and ask is a design decision, not a model property. We build the confidence scoring, the review queue and the audit trail that make that boundary explicit and adjustable per deployment.

R3

Evaluating output in high-stakes domains

Legal, medical and financial workflows cannot accept a plausible-sounding answer. Our work on retrieval, citation and verification against source documents came out of building an AI legal platform, and it carries into every product that answers a question with consequences.

R4

Systems that survive bad infrastructure

Intermittent connectivity, power interruption and low-end devices are the normal operating conditions for most of the businesses we build for. Offline-first data flow and predictable recovery are engineering requirements, not optional resilience work.

Commercialization

How a build becomes a product

  1. 01

    Built for one operator

    A system starts as client work with a real operator, real constraints and a deadline. That is where the requirements come from — not from a market study.

  2. 02

    Generalized into a module

    What proves out gets pulled back into shared modules: the ordering flow, the ledger, the approval queue. The next build starts further along.

  3. 03

    Released as a product

    Once a module carries several operators, it becomes a product with its own release cycle, documentation and pricing. DilaERP, DilaCRM and dila.menu all arrived this way.

  4. 04

    Taken to a new market

    Because the products were multilingual and multi-currency from the first line, entering a new market is a configuration and go-to-market problem rather than a rewrite.

Export capability

The products travel because they were never built for one market

Trilingual interfaces, right-to-left layout, multi-currency accounting and local payment behaviour are in the foundations, not in a localization backlog. The team has delivered software for clients in Iraq, Georgia, the United Arab Emirates and the United Kingdom, and has published apps to the Apple App Store and Google Play.

Languages shipped
Kurdish, Arabic, English
Client markets delivered
Iraq, Georgia, UAE, UK
Store presence
App Store and Google Play
Deployment model
Cloud or self-hosted
Where investment goes

Roadmap themes

These are the areas we would strengthen next with more capital and engineering capacity.

  1. 01

    Productization

    Take the three platforms from "deployable by us" to "adoptable without us": self-serve onboarding, documented configuration, tenant isolation and a support model that scales past the founding team.

  2. 02

    Applied language R&D

    Systematic evaluation and improvement of Kurdish and Arabic output quality for business workflows, with a test set and a measurable bar rather than spot checks.

  3. 03

    Canadian engineering capacity

    Build delivery and product capability in Ontario — engineering, quality and customer-facing roles attached to the products rather than to one-off projects.

  4. 04

    Market entry

    Position the export-ready products for Canadian and North American small and mid-sized operators, starting with the verticals we already have working software for.

  5. 05

    Security and procurement readiness

    The controls, documentation and processes larger buyers ask for before they will sign — built deliberately, and described only once they genuinely exist.

These are current priorities, not funding commitments. We make no claim of eligibility for any grant or funding programme.

What we cover

  • Web Design
  • Mobile App Development
  • UI/UX Design
  • AI Engineering
  • AI Agents and Integrations
  • Tech Due Diligence
  • Fractional CTO and Team Building
  • MVP Mobile/Website
Start a project

LET'S TALK

Tell us what you want to build, or ask about one of our products. Your message goes directly to the team.

Registered office

129 Compton Crescent
Bradford, Ontario L3Z 2X8, Canada

Design & interaction

THE STUDIO