Business software, built and run by one team
Multi-tenant platforms, finance-correct ERP back-offices and AI with guardrails — planned in writing, shipped in small tested steps, and run in production by the people who wrote them.
Who it is for For Gulf companies that need a finance-correct ERP with VAT and e-invoicing, founders who want a costed, phased plan before they build, and organisations commissioning a custom platform.
- Scoped from a statement of work
- AI built into the system
- Kept running once it is live
From the written plan to the system in production
Open a row to see what is inside it. Our own products are named; custom work is described in general terms, because client work stays confidential.
Planned in writing, shipped behind a green gate
The same six steps for a new platform or a new module. Each one leaves something you can read, test or sign.
-
Plan before code
A written definition, the decisions locked with their reasons, the architecture, and phases that each carry a measurable definition of done.
Development plan -
Agree the phases
A phased statement of work: formal sign-off before each phase, and payment tied to acceptance.
Statement of work -
Build behind a green gate
An increment is done only when the full test suite, run against a real database, and the real-browser tests all pass.
Tested increment -
Try to break it
Independent reviewers attack every significant change. A finding counts only when it is demonstrated, and each fix gets its own regression test.
Regression tests -
Ship with safety rails
Back up first, apply additive migrations, then check production health after the switch.
Health-checked release -
Run it, and keep the docs true
Backups with rehearsed restores and uptime checks; help sites updated in the same change as the code.
Runbooks and help sites
Proof you can check, not promises
What we can show your technical reviewer on the first call.
-
We run our own software in production
A paid-beta ERP with a large automated test suite — not a slide about what we could build.
-
Gulf compliance at the ledger level
A gapless counter and hash chain, and documents generated when issued, never on a draft. Sandbox-tested, and we say so.
-
AI with guardrails in the code
Confirmation before actions, a per-company consent switch, whitelisted queries instead of free SQL, and outside agents limited to the user’s own permissions.
-
Safety proven by tests
The ledger refuses unbalanced entries, the automation console provably cannot reach the order path, and halts cannot be skipped.
-
Built and run under one roof
Development and production environments, backups with restore drills, uptime checks and automatic certificates.
-
Plans that give real choices
A full-team and a lean AI-assisted option, each with its own cost and time ranges and exit gates, with regulatory decisions flagged early.
The documents you sign off on
Sample structures of three deliverables — drawn as shapes, with the sections each one really has. No client material.
-
Development plan
Specimen- Architecture and request flow
- Technology choices and reasons
- Phased roadmap with exit gates
- Risk register
Sample structure — no client material Detail withheld -
Phased statement of work
Specimen- Core platform, tenancy, roles, hosting
- Operational features
- Dashboards, mobile and APIs
- Production readiness
- User acceptance testing
Sample structure — no client material -
E-invoice register
Specimen- Invoice
- Issued
- Signed XML
- Hash chain
- Cleared or reported
Sample structure — no client material
Two full editions, not a translation pass
The development plan is delivered as a complete English edition and a complete Arabic one, each written and laid out in its own direction.
-
Development plan English
Specimen- Purpose and scope
- System architecture
- Phased roadmap
- Risk register
Sample structure — no client material Detail withheld -
خطة التطوير Arabic
نموذج- الغاية والنطاق
- بنية النظام
- خارطة الطريق المرحلية
- سجل المخاطر
هيكل نموذجي، دون أي مواد لعملاء تفاصيل محجوبة
Before and after the build
Most projects end in software. These services usually come first, or run beside it.
Our own products
Before you commit
Straight answers to what a board or a technical reviewer asks first.
Do you sell products or build custom software?
Both. We build and run our own ERP and e-commerce platforms, and a client can deploy them and extend them with modules. We also build custom platforms from a phased plan and a statement of work.
What do we get before development starts?
A development plan and roadmap: architecture, technology choices, phased scope with exit gates, team options, cost and time ranges, and a risk register. Then a phased statement of work in which payment is tied to accepted, working software.
Do you support KSA and UAE e-invoicing?
We have built e-invoicing modules to the KSA Phase 2 and UAE PINT AE specifications and tested them against sandbox environments. Going live is done together with you, using your own credentials.
How do you make sure what you ship works?
Every increment must pass the full automated test suite and real-browser tests before it ships. Significant changes also go through an adversarial review, and each confirmed issue gets its own regression test.
Can you host and run the system for us?
Yes: separate development and production environments, automatic certificates, health checks, nightly backups with rehearsed restores, and monitoring. We can also deploy into your own cloud.
How is AI kept safe with our data?
Customer data goes to a cloud AI model only after your company switches consent on; local models are also an option. The AI takes an action only after an explicit confirmation, and it cannot do anything the user could not do by hand.
Does it work properly in Arabic?
Yes. Every interface string is added in Arabic and English in the same change, and layouts use direction-neutral CSS, so right-to-left is there from the first commit rather than added at the end.
Who owns what you build for us, and who sees it?
Ownership is set out in the intellectual-property terms of the statement of work, before the build starts. Client work stays confidential: we do not publish client documents or name clients without their permission.
Who it is for, and in what form
Who it is for
- Gulf SMEs and mid-size groups that need a finance-correct ERP with VAT and national e-invoicing
- Multi-branch retailers and operators that need point of sale, inventory and consolidated accounts
- Founders and investors planning a SaaS product or a marketplace, who want a costed, phased build plan before committing money
- Organisations commissioning a custom multi-tenant platform under a phased statement of work
- Merchants who want a bilingual online store generated quickly and edited without code
- Companies that want an AI assistant inside their business software, without exposing their data
- Operators in specialised industries that need a domain module on a standard ERP core
Languages
Arabic and English in every interface and document, with right-to-left layout from the first commit. The ERP interface also runs in French and Spanish.
Formats
Web applications and APIs, desktop and point-of-sale clients, Word and PDF plans, container stacks and runbooks.
Client work stays confidential. We do not publish client documents or name clients without their permission.
Tell us what the system has to do
Your email or WhatsApp opens with a message that already names this service. Answer what you can — a few lines are enough to start.
Write in Arabic or English.
- To
- colorsx74@hotmail.com
- Subject
- Enquiry: Software & platforms (S-01)
- Message
- Hello ColorsX74,
We would like to talk about Software & platforms (S-01).
A few details:
- What the system has to do:
- Who will use it:
- What runs today, and what has to keep working:
- Timing:
From the page: https://
colorsx74.com/ services/ software
Your email app or WhatsApp opens with this message filled in. Nothing is sent until you press send, and you can change anything first.